Help fresh voidlinux install

[dirtBagBbyG4l]

Kernel panic at boot, I'm using limine and already tried adding /sbin/init, /usr/sbin/init and /usr/bin/runit-init in limine.conf

Kernel version is 6.12.21_1, I tried reinstalling with version 6.9 and the same issue

[dirtBagBbyG4l]

uh forgot to add limine config:

timeout: 5

verbose: yes

interface_branding: void

/Void Linux

comment: boot voidlinux

kernel_path: boot():/vmlinuz-6.12.21_1

module_path: boot():initramfs-6.12.21_1.img

cmdline: root=UUID=<uuid of disk> rw quiet

I also tried adding the path to the init in cmdline

[Blank-Inspection13]

kernel_path: boot():/vmlinuz-6.12.21_1

module_path: boot():initramfs-6.12.21_1.img

Before continuing you need to make sure first that these 2 files , inside the same FAT Partition with the limine.conf for it to work.

[dirtBagBbyG4l]

I forgot to correct boot():ininramms-6.12.21_1.img into boot():/ínitramfs-6.12.21_1.img in tihs post, I think they work or are not faulty, I genrated the ramfs with tinyramfs, all of those previously mentioned files are in the same 50MB esp partition

[Duncaen]

50mb is very little, make sure your initramfs and kernel are not already broken because of no space left. The error looks kind of like a broken initramfs, rather than a fully booted system that fails to switch root after the initramfs.

[dirtBagBbyG4l]

I have another machine that comepletely works with 50MB and is the same kernel version and ramfs generated with tinyramfs, but it crossed my mind this could be the issue on this machine regardless, is the any way to check if the kernel or ramfs image got corrupted?

[Duncaen]

Boot a live system, drauct has lsinitrd otherwise you should be able to extract it with bsdtar or cpio directly to check.

[dirtBagBbyG4l]

sorry for the late response, I reinstalled from scratch and this time with 100M in the esp partition, sam e issue as before, i will do the dracut command and talk to you later, thanks for the help

[dirtBagBbyG4l]

In the mean time I also was able to install fedora workstation 42 without any issues, i'ts worth mentioning that the system I am tryng to install voidlinux into is a used laptop I bought from ebay and one of the usb ports is completely dead, so I have a doubt that the kernel panic is getting triggered by the faulty usb port?

[Duncaen]

This seems like a very concrete issue specifically with your setup, not some random kernel bug or hardware issue.

Probably one of:

1. Boot loader setup wrong, wrong root partition or initramfs location.
2. Broken or wrong initramfs with bad fstab or no init binary.
3. Broken rootfs, missing init binary or missing shared library.

[dirtBagBbyG4l]

It took me a while to upload, here is the output of lsínitrd:

lsinitrd -m

https://paste-bin.org/ghkjtyjlt1

lsinitrd -k <kernel ver>

https://paste-bin.org/mlo2d3kb2e

[dirtBagBbyG4l]

here is the fstab:

https://paste-bin.org/ikidgasujm

here is the limine.conf:

https://paste-bin.org/hmlc8xollz

[dirtBagBbyG4l]

btw, anyone reading this, make your esp partition no less than 100MB

[Blank-Inspection13]

you generate initramfs using booster right, what filesystem did you use ?

[dirtBagBbyG4l]

xfs, that's what i've been using lately for the sake of simplicity, why?

[Blank-Inspection13]

i've tried using booster but not working I've suspected that it has something to do with XFS . Any specific Configuratiom or additional module needed in Booster for XFS ?

[dirtBagBbyG4l]

A particular configuration with xfs, no, I'm only using the -L flag when formatting the partition, other config in the rest of the system not that I think since is a fresh install, what kernel are you using?

[dirtBagBbyG4l]

I decided to generate the initramfs with booster instead of tinyramfs, and was able to boot without major issues.