keyboard buttons for changing volume level stops working on asus eeepc 1005ha

Bug #805218 reported by Dmitry Marin
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Seth Forshee
Oneiric
Fix Released
Medium
Seth Forshee

Bug Description

It's perfecly work in Ubuntu 11.04 but now in 11.10 Alfa it does'nt (Fn+F11/12/10). Brightness keys work well...

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: alsa-base 1.0.24+dfsg-0ubuntu2
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
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: corvax 1661 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 45'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,104383ce,00100004'
   Controls : 14
   Simple ctrls : 9
Date: Sun Jul 3 23:28:43 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=ru_RU.utf8
 LC_MESSAGES=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Internal Audio - HDA Intel
Symptom_Type: Volume slider, or mixer problems
Title: [HDA-Intel - HDA Intel, playback] volume slider problem
UpgradeStatus: Upgraded to oneiric on 2011-07-03 (0 days ago)
UserAsoundrc:
 #pcm.pulse { type pulse }
 #ctl.pulse { type pulse }
 #pcm.!default { type pulse }
 #ctl.!default { type pulse }
dmi.bios.date: 04/29/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1103
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005P
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1103:bd04/29/2010:svnASUSTeKComputerINC.:pn1005PE:pvrx.x:rvnASUSTeKComputerINC.:rn1005P:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005PE
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Dmitry Marin (corvax-corvax) wrote :
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Confirmed on a eeepc 1015pe.

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Changed in linux (Ubuntu Oneiric):
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
tags: added: regression-release
Revision history for this message
Seth Forshee (sforshee) wrote :

Please start with the steps under the "Step-by-step Troubleshooting" section of the following wiki page. This will help determine what component is causing the problem.

https://wiki.ubuntu.com/Hotkeys/Troubleshooting

Also provide the output of lsmod to see which kernel modules are loaded. Thanks!

Changed in linux (Ubuntu Oneiric):
assignee: Canonical Kernel Team (canonical-kernel-team) → Seth Forshee (sforshee)
status: Confirmed → Incomplete
Revision history for this message
Dmitry Marin (corvax-corvax) wrote :

xev (and showkey in console) doesn't show any code for Fn-F11. I think it's something with eeepc_laptop module, that don't load:
corvax@corvax-nb:~$ sudo modprobe eeepc-laptop
[sudo] password for corvax:
FATAL: Error inserting eeepc_laptop (/lib/modules/3.0-3-generic/kernel/drivers/platform/x86/eeepc-laptop.ko): No such device

Key press don't generate keycode...

Revision history for this message
Seth Forshee (sforshee) wrote :

Did you try the instructions from the "Fixing broken keys" section of /usr/share/doc/udev/README.keymap.txt.gz, as suggested in the wiki? What about acpi_listen?

Please run the following commands (you may need to run 'sudo apt-get install input-utils' first, if you haven't already):

  lsmod > lsmod.txt
  udevadm info --export-db > udev-db.txt
  cat /var/log/udev > udev.log
  lsinput > lsinput.txt

Then attach lsmod.txt, udev-db.txt, udev.log, and lsinput.txt to this bug report. Thanks!

Revision history for this message
Dmitry Marin (corvax-corvax) wrote :

Sorry, I forgeted to write that acpi_listen doesn't show anything. And
"/lib/udev/keymap -i input/event4" too.
And I was wrong: this netbok not Asus 1005HA, but 1005PE if it's important.

Revision history for this message
Seth Forshee (sforshee) wrote :

I see what's wrong. CONFIG_EEEPC_WMI was mistakenly disabled in oneiric due to some rejiggering in the Kconfig file. eeepc-wmi is the module you need, not eeepc_laptop.

I'm kicking off a test build now. It's end-of-day for me, so I'll post it tomorrow for verification.

Revision history for this message
Dmitry Marin (corvax-corvax) wrote :

Thanks, Seth. I hope it will help :)

Revision history for this message
Seth Forshee (sforshee) wrote :

The test build is available at:

http://people.canonical.com/~sforshee/lp805218/linux-3.0-3.4~lp805218v201107052231/

Please report back here whether or not this fixes your issue. Thanks!

Revision history for this message
Dmitry Marin (corvax-corvax) wrote :

Hello!
xev shows right events for Fn-keys:

 KeyRelease event, serial 41, synthetic NO, window 0x3800001,
   root 0xaa, subw 0x0, time 226120, (22,-10), root:(813,43),
   state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
   XLookupString gives 0 bytes:
   XFilterEvent returns: False

KeyPress event, serial 41, synthetic NO, window 0x3800001,
   root 0xaa, subw 0x0, time 227022, (22,-10), root:(813,43),
   state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
   XLookupString gives 0 bytes:
   XmbLookupString gives 0 bytes:
   XFilterEvent returns: False

KeyRelease event, serial 41, synthetic NO, window 0x3800001,
   root 0xaa, subw 0x0, time 227022, (22,-10), root:(813,43),
   state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
   XLookupString gives 0 bytes:
   XFilterEvent returns: False

corvax@corvax-nb:~$ lsmod|grep eee
eeepc_wmi 12685 0
asus_wmi 19333 1 eeepc_wmi

Now I need only find a method how to bind this keys for volume change in
new gnome3 with this awfull unity :-)

Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Oneiric):
status: Incomplete → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.0.0-4.5

---------------
linux (3.0.0-4.5) oneiric; urgency=low

  [ Ming Lei ]

  * SAUCE: fix yama_ptracer_del lockdep warning
    - LP: #791019

  [ Seth Forshee ]

  * SAUCE: (drop after 3.0) asus-wmi: Add callback for hotkey filtering
  * SAUCE: (drop after 3.0) eeepc-wmi: Add support for T101MT Home/Express Gate key
  * SAUCE: (drop after 3.0) asus-wmi: Enable autorepeat for hotkey input device
  * [Config] CONFIG_{ASUS,ASUS_NB,EEEPC}_WMI=m
    - LP: #805218

  [ Tim Gardner ]

  * [Config] updateconfigs after rebase to -rc6+
    Rebased against 4dd1b49c6d215dc41ce50c80b4868388b93f31a3
  * Adopt a 3 digit verion, e.g., 3.0.0-x.x
  * Revert "UBUNTU: add dependancies for module-init-tools"
    This dependency is no longer required for a 3 digit version.
 -- Tim Gardner <email address hidden> Tue, 05 Jul 2011 14:03:04 +0100

Changed in linux (Ubuntu Oneiric):
status: Fix Committed → Fix Released
Revision history for this message
Dmitry Marin (corvax-corvax) wrote :

With linux - 3.0.0-4.5 keycodes works correctly, but volume changing by keys don't work yet. I tried redefine audio keys In Settings-> Keyboard application and shotcuts was assigned right, but panel applet don't catch this hotkeys.

Revision history for this message
Seth Forshee (sforshee) wrote :

That's a desktop issue. You can try the following first (from https://wiki.ubuntu.com/Hotkeys/Troubleshooting):

for audio volume control hotkeys, gnome-sound-properties may be misconfigured. You can either examine with gconf-editor '/desktop/gnome/sound' or do 'gconftool --recursive-list /desktop/gnome/sound' to get the current settings; the particular configuration items are 'default_mixer_tracks' and 'default_mixer_device'.

If everything looks good there then we probably need a new task, I'm just not sure against what package. Maybe gnome-sound-properties?

Revision history for this message
Dmitry Marin (corvax-corvax) wrote :

Seth, it's ok already. Fixed in https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/805908
This bug may be closed now, thanks!

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.