13" Ryzen 7040: Blinking LED color pattern on startup

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.

quick update:

  • Resetting the BIOS didn’t fix the problem
  • RAM seems OK, memtest86 runs without error messages
  • The error only appears with the new 2.8k display. I used the old display for testing purposes again and the problem described doesn’t occur…

Any suggestions what to do?

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.)

I’d probably place a support ticket for that.

1 Like

Hi all,

at this point I would like to give a short update for anyone who may encounter the same error.

The official support was very helpful and came to the conclusion that there is a need to replace the Display.

The blinking LED shows the error code 12 - Internal Display Initialized failed.

Cheers

1 Like

I’ll just note here that I’ve had exactly the same symptoms with my DIY FW13 7840 with 2.8k display.

I have a request in with support for this.

Same symptoms are reported here, too:

1 Like

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.

My situation is that support have just ordered a replacement 2.8k screen.

I’ve also taken many steps with them in diagnosing this issue, so we’ll see what happens once the replacement is in place.

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.

The new beta bios does seem to fix this, i haven’t seen any of these blinks after I upgraded my bios when it was released.