public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Andrew Morton <akpm@osdl.org>,
	Mark Canter <marcus@vfxcomputing.com>,
	rlrevell@joe-job.com, nish.aravamudan@gmail.com,
	linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: intel 8x0 went silent in 2.6.11
Date: Tue, 08 Mar 2005 12:53:23 +0100	[thread overview]
Message-ID: <s5h1xaquzf0.wl@alsa2.suse.de> (raw)
In-Reply-To: <422CFB6E.1020002@drzeus.cx>

At Tue, 08 Mar 2005 02:10:06 +0100,
Pierre Ossman wrote:
> 
> Takashi Iwai wrote:
> 
> >>>Look at /etc/asound.state whether it contains the value of "Headphone
> >>>Jack Sense" control true or false.
> >>> 
> >>>
> >>>      
> >>>
> >>It saves the setting once I've been in 2.6.11. From an earlier kernel
> >>there is no such entry.
> >>    
> >>
> >
> >Of course, the earlier version didn't have this.
> >
> >And did you take a look at the latest content?  What stands on it?
> >Maybe you once saved a value wrongly corrected by any reason?
> >
> >  
> >
> I'm not sure what you mean. In the 2.6.10 version the last entry is 
> 'Stereo Mic'. In 2.6.11 there's 'Headphone Jack Sense' and 'Line Jack 
> Sense' following that.
>  From what I can tell every entry seems valid.

My question is its 'value'.  The entry in /etc/asound.state should
have a boolean value.

Let me repeat the explanation of the situation:

The existence of 'Headphone Jack Sense' and 'Line-in Jack Sense'
controls themselves are not the problem.  If they are set off, the
behavior of the driver must be identical with the older version.
No regression. The patch I mentionted turns off them as default unless
the device is known to work.  But the controls still exist, and you
can change them afterward manually.

So, the solution is once to turn off these controls via a mixer and
save the state via alsactl (usually the system does at shutdown), so
that the correct states are restored at the next reboot.  That's why I
asked you - to check the saved status of these controls.

If the correct values are saved there and still the problem exists,
someone else must have changed the mixer status.  For example, KDE
(kmix) seems to set up the mixer status by itself, and does not always
correctly.  That was my suspect.  I don't know GNOME does something
like that, too.


Takashi

  reply	other threads:[~2005-03-08 11:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 12:51 intel 8x0 went silent in 2.6.11 Pierre Ossman
2005-03-03 17:45 ` Nish Aravamudan
2005-03-03 18:46   ` Mark Canter
2005-03-03 18:52     ` [Alsa-devel] " Lee Revell
2005-03-03 19:06       ` Mark Canter
2005-03-03 19:09         ` Lee Revell
     [not found]           ` <Pine.LNX.4.62.0503031410450.19015@krusty.vfxcomputing.com>
2005-03-03 19:22             ` Lee Revell
     [not found]             ` <29495f1d050303114379ab96b5@mail.gmail.com>
2005-03-03 19:47               ` Lee Revell
2005-03-03 20:33           ` Mark Canter
2005-03-03 23:49             ` Andrew Morton
2005-03-04  0:37               ` Pierre Ossman
2005-03-04 21:16                 ` Pierre Ossman
2005-03-05 19:00                   ` Lee Revell
2005-03-07 20:13                     ` Pierre Ossman
2005-03-07 20:26                       ` Takashi Iwai
2005-03-07 13:50                   ` Takashi Iwai
2005-03-07 20:16                     ` Pierre Ossman
2005-03-07 20:21                       ` Takashi Iwai
2005-03-08  1:10                         ` Pierre Ossman
2005-03-08 11:53                           ` Takashi Iwai [this message]
2005-03-08 12:46                             ` Pierre Ossman
2005-03-09  1:53                             ` Mark Canter
2005-03-09  3:02                               ` Lee Revell
2005-03-04  2:50               ` Mark Canter
2005-03-04  5:13           ` Jeff Garzik
2005-03-04 18:02             ` Lee Revell
2005-03-03 19:42         ` Nish Aravamudan
2005-03-04 20:40       ` Bill Davidsen
2005-03-04 20:44         ` Lee Revell
2005-03-04 20:44         ` Mark Canter
2005-03-04  0:36   ` Pierre Ossman
2005-03-04 20:36   ` Bill Davidsen
2005-03-04 21:06     ` Lee Revell

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=s5h1xaquzf0.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcus@vfxcomputing.com \
    --cc=nish.aravamudan@gmail.com \
    --cc=rlrevell@joe-job.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