I ' ve been on void for almost a year on my main desktop , but I ' m running Arch Linux Arm ALARM on my laptop . I wanted to try getting another distro working on it the other day but the proprietary bootloader has once again decided to become sentient and prohibit me from booting from USB sticks or SD cards the only two available peripherals . At the moment I ' m rolling my own init system . Backstory systemd refused to let my laptop boot after I updated as my kernel did not have cgroups support . Rather than just complaining it would also completely hang at boot . I was stuck in a semiremote area so I went ' bugger it ' and wrote my own by adding ' initbinbash ' to my kernel command line and working things out from there . I still have to keep systemd installed to avoid problems with tools such as pgrep . And I have to run dbusdaemon system . And systemdudev daemon . The first because udev did not seem to work without it and the second because I could not get userspace firmware loading to work at all needed for wifi without it . On boot my process list is very short and simple my init acpid for lid openclose event handling gettys on each tty systemdudev and dbus , because I run systemdlinux syslog and bootlog , which I forgot I had installed at some point and probably are not configured to work properlyI ' d love to find out how to fix the udev dbus necessity , but I ' d like to fix my bootloader first . If this laptop gets put in a nonbootable state then I can no longer repair it , as the secondary bootloader I used to have access to is now gone . ie no access to boot options or any sort of configurability , the only ' recovery ' process is to completely reinstall chrome os , put the device back into developer mode and start again . Lesson don ' t buy devices with locked down bootloaders . They ' re perfectly fine until things go wrong , then you ' re in for a lot of fun .