Hi Tim,
thank for your comments.
On Thu, 2008-01-03 at 19:50 +0000, pd520@xxxxxxxxxx wrote:
I do not understand, I still cannot boot on the new kernel:
2.6.23.12-52.fc7
By "still cannot boot" what stopped it booting before this update?
Because I had the same problem, never resolved, with the previous update
of the kernel (2.6.23.8 if I remember)
That kernel boots for me, I didn't have to change anything to make it
boot.
This is why I do not undertsand why ity does not work for me !
This is my grub.conf:
boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,7)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.23.12-52.fc7)
root (hd0,7)
# kernel /boot/vmlinuz-2.6.23.12-52.fc7 ro root=LABEL=/ rhgb quiet selinux=0
kernel /boot/vmlinuz-2.6.23.12-52.fc7 ro root=/dev/sda8 rhgb quiet selinux=0
initrd /boot/initrd-2.6.23.12-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?
Like what ? I do not see any typo.
I already work around. I cannot see what is wrong. The kernel
2.6.21-1.3194 is absolutely fine, but not the new ones. Same syntax.
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.
Is it the password of grub ?
With the new kernel, if I put:
kernel /boot/vmlinuz-2.6.23.12-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?
The first time that I installed a FC7 I had a problem with the
root=LABEL=/ because I guess that I had 2 partitions on 2 different
drive with the same lable like /. So since that time, I avoid to use the
LABEL. When I will understand exactly what is going on, I will be able
to make more test. Right now, I have a kernel booting properly. Doing
the same thing and just booting another kernel should work and it does
not.
Try the following command to see what label is on /dev/sda8:
e2label /deb/sda8
Yes /dev/sda8 has a label /, as well as /dev/sdb5 which I only mount in
read-only.
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?
Yes
--
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Patrick Dupré pd520@xxxxxxxxxx
University of York Department of Chemistry
Heslington, York YO10 5DD United Kingdom
Phone: +44-(0)-1904-434384 Fax: +44-(0)-1904-432516
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
