Kernel Upgrade --- will not Boot, lost Init ...
Kernel Upgrade - startUp Trouble
I am trying to update my Kernel from 2.4.18-14 to 2.4.22 using RedHat 8. After doing lots of reading a following the (ambiguous instructions) I have managed to compile the new image and get the old kernel (plus the old one) onto the boot sector. My problem (the latest of many) comes when I try to boot the new Kernel. The following error is displayed:- --- EXT2-fs warning (device ide0(3,1)): ext2_read_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 128k freed. Warning: unable to open an initial console. Kernel Panic: No init Found. Try passing init= option to the kernel. --- There's LOTS of possibilities here - The Init files not moved and the old kernel can see it fine. I compiled the new kernel for ext3 so it 'should' be ok (I did nothing outlandish to the new config, just a basic setup to learn how to do this). My new /boot/grub/grub.conf files reads:- # 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,0) # kernel /vmlinuz-version ro root=/dev/hda3 # initrd /initrd-version.img #boot=/dev/hda default=1 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.22) root (hd0,0) kernel /vmlinuz-2.4.22 ro root=/dev/hda1 initrd /initrd-2.4.22.img title Red Hat Linux (2.4.18-14) root (hd0,0) kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ initrd /initrd-2.4.18-14.img The directory listing of /boot/ reads:- boot.b chain.b config-2.4.18-14 config-2.4.22 grub initrd-2.4.18-14.img initrd-2.4.22.img kernel.h lost+found message message.ja module-info -> module-info-2.4.18-14 module-info-2.4.18-14 os2_d.b System.map -> System.map-2.4.18-14 System.map-2.4.18-14 System.map-2.4.22 System.map-2.4.22.old vmlinux-2.4.18-14 vmlinuz -> vmlinuz-2.4.22 vmlinuz-2.4.18-14 vmlinuz-2.4.22 vmlinuz-2.4.22.old What does LABEL mean and why cannot the new Kernel image use this LABEL? (I had it set to this first but it would not boot unless I specifically pointed it at dev/hda1 (is this a path-like issue?)) I know that the vmlinux path is pointed at the new image but 'module-info' and 'System.map' are pointed at the old image. Should I change these as well or should they have been done automatically (seems logical)? Final BIG question --- the Linux mag I read which gave a blow by blow guide of the steps needed to do this made NO mentions of all of this occurring? Is this normal or should I be manually changing symlinks etc. It seems that there is no clearcut method for this in place ... Please Help Some one ..................garbled transmission end ........ 015464%&*$&£* |
renegade69 had the same problems. Here is a link to his thread:
http://www.linuxquestions.org/questi...highlight=ext3 ___________________________________ Be prepared. Create a LifeBoat CD. http://users.rcn.com/srstites/LifeBo...home.page.html Steve Stites |
All times are GMT -5. The time now is 11:39 PM. |