Required mkinitcpio hooks for the Pi 5

Which mkinitcpio hooks do we require for running the Pi 5 headless (ext4 filesystem)? I’m currently using:

HOOKS=(base udev autodetect modconf kms keyboard keymap block filesystems fsck)

I’m mostly wondering whether the kms hook is required.

I have dtoverlay=vc4-kms-v3d set in /boot/config.txt. I guess the kms hook would be required for this. Do I need this for headless?

Not sure if Arm is using mkinitcpio or dracut. Hopefully @Pudge or @sradjoker will be around soon to assist.

Pudge is a bigger expert on the headless side here but the archwiki says that kms has to be there:

https://wiki.archlinux.org/title/Kernel_mode_setting#mkinitcpio

As the person who tinkers with kernel configs and compiles them, I should probably know more about them.

We ship mkinitcpio by default but I use dracut on my Pi 4B and it doesn’t need any of these hooks

3 Likes

If you go here:

Then burn this to a micro SD card. Upon first boot it will auto start and prompt for the necessary configuration info.
It will set up a static IP adress, change the SSH port, set up mount points for the data SSD and Backup SSD, if you want it will format the DATA SSD.

When finished, after a reboot, you have a complete headless server ready to go.

If you want to experiment with setting up your own rpi headless server, install the package from here.

sudo pacman -S eos-hooks

Pudge

EDIT:
I just checked my RPi headless server, and the eos-hooks package is not installed.
Here is the PKGBUILD for eos-hooks.

Evidently, no mkinitcpio hooks are needed

3 Likes

Thanks @Pudge. Do the EOS config scripts set any configs in the eeprom & config.txt file? I’ve got everything set up & working, but I set some params in the aforementioned as part of the setup (mostly because the Argon ONE manual told me to). I’m not sure it would have been able to boot from the SSD without them.

yes the script writes to the /boot/config.txt file. No it dos not do anything to the eeprom.

Pudge

1 Like