toshiba laptop brightness not adjustable after hibernation

[Alejandro R. Mosteo]

Binary package hint: kde-guidance

Laptop is a toshiba satellite u200.

Distro is kubuntu feisty beta with kernel

# uname -a
Linux 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

It doesn't happen every time, but when it does:

Laptop brightness is at minimum after resuming the hibernation. The Fn-f6/f7 keys do something as the screen blinks, but brightness remains at minimum. The command line tool toshset doesn't work either, in the sense that brightness doesn't change, but it doesn't report failure either. The slider in guidance-power-manager also has no effect. Either of the three methods works when the screen is in 'normal' state (i.e. when it responds to adjustments after a normal boot).

Please advice on how to provide extra debugging information.

[Ante Karamatić (ivoks)]

I can confirm this on latest version of Ubuntu/Kubuntu.

[Ante Karamatić (ivoks)]

rmmoding video module does the trick.

[vasmik (vasmik)]

I can confirm this bug.
Toshiba Satellite A100-071. Fn+F6 and Fn+F7 keys don't work.

[Ante Karamatić (ivoks)]

Adding 'blacklist video' to /etc/modprobe.d/blacklist fixes this issue.

[Alejandro R. Mosteo (mosteo)]

I have had one occurrence of this problem using the 'blacklist video' trick suggested here, so it is not effective.

[Ante Karamatić (ivoks)]

mosteo wrote:
> I have had one occurrence of this problem using the 'blacklist video'
> trick suggested here, so it is not effective.

What's strange is that, after hibernation, it's impossible to change
brightness. But, when I close my lid, wait 2-3 seconds and open it
again, I can change brightness.

This is different behavior of 'dpmsing' off monitor on hitting keys.

[Alejandro R. Mosteo (mosteo)]

I can confirm that closing the lid, waiting for the screen to go off and opening it again fixes the problem for me too. I have the 'blacklist video' line there, tough, because I never bothered to remove it.

[Ante Karamatić (ivoks)]

This problem seems to be resolved with latest update of xserver-xorg-core package in gutsy.

[Luka Renko (lure)]

mosteo, vasmik: can you also confirm that this problem is fixed with up-to-date gutsy as reported by Ante?

[Alejandro R. Mosteo (mosteo)]

I'm in the middle of a business trip and cannot afford to have a failed upgrade. It will be the first thing I do once back at home. I will be able to report around the 7-8 nov.

[Luka Renko (lure)]

mosteo, no problem and thanks for reporting back.

[Alejandro R. Mosteo (mosteo)]

I have upgraded and a single test was successful, but it was not 100% repeatable before so it is soon to be sure of anything. Give me a week of usage or so to have more samples.

[Alejandro R. Mosteo (mosteo)]

It just has happened again to me with an up-to-date gutsy. Though, I'm not sure if the brightness was at minimum; it seemed stuck at the setting prior to hibernation. This would be a difference, in the past it was always stuck at the minimum setting.

I've checked that the closing-the-lid trick still works.

[Mattias Örtenblad (m-ortenblad)]

I have this problem i Hardy Heron Alpha 3 reported in bug 181374.

[Paul Kohler (moxiewhimsy)]

after the latest update of xserver-xorg-core package in gutsy, my hibernate doesn't work at all. Though possibly not the cause, since I hadn't hibernated in a while due to the above mentioned bug. Box is Toshiba Tecra A9-S9013X (x only means it came with XP pro.)

[Paul Kohler (moxiewhimsy)]

Oh, and my situation was different, the brightness level was consistently at a maximum, rather than 3/8 as I set in a configuration file which unfortunately I edited and forgot about.

[Launchpad Janitor (janitor)]

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!

[Leann Ogasawara (leannogasawara)]

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.

[vince (lapcchan)]

my notebook is panasonic cf-r3 and i also have this problem on 8.10 with kernel 2.6.27-7. it happens everytime after suspend and resume, even if i blacklist the video module.
it works fine if i boot with kernel 2.6.24-21(the old kernel of 8.04)

note: i am using third-party pcc-acpi driver from http://www.da-cha.jp/letsnote with the kenel 2.6.26 patch posted below. the driver works fine and i can adjust brightness no problem before i resume from suspend.

[vince (lapcchan)]

i just tried without loading the pcc-acpi driver(it used to adjust my laptop's brightness).

brightness still at minimum after resume with kernel 2.6.27-7. normal with kernel 2.6.24-21

[Leann Ogasawara (leannogasawara)]

Hi vince,

I actually think you have a different bug mainly because you have a different system than the original bug reporter. You mention having a panasonic laptop. I think the bug you want to track is bug 222324.

mosteo, since you are the original bug reporter, can you comment if this is still an issue for you with Intrepid? Thanks.

[Javier Jardón (jjardon)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!