Why does debian 10 try to access mmx64.efi with Secure Boot enabled when no such file exists
by Ulysses_ from LinuxQuestions.org on (#4Y9QP)
Tried to boot debian live from a USB flash drive that was made with Rufus. It produced this error:
Code:Failed to open /EFI/BOOT/mmx64.efi - Not foundTried to copy /EFI/boot/grubx64 to mmx64.efi in the same directory and it showed a grub menu but when you chose anything it produced this error:
Code:Error /live/vmlinuz-4.19.0-6-amd64 has invalid signature
Error you need to load the kernel firstTried to install shim-signed with apt in a VM booting from the debian live ISO image in order to get a mmx64.efi and copy it to the USB flash drive. It produced this error:
Code:Verification failed (0x1A) security violationWhy on earth would they make debian so hard to start with Secure Boot enabled?
Code:Failed to open /EFI/BOOT/mmx64.efi - Not foundTried to copy /EFI/boot/grubx64 to mmx64.efi in the same directory and it showed a grub menu but when you chose anything it produced this error:
Code:Error /live/vmlinuz-4.19.0-6-amd64 has invalid signature
Error you need to load the kernel firstTried to install shim-signed with apt in a VM booting from the debian live ISO image in order to get a mmx64.efi and copy it to the USB flash drive. It produced this error:
Code:Verification failed (0x1A) security violationWhy on earth would they make debian so hard to start with Secure Boot enabled?