[Toshiba Satellite R830-1H3] brightness control works until sleep

[To Do]

On my Toshiba Satellite R830, I have 12.10 AMD64. The Fn + F6, Fn + F7 buttons reduce/increase the brightness level of the screen. The issue is that they stop working after waking my computer from sleep. When this happens I cannot even control brightness by going to "System Settings/Brightness and Lock". I had Ubuntu 12.04 installed before and I had the same identical problem. Now I installed the upstream kernel 3.7rc5 and the situation is even worse, because on wakeup, the brightness is at 100% whereas on the standard kernel it remembers the brightness value.

WORKAROUND: I modified /etc/default/grub changing the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux acpi_backlight=vendor"

Then updated grub with:
sudo update-grub

and the problem is solved.

WORKAROUND: As root (not with sudo but actually changing user: su root), change the value in sys/class/backlight/intel_backlight/brightness . For instance:
echo 2937 > /sys/class/backlight/intel_backlight/brightness

or better still:
echo 300 | sudo tee /sys/class/backlight/intel_backlight/brightness > /dev/null

These values are not between 0 and 7 (as the ones in the other directory), but between 284 and 4539, or something like that. Source is http://askubuntu.com/a/196863/27968 .

WORKAROUND: In Raring:
echo 400 | sudo tee /sys/class/backlight/intel_backlight/brightness

http://www.toshiba.co.uk/innovation/download_bios.jsp?service=UK

Sent an e-mail upstream to: http://marc.info/?l=linux-acpi&m=136975088406475&w=2

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-32-generic 3.2.0-32.51
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 1801 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xc4820000 irq 49'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,1179062e,00100100 HDA:80862805,11790001,00100000'
   Controls : 25
   Simple ctrls : 12
