Fedora Core 4 Update: kernel-2.6.12-1.1398_FC4

[Paul_Maia at Dell.com]

Dave,
I did a quick search to find the bugzilla you mentioned, but was unable
to find it. Can you please forward the Bugzilla number for this issue,
so that I might find a solution.

I followed the instructions at the end of this email. On my system: Dell
PE2850 Server, 2.8 GHz, Perc 4/DC
the new kernel won't boot on either the original or the new
modprob.conf/hwconf files. The following is spewed when booting
2.6.12-1.1372_FC3smp:
mkrootdev: label / not found
umount /sys failed: 16
mount: error 19 mounting ext3
mount: error 2 mounting none
switch_root: mount failed: 22
umount /initrd/dev failed: 2
kernel panic - not syncing: attempting to kill init

Paul Maia
Dell, Inc.

-----Original Message-----
From: fedora-announce-list-bounces at redhat.com
[mailto:fedora-announce-list-bounces at redhat.com] On Behalf Of Dave Jones
Sent: Friday, July 15, 2005 12:33 PM
To: fedora-announce-list at redhat.com
Subject: Re: Fedora Core 4 Update: kernel-2.6.12-1.1398_FC4

 > ---------------------------------------------------------------------
 > Fedora Update Notification
 > FEDORA-2005-572
 > 2005-07-15
 > ---------------------------------------------------------------------
 > 
 > Product     : Fedora Core 4
 > Name        : kernel
 > Version     : 2.6.12                      
 > Release     : 1.1398_FC4                  
 > Summary     : The Linux kernel (the core of the Linux operating
system).
 > Description :
 > The kernel package contains the Linux kernel (vmlinuz), the core of
 > the Red Hat Linux operating system. The kernel handles the basic
 > functions of the operating system: memory allocation, process
 > allocation, device input and output, etc.

Some users noticed that after they updated to recent kernel updates,
their systems no longer booted.  If you had this problem, please check
that your /etc/modprobe.conf has entries for your disk controller(s)
If in doubt, you can run as root..

mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
kudzu

which should regenerate the modprobe.conf file.

*note* that you need to do this _before_ installing this kernel update.
The initrd gets built based upon the contents of /etc/modprobe.conf
during the post-install of the kernel rpm.

This problem in particular affected users of a broken RPM from
livna.org for the NVidia graphics driver, but judging from feedback
in bugzilla, there may be additional causes for the damage to
/etc/modprobe.conf

Thanks,

		Dave

--
fedora-announce-list mailing list
fedora-announce-list at redhat.com
http://www.redhat.com/mailman/listinfo/fedora-announce-list