After updating my Glimmer device from version 4.20 to the latest MrChromebox coreboot release, I’ve encountered an issue. If the eDP display panel is not connected to the laptop, coreboot fails to initialize entirely (there is no response from the Caps Lock LED).
I originally purchased several of these laptops without screens to use them as headless mini-servers, but this use case is no longer working. Is there any workaround or a potential fix for this?
No response from the caps lock LED, as in you can not trigger caps lock?
I am just a regular user, but I personally would go through the information on the following website on how to collect debug information.
Maybe someone immediately recognizes this issue but on the off chance that they don’t this helps tremendously. If you have a SuzyQ there are instructions on how to compile coreboot with debug information output enabled.
In the case where there is no display, the easiest way to check whether the BIOS has initialized is to connect an external USB keyboard and see if there is any response to Num Lock or Caps Lock — even USB testers work based on this principle. It’s an old trick
When the display is connected, the keyboard starts responding immediately after the splash screen appears. If the display cable is disconnected, there is no keyboard response even a minute after powering on.
After reading the page, I realized that I do not have USB Type-C. However, if the issue cannot be confirmed (personally, I find it easy to reproduce and suspect this situation is not limited to Glimmer) and there is additional interest, I can look into it.
For now, I restored the backup and rolled back to version 4.20.
