On Thu, 2008-01-03 at 19:50 +0000, [email protected] wrote: > I do not understand, I still cannot boot on the new kernel: > 18.104.22.168-52.fc7 By "still cannot boot" what stopped it booting before this update? That kernel boots for me, I didn't have to change anything to make it boot. > This is my grub.conf: > boot=/dev/sda > default=0 > timeout=10 > splashimage=(hd0,7)/boot/grub/splash.xpm.gz > hiddenmenu > password --md5 $1$Ey8yydw2$Ia5NHuLvdjduWOKIJM57u0 > title Fedora (22.214.171.124-52.fc7) > root (hd0,7) > # kernel /boot/vmlinuz-126.96.36.199-52.fc7 ro root=LABEL=/ rhgb quiet selinux=0 > kernel /boot/vmlinuz-188.8.131.52-52.fc7 ro root=/dev/sda8 rhgb quiet selinux=0 > initrd /boot/initrd-184.108.40.206-52.fc7.img > > > title Fedora (2.6.21-1.3194.fc7) > root (hd0,7) > kernel /boot/vmlinuz-2.6.21-1.3194.fc7 ro root=/dev/sda8 rhgb quiet selinux=0 > initrd /boot/initrd-2.6.21-1.3194.fc7.img > > > I have not problem to boot on: 2.6.21-1.3194.fc7 Using the above grub.conf stanza for that kernel? Your sample grub.conf is an exact copy of the file? There's no typing errors in the copy you e-mailed? By the way: CHANGE YOUR PASSWORD, NOW! You've just shown the world the hashsum for it, and that may be enough to crack it. > With the new kernel, if I put: > kernel /boot/vmlinuz-220.127.116.11-52.fc7 ro root=LABEL=/ rhgb quiet selinux=0 > > if fails because it try to boot on a /dev/sdb, *Why* does using LABEL=/ cause it to use /dev/sdb? Do you have two drives, is "/" the right label? Try the following command to see what label is on /dev/sda8: e2label /deb/sda8 > so I force it to boot on > /dev/sda8, but I get: > setuproot: moving /dev failed No such file or directory > setuproot: error mounting /proc > setuproot: error mounting /sys This is odd. Does using "/dev/sda8" definitely work for the other kernel? -- (This computer runs FC7, my others run FC4, FC5 & FC6, in case that's important to the thread.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.