Re: sb live (emu10k1) stops working between 2.6.23.1 and 2.6.23.7

[Jim Faulkner <jfaulkne@ccs.neu.edu>]

Hi Brian,

The solution is here:
http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-11/msg06482.html

You just need to run "alsactl -F restore" to force restoration of your
previous settings.  This needs to be done while /etc/asound.state consists
of your settings that work correctly under your previous kernel.
Hopefully Fedora hasn't already overwritten /etc/asound.state, I actually
manually run alsactl from /etc/rc.local and disable the alsa service just
to prevent my settings from being overwritten.

If your settings have already been overwritten, you may need to boot into
the old kernel, get it working, save the alsamixer settings (alsactl
store), reboot to the new kernel, then run "alsactl -F restore".  A
hassle, I know.

You might want to report this bug to the Fedora bug tracking system -- in
my opinion these kind of changes should not be made just for a minor
kernel update.

I also wonder if it is even possible to get digital output working under
newer kernels without an existing asound.state -- I tried in vain for
hours to get it working again by just using alsamixer, and I wasn't
getting anywhere.  asound.state consists of 225 controls for my SB Live,
and only 40 or so are exposed in alsamixer.  I wonder if alsamixer isn't
exposing the necessary control to enable digital output under newer
kernels.

Jim


On Thu, 20 Dec 2007, Brian wrote:

> Hi Jim,
>
> I've come across the exact same issue with my Creative Audigy ZS 2 and
> its digital output...  the sound no longer works after I upgraded my
> kernel to 2.6.23.8-34.fc7 (I'm running Fedora 7).  Same error message
> when using alsactl, etc.  I'm trying to fix this, and I'm not quite
> sure exactly what you mean by "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".  Could you explain in
> further detail how I would go about doing this to fix this problem?
> Would this require the kernel to be recompiled with the different
> emumixer.c file?
>
> I'm starting to wonder if I should just wait it out for another kernel
> update that will hopefully have this issue fixed rather than spending
> so much time on it trying to fix it now.
>
> Any help you can provide is very much appreciated.
>
> Thanks in advance.
>
> Brian
>
--
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/