• TheCheddarCheese@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      25 days ago

      I have the kernel in the bootloader, problem is I need to enroll it with MOK manager to actually boot it in secure boot. But it starts in /boot/efi with no option to go back to /boot so I don’t really understand how exactly I’m supposed to do it.

      • f00f/eris@startrek.website
        link
        fedilink
        English
        arrow-up
        1
        ·
        25 days ago

        I’ve honestly never wrestled with Secure Boot in this way; I usually disable it if it won’t let me boot my preferred kernel. From my brief online searches, enrolling your own keys is possible, but that depends on the kernel modules being signed in the first place, and carries risk of bricking devices if not done correctly. So you might just want to disable Secure Boot, or otherwise stick to kernels provided by your distribution.

      • BoyetLeonantus@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        25 days ago

        https://www.dannyvanheumen.nl/post/secure-boot-linux-shim-mokmanager/ seems to be a good introduction to the concept. Your distribution should have specific documentation on how to make custom kernels and secure boot work if you need more details.

        If you have already made a certificate and imported it with mokutil maybe you just need to select the MokManager.efi from your screenshot and start that to enroll the key.

  • kewjo@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    25 days ago

    generally you need to put your bios into secure boot “setup mode”, this changes based on bios but generally requires wiping any keys already enrolled. once you are in setup mode you can boot into your install. depending on your distro you can then sign your kernel+modules and update the tpm. arch wiki has a good guide. also beware each time you update your kernel you need to resign kernel and modules otherwise you won’t be able to boot

  • TheCheddarCheese@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    26 days ago

    Update: The file selection seems to begin at /boot/efi/ while the kernel is located in /boot/. Don’t know the reason for this.