LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Kernel Panic (init) with Slack and Grub (https://www.linuxquestions.org/questions/slackware-14/kernel-panic-init-with-slack-and-grub-401395/)

Diademed 01-09-2006 08:15 PM
Kernel Panic (init) with Slack and Grub
 
My grub boot looks something like(from the grub prompt):

root (hd0,0)
kernel /vmlinuz

where hda1 is my /boot partition.

So it appears to find the kernel fine, but when it tries to load init, it gets
Code:
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

Now, correct me if I am wrong, but Slack shouldn't need an init to boot.

Could it be I have the wrong kernel? I was forced to install by USB, and so couldn't load a new kernel, and when I got to the "select your kernel" screen, I skipped it, and used the default kernel.

(my Thinkpad X30 does not have floppy or CDROM)

Anyway, Can anyone tell me how to get by this and get into slack?

Cheers(!)
Dia

Woodsman 01-10-2006 12:23 AM
Quote:
root (hd0,0)
kernel /vmlinuz
You have part of the info correct. You need to use GRUB syntax to tell GRUB where the kernel resides. You also need to boot with the root partition read-only. Something like this:

title Slackware 10.2 - 2.4.31 - KDE 3.4.2
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 ro

If you have installed everything on one partition (hda1 / hda0,0) then be sure to add the /boot prefix to vmlinuz. Also notice that although GRUB begins counting partition and devices with zero, the kernel counts the first partition as hda1.

Diademed 01-10-2006 05:47 PM
Quote:
Originally Posted by Woodsman
You have part of the info correct. You need to use GRUB syntax to tell GRUB where the kernel resides. You also need to boot with the root partition read-only. Something like this:

title Slackware 10.2 - 2.4.31 - KDE 3.4.2
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 ro

If you have installed everything on one partition (hda1 / hda0,0) then be sure to add the /boot prefix to vmlinuz. Also notice that although GRUB begins counting partition and devices with zero, the kernel counts the first partition as hda1.
That's not quite right... the root command sets the root directory for grub, so you no longer have to give the full path for the kernel.

In any case, this seems to just be an issue with grub 0.97 on my system. 0.95 works fine.

Woodsman 01-10-2006 06:02 PM
Quote:
In any case, this seems to just be an issue with grub 0.97 on my system. 0.95 works fine.
Interesting. I'm using 0.97. I've had no boot-related issues arise.


All times are GMT -5. The time now is 05:27 AM.