alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: giggz <giggzounet@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [Regression] With the new 2.6.33 when I plug headphones, the speaker doen't get off anymore
Date: Mon, 01 Mar 2010 14:31:10 +0100	[thread overview]
Message-ID: <s5hzl2s2mox.wl%tiwai@suse.de> (raw)
In-Reply-To: <4B8A7DC5.1050302@gmail.com>

At Sun, 28 Feb 2010 15:29:25 +0100,
giggz wrote:
> 
> giggz a écrit :
> > giggzounet a écrit :
> >> Hi,
> >>
> >> I have installed debian stable lenny + backports on an eeepc 1201n. With
> >> the 2.6.30 or 2.6.32 from lenny-backport I don't have problem with sound
> >> : when I plug the headphones, speakers get off.
> >>
> >> I have tested with 2.6.33 and when I plug headphones, speakers don't get
> >> off anymore. so I have sound in headphones and speakers.
> >>
> >> 22:42 giggz@baal ~ % cat /proc/asound/card0/codec#* | grep Codec
> >> Codec: Realtek ALC269
> >> Codec: Nvidia MCP7A HDMI
> >>
> >> I attach the output of alsa-info with the 2.6.32.9 and the 2.6.33 (I'm
> >> in a Uni Campus and it's quite difficult to have internet on a external
> >> laptop...so I attach them at this mail and I don't upload them on pastbin).
> >>
> >> I have opened a bug on the kernel bugzilla (bug 15399). Should I provide
> >> anything more ?
> >>
> > 
> > Following the advice of Paul Menzel I did a "diff" of the sources of the
> > 2.6.32.9 kernel and of the 2.6.33. In patch_realtek.c, we see that there
> > is an new snd_hda_jack_detect funtion with 2 arguments. I have noticed
> > that the second argument is "normaly" the second argument of
> > snd_hda_codec_read. In the alc269_speaker_automute function there is
> > this new snd_hda_jack_detect function, but the second argument is "nid".
> > But in the old alc269_speaker_automute of the 2.6.32.9 the second
> > argument of snd_hda_codec_read is 0x15. So I think there is perhaps a
> > bug here...But I hesitate to modify the source...so I'm waiting the
> > anwser of the dev.
> > 
> > --- patch_realtek.c	2010-02-27 14:58:06.000000000 +0100
> > +++ patch_realtek_modif.c	2010-02-27 14:58:54.000000000 +0100
> > @@ -13381,7 +13381,7 @@
> >  	unsigned int present;
> >  	unsigned char bits;
> > 
> > -	present = snd_hda_jack_detect(codec, nid);
> > +	present = snd_hda_jack_detect(codec, 0x15);
> >  	bits = present ? AMP_IN_MUTE(0) : 0;
> >  	snd_hda_codec_amp_stereo(codec, 0x0c, HDA_INPUT, 0,
> >  				AMP_IN_MUTE(0), bits);
> > 
> 
> I tested it. And with this modif in the kernel, after recompilation and
> reboot, my problem is headphones and speaker is gone.

It implies that the setup of the headphone pin is wrong.  This doesn't
mean a bug of the driver, though.  It might have uncovered the BIOS
bug.

Could you provide alsa-info.sh without your patch to check the setup?


thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2010-03-01 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26  9:03 [Regression] With the new 2.6.33 when I plug headphones, the speaker doen't get off anymore giggzounet
2010-02-26  9:33 ` [Regression] With the new 2.6.33 when I plug in headphones, the speakers don't turn " Paul Menzel
2010-02-26 11:12   ` giggzounet
2010-02-26 11:15     ` giggzounet
2010-02-26 11:42       ` Paul Menzel
2010-02-26 12:09         ` giggzounet
2010-02-26 14:00         ` giggzounet
2010-02-26 22:34           ` Paul Menzel
2010-02-27 13:35             ` giggz
2010-02-27 13:29       ` giggz
2010-02-27 13:59 ` [Regression] With the new 2.6.33 when I plug headphones, the speaker doen't get " giggz
2010-02-28 14:29   ` giggz
2010-03-01 13:31     ` Takashi Iwai [this message]
2010-03-01 13:44       ` giggzounet
2010-03-01 18:06       ` giggz

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=s5hzl2s2mox.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=giggzounet@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).