[SLE] unresolved symbols in sound.o
My Soundblaster 16 clone is failing to work with kernel sound in SuSE Linux 6.3 It is a PnP card and has the same pnp config as it had when it worked under 5.3 The error messages suggest to me that there is a version conflict among kernel modules, which can't be right can it? Messages follow. Yours, dproc # insmod sound Using /lib/modules/2.2.13/misc/sound.o /lib/modules/2.2.13/misc/sound.o: unresolved symbol sound_preinit_lowlevel_drivers /lib/modules/2.2.13/misc/sound.o: unresolved symbol unregister_sound_dsp /lib/modules/2.2.13/misc/sound.o: unresolved symbol sound_unload_lowlevel_drivers /lib/modules/2.2.13/misc/sound.o: unresolved symbol unregister_sound_midi /lib/modules/2.2.13/misc/sound.o: unresolved symbol register_sound_dsp /lib/modules/2.2.13/misc/sound.o: unresolved symbol register_sound_mixer /lib/modules/2.2.13/misc/sound.o: unresolved symbol unregister_sound_mixer /lib/modules/2.2.13/misc/sound.o: unresolved symbol unregister_sound_special /lib/modules/2.2.13/misc/sound.o: unresolved symbol register_sound_special /lib/modules/2.2.13/misc/sound.o: unresolved symbol sound_init_lowlevel_drivers /lib/modules/2.2.13/misc/sound.o: unresolved symbol register_sound_midi -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
dproc@dol.net wrote:
My Soundblaster 16 clone is failing to work with kernel sound in SuSE Linux 6.3
It is a PnP card and has the same pnp config as it had when it worked under 5.3
The error messages suggest to me that there is a version conflict among kernel modules, which can't be right can it?
Messages follow. Yours, dproc
# insmod sound Using /lib/modules/2.2.13/misc/sound.o /lib/modules/2.2.13/misc/sound.o: unresolved symbol sound_preinit_lowlevel_drivers /lib/modules/2.2.13/misc/sound.o: unresolved symbol unregister_sound_dsp /lib/modules/2.2.13/misc/sound.o: unresolved symbol sound_unload_lowlevel_drivers /lib/modules/2.2.13/misc/sound.o: unresolved symbol unregister_sound_midi /lib/modules/2.2.13/misc/sound.o: unresolved symbol register_sound_dsp /lib/modules/2.2.13/misc/sound.o: unresolved symbol register_sound_mixer /lib/modules/2.2.13/misc/sound.o: unresolved symbol unregister_sound_mixer /lib/modules/2.2.13/misc/sound.o: unresolved symbol unregister_sound_special /lib/modules/2.2.13/misc/sound.o: unresolved symbol register_sound_special /lib/modules/2.2.13/misc/sound.o: unresolved symbol sound_init_lowlevel_drivers /lib/modules/2.2.13/misc/sound.o: unresolved symbol register_sound_midi
I've seen stuff like that too, and solved the problem, but I can't remember precisely which action I took was the key. But here are some things to try: 1. As root, call "depmod" or "depmod -a" (they're equivalent, but people here seem to prefer "depmod -a". That will fix up the module dependency file. 2. Use lsmod to see what modules are loaded. If your sound card module isn't loaded, load it with "modprobe". Also do the same for "soundcore". Of course, if you have a kernel version conflict, that's an entirely different matter. Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Thu, 01 Jun 2000, Paul W. Abrahams wrote:
dproc@dol.net wrote:
My Soundblaster 16 clone is failing to work with kernel sound in SuSE Linux 6.3
It is a PnP card and has the same pnp config as it had when it worked under 5.3
The error messages suggest to me that there is a version conflict among kernel modules, which can't be right can it?
Messages follow. Yours, dproc
# insmod sound Using /lib/modules/2.2.13/misc/sound.o /lib/modules/2.2.13/misc/sound.o: unresolved symbol sound_preinit_lowlevel_drivers
...snip...
I've seen stuff like that too, and solved the problem, but I can't remember precisely which action I took was the key. But here are some things to try:
1. As root, call "depmod" or "depmod -a" (they're equivalent, but people here seem to prefer "depmod -a". That will fix up the module dependency file.
2. Use lsmod to see what modules are loaded. If your sound card module isn't loaded, load it with "modprobe". Also do the same for "soundcore".
Of course, if you have a kernel version conflict, that's an entirely different matter.
Not quite there yet. I fixed the dependencies - thanks Paul, but now when I try to play a sound, the modules try to autoload, and fail with the following messages: rplayd[6410]: connect from localhost insmod: /lib/modules/2.2.13/misc/sb.o: init_module: Device or resource busy insmod: /lib/modules/2.2.13/misc/sb.o: insmod char-major-14 failed kernel: Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 kernel: sb: dsp reset failed. rplayd[6413]: warning: can't get client address: Resource temporarily unavailable rplayd[6413]: refused connect from unknown I saw a reference to this error in the archive, but I am afraid I don't understand what to do to fix it. dproc -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
dproc@dol.net wrote:
but now when I try to play a sound, the modules try to autoload, and fail with the following messages:
rplayd[6410]: connect from localhost insmod: /lib/modules/2.2.13/misc/sb.o: init_module: Device or resource busy insmod: /lib/modules/2.2.13/misc/sb.o: insmod char-major-14 failed kernel: Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 kernel: sb: dsp reset failed. rplayd[6413]: warning: can't get client address: Resource temporarily unavailable rplayd[6413]: refused connect from unknown
Looks to me like the first message is the cause of all the others. It happened to me too because I thought I had an es1371 when I actually had an es1370. You might, as an experiment, load the es1370 driver instead of (or possibly even in addition to) the es1371 driver. It's not very likely to solve the problem since lspci indicated a 1371, but it's worth a try. Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Fri, 02 Jun 2000, Paul W. Abrahams wrote:
dproc@dol.net wrote:
but now when I try to play a sound, the modules try to autoload, and fail with the following messages:
rplayd[6410]: connect from localhost insmod: /lib/modules/2.2.13/misc/sb.o: init_module: Device or resource busy ..snip.. Looks to me like the first message is the cause of all the others.
It happened to me too because I thought I had an es1371 when I actually had an es1370. You might, as an experiment, load the es1370 driver instead of (or possibly even in addition to) the es1371 driver. It's not very likely to solve the problem since lspci indicated a 1371, but it's worth a try.
/sbin/lsmod Module Size Used by sound 57400 0 soundlow 344 0 [sound] soundcore 2340 3 [sound]
Actually my card is a no-name ISA PnP with a CMedia CMI8330 chip (apparently also known as a SoundPro.) In SuSE 5.3 I had its SB16 dsp working great by compiling my isapnp.conf settings into the SB16 support in a custom SuSE 2.0.35 kernel. However I tried this in 6.3 using the sb.o module and I get the error above. It turns out that the new kernel has better documentation on the CMI8330 /usr/src/linux-2.2.13.SuSE/Documentation/sound/CMI8330 which suggests that both the sb module and the ad1848 module will work. So I commented out the sb section in /etc/modules.conf and customized the ad1848 lines and get a similar error: # modprobe -k ad1848 /lib/modules/2.2.13/misc/ad1848.o: init_module: Device or resource busy /lib/modules/2.2.13/misc/ad1848.o: insmod ad1848 failed # I want to know what "Device or resource busy" means. Is there some kind of debug option I can use to get a more specific error message? By the way here is my new modules.conf entry alias char-major-14 ad1848 options ad1848 io=0x530 irq=11 dma=3 soundpro=1 and FWIW : ppp_deflate 40108 0 (autoclean) bsd_comp 3764 0 (autoclean) ppp 20684 0 (autoclean) [ppp_deflate bsd_comp] slhc 4504 0 (autoclean) [ppp] parport_probe 3204 0 (autoclean) parport_pc 5808 1 (autoclean) lp 5828 0 (autoclean) parport 6984 1 (autoclean) [parport_probe parport_pc lp] serial 42932 1 (autoclean) memstat 1604 0 (unused) aha152x 29120 0 Tks again Paul for the ponters dproc -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
dproc@dol.net wrote:
/usr/src/linux-2.2.13.SuSE/Documentation/sound/CMI8330
which suggests that both the sb module and the ad1848 module will work.
So I commented out the sb section in /etc/modules.conf and customized the ad1848 lines and get a similar error:
# modprobe -k ad1848 /lib/modules/2.2.13/misc/ad1848.o: init_module: Device or resource busy /lib/modules/2.2.13/misc/ad1848.o: insmod ad1848 failed #
I want to know what "Device or resource busy" means. Is there some kind of debug option I can use to get a more specific error message?
That means that the driver probed the hardware were it thought the card would be. It found a device already using that space or no device at all.
By the way here is my new modules.conf entry
alias char-major-14 ad1848 options ad1848 io=0x530 irq=11 dma=3 soundpro=1
If your card is a Pnp device you have to configure it before loading the kernel module. You don't mention doing that. After boot the card may be in an undefined state. Here are steps to configure PnP cards: 1. Run # pnpdump -c > /tmp/isapnp.conf 2. Verify the file by looking at it with a text editor. Here is a tip: Lines with (CHECK) in them, like (IO 0 (SIZE 32) (BASE 0x0240) (CHECK)) caused an error in my machine, by removing them I didn't get the error. 3. Set up the card by running: # isapnp /tmp/isapnp.conf 4. If no errors are reported, then you are ready to load the kernel module. If necessary, edit your modules.conf to match the interrupt lines, I/O ports, DMA channels of isapnp.conf. 5. Verify that the card is working. If everything works, move /tmp/isapnp.conf to /etc. Next time you boot, the boot script will run isapnp automatically. -- Rafael -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Rafael E. Herrera" wrote:
dproc@dol.net wrote:
I want to know what "Device or resource busy" means. Is there some kind of debug option I can use to get a more specific error message?
That means that the driver probed the hardware where it thought the card would be. It found a device already using that space or no device at all.
Would it be more accurate if the message was "Device or resource busy or unavailable"? Looks to me as though the message is very misleading if the device just isn't there. I wonder who should be asked to fix that? Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Paul W. Abrahams" wrote:
"Rafael E. Herrera" wrote:
dproc@dol.net wrote:
I want to know what "Device or resource busy" means. Is there some kind of debug option I can use to get a more specific error message?
That means that the driver probed the hardware where it thought the card would be. It found a device already using that space or no device at all.
Would it be more accurate if the message was "Device or resource busy or unavailable"? Looks to me as though the message is very misleading if the device just isn't there. I wonder who should be asked to fix that?
My last claim is not right. Device busy means you queried the device and it did not acknowledge and resource busy means the driver asked for some system resource, e.g. io port, irq line, etc. and the kernel denied it because some other driver may be using it. There are probably separate messages when there is no hardware where you are probing. -- Rafael -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Sat, 03 Jun 2000, Rafael E. Herrera wrote:
# modprobe -k ad1848 /lib/modules/2.2.13/misc/ad1848.o: init_module: Device or resource busy /lib/modules/2.2.13/misc/ad1848.o: insmod ad1848 failed #
I want to know what "Device or resource busy" means. Is there some kind of debug option I can use to get a more specific error message?
That means that the driver probed the hardware were it thought the card would be. It found a device already using that space or no device at all.
"no device at all" was the key. Thanks to your suggestion, I carefully rechecked my isapnp.conf settings, then ran isapnp to reconfigure the card on the fly. ... ew embarrassing - my 6.3 partition had no isapnp package installed. After installing from series ap on the CD all is plain sailing and I am now happily listening to mp3 's (though midi is very ropey.) Thank you, proc -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
abrahams＠valinet.com -
dproc＠dol.net -
raffo＠neuronet.pitt.edu