Linux Mint 22

I had an odd and frustrating experience when trying to install Linux Mint, and I’m going to cover the sequence of events, and the steps I took to remediate it.

Which Linux distro are you using? Mint

Which release version? 22.2

Which kernel are you using? N/A

Which BIOS version are you using? LFSP0.03.2

Which Framework Desktop model are you using? AMD Ryzen™ AI Max 300 Series

I was able to boot the Linux Mint installer once, but as soon as it got to the option to install codecs and third party drivers it failed with an error. I did not write the error down, and opted to try again.

However, it would no longer boot.

Instead, every time I try to boot any Mint install drive I get the following message:

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

I tried disabling secureboot, factory resetting secureboot, clearing the CMOS, trying different thumb drives, trying different versions of the Mint ISO, trying both Rufus in various modes and Balena, etc…

At that point I attempted to install Ubuntu, which worked flawlessly.

As I don’t much care for Ubuntu I resumed attempting to install Mint, and was immediately successful at both booting from the Mint thumb drive and installing Mint.

My issue is now resolved, but I would like to know if anybody has any idea what happened here.

It seems MOK (part of secure boot) will be triggered if you opt to install extra codecs during installation of Mint. This is normally fine, but something went wrong & it didn’t finish.

Secure boot has been known to cause problems. It’s a microsoft thing that they never attempted to make user-friendly, nor play well with others. I always kill secure boot.

1 Like

Why would Microsoft fix something when it being broken in a way that makes things worse for everybody else is something that makes their offerings less unappealing?