Description of problem: Fedora 36 iso images 'burned' on USB boot fine on this computer. However, the Fedora 37 beta images lead to a 'no boot device found' message. They do boot if are actually burned to CDROM. On the same system , for the record, also Debian 11 hybrid images boot fine from USB. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Some more research i've done today: - after installing Fedora 36 the USB sticks boot again . - Next i started to install Debian 11 (to compare Fedora and Debian resource usage.) Then Debian installer said something interesting: "another OS is installed in BIOS compatibility mode. Do you wanna force UEFI mode for our installer?". I've answered yes, D11 was installed and booting and then, trying to install F37beta, selecting 'Kingmax' in the F10 boot menu lead to "NO BOOT DEVICE" message. Selecting, however "Internal EFI - hard disk", booted the F37beta USB stick. After installing F37b, both Debian and Fedora are in the GRUB menu. In this state, booting from Fedora 37b stick, using first 'Internal EFI shell -hard drive' menu option gives the expected USB stick GRUB shell. Using the 'Kingmax' line gives again 'No boot device'. So the EFI boot works, the BIOS boot does not. For Debian 11 USB stick, both options give the expected installer GRUB menu. More than this, the Debian installer boot menu says : BIOS or UEFI, depending on which option we choose in the computer F10 boot menu. At the very least we should says which installer/mode is invoked.
I've disabled UEFI boot then tried to boot F37b. Again, i got "No boot device". It seems that the presence of EFI entries breaks the capability to boot in BIOS mode. At least that's my understanding at this point.
The Lorax tool generates the installation images. Reassigning.
What hardware is this? Also see bug #2140385 for a similar repo. The F37 iso now uses GRUB for both BIOS and UEFI instead of syslinux for BIOS and GRUB for UEFI like F36 did. If the actual boot entries are causing problems then that sounds like a firmware issue, not a problem with the iso. Although there could be issue with both.
It's a HP DC 7800 built probably around 2010.
*** This bug has been marked as a duplicate of bug 2140385 ***