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.
Umm... thank you, but I'm not sure you understood my issue.
I ... can't.
I don't have any data that needs backing up. It's a new computer. I'm trying to install, but I can't boot off the live media.
Does the bios have an option to EFI boot from a USB? Sometimes there is a tiny file manager in the boot options that will allow you to boot from an EFI file off a USB key and not just by selecting a different boot option, the issue here seems to be that the firmware is trying to boot from a file that doesn't exist. The odd part is that it won't work from your USB because it seem to be trying to chain boot efi files that don't exist.
Are you sure your live media is good? Does it boot on another system?
This worked!!
Back into my live environment now.
I'll update my post once I've checked that there are no further problems.
Glad I could help, please leave an upvote on your way out :))