setting to 0 reduces actualy to minimum. doas wsconsctl display.brightness=0 display.brightness -> 0.00% $ xbacklight 0.000000
When I then try to "increase" a bit, it switches back to 100% brightness... $ doas wsconsctl display.brightness=10 display.brightness -> 10.00% $ xbacklight 10.000000 $ doas wsconsctl display.brightness=50 display.brightness -> 50.00% $ xbacklight 50.000000 On 2020-02-09 10:05, Caspar Schutijser wrote:
On Sun, Feb 09, 2020 at 01:38:05AM +0100, volker wrote:Hi, I have an older HP Elitebook 840 G1. It is a system with FN key to change brightness: FN-F9 down, and FN-F10 up. btw: both keys don't work... (I was running an OpenSuSE 15 before, they worked to change brightness). So I installed OpenBSD ("current" for other reasons), and reduced the brightness at the restart of the machine, when it still displays the BIOS message or the OpenBSD boot prompt. The kernel would start normally, and display the blue messages. When the inteldrm driver loads, the screens gets shortly dark, and then comes back with the 4 blue lines of the inteldrm at the top, but now in full brightness. Everything else remains in full brightness, I start X automatically, and when logged in, I can't change the brightness anymore. Neither with the keys, nor with wsconsctl. It stays at 100%. I can use wsconsctl on the command line, it responds with a change, but actually brightness remains "full" (100%) - no changes: $ doas wsconsctl display.brightness=50 display.brightness -> 50.00% $ doas wsconsctl display.brightness=10 display.brightness -> 10.00% $ xbacklight 10.000000 $ doas wsconsctl display.brightness=50 display.brightness -> 50.00% $ xbacklight 50.000000What happens when you set the brightness to 0? i.e. $ doas wsconsctl display.brightness=0
