So I upgraded to the 2.8K display on my Framework 13 7840u and after that I noticed that when waking the laptop form hibernate the diagnostic leds start flashing after about 30sec.
I can replicate this using “shutdown /h” in the windows terminal and waking it again. The sequence is: 1x white 11x green 2x red 1x green 3x blue 4x green.
I assume the sequences per model aren’t different, so according to this source framework-diagnostic-led-sequence.md · GitHub the display is not initialized.
The laptop and display work perfectly fine. I just wanted to ask if someone has noticed the same behavior / has a way to “fix” this. Maybe I have to reseat something.
this is one of the more fun types of computer bug: “it works and i dont know why”
i wonder if its an issue with the firmware not recognising it properly. maybe theres some kind of gpu driver log you can pull (not sure how it works on windows really) to see how it detects the display once its booted up and if anything unusual is in that log
There is nothing in the windows logs I can see related to graphics driver and display. It is weird to me why POST codes are displayed while fully booted up and in working state. In my naive pov I thought that POST is only run on boot not waking from sleep states. But then again the link I posted are the codes for the Intel models. It could be something else.
As I said there are no issues. For me at least just when the laptop is in standby for too long it switches to hibernation and when I wake it from that it just starts blinking consistently. I just today had an occurance with “shutdown -s -fw” but again only after I left BIOS and continued booting to windows.
Maybe I’ll try to chuck my ubuntu drive in there and see if I can see something in the logs. But I dont think I can find something. Maybe this is just a minor BIOS/firmware issue.
hibernation isnt the same as sleep - it fully shuts the system down (the difference from a regular shutdown is that the kernel first dumps the contents of RAM to some location on the disk* and then restores it on boot if required)
*this can be a file or partition, depending on operating system and configuration
one thing i thought of is whether you can actually see anything from the firmware before the OS initialises (could be that the windows display driver is fine with the display but the basic drivers of the firmware cant handle it properly)