alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: alsa-devel@alsa-project.org
Subject: Re: [solved] Conexant 5069: internal speakers are not muted when headphones are plugged in
Date: Sat, 05 Feb 2011 16:40:04 +0100	[thread overview]
Message-ID: <1296920404.3692.22.camel@mattotaupa> (raw)
In-Reply-To: <4D46A0C1.7010507@canonical.com>


[-- Attachment #1.1: Type: text/plain, Size: 2105 bytes --]

Am Montag, den 31.01.2011, 12:45 +0100 schrieb David Henningsson:
> On 2011-01-31 12:08, Paul Menzel wrote:

> > I encounter a problem with a Lenovo G555 where the internal speakers are
> > not muted when headphones are plugged in. Ubuntu 10.10 with Linux 2.6.35
> > [1] runs the Lenovo, but this seems to be a common problem [2][3].
> >
> > I tried to load the module with `model=lenovo`, but the only result was,
> > that the external speakers did not work at all. Do you have another idea
> > what to use for the `model`? The system has to rebooted every time,
> > since I cannot unload the module using
> >
> > 	sudo modprobe -r snd-hda-intel
> >
> > or
> >
> > 	sudo rmmod snd-hda-intel
> >
> > since it seems to be in use by the system.
> >
> > Seems like I missed `model=thinkpad` in [3]. But I do not have access to
> > the system right now, so I am sending this report anyway.
> >
> > Please find attached the output of `alsa-info.sh` with the default
> > behavior (headphones work, but internal ones are not muted) and with
> > `model=lenovo` (headphones do not work).
> >
> > David, do you know if your recent patches sent to this list
> >
> > [PATCH 2/2] ALSA: HDA: Add a new model "asus" for Conexant 5066/205xx [5]
> > [PATCH] ALSA: HDA: Add Lenovo vendor quirk for Conexant 205xx [6]
> >
> > will also address this issue¹? They are for 5066 and I have 5069
> > according to [2]. If yes, is there a package repository with a package
> > having this patches applied I can install using the package management
> > system?
> 
> You have an internal mic at 0x1a, so it seems like model=asus would be 
> the one for you. But if you just want headphones automuting, 
> model=ideapad or model=thinkpad should do as well.

For now automuting headphones is good enough and `model=thinkpad` works
as expected.

Can you give an estimate when a package with your patch for `model=asus`
will be available? Or do I have to wait for Linux 2.6.38 [1]?


Thanks,

Paul


[1] http://mailman.alsa-project.org/pipermail/alsa-devel/2011-January/036183.html

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

  reply	other threads:[~2011-02-05 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 11:08 Conexant 5069: internal speakers are not muted when headphones are plugged in Paul Menzel
2011-01-31 11:45 ` David Henningsson
2011-02-05 15:40   ` Paul Menzel [this message]
2011-02-07  5:31     ` [solved] " Steven Rosenberg

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=1296920404.3692.22.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --cc=alsa-devel@alsa-project.org \
    /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).