i am running 32-bit linux OS on an intel dual core (x66-64 bit) machine...i just compiled the latest 2.6.20.1 kernel on my FC5 box ...but am getting kernel panic on rebooting with the new kernel...i get the following error messages

PCI:BIOS bug: MCFG area at f0000000 is not E820-reserved
PCI:not using MMCONFIG
Unable to access resume device(LABEL=SWAP-sda10)
mount : could not find filesystem '/dev/root'
setuproot : mounting /dev failed:no such file or directory
setuproot : error mounting /proc:no such file or directory
setuproot : error mounting /sys failed:no such file or directory
switchroot: mount failed
kernel panic - not syncing: attempted to kill init

moreover when i select my old kernel at the grub prompt it boots fine..its just the new kernel...

fdisk -l shows this...
/dev/sda1 * 1 1912 15358108+ 7 HPFS/NTFS
/dev/sda2 1913 19456 140922180 f W95 Ext'd (LBA)
/dev/sda5 1913 7649 46082421 7 HPFS/NTFS
/dev/sda6 7650 12111 35840983+ 7 HPFS/NTFS
/dev/sda7 12112 16573 35840983+ 7 HPFS/NTFS
/dev/sda8 16574 17848 10241406 b W95 FAT32
/dev/sda9 17849 17861 104391 83 Linux
/dev/sda10 17862 17990 1036161 82 Linux swap / Solaris
/dev/sda11 17991 19456 11775613+ 83 Linux

output of my fstab file

[root@localhost ~]# cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
LABEL=SWAP-sda10 swap swap defaults 0 0

..heres my grub.conf...


[root@localhost ~]# cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,8 )
# kernel /vmlinuz-version ro root=/dev/sda11
# initrd /initrd-version.img
#boot=/dev/sda
default=2
timeout=30
splashimage=(hd0,8 )/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.20.1_FC5smp)
root (hd0,8 )
kernel /vmlinuz-2.6.20.1 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.20.1.img
title Fedora Core (2.6.15-1.2054_FC5smp)
root (hd0,8 )
kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.15-1.2054_FC5smp.img
title Win XP
rootnoverify (hd0,0 )
chainloader +1

its the first one 2.6.20.1 thats giving the problem...

really cant understand why this is happening...ive tried everything without success..

first i tried extracting the initrd image and modifying init..
3) 'cd /boot'
4) 'mkdir newinit'
5) 'cd newinit'
6) 'gunzip -c ../initrd-2.6.15-1.2054_FC5.img | cpio -idmv'
7) 'vi init'
8 ) Find 'mount /sysroot' (near the end of the file)
9) Delete or comment this out
10) Replace with 'mount -o defaults --ro -t
ext3 /dev/VolGroup00/LogVol00 /sysroot' where /dev/VolGroup00/LogVol00
is the mount point for /
11) ':wq' out of vi
12) 'find . | cpio --quiet -c -o >../newinitrd'
13) 'cd ..' - you are now in /boot
14) 'mv initrd-2.6.15-1.2054_FC5.img initrd-2.6.15-1.2054_FC5.bak' -
backup current initrd img file (just in case)
15) 'gzip -9 < newinitrd > initrd-2.6.15-1.2054_FC5.img'
16) Reboot the computer

ive tried to copy vmlinuz,System.map and generate initrd manually as well as doing a make install......no luck..then built SCSI support into the kernel...nothing!...still the same blasted messages... even tried commenting the initrd line in grub.conf (i am really desperate!)..is this a bug in FC5 has anyone successfully compiled a new kernel in an FC5 box....

I wonder why it seems to be trying to resume?

The mmcongig message can be ignored, since disabling it triggers the “work around” mentioned in the next line. If you don’t want to see the message, add pci=nommconf to the kernel= line in grub.conf. In any case, I don’t think it’s got anything to do with your system trying to “resume” from a “suspend.”

Also, do you have some reason for sticking with FC5? If I understood what I read here, the Fedora project terminated all “Fedora Legacy” support last month, and will not be providing any more bug fixes or upgrades for older releases.

thanks for replying...

does that mean that you cant compile the latest kernels on an FC5 box anymore..?i really have no reason for sticking with FC5 except that i have downloaded and burnt them to cds and i have to do the whole thing all over again with FC6...can the problem have something to do with the fact that i am using a 32 bit version on a 64 bit machine...in that case even if i install FC6 will i have the same problems that i have now when i try to compile new kernels on it...

Try the 64 bit version of FC6. And, if you have a DVD, use BitTorrent to download the ISO.

..but the problem is the FC5 cds work..the kernel shipped with the 32-bit version works its just that the new kernel that dosent work...surely i must be doing something wrong...if the older kernel works...