beta4 TC0 x86_64 freezing on boot on my desktop

[Carl_Miller]

I can't even attempt to boot beta4 TC0 x86_64 on my custom-built Ryzen desktop (specs at end of post). Whenever I do, the text mode boot menu comes up, with the “Continue booting” option grayed out, owing to a lack of bootables visible to it.

I've tried each of the following to get the installer to boot, with no success:

• Using a USB 3.0 flash drive
• Using a USB 2.0 flash drive
• Plugging the flash drive into a USB 3.0 port
• Plugging the flash drive into a USB 2.0 port
• Putting the flash drive at the top of the boot order
• Enabling CSM in the desktop's firmware

Specs:

• CPU: AMD Ryzen 5 5600X @ 3.7 GHz×6
• Motherboard: MSI B550-A PRO
• Memory: 2 × 8 GB G.Skill Ripjaws V DDR4-3200 CL16 SDRAM
• SSD 1: Western Digital Blue SN550 1 TB M.2 NVMe, hosting Garuda Linux
• SSD 2: Kingston 480 GB SATA, hosting Windows 10
• GPU: MSI Radeon RX 570 w/ 4 GB VRAM

[waddlesplash]

The first icon failing to light means the bootloader handoff into the kernel has not occurred (or failed) for some reason, so this is not a USB problem (or if it is, it's the BIOS' fault.)

Are you booting using EFI? Can you try to force EFI, if possible?

[Carl_Miller]

I was booting using legacy boot; attempting to force UEFI boot causes the live USB's bootloader to complain that the boot volume is invalid, as it can't find any bootable volume. This behavior also occurs when attempting to boot the beta4 TC0 ISO in VirtualBox with EFI enabled; leaving EFI disabled, the ISO lights all seven boot icons, but does not progress into a GUI.

[Carl_Miller]

I should also note that the invalid boot volume behavior seems to occur with any live USB flashed from within Windows or Linux; one flashed from within Haiku on one of my laptops has the behavior exhibited in the ticket.

[Carl_Miller]

I was mistaken in my past comments and the ticket body. It's a beta3 live USB that wouldn't light any icons, which was fixed by enabling CSM in my desktop's firmware (though it's necessary to enable fail-safe graphics mode, else my monitor throws “out of range”). beta4 live USBs continue to exhibit the invalid boot volume issue.

[Carl_Miller]

Nor do I get much further with the latest nightly (hrev56627); The disk icon is the last to light up, and then I get this error: ​https://media.discordapp.net/attachments/988928314666258485/1048956625165238342/IMG_2266.jpg

[Carl_Miller]

No longer an issue; was able to upgrade to beta4 using pkgman, though I have to manually select the boot volume every time (booting via EFI).

[waddlesplash]

I'm going to set this as "no change required" because I suspect it may not necessarily be fixed, but might be related to the other ticket about lag that you opened.