Re: [gentoo-dev] Broken Sound in KDE3

[Paul de Vrieze]

On Saturday 25 May 2002 22:11, Rob W wrote:
>
> My ISAPNP SB16 card is not working in Gentoo 2.4.19-gentoo in KDE3, with
> newly emerged ALSA driver, utils, tools, you name it. I remembered to
> 'rc-update add alsa boot' (note: boot, not default, as per a recent post
> here[on Gentoo forum-Hardware], although default does not work either
> and gives the same errors). Also, I did depmod -a, which yields 5
> 'unresolved symbols'errors in
> /lib/modules/2.4.19-gentoo/kernel/sound/pci/cs46xx/snd-cs46xx.o,
> ~/sound/pci/snd-cs4281.o
> ~snd-es1938.o,
> ~snd-sonicvibes.o
> ~/pci/trident/snd-trident-o.
>
> The card is recognized at boot, the alsa module (snd-sb16) and oss
> modules (snd-mixer-oss and snd-pcm-oss) load, but the ALSA module then
> generates errors complaining of 'hooks failed' and such. Below is the
> text, hand-typed into this message because cut-and-paste does not work
> across these apps:[sorry, relative newbie here, I'm sure there's a way
> to pipe the output into a text editor]
>
> ALSA lib conf.c:1520:(snd_config_load1) _toplevel_:6:8:Unexpected char
> ALSA lib conf.c:2616:(snd_config_hook_load) /etc/asound.conf may be old
> or corrupted: consider to remove or fix it
> ALSA lib conf.c:2463:(snd_config_hooks_call) function
> snd_config_hook_load returned error: Unknown error
> ALSA lib conf.c:2859:(snd_config_update_r) hooks failed, removing
> configuration
>
> This same error is generated if I type 'amixer' at the CLI. So I renamed
> /etc/asound.conf and sure enough, the error message went away, and all I
> got was an 'asound.conf missing' error.
>
> Oddly, after I unmuted amixer (only possible with /etc/asound.conf
> renamed, i.e., absent) I was able to play the pop.wav sound from the
> CLI. No other sound works, though: nothing in KDE Control Center, and
> nothing from xmms. KDE is set to use the ALSA sound system in Control
> Center, although it does not work if I select OSS either.
>
> I did a google search for unresolved symbol errors in sound, and got
> nothing useful.
>
> Was the ALSA system in Gentoo just updated so that my asound.conf is now
> broken? How can I fix it? This sound card used to work perfectly in Gentoo!
>
> Sorry this is so verbose, but I hope the detail helps.

The alsa version has been upgraded to a really new version. This has a number 
of consequences. For one the module names do not longer have a card part in 
them. Also the initscript has been renamed. The unresolved symbols are 
probably the result of lingering old alsa modules, so first start with 
removing the old versions of alsa-driver.

Good luck,
Paul

-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@××××××.nl
Homepage: http://www.devrieze.net