I have created an USB key with Mint, but when I boot from it I get a few lines of errors

  • Failed to open \EFI\BOOT\mmx64.efi - Not Found
  • Failed to load image ??: Not Found
  • Failed to start MokManager: Not Found
  • Something has gone seriously wrong: import_mok_state () failed: Not Found

I have tried disabling safe boot, and fast boot. I have confirmed that my system has UEFI.

I believe that I once managed to run Mint off the USB but have not managed to do so since

  • Skull giver@popplesburger.hilciferous.nl
    2·
    6 months ago

    It looks like Mint configured your system to load its secure boot keys into your computer, but didn’t place the files necessary to do so on the boot drive.

    If this is an installer drive, I’m very confused why Mint would try to load MOK Manager before installation. I can’t explain the problem in that case, so I wouldn’t know how to fix it. Perhaps a different installer image (an older one?) might help there.

    If you’ve installed Mint onto the flash drive, something went wrong setting up your bootloader. If your computer supports browsing to an EFI file to boot, you should try finding /EFI/BOOT/grub2/grub.efi (or something named similarly) to boot once. From there, you should find instructions for Mint to reinstall your bootloader. Hopefully it’ll be configured correctly once the bootloader is reinstalled.

    Another problem that may occur is that your motherboard is reordering drives between insertion. Your computer is currently configured to load EFI/BOOT/mmx64.efi from a specific EFI partition, but if your motherboard found another EFI partition (like, for example, one for a Windows install), it’ll get confused and fail to boot from the right place. If that’s the case, there’s not much you can do to fix the problem except for updating your motherboard’s firmware and keeping your fingers crossed. A workaround would be to copy the missing files and directories from your flash drive’s boot partition to your computer’s, making sure not to overwrite any files. This may require redoing after bootloader updates, but it would get the system booting again.

  • Kingofthezyx@lemm.ee
    2·
    6 months ago

    This just happened to me, once you make the bootable USB, open it up, go into EFI/boot, and copy grubx64.efi, then rename it to mmx64.efi

    Everything should work from there.

    • Skull giver@popplesburger.hilciferous.nl
      3·
      6 months ago

      mmx64 is the MOK manager. It’s a tool used to set up secure boot correctly so you can use secure boot with Linux. It’s supposed to run at least once for secure boot setup to get the basic keys loaded into the system.

      Putting grub in its place will boot Grub directly, but you just end up with a misconfigured boot setup that’ll only break when Grub eventually updates, or lacks Grub security updates since you copied rather than linked the bootloader.

      Your suggestion fixes the symptoms, but not the problem. The real solution will involve either installing the necessary tooling (like MOK Manager) correctly, or altering the UEFI boot configuration to load Grub rather than the MOK manager.

      The latter option may require secure boot to be disabled, though.

    • cosmicrookie@lemmy.worldOP
      1·
      6 months ago

      Yeah the bios did see the drives… I ended up installing Ubuntu instead. That seems to go well. Currently installing

  • hawgietonight@lemmy.world
    1·
    5 months ago

    I recall having the image not found error last time. A mix of creating the USB with another program and tinkering with bios solved the issue. Sorry can’t be more specific, but Linux is all about tinkering, so have fun :)