ubuntu-x-swat team mailing list archive

[Launchpad Bug Tracker <731866@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

There are two models of macbook that I've used: the macbook 6,1 and the
macbook 7,1. Both of them have their brightness set internally as an
integer value in the range [0..1023]. The nvidia-bl-dkms driver
acknowledges this and does everything good for the macbook 6,1. However,
for some unknown reason, if you're using a macbook 7,1 then the driver
suddenly thinks it has a range of [0..44000] to play with.

What's the problem? The hardware of the macbook 7,1 still only accepts
[0..1023], so higher values just get taken as 1023. This means, that for
(44000-1023)/44000 of the sample space of the brightness setting, it's
full brightness. That's most of it. So, it appears to the user using
brightness controls that the brightness is always maximum.

How did I work around it? With a quick bit of zenity hacking, I wrote a
simple slider GUI that allows the user to set brightness, but only
[0..1023] is available... ever. It doesn't take and believe the max
value from the driver (44000) so there's no problem.

** Affects: nvidia-graphics-drivers (Ubuntu)
     Importance: Undecided
         Status: New

-- 
nvidia-bl module with nvidia official driver exposes incorrect brightness range for Macbook 7,1
https://bugs.launchpad.net/bugs/731866
You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu.