While StartOS worked well on an earlier similar Minisforum model (the UN1265), I discovered that the Minisforum UN1290 doesn’t go as expected. This model is running a newer/nicer BIOS (listed on the Main tab as “BIOS Version 1.06”, and in the footer as “Version 02.22.0058 Copyright American Megatrends International LLC”). The installation goes fine, but upon reboot, the miniPC behaves as if there is no bootable device.
After some tinkering, I’ve gotten it to work with a minor hack, so thought I would share here for anyone facing the same issue.
You will need a keyboard, mouse, and monitor temporarily (after applying the fix, they are no longer required), and a bootable Linux USB thumb drive (I used Linux Mint 22.1).
Step 1
Complete the initial StartOS installation process. When the miniPC reboots, it will not launch StartOS. This is what we will be fixing in the following steps.
Step 2
Attach the keyboard, mouse, and monitor, insert the Linux USB drive, and power up the miniPC.
Step 3
Open terminal, and enter the following commands one by one (adjust the device path if you are using a SATA drive instead of NVMe):
#Mount the EFI partition so we can do some editing:
sudo mount /dev/nvme0n1p1 /mnt
#Make a folder under EFI called “BOOT”, which the miniPC expects:
sudo mkdir /mnt/EFI/BOOT
#Copy shimx64.efi (for Secure Boot) as BOOTX64.EFI which the miniPC expects:
sudo cp /mnt/EFI/startos/shimx64.efi /mnt/EFI/BOOT/BOOTX64.EFI
#Copy mmx64.efi (goes with the shim)
sudo cp /mnt/EFI/startos/mmx64.efi /mnt/EFI/BOOT/
#Copy grubx64.efi, which the shim expects to be in the same folder
sudo cp /mnt/EFI/startos/grubx64.efi /mnt/EFI/BOOT/
#Create grub.cfg, which grub expects in the same folder, pointing to the real one
sudo nano /mnt/EFI/BOOT/grub.cfg
-----Enter just the following two lines:
search --no-floppy --file /EFI/startos/grub.cfg --set=esp
configfile ($esp)/EFI/startos/grub.cfg
-----Then save the file (Ctrl+X → Y → Enter)
#Make sure writes are finished
sync
Step 4
Reboot. StartOS should now launch.