Which Linux distro are you using?
Fedora (Workstation Edition)
Which release version?
42
Which kernel are you using?
Linux 6.15.5-200.fc42.x86_64
Which BIOS version are you using?
BIOS Revision: 3.3
Which Framework Laptop 13 model are you using?
Framework Laptop 13 AMD Ryzen AI 300 Series
My laptop runs great. Super happy with it in general. However, one issue
PROBLEM
Screen sometimes goes black. Seemingly black, because if I look very careful, it’s not totally black, just that screen seem to have lost all light. Computer still runs and it’s possible to see the screen, but very vaguely. Closing the lid a second or two and reopen it, solves the problem temporarily. However, when this has happened once, it seem to happen more and more frequently.
If i restart the computer, it takes longer before it happens again. If I start the computer from suspend/sleep or whatever it may be called (when I just close the lid and leave the computer as was) my experience is that it takes much shorter before the problem happens. But if I restart the computer, it may run like 30-45 min or maybe longer (have not timed it), before it starts going black again.
Is this a known problem? Anyone at Linux, AMD or Framework working on a solution?
Or, is the problem possibly hardware dependent? Would I need to swap the screen? Feels like a sw issue.
Mine seemingly did this randomly for a while. It hasn’t happened since then. But when it did, I used brightnessctl to correct it and it’s fixed immediately.
Thanks @Richard3 I’ll look into that.
Yeah, I noticed that it was resetting to 5% (I think) for some unknown reason. I figured out brightnessctl and just used that to set it to 70% whenever it did that. It hasn’t done it in weeks since then.
@Richard3 Did you run a script to automatically adjust the brightnesslevel, if/when it went low? When setting my screen to 1% it’s still brighter compared to the problem I’ve described above, i.e. it’s not possible to read what’s on the screen, but if one happen to know approx what the screen looked like, when it went dark, it can be possible to “see” the screen, but superduper hard to navigate (not impossible, but close to). Hence, starting up the brightnessctl when this problem occurs.., is likely to be a challenge. Hence, question if you created a script for this?
I tried to set the screen to 0%, but the difference to 1% seem to be zero, while I can note the change to 2% → Maybe it’s not possible to set the screen to 0% as a user??
My current setting looks like this. Could it be that the computer for some reason jumps in to another Device than the “amdgpu_bl1” ?? (and, i’m a newbe to linux and fedora ..)
~$ brightnessctl -l
Available devices:
Device ‘amdgpu_bl1’ of class ‘backlight’:
Current brightness: 19661 (30%)
Max brightness: 65535
Device ‘input2::numlock’ of class ‘leds’:
Current brightness: 0 (0%)
Max brightness: 1
Device ‘chromeos:white:power’ of class ‘leds’:
Current brightness: 0 (0%)
Max brightness: 100
Device ‘input2::capslock’ of class ‘leds’:
Current brightness: 0 (0%)
Max brightness: 1
Device ‘input2::scrolllock’ of class ‘leds’:
Current brightness: 0 (0%)
Max brightness: 1
Device ‘chromeos::kbd_backlight’ of class ‘leds’:
Current brightness: 0 (0%)
Max brightness: 100
Device ‘chromeos:multicolor:charging’ of class ‘leds’:
Current brightness: 0 (0%)
Max brightness: 100
This sounds like the backlight is cutting out. It may be worth removing the screen surround and try jiggling the wires that connect the screen to the processor to see if it comes right when it goes dark.
So this is an interesting issue. I am experiencing something similar during boot up. I have my storage device encrypted so on boot up when the screen prompts for the password its very dim, unless I am plugged into a power source, then it is full brightness. Only started happening with the latest kernel release.