Thanks Nick, I have got the system booting on it's own again. But I can only boot the 2.4.18-14, and the 18-17.8.0 kernels. The 18-18.8.0 does not want to work. It brings up the same message as before, "kernel panic. No init. found. Try passing init=option to kernel".
What does this mean. I notice when it boots on the working kernel, it shows at the same location the other kernel locks up, this message "init version 2.84", and the proceeds to boot. Is the 18-18.8.0 kernel not installed properly? Hoe do I check, and if not, how do I re-install. LILO says everything is o.k. with the configuration, so must be something to do with the actual kernel. regards Greg On Tue, 2002-11-1at 22:00, Nick Lindsell wrote: > At 21:00 19/11/2002 +1100, you wrote: > >Hi list, > > > >problem with RH8. Went into the lilo config in the control center in > >KDE, and removed all the entries for old kernels so that only the > >current one is listed. I had 2.4.18-14, and 2.4.18-17.8.0, and I had > >just downloaded and installed 2.4.18-18.8.0. So I removed the old ones, > >and left only the 18.8.0 one and made it default. When I went to > >re-boot, I am now getting this error 'kernel panic. no init found. try > >passing init-option to kernel', and the system freezes. I can now only > >boot off floppy. When I go back into the control centre, and then > >select probe, it brings back all the old entries, and everything looks > >like it used to, but it still only shows the 18.8.0 kernel on the lilo > >boot when I re-boot the computer, and it still freezes. When I do check > >configuration in the control center this is what comes up: > >Configuration NOT ok. LILO said: > >LILO version 21.4-4 (test mode), Copyright (C) 1992-1998 Werner > >Almesberger > >'lba32' extensions Copyright (C) 1999,2000 John Coffman > >Reading boot sector from /dev/hda2 > >Merging with /boot/boot.b > >Mapping message file /boot/message > >Boot image: /boot/vmlinuz-2.4.18-14 > >Mapping RAM disk /boot/initrd-2.4.18-14.img > >Added 2.4.18-14 > >Boot image: /boot/vmlinuz-2.4.18-14debug > >Mapping RAM disk /boot/initrd-2.4.18-14debug.img > >Fatal: Duplicate label "2.4.18-14" > > > >and this is what the boot configuration file is configured like > >boot=/dev/hda > >prompt > >timeout=50 > >message=/boot/message > >root=/dev/hda3 > > > >image="/boot/vmlinuz-2.4.18-14" > > label="2.4.18-14" > > root="/dev/hda3" > > read-only > > initrd="/boot/initrd-2.4.18-14.img" > > > >image=/boot/vmlinuz-2.4.18-14debug > > label="2.4.18-14" > > root=/dev/hda3 > > read-only > > initrd="/boot/initrd-2.4.18-14debug.img" > > > >image="/boot/vmlinuz-2.4.18-17.8.0" > > label="2.4.18-17.8.0" > > root="/dev/hda3" > > read-only > > initrd="/boot/initrd-2.4.18-17.8.0.img" > > > >image=/boot/vmlinuz-2.4.18-17.8.0debug > > label="2.4.18-17.8.0" > > root=/dev/hda3 > > read-only > > initrd="/boot/initrd-2.4.18-17.8.0debug.img" > > > >image="/boot/vmlinuz-2.4.18-18.8.0" > > label="2.4.18-18.8.0" > > root="/dev/hda3" > > read-only > > initrd="/boot/initrd-2.4.18-18.8.0.img" > > > >image=/boot/vmlinuz-2.4.18-18.8.0debug > > label="2.4.18-18.8.0" > > root=/dev/hda3 > > read-only > > initrd="/boot/initrd-2.4.18-18.8.0debug.img" > > > >image=/boot/vmlinuz-2.4.18-18.8.0uml > > label="2.4.18-18.8.0" > > root=/dev/hda3 > > read-only > > > >image=/usr/src/linux/arch/i386/boot/bzImage > > label="Linux_Compiled" > > root=/dev/hda3 > > read-only > > optional > > > >other=/dev/hda1 > > label="NT" > > > > > >All I really want to do is boot from the new kernel, but my boot disk > >brings up the old kernel,and lilo is stuffed. > > > >HELP ME!!!! > >thanks > >Greg > > > > > Lilo is refusing to install because it detects a duplicate label > (as it reports). You need to change the "label=" sections to > reflect what you are trying to boot and have those labels unique > (the labels are what lilo display when you hit <tab> at the boot prompt. > > image="/boot/vmlinuz-2.4.18-14" > label="2.4.18-14" <<<<<< > root="/dev/hda3" > read-only > initrd="/boot/initrd-2.4.18-14.img" > > image=/boot/vmlinuz-2.4.18-14debug > label="2.4.18-14debug" <<<<<<< > root=/dev/hda3 > read-only > initrd="/boot/initrd-2.4.18-14debug.img" > > image="/boot/vmlinuz-2.4.18-17.8.0" > label="2.4.18-17.8.0" <<<<<<<< > root="/dev/hda3" > read-only > initrd="/boot/initrd-2.4.18-17.8.0.img" > > image=/boot/vmlinuz-2.4.18-17.8.0debug > label="2.4.18-17.8.0debug" <<<<<<<<<< > root=/dev/hda3 > read-only > initrd="/boot/initrd-2.4.18-17.8.0debug.img" > > image="/boot/vmlinuz-2.4.18-18.8.0" > label="2.4.18-18.8.0" <<<<<<<<<< > root="/dev/hda3" > read-only > initrd="/boot/initrd-2.4.18-18.8.0.img" > > image=/boot/vmlinuz-2.4.18-18.8.0debug > label="2.4.18-18.8.0debug" <<<<<<<<<< > root=/dev/hda3 > read-only > initrd="/boot/initrd-2.4.18-18.8.0debug.img" > > image=/boot/vmlinuz-2.4.18-18.8.0uml > label="2.4.18-18.8.0uml" <<<<<<<<< > root=/dev/hda3 > read-only > > image=/usr/src/linux/arch/i386/boot/bzImage > label="Linux_Compiled" > root=/dev/hda3 > read-only > optional > > other=/dev/hda1 > label="NT" > > > > then lilo should be able to install itself. > > ttfn > nick@nexnix > > > > > > > >-- > >redhat-list mailing list > >unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > >https://listman.redhat.com/mailman/listinfo/redhat-list > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > https://listman.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
