I assembled my new Framework laptop 16 yesterday and tested it out with a live Linux Mint environment.
Today I tried to install Linux Mint to a storage expansion card. During the instillation, I had to create a secure boot password for the codecs. When partitioning, I made a 32GB Swap and had the rest of the storage as root. During the instillation, there was a fatal error. I tried unmounting the partitions on the card to create a new table to try again (using fdisk). This also gave an error, so I decided to reboot.
When rebooting, the error shown in the image was displayed and then the computer is powered off. Trying to turn it on without the live USB inserted goes to bios. I tried re imaging the USB, but the Framework still displays the same error. I tried disabling secure boot; same result. I tried factory resetting secure boot; same result. I tried booting without the expansion card; same result.
Transcription:
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
The "#"s are completely solid (or possibly checked) characters.
I tried creating a debian USB, but using that gave the same error.
I'm unsure what I should do. Any help would be great. Thank you in advance!
Solution: Go into the BIOS with the USB inserted and locate the boot from file option, then navigate the usb to find the grub efi file and use it to boot.
I can kind of make out "Not Found" as the last words on every line with efi on the first line.
I don't have a framework so don't know the ins and out but my guess here is you need to hit whatever key is needed to bring up the boot drive selection menu to pick the installer USB.
You could also check that USB is towards the top in the BIOS settings if you want to change the default boot priority.
I don't know if CMOS battery resetting is still a thing; I haven't done it in a decade. That is another thought if some bad state (e.g., secure boot) is still getting held by the mobo chipset. I'd confirm with some documentation or Framework support first though. I've never done it on a secure boot system.
Thanks.
I've updated my post to add a transcription to the body.
It's already the only option there. I just got the same error.
I'm pretty sure the issue is with secure boot.
Check my other reply. Looks like your options are to rename a file or two, or change some BIOS/EFI settings to look for a different boot file (if available), or CMOS reset to clear nvram.