All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Andrew Morton <akpm@osdl.org>,
	Mark Canter <marcus@vfxcomputing.com>,
	nish.aravamudan@gmail.com, linux-kernel@vger.kernel.org,
	alsa-devel@lists.sourceforge.net
Subject: Re: Re: intel 8x0 went silent in 2.6.11
Date: Sat, 05 Mar 2005 14:00:47 -0500	[thread overview]
Message-ID: <1110049247.12201.11.camel@mindpipe> (raw)
In-Reply-To: <4228D013.8010307@drzeus.cx>

On Fri, 2005-03-04 at 22:16 +0100, Pierre Ossman wrote:
> Pierre Ossman wrote:
> > Andrew Morton wrote:
> > 
> >> Mark Canter <marcus@vfxcomputing.com> wrote:
> >>  
> >>
> >>> To close this issue out of the LKML and alsa-devel, a bug report has 
> >>> been written.
> >>>
> >>> It appears to be an issue with the 'headphone jack sense' (as kde 
> >>> labels it).  The issue is in the way the 8x0 addresses the docking 
> >>> station/port replicator's audio output jack.  The mentioned quick fix 
> >>> does not work for using the ds/pr audio output, but does resolve it 
> >>> for a user that is only using headphones/internal speakers.
> >>>   
> >>
> >>
> >> But there was a behavioural change: applications which worked in 2.6.10
> >> don't work in 2.6.11, is that correct?
> >>
> >> If so, the best course of action is to change the kernel so those
> >> applications work again.  Can that be done?
> >>
> >>  
> >>
> > Yes. Speakers worked in 2.6.10 and stopped working in 2.6.11. This could 
> > be changed by setting the default for the two new volumes to muted. I 
> > don't know how this affects the issue with the docking station or the 
> > bug that this is supposed to solve though.
> > 
> 
> It seems I spoke too soon. The defaults picked by the driver are 
> actually fine. It seems to be alsactl store/restore that did something 
> strange when coming from an older kernel.
> 

So is there a bug or not?  Mark seems to be the only one affected.

It's important to follow up, because these so-called "ALSA regressions"
are generating bad press.

Lee



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

WARNING: multiple messages have this Message-ID (diff)
From: Lee Revell <rlrevell@joe-job.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Andrew Morton <akpm@osdl.org>,
	Mark Canter <marcus@vfxcomputing.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: Sat, 05 Mar 2005 14:00:47 -0500	[thread overview]
Message-ID: <1110049247.12201.11.camel@mindpipe> (raw)
In-Reply-To: <4228D013.8010307@drzeus.cx>

On Fri, 2005-03-04 at 22:16 +0100, Pierre Ossman wrote:
> Pierre Ossman wrote:
> > Andrew Morton wrote:
> > 
> >> Mark Canter <marcus@vfxcomputing.com> wrote:
> >>  
> >>
> >>> To close this issue out of the LKML and alsa-devel, a bug report has 
> >>> been written.
> >>>
> >>> It appears to be an issue with the 'headphone jack sense' (as kde 
> >>> labels it).  The issue is in the way the 8x0 addresses the docking 
> >>> station/port replicator's audio output jack.  The mentioned quick fix 
> >>> does not work for using the ds/pr audio output, but does resolve it 
> >>> for a user that is only using headphones/internal speakers.
> >>>   
> >>
> >>
> >> But there was a behavioural change: applications which worked in 2.6.10
> >> don't work in 2.6.11, is that correct?
> >>
> >> If so, the best course of action is to change the kernel so those
> >> applications work again.  Can that be done?
> >>
> >>  
> >>
> > Yes. Speakers worked in 2.6.10 and stopped working in 2.6.11. This could 
> > be changed by setting the default for the two new volumes to muted. I 
> > don't know how this affects the issue with the docking station or the 
> > bug that this is supposed to solve though.
> > 
> 
> It seems I spoke too soon. The defaults picked by the driver are 
> actually fine. It seems to be alsactl store/restore that did something 
> strange when coming from an older kernel.
> 

So is there a bug or not?  Mark seems to be the only one affected.

It's important to follow up, because these so-called "ALSA regressions"
are generating bad press.

Lee


  reply	other threads:[~2005-03-05 19:00 UTC|newest]

Thread overview: 55+ 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 20:33             ` [Alsa-devel] " Mark Canter
2005-03-03 23:49             ` Andrew Morton
2005-03-04  0:37               ` Pierre Ossman
2005-03-04  0:37                 ` [Alsa-devel] " Pierre Ossman
2005-03-04 21:16                 ` Pierre Ossman
2005-03-04 21:16                   ` [Alsa-devel] " Pierre Ossman
2005-03-05 19:00                   ` Lee Revell [this message]
2005-03-05 19:00                     ` Lee Revell
2005-03-07 20:13                     ` Pierre Ossman
2005-03-07 20:13                       ` [Alsa-devel] " Pierre Ossman
2005-03-07 20:26                       ` Takashi Iwai
2005-03-07 20:26                         ` [Alsa-devel] " Takashi Iwai
2005-03-07 13:50                   ` Takashi Iwai
2005-03-07 13:50                     ` [Alsa-devel] " Takashi Iwai
2005-03-07 20:16                     ` Pierre Ossman
2005-03-07 20:16                       ` [Alsa-devel] " Pierre Ossman
2005-03-07 20:21                       ` Takashi Iwai
2005-03-07 20:21                         ` [Alsa-devel] " Takashi Iwai
2005-03-08  1:10                         ` Pierre Ossman
2005-03-08  1:10                           ` [Alsa-devel] " Pierre Ossman
2005-03-08 11:53                           ` Takashi Iwai
2005-03-08 11:53                             ` [Alsa-devel] " Takashi Iwai
2005-03-08 12:46                             ` Pierre Ossman
2005-03-08 12:46                               ` [Alsa-devel] " Pierre Ossman
2005-03-09  1:53                             ` Mark Canter
2005-03-09  1:53                               ` [Alsa-devel] " Mark Canter
2005-03-09  3:02                               ` Lee Revell
2005-03-09  3:02                                 ` [Alsa-devel] " 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-03 19:42           ` [Alsa-devel] " Nish Aravamudan
2005-03-04 20:40       ` Bill Davidsen
2005-03-04 20:40         ` [Alsa-devel] " Bill Davidsen
2005-03-04 20:44         ` Lee Revell
2005-03-04 20:44           ` [Alsa-devel] " Lee Revell
2005-03-04 20:44         ` Mark Canter
2005-03-04 20:44           ` [Alsa-devel] " Mark Canter
2005-03-04  0:36   ` Pierre Ossman
2005-03-04 20:36   ` Bill Davidsen
2005-03-04 20:36     ` Bill Davidsen
2005-03-04 21:06     ` Lee Revell
2005-03-04 21:06       ` Lee Revell
2005-03-21 22:21 ` Andrew Morton
2005-03-21 22:47   ` Pierre Ossman

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=1110049247.12201.11.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.