Open squareunix opened 10 years ago
Hello,
It should be fixed in upcoming version 0.86, please let me know
Works great. Thanks!!
On 18 March 2014 20:31, Guillaume Zin notifications@github.com wrote:
Hello,
It should be fixed in upcoming version 0.86, please let me know
Reply to this email directly or view it on GitHubhttps://github.com/guillaumezin/nvidiabl/issues/79#issuecomment-37983742 .
I had an older version of this driver installed on Xubuntu 12.04 on my Toshiba Satellite L755-1DR, and even though it wasn't on the "official" supported devices list it worked perfectly, I could set it from 0 to 127 and it would change accordingly. I even had set up a quick rudimentary script and bound it to two keys to change the brightness values on the go.
Recently I switched to Crunchbang Waldorf (also Debian-based) and wanted to set up the driver again so I downloaded the latest version and installed it but now I get some really weird brightness values:
If I set brightness to anything higher than 127 I get an error, but if I set it to 127 I get a really, really dark screen (can barely see anything), so I guess the driver is working but somehow it doesn't consider 127 as the max value anymore.
I saw in a similar thread the dev asked to do sudo modprobe -r nvidiabl && sudo modprobe nvidiabl screen_type=2 I get exactly the same result, same values, changing to 127 makes my screen really dark, etc. If I do sudo modprobe -r nvidiabl && sudo modprobe nvidiabl screen_type=3 I get:
BUT changing the brightness value does nothing at all.
EDIT: some extra stuff