Anytime I use sndconfig to set up my S3 SonicVibes sound
card, it correctly autodetects the sound card but when it
attempts to play the sample sound, it fails with the
"Device or resource busy" message. Manual configuration
doesn't work, either. HELP! Is this a known bug in 5.2?
This worked in Redhat 5.1. Is there a patch? A known
workaround? A fix expected in 5.3/6.0?? I'd really love
to get sound working... Thanks!!!
- Eric Wolf
Two more things... The exact error from sndconfig is...
ZDDDDDDDDDDDD4 modprobe error CDDDDDDDDDDDD?
3 The following error occurred running 3
3 the modprobe program: 3
3 /lib/modules/preferred/misc/sonicvibes. 3
3 o: init_module: Device or resource busy 3
3 ZDDDD? 3
3 3 Ok 3 3
3 @DDDDY 3
and my /etc/conf.modules looks like:
alias scsi_hostadapter aic7xxx
alias eth0 tlan
alias sound sonicvibes
I just noticed this via the "dmesg" command... I am assuming that
"sv" is sonicvibes. Is that right? Does the below mean that
something else is using IRQ 11? if that is the case, what options
can I use to re-assign the IRQ to something else? Thanks!
sv: version v0.5 time 22:32:15 Oct 13 1998
sv: io ports: 0x1020 0x1030 0x1048 0x104c 0x1040 0xac00 0xac10
sv: irq 11 in use
I'm assuming you mean that manual config worked in 5.1,
as sndconfig didn't support it then. You can look
at /proc/pci and /proc/interrupts - is something else using IRQ 11
according to those?
closed due to lack of response.