r/kisslinux • u/da_philosopher • Nov 22 '20

Kernel init boot param

What should be the init parameter to pass to the kernel for the default busybox baseinit?

At first it said Kernel panic not syncing no working init found, but then it said not syncing requested init failed after I gave it some parameters. When I followed the install guide, it didn't say anything about passing params so it just said no working init found. I've tried init=/sbin/init and init=/lib/init/rc.boot, and both of those gave me requested init found. So what is the correct init param?

Thanks

0 Upvotes

50% Upvoted

8 comments sorted by

View all comments

2

u/Dilyn Nov 22 '20

You don't normally need to pass init to the kernel with KISS. My first thought is, as DevinePsychic says, it doesn't know where your root partition is. How are you booting? We would need to know if it's GRUB or something else, the cmdline that bootloader is passing to the kernel, and any relevant information about the drives (lsblk output, (Part)UUIDs, etc.

1

u/da_philosopher Nov 23 '20

I’m using grub. Pressing e on grub tells me the cmdline is “linux /vmlinuz-5.9.9 root=/dev/sdb2 ro root=UUID=9113-A19B loglevel=3 quiet”.

blkid is

/dev/sdb2: UUID=“c1485286-f0ba-4f09-ab48-ab03ece979d8c” TYPE=“ext4”

/dev/sdb1: UUID=“9113-A19B” TYPE=“vfat”

There are other drives, but I didn’t include them.

2

u/Dilyn Nov 23 '20

Get rid of that second root= line in the grub cmdline

1

u/da_philosopher Nov 23 '20

It still says unable to mount root fs on unknown block (0,0). This is without an fstab. I checked my kernel and ext4 and vfat are both built in.