You are not logged in.
A few months ago my laptop started hanging at startup about 50% of the time. I apologize for the lack of details, I'm not sure where to look to start troubleshooting. When it hangs, it hangs at the black startup screen where text goes by very quickly. Upon successful bootup, that screen never stops long enough to be able to read it. When it hangs, I'm able to see the last 50-ish lines of text. The only thing I see that is odd when it hangs is the line:
framebuffer coreboot10: probe with driver framebuffer failed with error -17However, I see that line fly by when the laptop successfully boots, so not sure if that's a red herring or not. When it hangs, I have to manually power off with the power button and try again. If I recall, this issue started happening after a system update, but before that it had been working perfectly for two years. I'd love if someone could point me in the correct direction in figuring out how to troubleshoot this issue.
Last edited by DKEBeck (2024-08-21 13:12:33)
Offline
Try to add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters and in doubt post the complete system journal (of ay successful boot)
Adding the actual drm module (eg 915) to the initramfs might help, https://bbs.archlinux.org/viewtopic.php?id=295923
Offline
I added that kernel parameter but didn't notice a change. Here is a system journal of the last good boot:
https://pastebin.com/1JVnzgFA
and here is the complete system journal from the hung boot right before it:
https://pastebin.com/qnRGTaH4
Offline
Both run into
Aug 19 10:29:38 beck-lemur kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
Aug 19 10:29:38 beck-lemur kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Aug 19 10:29:38 beck-lemur kernel: sysfs: cannot create duplicate filename '/bus/platform/devices/simple-framebuffer.0'which heavily points at the relevant race condition.
Neither boot has "initcall_blacklist=simpledrm_platform_driver_init" - make sure it shows up in "cat /proc/cmdline" and see whether you run into the issue again.
If yes, try to add i915 to the initramfs.
There're clearly i915 and framebuffer_coreboot related errors in the bad boot.
Offline
Thanks seth - I didn't realize that the second link you provided in your original reply was my exact issue. And I remember it started in the end of May as well. Adding i915 to the initramfs fixed my problem. I've booted about 10 times successfully in a row now.
Offline