brightness control with a too low increment (+-1) compare to brightness number (>10000)

[Robert Biloute]

Hello,

For some days, my brightness control do not work on mbp 6.2 + Lucid.
Although the brightness level is displayed in the upper-right corner of the screen when I press the F1 and F2 keys, the brightness level does not change at all.
However, trying sudo pommed -d in a terminal gives me:

KEY: LCD backlight down
LCD stepping -1 -> 29464
E: Not primary DBus name owner
KBD: inhibit clear 0x08 -> 0x00

KEY: LCD backlight down
LCD stepping -1 -> 29463
E: Not primary DBus name owner

when I press two times the F1 key (=>decrease brightness). So it seems the stepping (-1) is just too small compared to the number representing the brightness (here: 29464), the brightness control is just too slow to be visible on a human time scale..

[wids (pwidden)]

Using f1 and f2 does change brightness levels, but the increment is tiny compared to the value.

paul@paul-mbp:~$ cat /sys/class/backlight/mbp_backlight/brightness
63959
paul@paul-mbp:~$ #2 sec hold of f1
paul@paul-mbp:~$ cat /sys/class/backlight/mbp_backlight/brightness
63934

[wids (pwidden)]

At first i thought suspend/resume had broken as when it resumed, the brightness was very low. There's a faint picture which i only noticed in low light.

also suspect this is related/the cause:
 http://ubuntuforums.org/showthread.php?t=1592642&page=2

as it occurred just after i did that nvidia upgrade.

All packages up to date, 10.04

[Robert Biloute (robertbiloute)]

same thing for me: after a suspend/resume, the brightness can be set so low that I thought my laptop was not resuming properly.
So it's just as if the 0-256 brightness is now coded on 0-65535 or something like this. This is great for a smoother brightness control, but it seems default value for brightness and brightness increment have not been adapted to that.

[Robert Biloute (robertbiloute)]

solved for me with the last mbp-nvidia... update