From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
The system crash early in the boot process.
Computer Compaq Deskpro P600 with
Intel PIIX4 ACPI
Video card ATI Mach64
Memory 384 MB
Grub entries of the last 2 kernels that crass at boot time. Too early to know where. The /var/log/messages files do not contain any record of the boots that crashed.
title Fedora Core (2.6.12-1.1390_FC4)
kernel /vmlinuz-2.6.12-1.1390_FC4 ro root=LABEL=/ rhgb quiet
title Fedora Core (2.6.12-1.1387_FC4)
kernel /vmlinuz-2.6.12-1.1387_FC4 ro root=LABEL=/ rhgb quiet
Last version that works.
Linux version 2.6.11-1.1381_FC5 (firstname.lastname@example.org) (gcc version
4.0.0 20050606 (Red Hat 4.0.0-11)) #1 Thu Jun 9 20:56:43 EDT 2005
Version-Release number of selected component (if applicable):
kernels 2.6.12-1.1390_FC4 2.6.12-1.1387_FC4
Steps to Reproduce:
1.Try to boot
Actual Results: Crashes. The computer is compleatly crashed. No activity of any kind
can you remove the 'quiet' from the boot command line, and see what the last
lines of text are ?
I removed the 'quiet' and the crash occurs after 'Set Host Name'. The next
operation, with feedback to the screen, in normal boot condition is 'Set Logical
[This comment has been added as a mass update for all FC4 kernel bugs.
If you have migrated this bug from an FC3 bug today, ignore this comment.]
Please retest your problem with todays 2.6.12-1.1398_FC4 update.
If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..
mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
It's possible you were hit by a recent mkinitrd bug.
Do these steps..
rpm -e kernel-2.6.12-1.1398_FC4 (only do this step if you have this installed)
yum update mkinitrd
yum update kernel
This should now work.
*** This bug has been marked as a duplicate of 163407 ***