PDA

View Full Version : [ubuntu] 18.04.1 No grub, you're looking for the wrong efi file!!!



AscottW
March 17th, 2019, 08:55 AM
I DO NOT HAVE DUAL BOOT ON MY MACHINE AT THIS TIME.

I only emphasize that because a LOT of the fixes I looked at dealt with dual boot only. Wanted to make that clear from the get-go. I also want to make clear that I have done over 15 hours of work over the past week or so to try and get this fixed. It is becoming quite...bothersome to say the least. Which is why I'm posting about my specific problem because either I am not following something correctly or the other similar posts are just different enough so as to render their fixes unusable for me.

The long-and-short of it: My laptop has a freshly installed Ubuntu 18.04.1 OS on the only hard disk available. There are currently no other operating systems installed. I am currently using a linux live USB to even write this.

Upon boot, grub is telling me it's looking for mmx64.efi. However, terminal is telling me I have shimx64.efi. How to do I tell grub that it's looking for the wrong thing so it's stops failing to load and failing to run a file that doesn't exist in my boot folder?

What didn't work:
Boot-Repair
Turning secure-boot off (and then on again...and then back off)
CSM/legacy boot (which is obvious to me now since I learned how to find the bootloader details and know I'm squarely on UEFI)
Wiping and reinstalling Ubuntu (several times over.)
Selecting LVM/not selecting LVM
Manually partitioning my drive
The dozens and dozens of forum posts and help articles I read written by rockstars trying to help others.

Thank you for any and all help you may be able to give,
A very weary traveler

Tech Details:


Notebook
product: Satellite E55t-A (PSKPJU)
vendor: TOSHIBA
version: PSKPJU-01E023
serial: YD053116P
width: 64 bits
capabilities:
smbios-2.7 dmi-2.7 smp vsyscall32



Motherboard
product: ZEMAA
vendor: TOSHIBA
physical id: 0
version: 1.00
serial: *
slot: *

BIOS
vendor: TOSHIBA
physical id: 0
version: 1.50
date: 12/02/2013
size: 64KiB
capacity: 4032KiB
capabilities:
pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi

BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0002,0001,0003,0009
Boot0000* ubuntu HD(1,GPT,34d69a0f-b533-40c3-8dd2-fcb01b026e0c,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(201a06796044,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(201a06796044,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0003* UEFI: PNY USB 2.0 FD 1100 PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(2,0)/HD(1,MBR,0x663eb4c4,0x3906b4,0x1240)..BO
Boot0009* UEFI: PNY USB 2.0 FD 1100 PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(1,0)/HD(1,MBR,0x663eb4c4,0x3906b4,0x1240)..BO

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 1.8G 1 loop /rofs
loop1 7:1 0 86.9M 1 loop /snap/core/4917
loop2 7:2 0 34.7M 1 loop /snap/gtk-common-themes/319
loop3 7:3 0 140.9M 1 loop /snap/gnome-3-26-1604/70
loop4 7:4 0 2.3M 1 loop /snap/gnome-calculator/180
loop5 7:5 0 13M 1 loop /snap/gnome-characters/103
loop6 7:6 0 14.5M 1 loop /snap/gnome-logs/37
loop7 7:7 0 3.7M 1 loop /snap/gnome-system-monitor/51
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part
└─sda2 8:2 0 465.3G 0 part /target
sdb 8:16 1 15G 0 disk /cdrom
├─sdb1 8:17 1 1.8G 0 part
└─sdb2 8:18 1 2.3M 0 part

oldfred
March 17th, 2019, 03:18 PM
Several others have had the missing mmx64.efi issue.
Quick fix is to just copy grubx64.efi and rename it to mmx64.efi.
Full install will have a copy of mmx64.efi in both /EFI/Boot & /EFI/ubuntu folders in the ESP - efi system partition.

The mmx64.efi file is for management of keys. It used to be that you could not install proprietary drivers with UEFI Secure Boot on as Canonical cannot certify them. But a user can, if he believes they are valid. So the mmx file is to allow a user to add key if required. If UEFI Secure boot off, it should not be needed.
I do have Secure Boot off, but no proprietary drivers, but it still has mmx64.efi installed by default.

System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1798171
Supposedly fix recently released. But ISO is frozen, so it will not have any fixes until install updated. Those still with errors in bug report may just have other issues?