The computer I use as my server, one with an Asrock H61TM-ITX motherboard, wouldn't boot into ZimaOS after installing using the install image.
I've tried the usual: tried with different SSDs, different USB install mediums, tried with and without Ventoy, cleared the CMOS, updated the BIOS/firmware, basically everything possible. Turns out, the problem might be that the motherboard is stubborn and won't boot the OS if it isn't listed in the EFI.
I only figured it out when I used Ventoy and used the "localboot" option using F4, there with the "Search and boot BOOTX64.EFI" option selected it finally booted into ZimaOS.
In order to have the computer boot into the OS without the manual use of Ventoy every single time, I had to boot into Linux (I used Linux Mint) and manually add an entry using the "efibootmgr" command:
After those commands are run one after the other, rebooting should fix the problem.
Now, I have two assumptions. Either the motherboard is truly stubborn and wouldn't boot because it's a somewhat old motherboard and isn't following standards, or it's because the file "bootx64.efi" isn't in all caps. I haven't had the time to try the last option because I had already spend way too many hours trying to figure this out, but it's something that might need to get looked into so that after the install is finished there's also an entry being added into the EFI so it can boot into the OS afterwards.
The computer I use as my server, one with an Asrock H61TM-ITX motherboard, wouldn't boot into ZimaOS after installing using the install image.
I've tried the usual: tried with different SSDs, different USB install mediums, tried with and without Ventoy, cleared the CMOS, updated the BIOS/firmware, basically everything possible. Turns out, the problem might be that the motherboard is stubborn and won't boot the OS if it isn't listed in the EFI. I only figured it out when I used Ventoy and used the "localboot" option using F4, there with the "Search and boot BOOTX64.EFI" option selected it finally booted into ZimaOS.
In order to have the computer boot into the OS without the manual use of Ventoy every single time, I had to boot into Linux (I used Linux Mint) and manually add an entry using the "efibootmgr" command:
After those commands are run one after the other, rebooting should fix the problem.
Now, I have two assumptions. Either the motherboard is truly stubborn and wouldn't boot because it's a somewhat old motherboard and isn't following standards, or it's because the file "bootx64.efi" isn't in all caps. I haven't had the time to try the last option because I had already spend way too many hours trying to figure this out, but it's something that might need to get looked into so that after the install is finished there's also an entry being added into the EFI so it can boot into the OS afterwards.