[Bug 1798171] Re: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

[Nexus]

The proposed workaround to create the mmx64.efi in /EFI/BOOT/ doesn't
work for me.

Does anybody know, which efi variable has been created by the installer,
that triggers the wrong boot process in the usb drive? In this case,
deleting or editing it, would be an option to try.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1798171

Title:
  System fails to boot with \EFI\BOOT\mmx64.efi - Not Found

Status in grub2 package in Ubuntu:
  Fix Released

Bug description:
  System: Dell Inspiron 11 3137 - BIOS A05 Phoenix SecureCore Technology

  Cosmic desktop installation on UEFI system with secure boot enabled,
  third party drivers checked, installation on entire disk.

  On boot the system fails with:

  Failed to open \EFI\BOOT\mmx64.efi - Not Found
  Failed to load image \EFI\BOOT\mmx64.efi - Not Found
  Failed to start MokManager: Not Found
  Something has gone seriously wrong: import_mok_state() failed
  : Not Found

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Tue Oct 16 19:26:56 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper --
  InstallationDate: Installed on 2013-09-03 (1868 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   LANG=C.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to cosmic on 2018-01-26 (263 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1798171/+subscriptions