After updating from 0.10 to 0.11 on Arch Linux, I could not boot into the OS and had the message vmlinuz-linux not found, so I disabled Secure Boot and chrooted via a USB bootable media.
I then changed /vmlinuz-linux to /boot/vmlinuz-linux in /boot/loader/entries/arch.conf. I rebooted, and this time it would still take me to UEFI BIOS, but with no error message of being unable to find the file.
Then, I changed the remaining files entries by appending /boot. That changed nothing on reboot.
Then, I tried running booster build booster-linux.img (which did nothing), reverted all aforementioned changes, and added booster.debug to the kernel parameter in /boot/loader/entries/arch.conf.
Then, I rebooted, and it took me to the OS (after it had dumped out loads of information that was being displayed too quickly to adequately capture). I removed the kernel parameter, and rebooted into the OS, so I effectively changed nothing.
After updating from
0.10
to0.11
on Arch Linux, I could not boot into the OS and had the messagevmlinuz-linux not found
, so I disabledSecure Boot
and chrooted via a USB bootable media.I then changed
/vmlinuz-linux
to/boot/vmlinuz-linux
in/boot/loader/entries/arch.conf
. I rebooted, and this time it would still take me to UEFI BIOS, but with no error message of being unable to find the file.Then, I changed the remaining files entries by appending
/boot
. That changed nothing on reboot.Then, I tried running
booster build booster-linux.img
(which did nothing), reverted all aforementioned changes, and addedbooster.debug
to the kernel parameter in/boot/loader/entries/arch.conf
.Then, I rebooted, and it took me to the OS (after it had dumped out loads of information that was being displayed too quickly to adequately capture). I removed the kernel parameter, and rebooted into the OS, so I effectively changed nothing.