Pierugg
2003-09-28, 03:17 AM CDT
Pacman <piercer@nospam_pacbell.net> wrote in message
news:220920031405000688%piercer@nospam_pacbell.net ...
> C) If its a new installation the floppy should have the same kernel
> number as your original that was under /boot on your hard drive. You
> can copy the kernel and associated files from /boot on the floppy over
> to the /boot on the hard drive. Make sure to check the grub or lilo
> conf file (whichever you are using) to make sure the entry is listed
> for that particular kernel.>
> P-
Hi,
There is no /boot on the floppy, all the files
(syslinux.cfg,vmlinuz,initrd.img,boot.msg,Ldlinux. sys) are at the root. So I
tried copying initrd.img to /boot on the hd (/ is /dev/hdb6), renaming
intird-2.4.20-8.img (which must be the buggy kernel) to
intird-2.4.20-8.old.img and renaming initrd.img (from the floppy) to
intird-2.4.20-8.img. i checked grub.conf, it was pointing to the right
place, so it looked ok. But when I rebooted I had the same error as usual,
that is "Kernel Panic: VFS: Unable to mount root fs on 00:00" or something
close to it. i searched on google and find those possible reasons for the
error:
1. You passed the kernel the wrong root drive.
2. The File system is not supported by the kernel.
3. The file system driver is compiled as a module and you are not using a
proper initrd.
4. Fine system is corrupt, whoops.
but if I can boot from the floppy then the kernel is right, so why won't it
boot when I put it on the HD?
Also someone suggested to me to do that:
boot from floppy,
insert your installation CD
copy the kernel-2.4.20-8.rpm file to your harddisk
rpm -e --nodeps kernel-2.4.20-8
rm -rf /lib/modules/`uname -r`
rpm -i kernel-2.4.20-8
and said it's really risky, is it really?
Thanks
Pierugg
news:220920031405000688%piercer@nospam_pacbell.net ...
> C) If its a new installation the floppy should have the same kernel
> number as your original that was under /boot on your hard drive. You
> can copy the kernel and associated files from /boot on the floppy over
> to the /boot on the hard drive. Make sure to check the grub or lilo
> conf file (whichever you are using) to make sure the entry is listed
> for that particular kernel.>
> P-
Hi,
There is no /boot on the floppy, all the files
(syslinux.cfg,vmlinuz,initrd.img,boot.msg,Ldlinux. sys) are at the root. So I
tried copying initrd.img to /boot on the hd (/ is /dev/hdb6), renaming
intird-2.4.20-8.img (which must be the buggy kernel) to
intird-2.4.20-8.old.img and renaming initrd.img (from the floppy) to
intird-2.4.20-8.img. i checked grub.conf, it was pointing to the right
place, so it looked ok. But when I rebooted I had the same error as usual,
that is "Kernel Panic: VFS: Unable to mount root fs on 00:00" or something
close to it. i searched on google and find those possible reasons for the
error:
1. You passed the kernel the wrong root drive.
2. The File system is not supported by the kernel.
3. The file system driver is compiled as a module and you are not using a
proper initrd.
4. Fine system is corrupt, whoops.
but if I can boot from the floppy then the kernel is right, so why won't it
boot when I put it on the HD?
Also someone suggested to me to do that:
boot from floppy,
insert your installation CD
copy the kernel-2.4.20-8.rpm file to your harddisk
rpm -e --nodeps kernel-2.4.20-8
rm -rf /lib/modules/`uname -r`
rpm -i kernel-2.4.20-8
and said it's really risky, is it really?
Thanks
Pierugg