Date: Mon, 19 Nov 2007 07:34:43 +0100
Message-ID: <s5hy7cubv5o.wl%tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: Jim Faulkner <jfaulkne@ccs.neu.edu>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: sb live (emu10k1) stops working between 2.6.23.1 and 2.6.23.7
In-Reply-To: <Pine.GSO.4.58.0711171201260.20067@denali.ccs.neu.edu>
References: <Pine.GSO.4.58.0711161613070.9346@denali.ccs.neu.edu>
	<Pine.GSO.4.58.0711171201260.20067@denali.ccs.neu.edu>
User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta28)
 (fuki) (+CVS-20070806) (i386-suse-linux)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1815
Lines: 41

At Sat, 17 Nov 2007 12:18:29 -0500 (EST),
Jim Faulkner wrote:
> 
> 
> I've done some more testing this morning, and it appears that the "ALSA:
> emu10k1 - Fix memory corruption" patch from 2.6.23.6 has broken digital
> output on my SB Live Value card.  Simply replacing the 2.6.23.7 emumixer.c
> with the version included in 2.6.23.1 I was able to get digital output
> working again under 2.6.23.7.
> 
> This does not appear to be a simple matter of adjusting the alsa mixer to
> compsensate for how the mixer controls are exposed to userspace.  I have
> duplicated all alsamixer settings between 2.6.23.1 and stock 2.6.23.7 in
> the "F5" view all controls mode, but still received no audio output.  I
> also tried adjusting other volume controls which normally do not need
> adjusting, but got nowhere.  It appears that the 2.6.23.6 emu10k1 patch
> broke digital output entirely on this card.
> 
> Just to add to the information in my first message, the SB Live card is
> connected from the yellow jack on the card to the "Digital Coax Input"
> connector on my external amplifier.

It's no regression of the driver.  The problem is just a wrong use of
alsactl in your init script.  It should use -F option to ignore
unmatching elements, which is caused when a mixer element is removed
or renamed.

This problem doesn't happen so often (as we try to keep the
compatibility as much as possible), so I didn't realize some distros 
still doing wrong for years.

Anyway, this won't be a problem in future since I changed the default
behavior of alsactl to with -F.


Takashi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/