Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Munzir Taha (منذر طه)" <munzirtaha@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: My Codec: IDT 92HD75B3X5 issues
Date: Tue, 29 Sep 2009 07:40:56 +0300	[thread overview]
Message-ID: <200909290740.57029.munzirtaha@gmail.com> (raw)
In-Reply-To: <s5hfxa74g1b.wl%tiwai@suse.de>

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.
> >
> > 1. No sense for headphone jack (jack_present?), when headphone is plugged
> > (present_int_hp?)
> >
> > 2. 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. 

> > 3. 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?

-- 
Munzir Taha
Telecommunications and Electronics Engineer
Master CIW Designer, ICDL, MOUS, Linux+, LPI, SCSA
Riyadh, SA

  reply	other threads:[~2009-09-29  4:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28  3:58 My Codec: IDT 92HD75B3X5 issues Munzir Taha (منذر طه)
2009-09-28  8:41 ` Takashi Iwai
2009-09-29  4:40   ` Munzir Taha (منذر طه) [this message]
2009-09-29  6:24     ` Takashi Iwai
2009-09-29 13:24       ` Munzir Taha (منذر طه)
2009-09-29 14:37         ` Takashi Iwai
2009-09-29 19:50           ` Munzir Taha (منذر طه)
  -- strict thread matches above, loose matches on Subject: below --
2009-09-30  5:18 Munzir Taha (منذر طه)
2009-09-30  6:36 ` Takashi Iwai
2009-10-01 11:07   ` Munzir Taha (منذر طه)
2009-10-01 13:30     ` Takashi Iwai
2009-10-01 14:11       ` Munzir Taha (منذر طه)
2009-10-01 14:17         ` Takashi Iwai
2009-10-01 14:42       ` Takashi Iwai
2009-10-01 22:11         ` Munzir Taha (منذر طه)
2009-10-02  5:34           ` Takashi Iwai
2009-10-02  6:15             ` Munzir Taha (منذر طه)
2009-10-02  6:37               ` Takashi Iwai
2009-10-02 11:24                 ` Munzir Taha (منذر طه)
2009-10-02 11:45                   ` Takashi Iwai
2009-10-02 16:07                     ` Munzir Taha (منذر طه)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200909290740.57029.munzirtaha@gmail.com \
    --to=munzirtaha@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox