Hi all, I own a Framework 13" Ryzen 7040 Laptop (BIOS 3.05).
Yesterday I replaced the display with the new 2.8K version. Even though the laptop seems to be running normally, I now have the blinking LED color pattern on startup.
About ~15s after powering on, the LED on the left side starts blinking in a color pattern. The pattern is as follows:
1xW, 11xG, 2xO, 1xG, 3xB, 4xG
W: White
G: Green
O: Orange
B: Blue
What does the pattern mean? My Linux starts normally - I haven’t noticed any problems while it’s running. Thanks for the help in advance.
Atleast for the 11th gen Intel there’s this guide, I think the code format is guite generic and I doubt they have changed it:
Basically then by that guide, there’s a orange blink on Internal display initialized OK part, meaning the initialization failed. (Whatever that may mean, I don’t personally know.)
Even though the Framework support was very accommodating, it couldn’t solve the problem with my 2.8k display - I hope you have more success.
They ended up sending me both a replacement display and a new AMD motherboard as the issue with the replacement display persisted.
I did everything they suggested. I reset the mainboard several times and finally removed all the components one after the other that could be unplugged. I removed the Wifi module, disconnected the webcam module, disconnected the speakers, the audio board, did a RAM and SSD swap… nothing helped.
As soon as I connected the 2.8k display the same error orrcurred every time.
So I returned all parts and received a refund and am continuing to use the stock display.
Displaying the BIOS code for display not initialized is a known issue on the 2.8K displays. Framework is trying to address it with a BIOS update though that is in beta form currently. If the display is functioning correctly other than the BIOS code; it is likely a false positive. Replacing the display will likely result in the same BIOS error code.
It may be helpful to purchasers that there is a known BIOS codes that may come up and that internally the issue is being addressed by engineering though a final fix has not been rolled out.