José Miguel Sarasola

The Unit debugging I'm guessing is the boot 'booster.log=debug,console' parameter? If it's that, when this error happens, I can only reboot doing Ctrl + Alt + Supr and that boot...

Did it, got to this screen:  Journalctl is not showing that boot try.

Not sure if I did it right. Cloned the repo, checkout to wip, `go build` and `sudo ./booster build --force /boot/booster-linux-zen.img`. Getting the same fsck message 

So, `sudo ./booster build --force --init-binary=../init/init /boot/booster-linux-zen.img`. Now instead of getting a message, the monitor looses display signal,

Also have tried with full path and moving the binary to a dir under /: `sudo ./booster build --force --init-binary=/usr/local/bin/init /boot/booster-linux-zen.img` and the same result

The monitor goes from a black screen to another one saying that it is not receiving signal and it will turn off by itself in a minute

If I comment the amdgpu (Or move it to modules) I end up with a black screen PD: I have to leave now, it's late here. As soon as I...

Exact same results Without amdgpu I get a black screen always, for rest of tests is enabled With logs -> I get like the picture I posted earlier Without logs...

There is probably something related to the AMDGPU drivers. Back in the day suddenly I started to need the module added explicitely to the mkinitcpio.conf, but since using that, it...

Nah, it looses the signal I can't see anything. My working mkinitcpio.conf in case it helps: ``` # vim:set ft=sh # MODULES # The following modules are loaded before any...