this post was submitted on 06 Jun 2024
1 points (100.0% liked)

Framework Laptop Community

2635 readers
1 users here now

Related links:

Related communities:

founded 3 years ago
MODERATORS
[email protected]
[email protected]
1
[SOLVED] Framework laptop 16 won't boot at all after failed Linux Mint install (i.ibb.co)
submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]
21 comments fedilink hide all child comments
 

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.

top 21 comments
sorted by: hot top controversial new old
[–] [email protected] 0 points 5 months ago (1 children)

Upvoted because you came back to put in the solution

[–] [email protected] 0 points 5 months ago

Thank you.

[–] [email protected] 0 points 5 months ago

I had pretty much the same problem on a ThinkPad T490 after a borked Mint install. It tells the EFI to boot into MOK Manager but doesn't provide it under the path (mmx64.efi).

I don't 100 % remember what I did to fix it but I think I booted into an EFI Shell and wiped boot entries off the NVRAM. Resetting the BIOS should do that, but this may vary by manufacturer.

[–] [email protected] 0 points 5 months ago (1 children)

maybe go to the boot manager and explicitly boot from the usb drive? seems like your uefi has an entry for which no file was found because your install failed?

[–] [email protected] 0 points 5 months ago

Already tried that.

It's definitely trying to boot off the USB. There's nothing else for it to boot from.

[–] [email protected] 0 points 5 months ago

I am 1st time linux user I wanted to install mint from usb. At first it worked then when i tried to install it, I could not because of bitlocker. I then rebooted but windows already activated bitlocker, and afterwards any usb boot would show the exact same error message you have. I ultimately had to wipe my encrypted partition of win and installed Ubuntu instead. I am happy for now, learning to use linux with Ubuntu and maybe try mint or arch when more advanced. Maybe that helps you in some way best of luck.

[–] [email protected] 0 points 5 months ago* (last edited 5 months ago) (1 children)

Kinda sounds like the bootloader didn't install or the boot partition got mangled.

If there isn't anything of value you could just reinstall, would make sense to use fresh media and use the built in verification before installation.

If you need the data back, use a valid live cd to copy it off the system first.

Edit: consider a page file over a swap partition as it can be adjusted on the fly without a reboot. I work with VMs a lot and having a page file has been very helpful when I need a little boost or want to slim down.

[–] [email protected] 0 points 5 months ago (1 children)

Umm... thank you, but I'm not sure you understood my issue.

If there isn’t anything of value you could just reinstall

use a valid live cd

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.

[–] [email protected] 0 points 5 months ago (1 children)

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?

[–] [email protected] 0 points 5 months ago (1 children)

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,

This worked!!

Back into my live environment now.

I'll update my post once I've checked that there are no further problems.

[–] [email protected] 0 points 5 months ago

Glad I could help, please leave an upvote on your way out :))

[–] [email protected] 0 points 5 months ago (1 children)

Here is a thread with your exact issue: https://forums.linuxmint.com/viewtopic.php?t=412942

[–] [email protected] 0 points 5 months ago (1 children)

Thank you.

This looks very promising. It doesn't seem to let me write to my live usb though. It just says "Read-only file system" (even when using sudo).

[–] [email protected] 0 points 5 months ago (1 children)

Are you booted off the USB? That won't work, they usually have a ram drive overlay. You'll have to boot from another OS and mount the USB to edit the files.

If it still comes up read-only trying searching some solutions for mounting in read/write. You might have to recreate the ISO USB and edit the files before first booting off it. Maybe there is a resize script to use the full disk on first boot that does some funky stuff or something.

https://unix.stackexchange.com/questions/13225/how-do-i-remove-a-read-only-file-system-from-a-usb-drive https://askubuntu.com/questions/910585/remove-read-only-partition-from-usb

[–] [email protected] 0 points 5 months ago* (last edited 5 months ago)

Are you booted off the USB?

No. I plugged it into my current laptop that already has Linux Mint installed.

If it still comes up read-only trying searching some solutions for mounting in read/write. You might have to recreate the ISO USB and edit the files before first booting off it. Maybe there is a resize script to use the full disk on first boot that does some funky stuff or something.

Thanks. I'll look into it. ... edit: not having much luck so far.

[–] [email protected] 0 points 5 months ago (1 children)

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.

[–] [email protected] 0 points 5 months ago (1 children)

Thanks.

I've updated my post to add a transcription to the body.

hit whatever key is needed to bring up the boot drive selection menu to pick the installer USB.

It's already the only option there. I just got the same error.

I'm pretty sure the issue is with secure boot.

[–] [email protected] 0 points 5 months ago

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.

[–] [email protected] 0 points 5 months ago (1 children)

I'm not able to help, but That text is really hard to read, can you either type it out or give a much better picture?

[–] [email protected] 0 points 5 months ago

Sorry. The hosting site may have reduced the quality. I've added a transcription to the post.

[–] [email protected] 0 points 5 months ago

The error shown in the image is unreadable. Can you take a pic of it specifically?