Lucid Puppy 5.25 - Kernel panic - No init found - Try init=

[svgt]

Hi,

I did the normal Full Puppy installation at ide disk. It was the one and only linux at the disk. I did the normal Grub installation into mbr. The lines in menu.lst are:

title Lucid Puppy 525 (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro vga=normal

I have done this procedure a lot of times without any problems. Now I get this message:

Kernel panic - No init found - Try passing init= option to kernel.

I searched for these items in the forum. I found something in the 5.25 thread. But there are about 128 pages. And I don't know any trick to get right one.

Regards Svgt

[puppyluvr]

Hello,
You are missing the line that points to the init...
I dont do the full install thing, but you need to point to the initrd on the next line after kernel /
Find initrd.gz
If it is in /boot add this...

initrd /boot/initrd.gz

If it is just on the top level, maybe try

initrd /dev/sda1/initrd.gz

You have to tell it where the kernel AND the initrd are...

[rjbrewer]

A "full" install does not use an initrd.gz line

[svgt]

With my full install, there is no need for the initrd line. And if paste such a line, I get the message: file not found

Because this event is unique, at which point of the installation procedure I made a mistake?

[rjbrewer]

With my full install, there is no need for the initrd line. And if paste such a line, I get the message: file not found

Because this event is unique, at which point of the installation procedure I made a mistake?

Just tried a full install of 525; worked fine.

Kernel panic mostly occurs with a bad burn to cd.

[puppyluvr]

So how does it load the initrd?

[rjbrewer]

That word never comes up.
Just the kernel line when pressing edit key at bootscreen.

Total amount of "inits" in my 6 puppy full installs:

[Béèm]

So how does it load the initrd?

In a FULL install he complete file system is already installed on the HDD.
No need for a initrd.gz. This is only needed for a FRUGAL install.

[Karl Godt]

title Lucid Puppy 525 (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro vga=normal

Is the simple normal Puppy full install menu.lst entry for one partition on the first primary partition of the first HD .
For an IDE-kernel it would be root=/dev/hda1 ,
IF
the main HD is master on the first IDE slot .

You can of course copy any initrd.gz somewhere to the partition and point grub to use it in the menu.lst .

However , it would need something like

+ if [ "$PUPMODE" != "2" ] ; then

##do all the loading of .sfs and .pupsave

+ else
+ echo "Booting full installation ... " >/dev/console
+ fi


After the kernel has mounted the rootfs on /dev/root (/dev/sda1 in this case )

the kernel searches actively for one file called 'init' on the HD .

I puppy5 init is a script located in /sbin , in puppy4 a symlink to busybox .

Should be located in some "superuserbin" directory .

For a frugal installation actually two inits are run : first in initrd.gz and , after that , second in /sbin/ .

I would use the "find" command from live-cd to search for the link or script "init" like

Code: Select all

find /mnt/sda1/ -maxdepth 4 -iname "*init*"

[puppyluvr]

Hello,
OK, I am confused..
No initial ramdisk.. that I get..
Since the save is also on the HDD partition, (ala save to sda1 etc)..:
.
What gets run from ram, and what from the HDD after boot??
Does it layer onto the initial .sfs like a frugal, or load the contents of the partition..

If you specify a save file size, does it create a "copyable" 2fs/3fs file, like a frugal..
I know, I know... Back to bk.org...

No wonder I like frugal so much..LOL..

[Béèm]

puppyluvr, have a look at the pupmode 2 section of how puppy works

[puppyluvr]

Hello,
Wow, I never realized a full install ran SO differently.....
Very interesting....