cannot change brightness in Gutsy with thinkpad X61s

Bug #129913 reported by Carlos Perelló Marín
12
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I just got a Thinkpad X61s and installed latest Gutsy version on it.

When I try to change the brightness using the hotkeys in the keyboard I get the splash screen that shows the progress bar for the bright level but it's stalled and I cannot move it up or down.

Also, from time to time, without doing anything in the laptop I get the same splash screen and the screen starts blinking. It's like something is trying to change the bright level automatically but is not able and enters in an endless loop until I press the hot key manually which stops that.

Though, when I plug in the power cord the bright level gets high, and when I remove the cord, it goes low without any problem.

I tried with compiz and without it and the problem is still there.

I'm using GNOME with latest updates until today.

Btw, I have another laptop, a Thinkpad X41s which had this same problem with Feisty. At some point, the splash screen to show the bright level disappear for ever and I was able to use the keys again. I haven't find the way to disable it for the other computer so any hint will be welcomed.

Cheers.

Revision history for this message
Carlos Perelló Marín (carlos) wrote :

Latest gnome-power-manager update fixed this a bit. Now, I'm able to change the level progress bar, although the brightness doesn't change at all. The blinking problem is still there, though.

Revision history for this message
Loïc d'Anterroches (diaeresis+bugs) wrote :

I have a X61s, the problem with the brightness comes from the fact that the X61s has 16 levels of brightness and this is not well supported for the moment by the ACPI code.

See: http://<email address hidden>/msg00692.html

Changed in acpi-support:
importance: Undecided → Medium
Revision history for this message
Tom Vetterlein (smbm) wrote :

I'm getting this on my R61 too

Revision history for this message
Anthony DeStefano (ajd-tasteslikeburning) wrote :

I can also verify this on Thinkpad T23. It may be related to a recent ACPI update. There are issues when manipulating /proc/acpi/ibm/brightness directly.

|-/proc/acpi/ibm-|
root@mercury$ cat /proc/acpi/ibm/brightness
level: 2
commands: up, down
commands: level <level> (<level> is 0-7)
|-/proc/acpi/ibm-|
root@mercury$ echo up > /proc/acpi/ibm/brightness
|-/proc/acpi/ibm-|
root@mercury$ cat /proc/acpi/ibm/brightness
level: 0
commands: up, down
commands: level <level> (<level> is 0-7)
|-/proc/acpi/ibm-|
root@mercury$ echo up > /proc/acpi/ibm/brightness
|-/proc/acpi/ibm-|
root@mercury$ cat /proc/acpi/ibm/brightness
level: 1
commands: up, down
commands: level <level> (<level> is 0-7)
|-/proc/acpi/ibm-|
root@mercury$ echo up > /proc/acpi/ibm/brightness
|-/proc/acpi/ibm-|
root@mercury$ cat /proc/acpi/ibm/brightness
level: 2
commands: up, down
commands: level <level> (<level> is 0-7)
|-/proc/acpi/ibm-|
root@mercury$ echo up > /proc/acpi/ibm/brightness
|-/proc/acpi/ibm-|
root@mercury$ cat /proc/acpi/ibm/brightness
level: 1
commands: up, down
commands: level <level> (<level> is 0-7)
|-/proc/acpi/ibm-|
root@mercury$ echo level 7 > /proc/acpi/ibm/brightness
|-/proc/acpi/ibm-|
root@mercury$ cat /proc/acpi/ibm/brightness
level: 7
commands: up, down
commands: level <level> (<level> is 0-7)
|-/proc/acpi/ibm-|
root@mercury$ echo level 7 > /proc/acpi/ibm/brightness
|-/proc/acpi/ibm-|
root@mercury$ echo level 6 > /proc/acpi/ibm/brightness
|-/proc/acpi/ibm-|
root@mercury$ cat /proc/acpi/ibm/brightness
level: 6
commands: up, down
commands: level <level> (<level> is 0-7)
|-/proc/acpi/ibm-|
root@mercury$ echo level 7 > /proc/acpi/ibm/brightness
|-/proc/acpi/ibm-|
root@mercury$ cat /proc/acpi/ibm/brightness
level: 1
commands: up, down
commands: level <level> (<level> is 0-7)

Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Martin Pool (mbp) wrote :

I have an X61s (7669-7DM). In both Gutsy and Hardy (32-bit), I can change the brightness using either the function keys or the gnome panel control.

The brightness does seems to change away from my manually set value after a short delay. I'm not sure if this is specific to my hardware or just a different bug in gnome brightness management.

Revision history for this message
Martin Pool (mbp) wrote :

This is working again with today's hardy updates (Linux lithe 2.6.24-15-generic #1 SMP Fri Apr 4 03:48:31 UTC 2008 i686 GNU/Linux). Thanks!

Revision history for this message
Loïc d'Anterroches (diaeresis+bugs) wrote :

I confirm, this is working with Hardy Heron.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 129913] Re: cannot change brightness in Gutsy with thinkpad X61s

As of today's Intrepid, brightness controls are working well with both
the panel applet and keys.

Revision history for this message
Martin Pool (mbp) wrote :

Working for me.

Changed in linux:
status: Incomplete → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Moving this from Fix Committed to Fix Released based on comment 11 - https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/129913/comments/11

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 129913] Re: cannot change brightness in Gutsy with thinkpad X61s

Thanks Leann.

It's still working well in Jaunty.
--
Martin <http://launchpad.net/~mbp/>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.