Screen Dimmed After Resume

[Michael Fletcher]

I am able to suspend and resume using my new EeeTOP ET1602. The problem is that the screen is dimmed after a resume.

It seems only half as bright it used to be. The brightness controls still work but the highest brightness mode is only have as bright as it used to be.

Suspending using the power button, the menu on the top right or pushing FN-ZZ all have the same effect.

Rebooting fixes the problem.

This happens on 9.10 alpha 3 livecd as well as my installed 9.04.

ProblemType: Bug
Architecture: i386
Date: Thu Aug 6 03:34:38 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090722.2)
MachineType: ASUSTeK Computer INC. ET1602
Package: linux-image-2.6.31-3-generic 2.6.31-3.19
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
RelatedPackageVersions: linux-backports-modules-2.6.31-3-generic N/A
SourcePackage: linux
Uname: Linux 2.6.31-3-generic i686
dmi.bios.date: 11/21/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0202
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: ET1602
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd11/21/2008:svnASUSTeKComputerINC.:pnET1602:pvrQTCEDA85004248:rvnASUSTeKComputerINC.:rnET1602:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: ET1602
dmi.product.version: QTCEDA85004248
dmi.sys.vendor: ASUSTeK Computer INC.

[Jens Jorgensen (jorgensen)]

I can confirm this behavior on my ET1602 also. My install is a fresh 9.10 from the release DVD. xrandr seems not to know anything about backlight either, as mentioned the only way to fix it seems to be to reboot.

[Nick Payne (npayne12)]

I have this same problem on my HP Mini 311 running 9.10.

[Jeremy Foshee (jeremyfoshee)]

Hi Michael,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Michael Fletcher (mikefletcher)]

I will but not for 2-3 weeks. I am moving homes and the troublesome
computer is packed.

On Sun, Mar 14, 2010 at 12:41 AM, Jeremy Foshee
<email address hidden> wrote:
> Hi Michael,
>
> If you could also please test the latest upstream kernel available that
> would be great.  It will allow additional upstream developers to examine
> the issue.  Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag.  This can be done by clicking on the yellow
> pencil icon next to the tag located at the bottom of the bug description
> and deleting the 'needs-upstream-testing' text.  Please let us know your
> results.
>
> Thanks in advance.
>
> [This is an automated message.  Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
>       Status: New => Confirmed
>
> --
> Screen Dimmed After Resume
> https://bugs.launchpad.net/bugs/409664
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Confirmed
>
> Bug description:
> I am able to suspend and resume using my new EeeTOP ET1602.  The problem is that the screen is dimmed after a resume.
>
> It seems only half as bright it used to be.  The brightness controls still work but the highest brightness mode is only have as bright as it used to be.
>
> Suspending using the power button, the menu on the top right or pushing FN-ZZ all have the same effect.
>
> Rebooting fixes the problem.
>
> This happens on 9.10 alpha 3 livecd as well as my installed 9.04.
>
> ProblemType: Bug
> Architecture: i386
> Date: Thu Aug  6 03:34:38 2009
> DistroRelease: Ubuntu 9.10
> LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090722.2)
> MachineType: ASUSTeK Computer INC. ET1602
> Package: linux-image-2.6.31-3-generic 2.6.31-3.19
> ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
> ProcEnviron:
>  LANG=en_US.UTF-8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
> RelatedPackageVersions: linux-backports-modules-2.6.31-3-generic N/A
> SourcePackage: linux
> Uname: Linux 2.6.31-3-generic i686
> dmi.bios.date: 11/21/2008
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 0202
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: ET1602
> dmi.board.vendor: ASUSTeK Computer INC.
> dmi.board.version: Rev 1.xx
> dmi.chassis.asset.tag: Asset-1234567890
> dmi.chassis.type: 3
> dmi.chassis.vendor: Chassis Manufacture
> dmi.chassis.version: Chassis Version
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd11/21/2008:svnASUSTeKComputerINC.:pnET1602:pvrQTCEDA85004248:rvnASUSTeKComputerINC.:rnET1602:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
> dmi.product.name: ET1602
> dmi.product.version: QTCEDA85004248
> dmi.sys.vendor: ASUSTeK Computer INC.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/...

[Michael Fletcher (mikefletcher)]

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mikefletcher 1695 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe938000 irq 28'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1043835f,00100001'
   Controls : 26
   Simple ctrls : 14
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=a18a7d1d-cb4e-4598-8f92-280305d92d9a
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: ASUSTeK Computer INC. ET1602
Package: linux (not installed)
ProcCmdLine: root=UUID=e3dfe202-8707-4379-a572-d9487f3976d6 ro xforcevesa quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_CA.UTF-8
RfKill:

Uname: Linux 2.6.33-020633-generic i686
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
WpaSupplicantLog:

dmi.bios.date: 11/21/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0202
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: ET1602
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd11/21/2008:svnASUSTeKComputerINC.:pnET1602:pvrQTCEDA85004248:rvnASUSTeKComputerINC.:rnET1602:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: ET1602
dmi.product.version: QTCEDA85004248
dmi.sys.vendor: ASUSTeK Computer INC.

[Michael Fletcher (mikefletcher)]

I retested using the mainline 2.6.33-020633-generic and the problem remains. I tried the daily 2.6.34 but it crashes hard on bootup itializing the cpu.

[Tim Eager (tim-eager)]

I think I have the same issue, although with a couple of variations (Sony Vaio FW290J):

After resume, my brightness controls do NOT work, although I just discovered that modifying /proc/acpi/video/VGA/LCD/brightness directly DOES work.

Also, I have a panel notification icon about a "serious kernel problem" each time I resume.

I'm running Lucid Beta. "/proc/version" reports:

Linux version 2.6.32-19-generic (buildd@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #28-Ubuntu SMP Thu Apr 1 10:39:41 UTC 2010

[Tim Eager (tim-eager)]

Update - if I suspend/resume AFTER modifying /proc/.../LCD/brightness directly, the display brightness is not dimmed after resume.

HOWEVER, if I unplug AC power and then plug back in, the brightness reverts to the dimmed value.

For example, this is after resume (with a previously modified /proc/.../brightness):

<PROMPT>$ cat /proc/acpi/video/VGA/LCD/brightness
levels: 20 24 29 36 44 53 63 76 100
current: 100

AC adapter unplugged:

<PROMPT>$ cat /proc/acpi/video/VGA/LCD/brightness
levels: 20 24 29 36 44 53 63 76 100
current: 29

AC adapter plugged in:

<PROMPT>$ cat /proc/acpi/video/VGA/LCD/brightness
levels: 20 24 29 36 44 53 63 76 100
current: 44

[Tim Eager (tim-eager)]

Same behavior with mainline kernel:

Linux version 2.6.34-020634rc3-generic (root@zinc) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #020634rc3 SMP Tue Apr 6 11:48:30 UTC 2010

[Teo (teo1978)]

Same problem here with Ubuntu 10.04 on an Asus m51sn laptop.

There seem to be quite a few duplicates of this bug (well I don't know which is the duplicate of which but this has been confirmed at least).

I'm not 100% sure, but these:
275902
480412
504998
seem all to describe the same problem or very similar.

By the way as a workaround I unplug and replug the power adapter and brightness goes back to its normal value (the very moment I _un_plug it, it gets brighter, though not full brightness, as it goes to the brightness level of battery mode, which is brighter than the buggy dark of a resumed suspend state; then after replugging it gets back to full brightness)

[jokerejoker (jokerejoker)]

I have the same problem in ubuntu 10.10 maverick.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.