Hi, does somebody else experience booting problems after normal installation on SD32G2 based Shuttle systems. A CentOS 5.0 installation can be performed without any problems but after the first reboot the systems are just stopping the boot process after the grub is searching for the kernel. The last line is some- thing like: [ Linux-initrd @ 0x37db8000, 0x237858 bytes]. We tried already the newest update of the CentOS 5 kernel, the newest centosplus kernel and also FC6 kernel with always the same result. No error message, nothing! Unfortunately we have 15 machines of this type which should be installed with Linux ASAP (and no, I was not asked when somebody else has bought these machines). Every hint or experience with such system is welcome, thanks, Gernot
Gernot Stocker wrote:
Hi, does somebody else experience booting problems after normal installation on SD32G2 based Shuttle systems. A CentOS 5.0 installation can be performed without any problems but after the first reboot the systems are just stopping the boot process after the grub is searching for the kernel. The last line is some- thing like: [ Linux-initrd @ 0x37db8000, 0x237858 bytes]. We tried already the newest update of the CentOS 5 kernel, the newest centosplus kernel and also FC6 kernel with always the same result. No error message, nothing! Unfortunately we have 15 machines of this type which should be installed with Linux ASAP (and no, I was not asked when somebody else has bought these machines). Every hint or experience with such system is welcome, thanks, Gernot
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Gernot,
A stock answer: Try turning off APIC on the kernel command line in GRUB. Try noapic and/or acpi=off.
Please tell us more about the configuration..
Bob...
On Tuesday 05 June 2007, Bob Chiodini wrote:
Gernot,
A stock answer: Try turning off APIC on the kernel command line in GRUB. Try noapic and/or acpi=off.
Please tell us more about the configuration..
Hi Bob, thanks for the stock answer, but the solution for the problem was stock answer two ;-): If nothing helps, do a BIOS upgrade!
Thanks anyway, Gernot
-
Bob Chiodini -
Gernot Stocker