https://bugzilla.novell.com/show_bug.cgi?id=297155#c2 --- Comment #2 from Tobias Burnus 2007-08-13 12:09:28 MST --- (In reply to comment #1 from Danny Kukawka)

a small comment: you should use sysfs to change the brightness and no longer the proc interface.

Actually, I usually simply use the Fn+brighter/darker buttons, which works (8 brightness steps); otherwise I want that kpowersave works. In terms of sysfs I have: /sys/class/backlight/thinkpad_screen/ brightness/actual_brightness (0 to 7, same problems as described above) max_brightness (always 7) /sys/class/backlight/acpi_video0/ actual_brightness brightness max_brightness: always 100 /sys/class/backlight/acpi_video1/ actual_brightness between 20 and 100 - this value actually seems to work -- I get 8 different % values. brightness - remains at 100 [I'm using the Fn-brightness buttons] max_brightness (is 100) Using "echo 50 > brightness", I often end up with actual_brightness = 20; I have to use the command once or twice again to get the desired value. Why does acpi_video1 work and thinkpad_screen does not? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=297155#c4 --- Comment #4 from Christopher Stender 2007-08-13 12:27:21 MST --- Beta2 will fix the acpi_video bug. You can work around it this way: echo "install video /bin/true" > /etc/modprobe.d/intel-i810-xorg-x11 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=297155#c6 Tobias Burnus changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|burnus@gmx.de | --- Comment #6 from Tobias Burnus 2007-09-11 03:58:40 MST --- (In reply to comment #5 from Christopher Stender)

Can you still reproduce this bug with beta3?

I still have the same problem: Using Fn+brightness I can change the brightness in 15 (new!) steps, using e.g. kpowersave, only a limited brightness range is accessible. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=297155#c8 --- Comment #8 from Tobias Burnus 2007-09-11 08:14:15 MST --- I pressed Fn-darker until I reached maximal darkness; And now: $ cd /sys/class/backlight/thinkpad_screen/ $ cat actual_brightness 0 # press now "Fn+brighter" and cat then actual_brightness: 1 # ditto 2 3 4 5 6 7 0 # screen is brighter, but number wrapped around. 1 2 3 4 5 6 7 # maximal brightness after 15 times pressing "Fn+brighter" Depending in which half I am, the brightness "7" goes either to the middle or to the brightness; and "0" goes to the middle or to the lowest brightness. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=297155#c10 --- Comment #10 from Danny Kukawka 2007-09-11 08:21:13 MST --- IMO a duplicate of bug #308264 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=297155#c12 Tobias Burnus changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #12 from Tobias Burnus 2007-09-12 02:31:11 MST --- In principle as 297155 < 308264 it should be the other way round ;-) I marked this bug as duplicate of bug 308264 and will add a comment there. *** This bug has been marked as a duplicate of bug 308264 *** https://bugzilla.novell.com/show_bug.cgi?id=308264 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.