brightness hotkeys not functional on Gigabyte Spring Peak

[Earl Malmrose]

The brightness hotkeys generate no events. Neither do the wifi, 3G, and BT toggle hotkeys. The volume hotkeys do work.

This is very similar to bug #571421, but on a different laptop.

$ /lib/udev/findkeyboards
AT keyboard: input/event5
$ sudo /lib/udev/keymap -i input/event5
Press ESC to finish
scan code: 0xAE key code: volumedown
scan code: 0xB0 key code: volumeup
scan code: 0xA0 key code: mute
scan code: 0x01 key code: esc
$ head /sys/class/dmi/id/sys_vendor
GIGABYTE
$ head /sys/class/dmi/id/product_name
Spring Peak

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: oem 1278 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x9a500000 irq 22'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:10ec0269,14581325,00100004 HDA:80862802,80860101,00100000'
   Controls : 16
   Simple ctrls : 8
Date: Fri May 14 10:54:00 2010
HibernationDevice: RESUME=UUID=46356722-1463-4e4a-b348-5c2ee34a3a3b
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: GIGABYTE Spring Peak
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=9fa07e57-4668-47f0-8779-81a7ae0ecb8d ro quiet splash i8042.noloop
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 02/05/2010
dmi.bios.vendor: GIGABYTE
dmi.bios.version: ASBF07
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: GA-XXXXXXX
dmi.board.vendor: GIGABYTE
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnGIGABYTE:bvrASBF07:bd02/05/2010:svnGIGABYTE:pnSpringPeak:pvrASBF07:rvnGIGABYTE:rnGA-XXXXXXX:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Spring Peak
dmi.product.version: ASBF07
dmi.sys.vendor: GIGABYTE

[Kamal Mostafa (kamalmostafa)]

The brightness keys (and other dysfunctional special keys) do generate "IO-APIC-fasteoi acpi" interrupts per /proc/interrupts, but no reaction from acpi_listen or /lib/udev/keymap.

The underlying ACPI brightness functionality works fine (/proc/acpi/fideo/OVGA/DD02/brightness).

[bhuvi (bhuvanesh)]

same problem for me on lenovo G550 laptop. https://bugs.launchpad.net/ubuntu/+source/udev/+bug/530238

[Q. Z. Zuo (zealotzuo)]

This bug seems to persist in oneiric for me.

Is there any update on the process of fixing it?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.

[penalvch (penalvch)]

Earl Malmrose, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try 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 run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

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

Also, if you could 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

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

[Daniel Gimpelevich (daniel-gimpelevich)]

Still an issue in Precise.

[Launchpad Janitor (janitor)]

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