No bootable drive detection logic

Hi,

What is the logic for “no bootable hard drive detection” by UEFI?

The issue: I screwed up creating an UKI kernel image, which was missing most things, and when trying to boot the machine, it failed, rebooted itself into the “no bootable drive” QR code screen, and refused to see systemd-boot EFI executable until hard power off.

I now fixed my UKI generation, but this feels weird.

note : it might also be linked systemd-boot which apparently has no timeout.

Which Linux distro are you using? Gentoo (probably irrelevant)

Which kernel are you using? 6.16.3 (Probably irrelevant)

Which BIOS version are you using? 3.04

Which Framework Laptop 13 model are you using? AMD Ryzen™ AI 300

Hi @serafean If you’re still having this issue, please give our support team a shout here.

Well, I can still reproduce the behaviour with the bad kernel image, but I can boot fine since I fixed my UKI generation.

So this was more of a question to get someone in the know of this area to chime in.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.