At Mon, 13 Feb 2006 04:09:00 -0800,
Andrew Morton wrote:
>
>
>
> Begin forwarded message:
>
> Date: Sat, 14 Jan 2006 00:03:48 +0200
> From: ghrt <[email protected]>
> To: [email protected]
> Subject: PROBLEM: SB Live! 5.1 (emu10k1, rev. 0a) doesn't work with 2.6.15
>
>
> hello
>
> i've compiled vanilla 2.6.15 and my sound card doesn't work anymore.
> i can see it in kmix (and adjust the volumes, too), it appears in
> dmesg (at ALSA devices), xmms & mplayer doesn't say anything about
> errors, but it doesn't make any sound.
> the onboard soundcard, via8233, works well with the same 2.6.15.
> sb live! works well with 2.6.14.2 and previous.
> i'm using an updated Slackware.
>
> if you have any questions i'll answer.
First check /proc/asound/cards to see whether the emu10k1 model is
detected properly. If '[Unknown]' is shown, your model is not
listed in the whitelist.
There was a bug that the front control conflicts with ac97 and emu10k1
dsp which was already fixed in the latest version (at least on
2.6.16-rc3).
Takashi
> > i've compiled vanilla 2.6.15 and my sound card doesn't work anymore.
> > i can see it in kmix (and adjust the volumes, too), it appears in
> > dmesg (at ALSA devices), xmms & mplayer doesn't say anything about
> > errors, but it doesn't make any sound.
> > the onboard soundcard, via8233, works well with the same 2.6.15.
> > sb live! works well with 2.6.14.2 and previous.
> > i'm using an updated Slackware.
> >
> > if you have any questions i'll answer.
>
> First check /proc/asound/cards to see whether the emu10k1 model is
> detected properly. If '[Unknown]' is shown, your model is not
> listed in the whitelist.
>
> There was a bug that the front control conflicts with ac97 and emu10k1
> dsp which was already fixed in the latest version (at least on
> 2.6.16-rc3).
For what it is worth, I had issues with my SB Live! but as this all
(appeared) to start when my CPU died and I had to reset BIOS or if I
did indeed move up to 2.6.15 at around the same time I can't remember
(2.6.15 release and CPU died all around same date) - refer to the
following:
http://lkml.org/lkml/2006/2/11/4
As stated the solution for me was to update alsa-utils and alsa-libs
which fixed the issues I was getting - I found that if one of the
'controls' (15, I think?) was invalid at boot, all the volume settings
in alsamixer got set to '0' (i.e. mute/turned off) - no sound.
Nick
At Mon, 13 Feb 2006 18:54:22 +0000,
Nick Warne wrote:
>
> > > i've compiled vanilla 2.6.15 and my sound card doesn't work anymore.
> > > i can see it in kmix (and adjust the volumes, too), it appears in
> > > dmesg (at ALSA devices), xmms & mplayer doesn't say anything about
> > > errors, but it doesn't make any sound.
> > > the onboard soundcard, via8233, works well with the same 2.6.15.
> > > sb live! works well with 2.6.14.2 and previous.
> > > i'm using an updated Slackware.
> > >
> > > if you have any questions i'll answer.
> >
> > First check /proc/asound/cards to see whether the emu10k1 model is
> > detected properly. If '[Unknown]' is shown, your model is not
> > listed in the whitelist.
> >
> > There was a bug that the front control conflicts with ac97 and emu10k1
> > dsp which was already fixed in the latest version (at least on
> > 2.6.16-rc3).
>
> For what it is worth, I had issues with my SB Live! but as this all
> (appeared) to start when my CPU died and I had to reset BIOS or if I
> did indeed move up to 2.6.15 at around the same time I can't remember
> (2.6.15 release and CPU died all around same date) - refer to the
> following:
>
> http://lkml.org/lkml/2006/2/11/4
>
> As stated the solution for me was to update alsa-utils and alsa-libs
> which fixed the issues I was getting - I found that if one of the
> 'controls' (15, I think?) was invalid at boot, all the volume settings
> in alsamixer got set to '0' (i.e. mute/turned off) - no sound.
Such a problem is usually because of init script rather alsa-lib
version. It should call alsactl with -F option.
Takashi
> > http://lkml.org/lkml/2006/2/11/4
Sorry, my bad cut 'n' paste - link should be:
http://lkml.org/lkml/2006/2/11/43
Nick
> > As stated the solution for me was to update alsa-utils and alsa-libs
> > which fixed the issues I was getting - I found that if one of the
> > 'controls' (15, I think?) was invalid at boot, all the volume settings
> > in alsamixer got set to '0' (i.e. mute/turned off) - no sound.
>
> Such a problem is usually because of init script rather alsa-lib
> version. It should call alsactl with -F option.
I would agree - but I only have one asound.state file, and also doing
the upgrade to said alsa utils and libs *fixed* it...
On my system at least something was going awry.
Nick