Hey everyone. Last Monday, my Framework 13 (AMD)'s display suddenly died. I had briefly left the room to brush my teeth and upon my return, I was greeted by a pitch black screen – no light at all. When I turn the laptop on, the following blinking sequence takes place a minute after pressing the power button: W GGGGGGGGGGGR O GBBBGGG.
(Link to the video on Proton Drive here.)
Based on my interpretation of this document, the sequence after the white blink means the internal display failed to initialize and the one after the orange blink indicates a POST code of 01110000. This, converted to hexadecimal, is 0x70. In InsydeH2O’s documentation, this POST code means PEI_SIO_INIT (Super I/O Initialization). However, someone suggested to me that the code should be read in reverse since the bits are reported from 0 to 7. In that case, it’s 0b00001110 = 0x0E, which is unfortunately nowhere to be found in the POST code documentation.
Attempts in troubleshooting
- I turned it off and on again. No, it did not work.
- I connected the laptop to an external display via HDMI. It still outputs to an external display.
- I checked the detected displays in Pop!_OS 22.04’s display settings. It detects the external display AND the internal display, albeit with the wrong resolution (1366 x 768).
- Here’s what I found interesting: I booted other Linux distros from a Ventoy USB drive (Pop!_OS 24.04, Fedora 40 and its KDE spin) and they did not detect the internal display in their display settings. However, Pop!_OS 22.04 booted from the USB drive detects the internal display! (What could be so special with Pop!_OS 22.04? Come to think of it, I should also try Ubuntu 22.04 and Linux Mint 21.3.)
- I had unplugged the internal display and booted to Pop!_OS 22.04. The display is no longer detected.
- I actually have another broken FW13 display. Despite its state, I know that it was correctly recognized by the display settings before. I plugged in the old display and it is detected, but also with the wrong reported resolution (1366 x 768).
- I disconnected the battery from the board for at least 5 minutes. Then, I plugged it back in and turned on the laptop. Still no display.
Potentially relevant information at the time of the incident?
- The laptop was being charged by a Xiaomi 67 W power adapter.
- I had been running a rather resource-intensive Python script analyzing some atmospheric data. It got kinda hot.
- (I think the laptop had just gone to sleep? I could be misremembering.)
I don’t think the display itself is dead. What else can I do?
Addendum
- I have already read some posts related to this issue and a common suggestion was reseating the cable. Given how many times I’ve plugged and unplugged the displays, I consider that done. Haven’t tried reseating the cable on the display’s end, but I think the issue is on the board’s end since it is common across the two displays.
- The internal display is (incorrectly) recognized in Ubuntu 22.04, but not Linux Mint 21.3. Surprisingly, Linux Mint Debian Edition 6 does (incorrectly) recognize it!
