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
Date: Mon, 19 Nov 2007 07:34:43 +0100 [thread overview]
Message-ID: <s5hy7cubv5o.wl%tiwai@suse.de> (raw)
In-Reply-To: <Pine.GSO.4.58.0711171201260.20067@denali.ccs.neu.edu>
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
next prev parent reply other threads:[~2007-11-19 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 21:30 Jim Faulkner
2007-11-17 17:18 ` Jim Faulkner
2007-11-19 6:34 ` Takashi Iwai [this message]
2007-11-18 9:41 Nick Warne
[not found] <20071119225542.1e0577e4@linuxamd.linicks.net>
2007-11-20 0:12 ` Jim Faulkner
[not found] <9qhy2-5v-13@gated-at.bofh.it>
[not found] ` <9qzv5-36l-21@gated-at.bofh.it>
[not found] ` <1a8e6a68-053a-4148-83b9-417bcd19b732@e4g2000hsg.googlegroups.com>
2007-12-21 14:44 ` Jim Faulkner
2007-12-21 13:06 ` Takashi Iwai
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=s5hy7cubv5o.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=gregkh@suse.de \
--cc=jfaulkne@ccs.neu.edu \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®