@juliank Does that mean it works as designed? So, do I just need to wait
until the live distros release new images with an updated bootloader?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Tit
@Markus You can only boot very recent media that have been signed post-
BootHole, given that the dbx update was applied in Ubuntu 20.04 (which
LM20 is based), which revoked any older bootloader.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug is now two years old but I stumbled just recently over it. I'd
like to add my story about that bug of the missing "mmx64.efi" file.
I am running a custom built PC based on an ASUS Z97-A/USB 3.1 mainboard.
Shortly after the COVID-19 era started (earlier this year), I made a
fresh dual boot
I got this error:
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
I have an HP Pavilion g6 Notebook PC. It was working fine the other
had the same error with Clear Linux:
Failed to open \EFI\org.clearlinux\mmx64.efi - Not Found
Failed to load image \EFI\org.clearlinux\mmx64.efi - Not Found
Failed to start MokManager: Not Found
Something has gone seriously wrong: import_mok_state() failed
: Not Found
doing this from #51:
# chat
I'm also booting from the daily image, and on a fresh install from UEFI i'm
getting a boot message of "missingFailed to load image \EFI\BOOT\mmx64.efi -
Not Found
Failed to start MokManager: Not Found
Something has gone seriously wrong: import_mok_state() failed "
I did a lvm encrypted boot, with
Note - On an install last night from eoan livecd, i had the inverse
problem. I had to copy the mxx64.efi to grubx64.efi in order to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
Hello--
thank you to all those who took time to comment and provide strategies to this
problem.
I'd like to thank several of the posters here, poster #57's idea solved
the prolem for me.
#I was trying to install 18.04 LTS through USB;
#there was a previous install, and I wanted to keep the files
Would it be possible to backport the fix from 19.04 to 18.04 LTS? The
bug is quite difficult to work around, and easy to trigger - just abort
the setup some time after checking the third-party-drivers box.
For anyone who still needs a workaround for 18.04, because you for some reason
don't want
This bug was fixed in the package debian-installer - 20101020ubuntu567
---
debian-installer (20101020ubuntu567) disco; urgency=medium
* build/util/efi-image: make MokManager available in EFI images.
(LP: #1798171)
-- Mathieu Trudel-Lapierre Wed, 20 Mar 2019
15:57:02 -0400
*
** Changed in: debian-installer (Ubuntu)
Status: New => Fix Committed
** Changed in: debian-installer (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Also affects: debian-installer (Ubuntu Disco)
Importance: High
Assignee: Mathieu Trudel-Lapierre (cyp
** Changed in: debian-installer (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To m
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - No
** Branch linked: lp:~ubuntu-core-dev/debian-installer/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To manage notifi
Disabling Secure Boot temporarily in order to finish the installation
(mmx64.efi is supposed to be installed on disk at the end of the
install), or editing an installation image on USB to copy
grubx64.efi in a new file called mmx64.efi
Should be good workarounds for this.
Please don't run a sy
** Changed in: grub2 (Ubuntu)
Assignee: Miguel Alcaide (migalc) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not
Additional Information:
system-rescue-cd was able to boot in EFI mode. Other ubuntu/debian based
usb sticks either could not be enumerated; or failed with the previously
mentioned error. Once I was able to boot up into EFI mode it was a
simple fix thanks to Panu.
An observation:
The Secure Boot
I can confirm this issue impacts the current ISO for the 18.04.2 LTS
release.
Impacted installation was on a Dell Inspiron 3668 with firmware version
1.3.4.
Ubuntu LiveUSB has the above error and is unable to boot after a failed
installation with the Secure Boot configuration checked in the
insta
That worked Thanks!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To manage notifications about this bug go to:
https:/
I was able to solve this with the information from comment #25.
I booted my system with a separate system rescue CD stick (see
http://www.system-rescue-cd.org/). Then, in rootshell, I did:
# chattr -i /sys/firmware/efi/efivars/Mok*
# rm /sys/firmware/efi/efivars/Mok*
After this, the Ubuntu inst
Yea, i'm stuck stuck on my Lenovo P1 just like #45, even after copying
over.
/EFI/BOOT/grubx64.efi to /EFI/BOOT/mmx64.efi
This time the Lenovo Logo doesn't disappear and I don't have those
errors but it's just sitting there and the grub doesn't show up. I tried
setting the Video to Discrete and H
Same error message as reported above.
Ubuntu Studio 18.10 - Lenovo M700, Windows 10 Pro
1) Created installation USB with Rufus
2) Open installation USB with W10 File Explorer
3) Navigate to /EFI/BOOT/grubx64.efi
4) Right click file grubx64.efi
5) Rename file to mmx64.efi
6) Proceed with Ubuntu
Comment #47 seems to have worked for me as well :), though step 1 is
varied
1. Created Ubuntu 18.10 installation USB with Dell Media Creation
Utility Tool
steps 2 and 3 the same
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Ubuntu 18.10 - Lenovo IdeaPad 700-15
It's working for me ):
1. Create installation USB with Unetbootin.
2. Copy /EFI/BOOT/grubx64.efi to /EFI/BOOT/mmx64.efi
3. Boot with UEFI and install...
:-) Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
It looks like the Ubuntu default installation ISOs (18.10 and 18.04.1)
from Ubuntu.com are still missing /EFI/BOOT/mmx64.efi. Getting the same
error on Asus Sabertooth S170 Mark 1 motherboard on fresh install.
Can’t install Ubuntu due to missing mmx64.efi error.
--
You received this bug notificat
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
Same issue on an ASUS ROG G751-VT.
Installation media made with Rufus v3.4.
ISO downloaded 2019-01-15
Only difference for me was, the graphical install hung right after I setup
secure boot password and then tried to proceed to the next screen. I assumed it
was related to that when I saw the error
I think I got a download this way, thank you.
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Miguel Alcaide (migalc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
Syste
Exactly the same problem here as ScarySquirrel described above.
A new X1 carbon, updated windows 10.
Was able to boot from a live USB once. Decided to restart laptop to install
Ubuntu later.
```Failed to open \EFI\BOOT\mmx64.efi - Not Found
Failed to load image \EFI\BOOT\mmx64.efi - Not Found
Fail
// , Just downloaded the latest Ubuntu (18.10), and created an image
with the Ubuntu Startup Disk Creator for it.
The first time I ran the disk on my laptop, I was able to start up
Ubuntu.
The second time I ran this bootdisk, though, I had no luck.
The only difference between the first and the s
Hi, yes i've tried with unetbootin and there was the same problem. Akeo
(b-pete-r)
The iso image don't have the mmx64.efi file and i don't know if that should be
auto generated on install or not.
For example, i've have no problem with Rufus and Unetbootin with the ubuntu
18.08.1.. so i thik is t
Update:
I copied mmx64.efi from /efi/boot on my hard drive to the same location in the
iso.
I now receive the below warning and system attempts to bootloop forever:
System BootOrder not found. Initializing defaults.
Creating Boot entry "Boot0002" with label "ubuntu" for file
"\EFI\ubuntu\shim64
Rufus developer here. I am indeed seeing sporadic reports from users
running into the bug above after they created installation media from
the Ubuntu ISO (NB: For most UEFI bootable media generation, what Rufus
does is simply copy the ISO content to a FAT32 file system on the USB),
and the root of
After weeks of searching like Ondrej, the problem was that in the bootable USB
dint't exist the file mmx64.efi so the workaround was to copy de existing file
grubx64.efi and rename to mmx64.efi in the bootable USB drive (so USB Drive
folder /EFI/BOOT now i have three files BOOTx64.EFI, grubx64.
Ondrej Was there already a file named mmx64.efi in the /EFI/BOOT/ folder?
This seems strange as I already have a file by that name so I don't want to
write over it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Ondrej would you be able to step me through this. I am a novice and want
to make sure I do not mess anything up. Thx!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boo
Finally, I managed to find workaround. I had made a copy of
/EFI/BOOT/grubx64.efi with the name mmx64.efi on the bootable medium.
After this, the USB disc was able to boot again and I was able to
continue with installation process. After successful instalation
wverything was OK.
--
You received t
Forgot to mention hardware = Intel NUC Kit NUC8i7HVK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To manage notifications
Same problem: Initial boot from Ubuntu 18.10 USB worked but the
installation crashed while I was inputting information (black screen).
Was then able to boot from Windows 10 USB stick and install. Windows
works fine. But still not able to boot from Ubuntu USB with message:
Failed to open \EFI\BOOT\
Exactly same problem like #25. I found MokAuth and MokNew in efivars,
but was unable to remove them. Other distros are able to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
Syst
Hello
I have been having the issue described by Jean in the original description.
Same exact error message when trying to boot Ubuntu 18.04, seems like Grub
isn't being installed correctly.
This issue is new after a Windows update and I wasn't being given the option to
boot into Linux.
I reinsta
ubuntu-18.10-desktop-amd64.iso to be exact.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To manage notifications about this
I don't have Ubuntu installed. The incomplete installation is what put
me in this situation to begin with.
I use a fresh Ubuntu 18.10 ISO I just downloaded today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
If you are seeing this issue, what image are you using? Have you tried
booting to Ubuntu without the ISO connected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot
I appear to have the same issue as described by comment #24/#25.
The installer didn't crash on me though. I also typed in a password and
continued, but it didn't crash on me. I aborted the installation when
picking where to install to due to needing to change settings in my BIOS
for Ubuntu to be a
I've been helping a user on IRC #ubuntu reporting this problem using the
18.10 ISO installer. In this case during the (first) installer run the
PC crashed and rebooted before completing the install.
>From then on trying to boot the installer is failing with these error
messages:
Failed to open \E
Hello, I have the same problem with my Ace aspire A515-51G, when
starting by USB it can not load the mmx64.efi file. As additional
information, the problem occurred in the installation, when the
installer asked me to enter a password for UEFI. The system was stuck a
few moments and then it was rest
Here the same issue. I try to do a fresh install of Ubuntu 18.10
After stopping the isnstallation and rebooting from a 18.10 bootable USB-stick:
ailed 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 go
I am facing the same problem now with Ubuntu 18.10. I entered the live
environment once after creating the bootable USB disk, then after a
reboot, it shows the error message as described as above. Is this a bug
or is there something wrong with my system?
--
You received this bug notification beca
Now I have Ubuntu 18.10 installed.
Workaround is to use a working grub2 (for example booting up with Ubuntu
18.04 installation media) and move to grub command line. There I created
a new menuentry for loading Ubuntu 18.10 installer from another USB
stick.
https://askubuntu.com/questions/436519/bo
Even though Ubuntu 18.04 installation USB stick works fine, I see same
kind of mmx64.efi error flashing quickly. However it does not halt there
unlike in Ubuntu 18.10 installation media.
The error I see when booting up with Ubuntu 18.04 installation media:
Failed to open \EFI\BOOT\mmx64.efi - Not
However, using the same usb-creator-gtk (version 0.3.5) in Ubuntu 18.04,
I created an installation USB stick from Ubuntu 18.04. That works
without any problem in MSI laptop. There is no /EFI/BOOT/mmx64.efi file
either in that USB stick, but it works anyway.
The result is that I am not able to inst
I was about to install Ubuntu 18.10 into laptop (MSI GT62VR 7RE
Dominator Pro) using USB installation media. It was able to boot up and
start installation until the installation halted with a black screen.
After I rebooted I got the same error about missing mmx64.efi.
Windows 10 boots up fine with
This bug was fixed in the package grub2 - 2.02+dfsg1-5ubuntu8
---
grub2 (2.02+dfsg1-5ubuntu8) cosmic; urgency=medium
* debian/patches/grub-install-extra-removable.patch: install mmx64.efi to
the EFI removable path to avoid boot failures after install when certs
need to be en
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To ma
** Package changed: ubiquity (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To manage notification
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1798171
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Using an ACER Aspire v3-572G-70Q8, NVIDIA GEFORCE 840M
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To manage notifications
Sorry, I have a lot of old efi entries (OEM/WINDOWS)
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0050,0003,0002,0004,2001,2002,2003
Boot* ubuntu
HD(2,GPT,ea852bc6-160a-4d85-b643-54fefb672533,0x12c800,0x96000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* LINUXmint
PciRoot(0x0)
ls -altrR /boot/efi/
/boot/efi/:
total 12
drwx-- 3 root root 4096 Dec 31 1969 .
drwx-- 4 root root 4096 Oct 16 13:30 EFI
drwxr-xr-x 4 root root 4096 Oct 17 12:51 ..
/boot/efi/EFI:
total 16
drwx-- 3 root root 4096 Dec 31 1969 ..
drwx-- 2 root root 4096 Oct 16 13:30 BOOT
drwx-
> I cannot reproduce on any other machine, setting to incomplete for
now.
Please include in the bug description what machine this is happening on
(and firmware revision also, please).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Note from the subject line, mmx64 isn't missing, but the firmware is
looking for it in /BOOT/ while it lives in /ubuntu/ ... Not sure why
this is, however.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
This is the output on the Inspiron 11 with secure boot off
BootCurrent: 0013
Timeout: 0 seconds
BootOrder: ,0010,0011,0012,0013,0014,0015,0016,0017,0018,0019,001A,001B
Boot* ubuntu
HD(1,GPT,efb1a75e-ea53-471c-a21d-17bad475f131,0x800,0x10)/File(\EFI\ubuntu\shimx64.efi)
Boot0010
Clearly not a bug in mokutil if we're having issues with booting -- I'm
removing the task.
** No longer affects: mokutil (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System
I think we'll also need to see what's in /boot/efi in general:
sudo ls -latrR /boot/efi
There is absolutely no reason for mmx64.efi to be missing, ever -- it's
the indication of an incomplete install, or at the very least an issue
with the firmware of the system. We always install mmx64.efi.
--
@Pau, could you boot your system (with secure boot disable), then from a
terminal run the command in command #3:
sudo efibootmgr -v
and paste the output.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Also affects: mokutil (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mokutil (Ubuntu)
Importance: Undecided => Critical
** Changed in: mokutil (Ubuntu)
Status: New => Confirmed
** Tags added: rls-dd-incoming
--
You received this bug notification because you ar
I have the same problem, I updated some packages yesterday and I have to
run in NON-SECURE option in UEFI. I have the NVIDIA up to date (before I
could use the graphic card)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I cannot reproduce on any other machine, setting to incomplete for now.
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
installer logs from the affected system
** Attachment removed: "Casper.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1798171/+attachment/5201867/+files/Casper.txt
** Attachment removed: "UbiquitySyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1798171/+at
Can you please boot on a live CD and run "sudo efibootmgr -v"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To manage notif
** Attachment added: "DSC_0954.JPG"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1798171/+attachment/5201872/+files/DSC_0954.JPG
** Description changed:
- Cosmic desktop installation on UEFI system with secure boot enabled and
- third party drivers checked. On boot the system fails
72 matches
Mail list logo
