Problem with HP Touchsmart tm2 backlight

Bug #697514 reported by Robert Ou
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Ubuntu does not always turn on the backlight properly for the HP Touchsmart tm2 laptop. I have debugged this issue and it seems to be related to the _BCL ACPI function.

The original code is:
                    Method (OBCL, 0, NotSerialized)
                    {
                        BINI ()
                        If (LEqual (IOSR, One))
                        {
                            Return (Package (0x0D)
                            {
                                0x64,
                                0x3C,
                                0x06,
                                0x0A,
                                0x14,
                                0x1E,
                                0x28,
                                0x32,
                                0x3C,
                                0x46,
                                0x50,
                                0x5A,
                                0x64
                            })
                        }
                        Else
                        {
                            Store (Package (0x0D)
                                {
                                    0x64,
                                    0x3C,
                                    Zero,
                                    0x0A,
                                    0x14,
                                    0x1E,
                                    0x28,
                                    0x32,
                                    0x3C,
                                    0x46,
                                    0x50,
                                    0x5A,
                                    0x64
                                }, Local0)
                            If (LEqual (OSYS, 0x07D6))
                            {
                                Return (Package (0x0D)
                                {
                                    0x64,
                                    0x3C,
                                    0x06,
                                    0x0A,
                                    0x14,
                                    0x1E,
                                    0x28,
                                    0x32,
                                    0x3C,
                                    0x46,
                                    0x50,
                                    0x5A,
                                    0x64
                                })
                            }

                            Return (Local0)
                        }
                    }
In this original code, if IOSR isn't 1 and the OS is not Vista, the backlight table will contain 0 for the third entry instead of 6. If Linux sets the backlight to 0, it doesn't seem to be able to turn it on again. I don't know what conditions will cause IOSR to change. Hacking the code to the following seems to fix it and does not affect Windows 7, but I feel that hacking the BIOS is not the best solution and the best long term solution is to make Linux work around the issue:
                    Method (OBCL, 0, NotSerialized)
                    {
                        BINI ()
                        Return (Package (0x0D)
                        {
                            0x64,
                            0x3C,
                            0x06,
                            0x0A,
                            0x14,
                            0x1E,
                            0x28,
                            0x32,
                            0x3C,
                            0x46,
                            0x50,
                            0x5A,
                            0x64
                        })
                    }

An unrelated issue is that there is only one _BQC function for the two graphics cards (Intel, ATI), which confuses Linux and makes it unable to correctly determine the current backlight level, which confuses the GNOME backlight widget. I haven't been able to fix this one.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-24-generic 2.6.35-24.42
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices: aplay: device_list:235: no soundcards found...
Architecture: amd64
ArecordDevices: arecord: device_list:235: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Jan 4 21:10:33 2011
HibernationDevice: RESUME=UUID=0e1f69a5-b0a9-489b-97d9-f7ab6df34bfb
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic root=UUID=3a3bdef2-d2b1-42e9-b4f4-8774f733d24a ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 07/30/2010
dmi.bios.vendor: Insyde
dmi.bios.version: F.12
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1486
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 83.1A
dmi.chassis.asset.tag: CNU03037KH
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/30/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr0489200000252A20001220000:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP TouchSmart tm2 Notebook PC
dmi.product.version: 0489200000252A20001220000
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Robert Ou (some-h4x0r) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Robert,

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: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Robert Ou (some-h4x0r) wrote :

Just tested linux-image-2.6.37-999-generic_2.6.37-999.201101131119_amd64, which did not fix either problem (backlight turns off, _BQC).

tags: removed: needs-upstream-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Robert Ou (some-h4x0r) wrote :

AFAIK this hasn't been fixed yet

Changed in linux (Ubuntu):
status: Expired → New
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
ManDay (manday) wrote :

I filed a bug at https://bugzilla.kernel.org/show_bug.cgi?id=34582 a few days ago. I've found similar reports everywhere, this is by far the closes to any solution I've seen. Thanks! I hope things get upstream and get fixed asap.

Revision history for this message
Maarten Bezemer (veger) wrote :

Thanks for taking the time to report this bug in the upstream bug tracking system this is a tremendous help. Launchpad has the ability to watch lots of upstream bug trackers and this can be done by following the procedure documented at https://wiki.ubuntu.com/Bugs/Watches. I've added the bug watch for this bug report.

Changed in linux:
importance: Unknown → Medium
status: Unknown → Incomplete
Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
penalvch (penalvch) wrote :

Robert Ou, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, 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 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 and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

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.

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

where VERSION-NUMBER is the version number of the kernel you tested.

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

where VERSION-NUMBER is the version number of the kernel you tested.

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

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
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.