Bug #3167
closedUEFI boot hangs right after initializing UEFI framebuffer
0%
Description
This happens on a recent Tuxedo laptop. See attached screenshot.
I have come up with a working (but hacky) patch:
https://www.dragonflybsd.org/~mneumann/patch-fb-machdep.c
After patching, if I set loader tunable sc.probe_early=1 then it correctly boots.
Files
Updated by mneumann almost 6 years ago
See commit
https://gitweb.dragonflybsd.org/dragonfly.git/commit/c2a57f42609ac17ec656d5600c7f70f38fc8ba62
Try booting with machdep.hack_efifb_probe_early=1.
Updated by shassard almost 6 years ago
I've tried this patch on my Lenovo Yoga 920 that previously was unable to get past the loader initial screen.
It now boots perfectly and I'm able to fire up Xorg without issues.
Updated by mneumann about 4 years ago
With commit b1122e3cbd55be825debb5766a4242317c71d40d the machdep.hack_efifb_probe_early tunable is removed. It should just boot fine.
Updated by mneumann almost 3 years ago
- Status changed from New to Resolved
This has been long fixed.
Updated by daftaupe about 2 years ago
I tried booting the latest release medium available (6.2.2) and master, but can't get past that EFI framebuffer information on my Dell Chromebook 7310.
I've seen on the screenshot you tried loading drm and i915, I tried the same but that didn't change anything unfortunately.
I have no idea if the system is booting behind the scene or if it's stuck.
Updated by mneumann about 2 years ago
I've seen similar problems when I tried a very new laptop a few weeks ago.
I am not quite sure but I am assuming the problem is that your GPU is too recent and not supported by our drm stack, and as such it cannot attach early at boot time and that's why you don't see a system console... but then, it should actually work without loading a drm module, plain old text console...
Updated by daftaupe almost 2 years ago
@mneumann, no that's the initial issue, it doesn't work with the regular console. The GPU is not that recent, it's a Intel HD Graphics 5500 from a Broadwell i3-5005U.
I tried setting drm_load=NO and i915_load=NO but it seems to have no effect as it's probably what's happening as default.