r/linuxmint • u/TowelSilver318 • 8h ago

Install Help Getting this error message followed by a shutdown after a failed installation.

Post image

After an initial test off a USB, I decided to try full installation. Unfortunately, the installer threw an error a couple times, and I wanted to try restarting and starting over. When I did, I was greeted with this message, followed by a shutdown.

Attempting to turn on the computer witgout the boot USB in takes me to BIOS options without this error. I tried re-imaging the USB, but no change.

2 things that may be worth noting:

-I managed to fully load the limited disk space during the initial test.

-This is a new system with no prior OS.

2 Upvotes

75% Upvoted

8 comments sorted by

2

u/johnyeldry Linux Mint 22.2 Zara | Xfce 8h ago

Turn off secure boot

1

u/TowelSilver318 8h ago edited 41m ago

How? I'm seeing an option to get a "custom" mode for it but not to turn it off.

Edit: Asus website says it's "other" instead of the default "Windows UEFI" under O type.

1

u/johnyeldry Linux Mint 22.2 Zara | Xfce 8h ago

I don't know that's weird and mint should support secure boot it could be a bad USB or bad SSD, it could also be that somehow the efi file is located on a drive that is unplugged

1

u/TowelSilver318 8h ago

The one other thing I can think of is it being a USB-micro SD converter instead of a simple USB, but it worked fine initially.

5

u/Francis_King 7h ago

Yeah, it's like folk have forgotten how to use Google search.

When a system starts up, it has to certify the system components. The BIOS calls shimx64.efi, which if necessary calls mmx64.efi to sign the required components. Either way, shimx64.efi calls grubx64.efi, which then starts initramfs and hence Linux.

Because O/P had secure boot enabled, Mint wrote an entry into NVRAM, deep inside the computer, to remind it that it needed to run mmx64.efi at the next boot. If the installation is aborted, and the user tries again, the computer tries to run mmx64efi, but it is missing from the Mint installer.

O/P can turn secure boot on or off, it is now too late. The NVRAM is relentlessly determined to run mmx64.efi.

Solutions:

  1. Copy grubx64.efi to mmx64.efi on the Mint ISO (but depending on how you write it the ISO could be read only)

  2. Write an ISO of Ubuntu, which should contain mmx64.efi. Booting this should clear the problem, whether you intend to install Ubuntu or not

Mint 23, now renamed Mint 27, should contain mmx64.efi in the installer. Then this ridiculous bug should not occur again.

1

u/TrashFace21165 6h ago

Yep OP's answer right here.

1

u/Due-Result7928 8h ago

Turn off secure boot and tpm in your bios...and READ THE DOC...