On Tue, Sep 29, 2009 at 7:40 AM, Munzir Taha (منذر طه) munzirtaha@gmail.com wrote:
On Yaum al-Ithnain 08 Shawwal 1430 11:41:52 am Takashi Iwai wrote:
At Mon, 28 Sep 2009 06:58:46 +0300,
Munzir Taha (=?utf-8?q?=D9=85=D9=86=D8=B0=D8=B1?=
=?utf-8?q?_=D8=B7=D9=87?=) wrote:
Hi sirs, These are the issues I have with my Laptop HP Pavilion dv6 1225ee regarding audio support.
- No sense for headphone jack (jack_present?), when headphone is plugged
(present_int_hp?)
- There headphone mic jack is not working. The one next to the webcam is
always recording even when I change the "Mic Jack" control from "Mic In" to "Line In"
Make sure that you use alsa-driver-snapshot tarball instead of 1.0.21 released version. There are many fixes since 1.0.21 release.
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-sn apshot.tar.gz
Thanks a lot Takashi, things are better now. However, when I tested the internal mic it's very noisy. I played a bit with the capture and digital controls but still compared with Windows, it's lame.
- The mute/unmute LED doesn't change color to RED when its muted like in
Windows.
This isn't supported yet as we have no hardware information. Likely one of GPIO pins corresponds to the LED on/off. You can try hda-verb to change the GPIO data bit.
Ok, I will try it and report back.
Touching that LED shows this in /var/log/messages:
Sep 28 06:53:47 dv6 kernel: [ 9197.986789] atkbd.c: Unknown key released (translated set 2, code 0x94 on isa0060/serio0). Sep 28 06:53:47 dv6 kernel: [ 9197.986791] atkbd.c: Use 'setkeycodes e014 <keycode>' to make it known. Sep 28 06:53:47 dv6 kernel: [ 9198.353568] atkbd.c: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0). Sep 28 06:53:47 dv6 kernel: [ 9198.353572] atkbd.c: Use 'setkeycodes e014 <keycode>' to make it known. Sep 28 06:53:47 dv6 kernel: [ 9198.359205] atkbd.c: Unknown key released (translated set 2, code 0x94 on isa0060/serio0). Sep 28 06:53:47 dv6 kernel: [ 9198.359208] atkbd.c: Use 'setkeycodes e014 <keycode>' to make it known.
It's not about the sound driver but the input layer, as you can find. You can defien the scan code 0xe014 by yourself.
You are right. What's the best component to report this bug against? kernel?
Those keys are a 'HAL' thing. Until recently there has been a website by the HAL developer with detailed instructions. Search for 'HAL Quirk Site' on Google to view the site in Google cache. The website was not updated for some time (http://www.mail-archive.com/pm-utils@lists.freedesktop.org/msg01594.html) and being obsolete, it was probably taken down. Your changes would need to make it eventually to the hal-info repository, http://cgit.freedesktop.org/hal-info/ Use the Freedesktop Bugzilla, product 'hal' and component 'hal-info' when reporting, https://bugs.freedesktop.org/enter_bug.cgi?product=hal
Simos