LEDs blinking pattern - Code 123 on startup

Framework Laptop 13 Linux
1

Context

Which Linux distro are you using?
Manjaro Linux, updated continuesly every day

Which kernel are you using?
Linux 6.12.20-2-MANJARO

Which BIOS version are you using?
Not known

Which Framework Laptop 13 model are you using?
13th Gen Intel® Core™ i7-1370P × 20

Description

I bought a Frame.work 13 a year and a half ago, made a double partition on it (Windows 11 + Manjaro), with ciphered NVME

It worked well until last two weeks when it began to panick at startup: the screen stays black, with LEDs blinking on the side.

The LEDs are blinking followingly :
⁃ one white
⁃ twelve green
⁃ One orange
⁃ and the following 8-blink sequence : GBBBBGBB (with G = green, B = blue)

I saw a knowlegde base article about it, and since the first twelve green blinks I suppose the hardware checks are OK, but I didn’t find nowhere the meaning of the 8-bit code (which is 123 is my knowledge of base 2 is correct (0x01111011)).

I read some posts already done about this subject :

At first, I just shutdown the laptop by pressing the start button and waited a few minutes before starting again, but the more time passed the more it remains unresponsive, with LEDs blinking the same sequence given above. I’m currently writing this post after a 2-days vacation, and since you read these lines it worked just fine, but I’m very concerned since I’m using my Frame.work on a daily basis to work.

Did someone already heard about this problem? Is there any documentation about the bit-sequence (a list with all 255 possibilities to know what to check as instance) ?

2

One of these knowledge base articles, correct? My Framework Laptop (Intel 12th Gen Intel® Core™) is not powering on

For interpreting the last 8-bits, referred to as the post code section in knowledge base articles, you need Framework support. That section is not be straight forward to interpret, and also may be different for different motherboards.

If you see an old github gist link, note that it’s many years old at this point. So it may not apply to current boards. And I don’t think anyone found it actually useful when it was current anyway.

2 Likes