This past Tuesday (February 27, 2024), I embarked on a new adventure (experiment?). It all started when I tried to boot up a few live images of several distributions I wanted to check out, but they all locked up after about five minutes or so, preventing me from evaluating them (In particular, I wanted to check out RebornOS, a new-to-me Arch-based distribution). I tried wiping and (re)installing Ventoy on my 128GB USB drive to no avail, then I tried ‘burning’ a live image to another USB stick with the same sad result, so I decided to try wiping my desktop computer’s M.2 SSD system drive and start over (I’ve been wanting to do it anyway, and this issue gave me an excuse) .
For partition management (and system troubleshooting), I use the live image environment from System Rescue, which includes gPartEd (the GNU partition editor), and a suite of diagnostic/recovery utilities. It doesn’t support Secure boot, so I had to enter my computer’s UEFI user interface, and disable it, then I booted System Rescue up, and used the partition editor to remove all partitions on the disk. Next, I created a new 1GB (1024MB) partition, formatted with the fat32 filesystem, and I set the esp and boot flags to make it a valid EFI partition. I named it esp, and labeled it EFI so it can be recognized as such by humans. I also created a temporary partition to consume the last half of the available disk space, so Windows won’t use it when I install it next.
My next move was to re-enable Secure Boot, then install and set up Windows 11 to meet my wishes, including switching my Windows 11 user account type to ‘Local’ (I had to sign in with my Microsoft account during installation), by clicking ‘sign in with a local account’ in the Windows Settings app under Accounts, your info. I don’t want Microsoft Copilot enabled, and if it’s there in my local Microsoft 11 account, I can’t find it - I looked.
With Windows 11 installed and set up as I wanted, I went back to the UEFI interface, and disabled secure boot again so I could boot into the RebornOS live environment after removing that temporary partition I mentioned earlier. Now the RebornOS image on my Ventoy disk booted up, and worked perfectly, confirming that a completely fresh start solved my initial issue. I installed and configured RebornOS (with the KDE Plasma DE), giving it a 40GB root partition, and 100GBs for /home, leaving more than enough space for a third, and perhaps a fourth distribution, to be added later.
Since RebornOS is an Arch-based distribution, I decided to set it up with Secure Boot support (Steps follow):
-
Enable the AUR repository for the RebornOS software manager, then install the shim-signed, sbsigntools, efitools, and refind packages.
-
In a terminal emulator, run
sudo refind-install --shim /usr/share/shim-signed/shimx64.efi --localkeys
to install rEFInd in the EFI partition, and create the keys needed forMOK
enrollment. -
Sign/resign the kernel images (/boot/vmlinuz-linux and /boot/efi/EFI/Boot/bootx64.efi):
sudo sbsign --key /etc/refind.d/keys/refind_local.key --cert /etc/refind.d/keys/refind_local.crt --output /boot/vmlinuz-linux /boot/vmlinuz-linux
sudo sbsign --key /etc/refind.d/keys/refind_local.key --cert /etc/refind.d/keys/refind_local.art --output /boot/efi/EFI/Boot/bootx64.efi /boot/efi/EFI/Boot/bootx64.efi
-
Reboot, enabling Secure Boot in the UEFI interface. When you encounter the boot error before rEFInd loads, follow the prompts to complete MOK enrollment, then when you reboot again, rEFInd will load successfuly, and so will RebornOS (or whichever Arch-based distribution you set up for Secure Boot).
I didn’t make notes about the steps I took to enroll rEFInd with the MOK utility, so I don’t have those steps handy, sorry.
After completing enrollment, I had to hide any icons (press the minus (-) key on your keyboard, and choose ‘y’ in the resulting dialog) that didn’t load one of the installed OS’s correctly (there were multiple icons for each installed OS).
With rEFInd, Windows 11, and RebornOS installed and working correctly with Secure Boot enabled, I installed my preferred GNU/Linux distribution, Solus. It supports Secure Boot by default, so I didn’t have to do anything for that, but when I rebooted the computer after installing it, I entered the UEFI interface to make rEFInd (not rEFInd [DIRECT], or Solus) the first boot option. When I saved my changes in the UEFI interface, and rebooted again, I was very pleased to see that Solus was listed as one of the boot options in the rEFInd screen, and after hiding two (Solus) icons that didn’t work correctly, I now have three icons on my rEFInd boot screen, one for Windows 11, one for Solus Linux, and a third for RebornOS (just what I wanted).
The reason I installed the OSes in the order I used, was to see if rEFInd discovered the installed operating systems automatically without me having to do anything in its configuration file (refind.conf). Since I still have enough unused space on my M.2 SSD drive, I’ll probably set that space up for test OSes (distributions I want to check/try out). I like RebornOS a lot. It has everything I want in a distribution, including drivers for my Nvidia graphics adapter, drivers for my Wi-Fi6 USB adapter, my favorite onedrive client for GNU/Linux, and the MEGAsync desktop client, all of which work perfectly after build/installation. I may find myself switching again. Who knows,
Ernie