Disk images use the actual almalinux secure boot key. When the almalinux secure boot key changes which should be very rare, you will need to disable secure boot temporarily and enroll the new key with mokutil by running:
sudo cp /usr/share/pki/sb-certs/secureboot-kernel-x86_64.cer /etc/secureboot_key/MOK.der
sudo mokutil --import /etc/secureboot_keys/MOK.der
Reboot, enroll the key in shim and re-enable secureboot.
Arch Linux does not have secure boot support through its official repository. Linuxloops will install the "shim-signed" bootloader AUR package.
Artix Linux does not have secure boot support through its official repository. Linuxloops will install the "shim-signed" bootloader AUR package.
BlendOS does not have secure boot support through its official repository. Linuxloops will install the "shim-signed" bootloader AUR package.
Before installing brunch, please refer to the brunch readme for more information on device compatibility.
Please raise brunch issues on the brunch github repository.
CachyOS does not have secure boot support through its official repository. Linuxloops will install the "shim-signed" bootloader AUR package.
ChromeOS-Flex disk images cannot be booted from a btrfs partition due to the absence of btrfs support in the ChromeOS-Flex kernel config.
If you install the nvidia proprietary driver, the first boot after each kernel update will be long as the nvidia kernel modules are being rebuilt.
If you install the nvidia proprietary driver, you will need to disable Secure Boot.
Kali does not have secure boot support in full disk install.
Manjaro does not have secure boot support through its official repository. Linuxloops will install the "shim-signed" bootloader AUR package.
Disk images use the actual OpenSUSE secure boot key. When the OpenSUSE secure boot key changes which should be very rare, you will need to disable secure boot temporarily and enroll the new key with mokutil by running:
sudo cp /usr/share/efi/x86_64/grub.der /etc/secureboot_key/MOK.der
sudo mokutil --import /etc/secureboot_keys/MOK.der
Reboot, enroll the key in shim and re-enable secureboot.
parrot does not have secure boot support in full disk install.
On the first boot you will be prompted to configure qubes, if you experience a crash after the first boot with the default qubes settings you should disable usb qubes in the configuration menu.
Disk images use the actual rockylinux secure boot key. When the rockylinux secure boot key changes which should be very rare, you will need to disable secure boot temporarily and enroll the new key with mokutil by running:
sudo cp /usr/share/pki/sb-certs/secureboot-kernel-x86_64.cer /etc/secureboot_key/MOK.der
sudo mokutil --import /etc/secureboot_keys/MOK.der
Reboot, enroll the key in shim and re-enable secureboot.
SteamOS installed from the 3.6 branch of the SteamOS packages repository (https://steamdeck-packages.steamos.cloud/archlinux-mirror/) with minor adjustments to support standard computers usage.
Packages can be installed and updated with pacman, however native packages available in the SteamOS packages repository are not the latest versions, therefore for sensitive apps such as web browsers and such it is recommended to use the flatpak version (available by default in the Discover app).
2 environments are available:
- Desktop: Boots to Plasma session. The gamescope session can be launched within Plasma through the "SteamDeck Session" shortcut (in "Game" section).
- Gamescope: Same as the SteamDeck. Boots directly into the SteamOS session. Plasma can be launched with the "Switch to Desktop" SteamOS option.
Note: The gamescope session is not compatible with nvidia gpu but you can use the standard steam app within a desktop environment.
Tails disk images can only be installed on ext4 partitions (due to the lack of kernel modules for ntfs / exfat support in its initramfs).