Re: [gentoo-user] x86 boot failure [solved]
Walter Dnes waltd...@waltdnes.org writes: On Thu, May 06, 2010 at 11:49:01AM -0230, Roger Mason wrote Egg on face. The processor is listed in the bios as Intel EM64T. Does that mean I should re-build this as an amd64 system? No, it's not necessary. 64-bit Intel and AMD cpus will run 32-bit mode without problems. It's your decision which one to use. General rule of thumb... - If you have 4 gigs or more of RAM, the 64-bit OS will take better advantage of it than a 32-bit OS. - If you have 3 gigs or less of RAM, stick with 32-bit. I'm running 32-bit mode on an Intel(R) Core(TM)2 Duo CPU E4600 and it works fine. I did some reading and found that Grub does not work on this hardware. I installed and configured lilo and the system booted. Cheers, Roger
Re: [gentoo-user] x86 boot failure
On Thu, May 06, 2010 at 11:49:01AM -0230, Roger Mason wrote Egg on face. The processor is listed in the bios as Intel EM64T. Does that mean I should re-build this as an amd64 system? No, it's not necessary. 64-bit Intel and AMD cpus will run 32-bit mode without problems. It's your decision which one to use. General rule of thumb... - If you have 4 gigs or more of RAM, the 64-bit OS will take better advantage of it than a 32-bit OS. - If you have 3 gigs or less of RAM, stick with 32-bit. I'm running 32-bit mode on an Intel(R) Core(TM)2 Duo CPU E4600 and it works fine. -- Walter Dnes waltd...@waltdnes.org
Re: [gentoo-user] x86 boot failure
On Thursday 06 May 2010 17:03:54 Dale wrote: Neil Bothwick wrote: On Thu, 06 May 2010 10:03:59 -0500, Dale wrote: Did you mean press e ? No. I don't see anything in the man page about hitting the c key. What does that do? I've used e, b and such but never heard of c. It drops you to the grub command line, it's documented on the GRUB menu screen itself, just after it tells you about e. Oh OK. I didn't reboot and read that part. lol I learned something today. Just hope I will remember it when I need it.;-) 'c' is good as long as the error is only with the GRUB entry. I usually find that on new installs the causes of failure to boot may be deeper and I will need to chroot back into the installation to fix things; e.g. reconfigure the kernel, add drivers and what not. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] x86 boot failure
Are you sure ext[234] is compiled statically into the kernel in this .config? Also the drivers for the EIDE / SATA controller. Missing FS and/or controller drivers will result in a regular kernel boot with a panic at the end, when it's time to mount root and load init. In this case grubs seems to load the kernel image, but the kernel hangs before printing anything. I would check the processor type setting (A 3GHz Celeron should be P4-based) and/or muck around with ACPI. Also try disabling framebuffer drivers and using a plain VGA console. Leave all advanced settings in your bios to their defaults. And no, EM64T just means it *can* run amd64 -- i686 is fine and IMO a lot better for that kind of hardware if you do not absolutely need to run 64-bit code for some reason. andrea
Re: [gentoo-user] x86 boot failure
On Fri, 7 May 2010 07:28:00 +0100, Mick wrote: It drops you to the grub command line, it's documented on the GRUB menu screen itself, just after it tells you about e. Oh OK. I didn't reboot and read that part. lol I learned something today. Just hope I will remember it when I need it.;-) 'c' is good as long as the error is only with the GRUB entry. I usually find that on new installs the causes of failure to boot may be deeper and I will need to chroot back into the installation to fix things; e.g. reconfigure the kernel, add drivers and what not. Indeed, but in this case the question was about getting to a grub proompt, and pressing c is a lot simpler than digging out a live CD, rebooting and setting up a chroot. -- Neil Bothwick I couldn't repair your brakes, so I made your horn louder. signature.asc Description: PGP signature
Re: [gentoo-user] x86 boot failure
On Thursday 06 May 2010 12:52:55 Mick wrote: When I get problems like this I usually run grub in a terminal and then use autocompletion to find out what grub sees: root (hd --tab it will list all partitions and hopefully help you find your boot partition. Then search for the kernel image: kernel /boot/ --tab If you have chosen the correct grub root partition you should find your kernel image in there. The problem with that is that grub in a running system may detect the disks in a different order from the booting grub. Better would be to interrupt the boot with e or (as Neil suggested) c. Either will allow you to use the Tab key to find disks, partitions and images. -- Rgds Peter.
Re: [gentoo-user] x86 boot failure
Hello Andrea, Andrea Conti a...@alyf.net writes: I would check the processor type setting (A 3GHz Celeron should be P4-based) and/or muck around with ACPI. Also try disabling framebuffer drivers and using a plain VGA console. Leave all advanced settings in your bios to their defaults. And no, EM64T just means it *can* run amd64 -- i686 is fine and IMO a lot better for that kind of hardware if you do not absolutely need to run 64-bit code for some reason. That is what I thought. I looked into the BIOS: no AHCI support. I edited the genkernel .config and set the various SATA drivers as built-in. There seemed to be nothing wrong with grub or its configuration (I rebuilt it anyway, just in case). In the end I gave up and installed the machine as an amd64. I may know today how that turned out: my install script shuts the machine down at the end and I'll need to get someone to re-boot it for me as I'm not in the office. I'll let you know what happened. Thanks Andrea and everyone else for your help. Roger
Re: [gentoo-user] x86 boot failure
On 7 May, Roger Mason wrote: Hello Andrea, Andrea Conti a...@alyf.net writes: I would check the processor type setting (A 3GHz Celeron should be P4-based) and/or muck around with ACPI. Also try disabling framebuffer drivers and using a plain VGA console. Leave all advanced settings in your bios to their defaults. And no, EM64T just means it *can* run amd64 -- i686 is fine and IMO a lot better for that kind of hardware if you do not absolutely need to run 64-bit code for some reason. That is what I thought. I looked into the BIOS: no AHCI support. I edited the genkernel .config and set the various SATA drivers as built-in. There seemed to be nothing wrong with grub or its configuration (I rebuilt it anyway, just in case). In the end I gave up and installed the machine as an amd64. I may know today how that turned out: my install script shuts the machine down at the end and I'll need to get someone to re-boot it for me as I'm not in the office. I'll let you know what happened. Thanks Andrea and everyone else for your help. One more hint (that I've got earlier on this list) Boot from a rescue CD (preferably http://www.sysresccd.org/ ) then execute lspci -k it shows you all drivers that have been selected during boot. Good luck, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
Re: [gentoo-user] x86 boot failure
Helmut Jarausch jarau...@igpm.rwth-aachen.de writes: One more hint (that I've got earlier on this list) Boot from a rescue CD (preferably http://www.sysresccd.org/ ) then execute lspci -k it shows you all drivers that have been selected during boot. Many thanks fir the information. Cheers, Roger
[gentoo-user] x86 boot failure
Hello all, I just built a new machine (celeron 3 GHz) using a script that builds the kernel using genkernel and a config that is copied from that of the kernel on the install cd. The latter was downloaded and burned from a very recent autobuild. The build process appears to complete successfully, with nothing untoward in the logs. However, the machine will not boot but hangs at this point in the process: root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/kernel-genkernel-x86-2.6.32-gentoo-r7 root=/dev/ram0 init=linuxrc ramdisk=8192 real_root=/dev/sda3 vga=791 [Linux-bzImage, setup=0x3000, size=0x2a8d80] This is the grub.conf: default 0 timeout 5 title Gentoo genkernel-x86-2.6.32-gentoo-r7 root (hd0,0) kernel /boot/kernel-genkernel-x86-2.6.32-gentoo-r7 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda3 vga=791 initrd /boot/initramfs-genkernel-x86-2.6.32-gentoo-r7 I have verified that the names of the kernel and initrd on the disk match those in grub.conf. In any case a wrong filename is usually signalled as 'not found' during the boot process. Can anyone suggest how to debug this? Thanks, Roger
Re: [gentoo-user] x86 boot failure
On 6 May 2010 09:37, Roger Mason rma...@mun.ca wrote: Hello all, I just built a new machine (celeron 3 GHz) using a script that builds the kernel using genkernel and a config that is copied from that of the kernel on the install cd. The latter was downloaded and burned from a very recent autobuild. The build process appears to complete successfully, with nothing untoward in the logs. However, the machine will not boot but hangs at this point in the process: root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/kernel-genkernel-x86-2.6.32-gentoo-r7 root=/dev/ram0 init=linuxrc ramdisk=8192 real_root=/dev/sda3 vga=791 [Linux-bzImage, setup=0x3000, size=0x2a8d80] This is the grub.conf: default 0 timeout 5 title Gentoo genkernel-x86-2.6.32-gentoo-r7 root (hd0,0) kernel /boot/kernel-genkernel-x86-2.6.32-gentoo-r7 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda3 vga=791 initrd /boot/initramfs-genkernel-x86-2.6.32-gentoo-r7 I have verified that the names of the kernel and initrd on the disk match those in grub.conf. In any case a wrong filename is usually signalled as 'not found' during the boot process. Can anyone suggest how to debug this? When I get problems like this I usually run grub in a terminal and then use autocompletion to find out what grub sees: root (hd --tab it will list all partitions and hopefully help you find your boot partition. Then search for the kernel image: kernel /boot/ --tab If you have chosen the correct grub root partition you should find your kernel image in there. -- Regards, Mick
Re: [gentoo-user] x86 boot failure
Mick michaelkintz...@gmail.com writes: On 6 May 2010 09:37, Roger Mason rma...@mun.ca wrote: Can anyone suggest how to debug this? When I get problems like this I usually run grub in a terminal and then use autocompletion to find out what grub sees: root (hd --tab it will list all partitions and hopefully help you find your boot partition. Then search for the kernel image: kernel /boot/ --tab If you have chosen the correct grub root partition you should find your kernel image in there. I assume you mean to boot from the install CD then chroot into the new install and run grub from bash? Thanks, Roger
Re: [gentoo-user] x86 boot failure
On Thu, 06 May 2010 10:08:42 -0230, Roger Mason wrote: I assume you mean to boot from the install CD then chroot into the new install and run grub from bash? Press c at the GRUB menu. -- Neil Bothwick The human mind ordinarily operates at only ten per cent of its capacity ... the rest is overhead for the operating system. signature.asc Description: PGP signature
Re: [gentoo-user] x86 boot failure
Neil Bothwick wrote: On Thu, 06 May 2010 10:08:42 -0230, Roger Mason wrote: I assume you mean to boot from the install CD then chroot into the new install and run grub from bash? Press c at the GRUB menu. Did you mean press e ? Dale :-) :-)
Re: [gentoo-user] x86 boot failure
On 6 May 2010 13:38, Roger Mason rma...@mun.ca wrote: Mick michaelkintz...@gmail.com writes: On 6 May 2010 09:37, Roger Mason rma...@mun.ca wrote: Can anyone suggest how to debug this? When I get problems like this I usually run grub in a terminal and then use autocompletion to find out what grub sees: root (hd --tab it will list all partitions and hopefully help you find your boot partition. Then search for the kernel image: kernel /boot/ --tab If you have chosen the correct grub root partition you should find your kernel image in there. I assume you mean to boot from the install CD then chroot into the new install and run grub from bash? Yes, use a live CD, chroot, su to root and run grub from a terminal. -- Regards, Mick
Re: [gentoo-user] x86 boot failure
On Thu, 06 May 2010 08:34:49 -0500, Dale wrote: Press c at the GRUB menu. Did you mean press e ? No. -- Neil Bothwick RAM DISK is NOT an installation procedure! signature.asc Description: PGP signature
Re: [gentoo-user] x86 boot failure
Roger Mason rma...@mun.ca writes: Can anyone suggest how to debug this? Egg on face. The processor is listed in the bios as Intel EM64T. Does that mean I should re-build this as an amd64 system? If the answer to that is yes, then I don't understand why the x86 install CD booted without problems. Cheers, Roger
Re: [gentoo-user] x86 boot failure
On 6 May 2010, at 09:37, Roger Mason wrote: ... I just built a new machine (celeron 3 GHz) using a script that builds the kernel using genkernel and a config that is copied from that of the kernel on the install cd. Are you sure ext[234] is compiled statically into the kernel in this .config? Also the drivers for the EIDE / SATA controller. The liveCD configs I've seen generally store these as modules. I, too, usually take a copy of the config from a working LiveCD when I compile a kernel, but I *always* have to change something. Stroller.
Re: [gentoo-user] x86 boot failure
Neil Bothwick wrote: On Thu, 06 May 2010 08:34:49 -0500, Dale wrote: Press c at the GRUB menu. Did you mean press e ? No. I don't see anything in the man page about hitting the c key. What does that do? I've used e, b and such but never heard of c. Dale :-) :-)
Re: [gentoo-user] x86 boot failure
On Thu, 06 May 2010 10:03:59 -0500, Dale wrote: Did you mean press e ? No. I don't see anything in the man page about hitting the c key. What does that do? I've used e, b and such but never heard of c. It drops you to the grub command line, it's documented on the GRUB menu screen itself, just after it tells you about e. -- Neil Bothwick There was a young man from the border Who had an attention disorder. When he reached the last line He would run out of time And signature.asc Description: PGP signature
Re: [gentoo-user] x86 boot failure
Stroller strol...@stellar.eclipse.co.uk writes: On 6 May 2010, at 09:37, Roger Mason wrote: ... I just built a new machine (celeron 3 GHz) using a script that builds the kernel using genkernel and a config that is copied from that of the kernel on the install cd. Are you sure ext[234] is compiled statically into the kernel in this .config? Yes. Also the drivers for the EIDE / SATA controller. The liveCD configs I've seen generally store these as modules. I, too, usually take a copy of the config from a working LiveCD when I compile a kernel, but I *always* have to change something. This what grep SATA kernel-config says: # CONFIG_BLK_DEV_IDE_SATA is not set CONFIG_SATA_PMP=y CONFIG_SATA_AHCI=m CONFIG_SATA_SIL24=m CONFIG_SATA_SVW=m CONFIG_SATA_MV=m CONFIG_SATA_NV=m CONFIG_SATA_QSTOR=m CONFIG_SATA_PROMISE=m CONFIG_SATA_SX4=m CONFIG_SATA_SIL=m CONFIG_SATA_SIS=m CONFIG_SATA_ULI=m CONFIG_SATA_VIA=m CONFIG_SATA_VITESSE=m CONFIG_SATA_INIC162X=m lspci says: 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA So, what must I set? Thanks for the help. Roger
Re: [gentoo-user] x86 boot failure
On 6 May, Roger Mason wrote: Stroller strol...@stellar.eclipse.co.uk writes: On 6 May 2010, at 09:37, Roger Mason wrote: ... I just built a new machine (celeron 3 GHz) using a script that builds the kernel using genkernel and a config that is copied from that of the kernel on the install cd. Are you sure ext[234] is compiled statically into the kernel in this .config? Yes. Also the drivers for the EIDE / SATA controller. The liveCD configs I've seen generally store these as modules. I, too, usually take a copy of the config from a working LiveCD when I compile a kernel, but I *always* have to change something. This what grep SATA kernel-config says: # CONFIG_BLK_DEV_IDE_SATA is not set CONFIG_SATA_PMP=y CONFIG_SATA_AHCI=m CONFIG_SATA_SIL24=m CONFIG_SATA_SVW=m CONFIG_SATA_MV=m CONFIG_SATA_NV=m CONFIG_SATA_QSTOR=m CONFIG_SATA_PROMISE=m CONFIG_SATA_SX4=m CONFIG_SATA_SIL=m CONFIG_SATA_SIS=m CONFIG_SATA_ULI=m CONFIG_SATA_VIA=m CONFIG_SATA_VITESSE=m CONFIG_SATA_INIC162X=m lspci says: 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA So, what must I set? Thanks for the help. Check the BIOS if it supports AHCI SATA. Select it if possible. Then set CONFIG_SATA_AHCI=y (not m, since the kernel must be able to access the disk to load any module). Helmut.
Re: [gentoo-user] x86 boot failure
Neil Bothwick wrote: On Thu, 06 May 2010 10:03:59 -0500, Dale wrote: Did you mean press e ? No. I don't see anything in the man page about hitting the c key. What does that do? I've used e, b and such but never heard of c. It drops you to the grub command line, it's documented on the GRUB menu screen itself, just after it tells you about e. Oh OK. I didn't reboot and read that part. lol I learned something today. Just hope I will remember it when I need it.;-) Thanks. Dale :-) :-)
Re: [gentoo-user] x86 boot failure
On Thu, 06 May 2010 13:07:37 -0230, Roger Mason wrote: This what grep SATA kernel-config says: # CONFIG_BLK_DEV_IDE_SATA is not set CONFIG_SATA_PMP=y CONFIG_SATA_AHCI=m CONFIG_SATA_SIL24=m CONFIG_SATA_SVW=m CONFIG_SATA_MV=m CONFIG_SATA_NV=m CONFIG_SATA_QSTOR=m CONFIG_SATA_PROMISE=m CONFIG_SATA_SX4=m CONFIG_SATA_SIL=m CONFIG_SATA_SIS=m CONFIG_SATA_ULI=m CONFIG_SATA_VIA=m CONFIG_SATA_VITESSE=m CONFIG_SATA_INIC162X=m lspci says: 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA So, what must I set? Read the help for each one, if still unsure enable them all. Or, as Helmut suggested, switch your BIOS to use AHCI. -- Neil Bothwick NOTE: In order to control energy costs the light at the end of the tunnel has been shut off until further notice... signature.asc Description: PGP signature