Date: Sat Oct 20 19:04:25 2012
HibernationDevice: RESUME=UUID=7d4873fc-c21f-4172-977f-2fb7c1667f24
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: TOSHIBA SATELLITE R830
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=4ad29e86-825e-4c7c-b220-5eab7199b9e2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-32-generic N/A
 linux-backports-modules-3.2.0-32-generic N/A
 linux-firmware 1.79.1
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2012
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.90
dmi.board.asset.tag: 0000000000
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.90:bd07/31/2012:svnTOSHIBA:pnSATELLITER830:pvrPT32LE-01Y00DFR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: SATELLITE R830
dmi.product.version: PT32LE-01Y00DFR
dmi.sys.vendor: TOSHIBA
---
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 2074 F.... pulseaudio
 /dev/snd/pcmC0D0c: chris 2074 F...m pulseaudio
 /dev/snd/pcmC0D0p: chris 2074 F...m pulseaudio
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=7d4873fc-c21f-4172-977f-2fb7c1667f24
InstallationDate: Installed on 2012-09-19 (54 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: TOSHIBA SATELLITE R830
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=4ad29e86-825e-4c7c-b220-5eab7199b9e2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-18-generic N/A
 linux-backports-modules-3.5.0-18-generic N/A
 linux-firmware 1.95
Tags: quantal running-unity
Uname: Linux 3.5.0-18-generic x86_64
UpgradeStatus: Upgraded to quantal on 2012-10-23 (20 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/31/2012
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.90
dmi.board.asset.tag: 0000000000
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.90:bd07/31/2012:svnTOSHIBA:pnSATELLITER830:pvrPT32LE-01Y00DFR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: SATELLITE R830
dmi.product.version: PT32LE-01Y00DFR
dmi.sys.vendor: TOSHIBA

[penalvch (penalvch)]

To Do, thank you for reporting this and helping make Ubuntu better. Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

As well, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.7-rc1-quantal

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[To Do (entodoays)]

Thanks for your comment.

For the first bit, please see the attached dmsg file.

Regarding upstream kernel testing, can you please indicate a link to where I find it? The link provided is for "Mainline kernels" and not upstream ones.

[penalvch (penalvch)]

To Do, thank you for posting your dmesg. Regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069144/comments/3 :
>"Regarding upstream kernel testing, can you please indicate a link to where I find it?"

http://kernel.ubuntu.com/~kernel-ppa/mainline

"The link provided is for "Mainline kernels" and not upstream ones."

Mainline kernels and upstream kernels are one in the same. However, I see how the article could be ambiguous on whether a mainline kernel is an upstream one. I've updated it to help clear this up.

[To Do (entodoays)]

Sorry for this question, but is it possible to test a quantal kernel on precise? In other words, are you recommending testing of kernel v3.7-rc2-quantal or v3.4-rc7-precise?

[penalvch (penalvch)]

To Do, thank you for your comment. Regarding it https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069144/comments/5 :
>"Sorry for this question, but is it possible to test a quantal kernel on precise?"

Yes.

>"In other words, are you recommending testing of kernel v3.7-rc2-quantal or v3.4-rc7-precise?"

v3.7-rc2-quantal.

[To Do (entodoays)]

I installed the upstream kernel v3.7-rc2-quantal but it doesn't even have brightness controls in System settings, let alone shortcut keys.

I noticed however that there is not linux-headers file, only the linux-headers generic one. It seems strange to me.

[penalvch (penalvch)]

To Do, thank you for testing the mainline kernel. Did this problem not occur in a release prior to Precise?

[To Do (entodoays)]

This is a new computer and never had another Ubuntu version installed. On my previous computer a Dell Inspiron 6400, I never had this problem. The first Ubuntu on that PC was 10.10 32 bit and I upgraded every version until 12.04.

[penalvch (penalvch)]

To Do, could you please test for this in a Lucid live environment via http://releases.ubuntu.com/lucid/ ?

[To Do (entodoays)]

I tested brightness control on a Lucid live usb. Before putting my computer on sleep, brightness control works, albeit not with the shortcut keys but only through the "Power Management" tab.
After I woke up my computer from sleep the screen stayed black. The computer was on and I managed to turn it off "normally" but the display did not turn on.

[To Do (entodoays)]

Now that I think of it, on my old Dell, the brightness control keys worked even on the login screen (lightDM). On this pc, they only work after I login. I do not know if this is relevant though.

[penalvch (penalvch)]

To Do, due to the inconclusive test for Lucid, could you please test Maverick live environment via http://releases.ubuntu.com/maverick/ ?

[To Do (entodoays)]

Should I test it for Natty and Oneiric as well?

[penalvch (penalvch)]

To Do, no need to test in Natty/Oneiric if you could suspend successfully but could not adjust the brightness.

[To Do (entodoays)]

So I tested Maverick, Natty and Oneiric.

Results:

Maverick: Brightness could be controlled before going to sleep. Did not wake up.
Natty/Oneiric: Brightness could be controlled before going to sleep. After waking up, brightness could no longer be adjusted.

[penalvch (penalvch)]

To Do, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Thank you for your understanding.

Marking Triaged as mainline tested kernel-bug-exists-upstream-v3.7-rc2-quantal, regression tested back to Natty, and debugging information attached.

[To Do (entodoays)]

I'm a bit at a loss in identifying the maintainer to email. There are quite a few which seem concerned.

Is it ACPI VIDEO DRIVER <email address hidden>?

[penalvch (penalvch)]

To Do, could you please send this to ACPI:
<email address hidden>

Thank you for your understanding.

[To Do (entodoays)]

How do I find the Output of Oops.. in this case?

[To Do (entodoays)]

Also, please help on what to include as "any further debugging information" in https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream . I'm at a loss here too.

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[To Do (entodoays)]

apport information

[penalvch (penalvch)]

To Do, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069144/comments/20 :
>"How do I find the Output of Oops.. in this case?"

Since your problem does not entail a kernel oops, please ignore this part.

Regarding https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069144/comments/21 :
>"Also, please help on what to include as "any further debugging information" in https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream . I'm at a loss here too."

You want to ensure you boot into the newest mainline kernel available (v3.7-rc5-raring) via https://wiki.ubuntu.com/Kernel/MainlineBuilds and test for this problem. If reproducible, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[To Do (entodoays)]

Dear Sirs,

I'm filing a bug report against a mainline kernel following the
instructions in
https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream
as strictly as possible.

I put all the information required in the attachments. I hope this helps
information helps to resolve this issue.

Many thanks in advance for all the good work.

Regards,

Todo.

[To Do (entodoays)]

Dear Sirs,

I'm filing a bug report against a mainline kernel following the
instructions in
https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream
as strictly as possible.

I put all the information required in the attachments. I hope this helps
information helps to resolve this issue.

Many thanks in advance for all the good work.

Regards,

Todo.

[To Do (entodoays)]

Dear Sirs,

I'm filing a bug report against a mainline kernel following the
instructions in
https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream
as strictly as possible.

I put all the information required in the attachments. I hope this helps
information helps to resolve this issue.

Many thanks in advance for all the good work.

Regards,

Todo.

[To Do (entodoays)]

I found a solution to the problem.

I modified /etc/default/grub changing the line:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux acpi_backlight=vendor"

Then updated grub with "sudo update-grub" and the problem is solved.

[To Do (entodoays)]

Now that I have upgraded to Ubuntu 13.04, the problem is back and, after waking from sleep, can only change the brightness with the "echo 400 | sudo tee /sys/class/backlight/intel_backlight/brightness" command.

More information here: http://askubuntu.com/questions/286662/modifying-brightness-control-shortcut-key-bindings

[penalvch (penalvch)]

To Do, could you please provide the full laptop model (ex. Toshiba Satellite R830-10C)?

[To Do (entodoays)]

Toshiba Satellite R830-1H3 is the full model number.

[penalvch (penalvch)]

To do, thank you for providing the requested information. Could you please test the latest upstream kernel available (v3.10-rc1) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[To Do (entodoays)]

I'm ready to test but I'm a bit confused.

1. The 3.10rc1 kernel is labelled Precise but I'm on raring. Is this a problem?
2. There are two different kernel sets, one labelled "generic" and one "virtual". There is no linux-image-extras "generic" but there is one for "virtual". Which is the one to test?

Thanks for your help.

[To Do (entodoays)]

I checked again and now the 3.10 kernel is labelled "saucy" and there's no longer any virtual packages. It is lacking the extras package. I'll try it and see what happens.

[penalvch (penalvch)]

To Do, could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc3-saucy/ and report the results?

[To Do (entodoays)]

Tested 3.10rc3. The problem remains. No change in behaviour whatsoever.

I noticed that with Ubuntu 12.10 and hence the 3.5.0 kernel, adding acpi_backlight=vendor increased the number of brightness levels. With Ubuntu raring and the 3.8.0 kernel, this grub command no longer changes the number of levels. However, it is doing something, because if I remove this grub command, when I wake my computer from sleep, the brightness level goes up to maximum, whereas with the Grub command it is remembered.

A solution to me seems to make the brightness control associated with /sys/class/backlight/intel_backlight/brightness instead of /sys/class/backlight/toshiba/brightness. This would solve the problem but I don't have a clue how to produce such a change without using scripts, shortcuts associated with those scripts and setting the permissions for the file to 777 or something which allows the user to change the value without using sudo.

[To Do (entodoays)]

I noticed that there's a tag with Bios version 3.9. Actually I have Bios version 4.10

[To Do (entodoays)]

Dear Sirs,

I've gone through the upstream kernel testing procedure as strictly as
possible and here are the results of the tests done.

I hope this helps render Linux and Ubuntu and better product.

Regards,

To Do

Test Results:
----------------
1. One line summary of the problem:
[Toshiba Satellite R830] brightness control works until sleep

2. Full description of the problem/report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069144
On my Toshiba Satellite R830, I have 13.04 AMD64. The Fn + F6, Fn + F7
buttons reduce/increase the brightness level of the screen. The issue is
that they stop working after waking my computer from sleep. When this
happens I cannot even control brightness by going to "System
Settings/Brightness and Lock". I had Ubuntu 12.04 and 12.10 installed
before and I had the same identical problem.

With the two previous versions of Ubuntu (and hence kernels 3.2.0 and
3.5.0) there was a workaround:
WORKAROUND: I modified /etc/default/grub changing the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux
acpi_backlight=vendor"

Then updated grub with:
sudo update-grub

and the problem was solved.

This workaround does not work with 13.04. Furthermore I noticed that
with Ubuntu 12.10 and hence the 3.5.0 kernel, adding
acpi_backlight=vendor increased the number of brightness levels. With
Ubuntu raring and the 3.8.0 kernel, this grub command no longer changes
the number of levels. However, it is doing something, because if I
remove this grub command, when I wake my computer from sleep, the
brightness level goes up to maximum, whereas with the Grub command it is
remembered.

I noticed that the brightness keys and brightness and lock settings
change the /sys/class/backlight/toshiba/brightness value. Now this no
longer has any effect on the actual brightness level after wakeup from
sleep. However /sys/class/backlight/intel_backlight/brightness is
associated with the actual brightness level, before and after wakeup
from sleep. If I change this value with echo 300 | sudo tee
/sys/class/backlight/intel_backlight/brightness, the level changes.

3. Keywords
Toshiba, brightness control, kernel

4. Kernel version (from /proc/version):
Linux version 3.10.0-031000rc3-generic (apw@gomeisa) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201305261935 SMP Sun May 26 23:35:53
UTC 2013

5. Output of Oops..
No oops crash

6. A simple shell script
No script is needed. Simply put the laptop on sleep, wait a few seconds
and wake it from sleep.

7. Environment
Description: Ubuntu 13.04
Release: 13.04

7.1 Software (add the output of the ver_linux script here)
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux chris-SATELLITE-R830 3.10.0-031000rc3-generic #201305261935 SMP
Sun May 26 23:35:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Gnu C 4.7
Gnu make 3.81
binutils 2.23.2
util-linux 2.20.1
mount support
module-init-tools 9
e2fsprogs 1.42.5
pcmciautils 018
PPP ...

[To Do (entodoays)]

I've gone through the upstream kernel testing procedure as strictly as
possible and here are the results of the tests done.

Test Results:
----------------
1. One line summary of the problem:
[Toshiba Satellite R830] brightness control works until sleep

2. Full description of the problem/report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069144
On my Toshiba Satellite R830, I have 13.04 AMD64. The Fn + F6, Fn + F7
buttons reduce/increase the brightness level of the screen. The issue is
that they stop working after waking my computer from sleep. When this
happens I cannot even control brightness by going to "System
Settings/Brightness and Lock". I had Ubuntu 12.04 and 12.10 installed
before and I had the same identical problem.

With the two previous versions of Ubuntu (and hence kernels 3.2.0 and
3.5.0) there was a workaround:
WORKAROUND: I modified /etc/default/grub changing the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux
acpi_backlight=vendor"

Then updated grub with:
sudo update-grub

and the problem was solved.

This workaround does not work with 13.04. Furthermore I noticed that
with Ubuntu 12.10 and hence the 3.5.0 kernel, adding
acpi_backlight=vendor increased the number of brightness levels. With
Ubuntu raring and the 3.8.0 kernel, this grub command no longer changes
the number of levels. However, it is doing something, because if I
remove this grub command, when I wake my computer from sleep, the
brightness level goes up to maximum, whereas with the Grub command it is
remembered.

I noticed that the brightness keys and brightness and lock settings
change the /sys/class/backlight/toshiba/brightness value. Now this no
longer has any effect on the actual brightness level after wakeup from
sleep. However /sys/class/backlight/intel_backlight/brightness is
associated with the actual brightness level, before and after wakeup
from sleep. If I change this value with echo 300 | sudo tee
/sys/class/backlight/intel_backlight/brightness, the level changes.

3. Keywords
Toshiba, brightness control, kernel

4. Kernel version (from /proc/version):
Linux version 3.10.0-031000rc3-generic (apw@gomeisa) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201305261935 SMP Sun May 26 23:35:53
UTC 2013

5. Output of Oops..
No oops crash

6. A simple shell script
No script is needed. Simply put the laptop on sleep, wait a few seconds
and wake it from sleep.

7. Environment
Description: Ubuntu 13.04
Release: 13.04

7.1 Software (add the output of the ver_linux script here)
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux chris-SATELLITE-R830 3.10.0-031000rc3-generic #201305261935 SMP
Sun May 26 23:35:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Gnu C 4.7
Gnu make 3.81
binutils 2.23.2
util-linux 2.20.1
mount support
module-init-tools 9
e2fsprogs 1.42.5
pcmciautils 018
PPP 2.4.5
Linux C Library 2.17
Dynamic linker (ldd) 2.17
Procps 3.3.3
...

[To Do (entodoays)]

There is a related bug on the kernel bug tracker: https://bugzilla.kernel.org/show_bug.cgi?id=21012 for Kernel 3.2.

I tried the workaround suggested in comment 19 but this stops my laptop going in sleep mode.

Any ideas how to modify this script to make it work?

-----------------
#!/usr/bin/env sh
# /etc/pm/sleep.d/99toshiba

if [ $1 == suspend ]
then
        cat /sys/class/backlight/intel_backlight/brightness >
/var/run/brightness
elif [ $1 == resume ]
then
        echo 3 > /sys/class/backlight/toshiba/brightness
        cat /var/run/brightness >
/sys/class/backlight/intel_backlight/brightness
fi

[penalvch (penalvch)]

To Do, thank you for posting the results of your search.

As an FYI, that bug report is way to broad, and risks being considered useless. It would be best to avoid such reports as upstream largely ignores bugzilla, in favor of the appropriate mailing list. As well, this bugzilla report in particular is more of a forum of potentially related "Me too!" comments, which is not what you want in a bug report. Instead, one would want maintainers discussing code development or posting patches with a chance of being accepted into the stable kernel. In addition, that report isn't even toggled to the correct provider group, so the appropriate maintainer(s) wouldn't even be viewing that report.

Much of the same applies for downstream report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778 . Doing "Every hardware from a vendor" reports is frowned upon both up and downstream. It is also advised to avoid marking this report a duplicate of either at the risk of your problem being marginalized and ignored.

The maintainers of the problem you have, would be subscribers of the linux-acpi mailing list (I've had a similar problem with different hardware which went to the linux-acpi mailing list first, and was ultimately resolved in a very timely manner).

With this in mind, before we upstream this report in the method requested by upstream, could you please test the newest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc4-saucy/ ?

[To Do (entodoays)]

I went through the changes file in the 3.10-rc4-saucy folder and there's absolutely no reference to brightness, acpi, video, toshiba, power management.

Is it really worth testing if no changes have been done with respect to this issue?

I sent an e-mail with the testing results to the maintainers but didn't receive a reply.

The reporting procedure says to post this issue on bugzilla if no reply is received. No time limit is given in the procedure. In your opinion, till when should I wait before posting on bugzilla?

[To Do (entodoays)]

I tested the 3.10-rc4 kernel. Problem is not solved.

[penalvch (penalvch)]

To Do, thank you for performing the requested test. Could you please provide a URL of the post you made to upstream ~May 29?

[To Do (entodoays)]

Sorry but I don't understand your request. The testing I had done on kernel 3.10-rc3 is found on comment 55 (28-May) in this bug report.

I did not go through all the procedure again for 3.10-rc4. I simply installed, tried the brightness controls which worked before putting to sleep. Put my laptop to sleep and woke it up again. Brightness controls didn't work any longer.

[penalvch (penalvch)]

To Do, I am requesting a hyperlink to the post you made to the linuxacpi mailinglist. Did you not post to them in or around May 29?

[To Do (entodoays)]

On May 28, I sent an email to <email address hidden> with the testing results. I never received a reply, not even a confirmation of receipt.

A google search for the linux-acpi mailing list gave me these links:

Th report: http://marc.info/?l=linux-acpi&m=136975088406475&w=2
A reply: http://marc.info/?l=linux-acpi&m=136991792531545&w=2

[penalvch (penalvch)]

To Do, as per the reply http://marc.info/?l=linux-acpi&m=136991792531545&w=2 Aaron Lu (looks like he works for Intel) would like you to file a bugzilla report, and attach a acpidump to it. It would be best to file a separate report following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Second_Step:_Reporting_on_Bugzilla.kernel.org_after_No_E-Mail_Response_from_Maintainer . Please disregard the part about looking for duplicates, for the reasons noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069144/comments/57 . As well, it is advised to create the report with the following:
Product: ACPI
Component: Power-Video
Severity: Low
^ (as you do have a WORKAROUND)
Tree: Mainline
Regression: No
URL: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069144
Kernel Version: 3.10.0-031000rc4.201306020443
^ (though it wouldn't hurt to test 3.10-rc5 as they have a tendency to ask you to test the newest mainline kernel available and 3.10-rc4 is already old)
Summary: [Toshiba Satellite R830] brightness control works until sleep

Let me know when you have posted it to Bugzilla and feel to CC me to it.

[To Do (entodoays)]

I tested 3.10rc5 and submitted the kernel bug report here: https://bugzilla.kernel.org/show_bug.cgi?id=59651.

[To Do (entodoays)]

For the time being I am using the following workaround:

1. Created two scripts to increase and decrease the brightness (see attachments).
2. I put them in a folder under home and made them executable.
3. Added the following line before the exit line in /etc/rc.local

chmod 646 /sys/class/backlight/intel_backlight/brightness

4. Created custom keyboard shortcuts associated with these scripts. I assigned Alt + ↑ and Alt + ↓.

Now I have two sets of brightness controls, one of which, the normal ones (Fn + F6/F7), work until sleep. The others work before and after sleep.

[To Do (entodoays)]

I managed to solve the problem in a much cleaner way.

I tried to create a custom xorg.conf file with the following content but my system didn't boot.

Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "Backlight" "intel_backlight" # use your backlight that works here
EndSection

Finally, I tried the following procedure:
http://askubuntu.com/a/281685/27968

I got errors when starting lightdm BUT it created a xorg.conf.failsafe file.

I opened it and modified it by adding the option line under "Device" as follows:

Section "Device"
       Identifier "Configured Video Device"
       Driver "intel"
       Option "Backlight" "intel_backlight"
EndSection
#
Section "Monitor"
       Identifier "Configured Monitor"
EndSection
#
Section "Screen"
       Identifier "Default Screen"
       Monitor "Configured Monitor"
       Device "Configured Video Device"
EndSection

And bingo! Everything is working as it should.