Created attachment 1922475 [details] lspci -v output Created attachment 1922475 [details] lspci -v output Tested with Fedora-Workstation-Live-x86_64-37_Beta-1.5.iso. Using Fedora Media Writer to write ISO w/ verified CHECKSUM to USB stick. Upon booting the USB, "GRUB Loading. Welcome to GRUB!" appears on a black screen, but nothing else happens. System: HP Pavilion dv7-6178us Intel(R) Core(TM) i7-2630QM BIOS only, no UEFI. Very few config options in the BIOS. (Although dmidecode reports "UEFI is supported" by the motherboard, it seems HP only shipped BIOS updates for these older pre-2012 models)
Created attachment 1922476 [details] dmidecode output
Are you running the latest firmware update available for the system?
It's possible that the BIOS's 'UEFI supported' is confusing grub. Do you get a grub shell at all? Also, just for completeness, I'd try using dd to write the USB stick. You shouldn't need to use media writer.
(In reply to Adam Williamson from comment #2) > Are you running the latest firmware update available for the system? Unfortunately yes, Version F.1B (10/05/2011) is the latest BIOS. (In reply to Brian Lane from comment #3) > It's possible that the BIOS's 'UEFI supported' is confusing grub. Do you get > a grub shell at all? No grub shell, only a blinking cursor after the "Welcome to GRUB!" message, and the system seems unresponsive, e.g. Ctrl-Alt-Del doesn't work and I have to hard reboot. > Also, just for completeness, I'd try using dd to write the USB stick. You > shouldn't need to use media writer. I ended up installing fresh F36 and then doing a system upgrade to F37 beta. But I'm happy to continue troubleshooting/testing anything to resolve this issue. Writing the ISO image with dd resulted in the same behavior.
One difference I noticed is the USB drive is GPT for F37, but MBR for F36 and earlier. My system drive is also MBR.
(In reply to Ben Brian from comment #5) > One difference I noticed is the USB drive is GPT for F37, but MBR for F36 > and earlier. My system drive is also MBR. It's actually both, we still make a hybrid iso, but it is now created using grub2 code instead of syslinux.
It seems GPT on ISO image makes some systems unhappy with legacy boot. Taking the very same content but building it with xorriso with -append_part_as_gpt omitted fixes the issue. So, it's about GPT, not isolinux->grub change. This has been identified to be an issue at least on Thinkpad P52 and HP EliteBook 840 G4. I wouldn't be surprised if some other systems are affected too. I found this out by Qubes OS users testing development builds that use Fedora 37 as dom0. But I have verified it using Fedora Live image too, just to be sure. Fedora-Workstation-Live-x86_64-38-20230222.n.0.iso is affected too. I also checked with plain setup of partition table + grub2-install. With MBR partitions, I get grub prompt, with GPT (including "BIOS boot" partition), system doesn't recognize it as bootable (resets instantly). I _guess_ BIOS there is making some extra assumptions based on GPT presence. On one affected system, I tested also installation from MBR-based installation image (but only with Qubes this time) and the resulting system did not boot due to the very same change - GPT on the disk. I'm not sure what is the right way for Fedora to follow here (as I've seen voices to abandon legacy boot support completely), but for Qubes I'm strongly considering reverting the whole "GPT on BIOS"[1] change. [1] https://www.fedoraproject.org/wiki/Changes/GPTforBIOSbyDefault
*** Bug 2140199 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.