start_image returned Unsupported in v3.4
ventoy opened this issue · 5 comments
Many Ventoy users report that with
Super-UEFIinSecureBoot-Disk v3.4, it report error when Secure BOOT is disabled in the BIOS. With v3.3 it was OK.
ventoy/Ventoy#1707
@ValdikSS shim is updated.
Do you plan to update your SUPER-UEFIinsecureboot-disk?
I don't know if it is related to Super-UEFIinSecureBoot-Disk or not, but I am having the same issues with Ventoy (including the new 1.0.82) and the Fedora 37 live CD flashed to a USB drive with Balena Etcher. On most systems, especially newer ones, it works great. On older ones I get a lot of problems, though.
MSI Z97A Krait Edition motherboard in custom build PC (BIOS version 2.0 and latest 2.3) with Secure Boot disabled
Invalid image
Failed to read header: Unsupported
Failed to load image: Unsupported
start_image() returned Unsupported
then it reboots
Dell Latitude 7490 laptop (latest BIOS) with secure boot enabled
Failed to open \EFI\BOOT\∎ - Invalid Parameter
Failed to load image ∎∎: Invalid Parameter
start_image() returned Invalid Parameter, falling back to default loader
but then Fedora continues to grub and works anyway, but Ventoy reboots
So there seems to be some incompatibility upstream from Fedora. I have found that if I take the mmx64.efi and BOOTX64.EFI files from either Parted Magic or Ubuntu 22.04 and replace Ventoy's versions, it has worked on every system I have tried so far. IIRC Parted Magic is based on Slackware Linux.
https://ask.fedoraproject.org/t/f37-invalid-image-error-while-booting/26632/6
Also posted there where someone else is having the same issue with Fedora 37
Do you plan to update your SUPER-UEFIinsecureboot-disk?
Please keep in mind that this project is just a proof-of-concept, a showcase.
As far as I'm aware, Ventoy is the only project which included SUISBD files, and now the developer updates shim executables, which are the reason for the issues, by themself, that's why there's no reason for me to update this project.