Re: alsa: no device
Am Mit, 2002-11-13 um 04.13 schrieb Jack O'Quin:
>
> Seems like you need to find were the OSS driver is getting loaded.
> Try something like "grep cmpci /etc/modutils/*". If you can find an
> alias for that driver, comment it out, run update-modules and then
> reboot.
yes, i've done that. "lsmod | grep snd" now gives the following:
snd-pcm-oss 36100 1 (autoclean)
snd-mixer-oss 9216 1 (autoclean)
snd-cmipci 14820 2 (autoclean)
snd-pcm 49440 0 (autoclean) [snd-pcm-oss snd-cmipci]
snd-mpu401-uart 2704 0 (autoclean) [snd-cmipci]
snd-opl3-lib 5344 0 (autoclean) [snd-cmipci]
snd-hwdep 3680 0 (autoclean) [snd-opl3-lib]
snd-rawmidi 12864 0 [snd-mpu401-uart]
snd-timer 10432 0 [snd-pcm snd-opl3-lib]
snd-seq-device 3904 0 [snd-opl3-lib snd-rawmidi]
snd 25704 0 [snd-pcm-oss snd-mixer-oss snd-cmipci
snd-pcm snd-mpu401-uart snd-opl3-lib snd-hwdep snd-rawmidi snd-timer
snd-seq-device]
soundcore 3684 7 [snd]
unfortunately, programs relying on alsa still don't work. alsaplayer has
the most eloborated error message:
snd_pcm_open: No such file or directory (default)
/usr/lib/alsaplayer/output/libalsa.so failed to load
I could not find a suitable output module on your system. Make sure
they're in "usr/lib/alsaplayer/output/".
failed to load output add-on. exitting...
the output-directory just contains libalsa.so, but specifically loading
that output add-on results in a somewhat snappish "failed to load output
add-on. exitting..."
it seems to me, that i've come quite a long way, but still i can't use
alsa.
> I know nothing about either of these drivers or about this specific
> device. Sorry I can't help more. I hope someone else can fill in the
> blanks.
well, many thanks so far. anybody else any ideas?
thaden.
Reply to: