Mailing List Archive

Would you be running RedHat 9? I've run into this as well, and it seems
to be related to the new threading in the kernel they ship. It looks
like the alsa folks are working on it, but in the meantime you can
probably get a stock kernel and build it yourself. I've also been
running the latest RedHat 8.0 kernel without problems for the last few days.

Mike


Alex Davidson wrote:

>No sign of any "snd-" stuff in lsmod.
>
>Running:
>/etc/rc.d/init.d/alsasound start
>returned the following:
>starting sound driver: snd-sb16
>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
>schedule_work
>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed
>done
>
>Would I be better off spending some hard-earned on a sound card that will
>work out of the box you think? (Is there even such a thing?)
>
>

Alex Davidson wrote:
> No sign of any "snd-" stuff in lsmod.

So now you've narrowed the problem/solution...

> Running:
> /etc/rc.d/init.d/alsasound start
> returned the following:
> starting sound driver: snd-sb16
> /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
> schedule_work
> /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
> /lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
> /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed
> done

You'd think sb16 would be a good choice. However, I have
two boxes from Creative Labs that say "Sound Blaster 16 PCI"
on all six sides of the box. So is the driver for these cards
snd-sb16? Of course not ;-). The driver is "snd-ens1371".

Go to http://www.alsa-project.org/alsa-doc/ to find your
card make and model then click "Details" to see the exact
module name and info about configuring your card.

> Would I be better off spending some hard-earned on a sound card that will
> work out of the box you think? (Is there even such a thing?)

In any case, you'd need to get the drivers compiled and
installed properly. A Sound Blaster 16 (if that's what
you have) is about as tried and true as you can get.

-- bjm

Well, I've tried everything I can think of without success. Ultimately I
would just like sound to go from my capture card to my sound card
successfully but the OSS drivers don't seem to be doing it so I'm trying to
get ALSA working without the following error on boot:
Error while initializing the sound driver
device /dev/dsp can't be opened (No such device)
The sound server will continue, using the null output device.

Red Hat 9 recognizes the sounds card as a SoundBlaster Vibra 16X (CT4170)
and according to www.alsa-project.org/also-doc/ I should be using snd-sb16
but I have tried every possible setting for a SoundBlaster with no change in
the error message.

Here is my modules.conf in case someone can see something silly I'm (not)
doing. I commented out the last 4 lines as I didn't know if they would
conflict:
alias eth0 3c59x
alias scsi_hostadapter aic7xxx
alias usb-controller usb-uhci
# ORIGINAL SOUND SETTING
#alias sound-slot-0 sb
#
#Added For Alsa
alias char-major-116 snd
alias snd-card-0 snd-sb16
# module options should go here
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
#alias char-major-81 bttv
#options bttv card=22 pll=0 radio=1 tuner=2
#post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L>/dev/null
2>&1 || :
#pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S>/dev/null
2>&1 || :

One thing I'm not sure on is whether I'm supposed to create a .asoundrc
file - myth docs make no mention of it.

Thanks for any pointers.

Alex

----- Original Message -----

> Alex Davidson wrote:
> > No sign of any "snd-" stuff in lsmod.
>
> So now you've narrowed the problem/solution...
>
> > Running:
> > /etc/rc.d/init.d/alsasound start
> > returned the following:
> > starting sound driver: snd-sb16
> > /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
> > schedule_work
> > /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
> > /lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
> > /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed
> > done
>
> You'd think sb16 would be a good choice. However, I have
> two boxes from Creative Labs that say "Sound Blaster 16 PCI"
> on all six sides of the box. So is the driver for these cards
> snd-sb16? Of course not ;-). The driver is "snd-ens1371".
>
> Go to http://www.alsa-project.org/alsa-doc/ to find your
> card make and model then click "Details" to see the exact
> module name and info about configuring your card.
>
> > Would I be better off spending some hard-earned on a sound card that
will
> > work out of the box you think? (Is there even such a thing?)
>
> In any case, you'd need to get the drivers compiled and
> installed properly. A Sound Blaster 16 (if that's what
> you have) is about as tried and true as you can get.
>
> -- bjm

As "root", try:

modprobe snd-sb16

to see if it gives any more specific info about why the
driver won't load.

-- bjm

/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
schedule_work
/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
/lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed

----- Original Message -----

> As "root", try:
>
> modprobe snd-sb16
>
> to see if it gives any more specific info about why the
> driver won't load.
>
> -- bjm

I don't believe ALSA works under RedHat 9 yet. I'm running RedHat 9 on
my MythTV box, but I am using the latest kernel from 8.0 (2.4.18-17.8.0)
instead of any of the RedHat 9 kernels. With 2.4.20-9, ALSA would
compile and install, but depmod would report unresolved symbols, so it
would never work.

Mike


Alex Davidson wrote:

>Well, I've tried everything I can think of without success. Ultimately I
>would just like sound to go from my capture card to my sound card
>successfully but the OSS drivers don't seem to be doing it so I'm trying to
>get ALSA working without the following error on boot:
>Error while initializing the sound driver
>device /dev/dsp can't be opened (No such device)
>The sound server will continue, using the null output device.
>
>Red Hat 9 recognizes the sounds card as a SoundBlaster Vibra 16X (CT4170)
>and according to www.alsa-project.org/also-doc/ I should be using snd-sb16
>but I have tried every possible setting for a SoundBlaster with no change in
>the error message.
>
>Here is my modules.conf in case someone can see something silly I'm (not)
>doing. I commented out the last 4 lines as I didn't know if they would
>conflict:
>alias eth0 3c59x
>alias scsi_hostadapter aic7xxx
>alias usb-controller usb-uhci
># ORIGINAL SOUND SETTING
>#alias sound-slot-0 sb
>#
>#Added For Alsa
>alias char-major-116 snd
>alias snd-card-0 snd-sb16
># module options should go here
># OSS/Free portion
>alias char-major-14 soundcore
>alias sound-slot-0 snd-card-0
># card #1
>alias sound-service-0-0 snd-mixer-oss
>alias sound-service-0-1 snd-seq-oss
>alias sound-service-0-3 snd-pcm-oss
>alias sound-service-0-8 snd-seq-oss
>alias sound-service-0-12 snd-pcm-oss
>#alias char-major-81 bttv
>#options bttv card=22 pll=0 radio=1 tuner=2
>#post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L>/dev/null
>2>&1 || :
>#pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S>/dev/null
>2>&1 || :
>
>One thing I'm not sure on is whether I'm supposed to create a .asoundrc
>file - myth docs make no mention of it.
>
>Thanks for any pointers.
>
>Alex
>
>----- Original Message -----
>
>
>
>>Alex Davidson wrote:
>>
>>
>>>No sign of any "snd-" stuff in lsmod.
>>>
>>>
>>So now you've narrowed the problem/solution...
>>
>>
>>
>>>Running:
>>>/etc/rc.d/init.d/alsasound start
>>>returned the following:
>>>starting sound driver: snd-sb16
>>>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
>>>schedule_work
>>>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
>>>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
>>>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed
>>>done
>>>
>>>
>>You'd think sb16 would be a good choice. However, I have
>>two boxes from Creative Labs that say "Sound Blaster 16 PCI"
>>on all six sides of the box. So is the driver for these cards
>>snd-sb16? Of course not ;-). The driver is "snd-ens1371".
>>
>>Go to http://www.alsa-project.org/alsa-doc/ to find your
>>card make and model then click "Details" to see the exact
>>module name and info about configuring your card.
>>
>>
>>
>>>Would I be better off spending some hard-earned on a sound card that
>>>
>>>
>will
>
>
>>>work out of the box you think? (Is there even such a thing?)
>>>
>>>
>>In any case, you'd need to get the drivers compiled and
>>installed properly. A Sound Blaster 16 (if that's what
>>you have) is about as tried and true as you can get.
>>
>>-- bjm
>>
>>
>
>_______________________________________________
>mythtv-users mailing list
>mythtv-users@snowman.net
>http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
>
>
>

Alex Davidson wrote:
> /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
> schedule_work
> /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
> /lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
> /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed

Okay.

depmod -a

If this give a message like:

depmod: *** Unresolved symbols in /lib/modules/...

you may need to recompile ALSA with the same kernel source
(/usr/src/linux/) as the kernel that is currently running.

-- bjm

This is the exact problem I had (and as far as I can tell, everyone has)
with building ALSA under RedHat 9. It's due to kernel code that RedHat
has backported from the 2.5 kernels. I don't think even the CVS version
of ALSA has this fixed.

Mike

Alex Davidson wrote:

>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
>schedule_work
>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed
>
>

I ran into this issue as well with RH9. Haven't resolved it. I'm
waiting for ALSA to fix it. Does anyone know if they are working on it?


On Tue, 2003-04-22 at 20:05, Mike Wohlgemuth wrote:
> This is the exact problem I had (and as far as I can tell, everyone has)
> with building ALSA under RedHat 9. It's due to kernel code that RedHat
> has backported from the 2.5 kernels. I don't think even the CVS version
> of ALSA has this fixed.
>
> Mike
>
> Alex Davidson wrote:
>
> >/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
> >schedule_work
> >/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
> >/lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
> >/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed
> >
> >
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@snowman.net
> http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
>

I got the unresolved sumbols thing.

I'm completely out of my depth with Linux so maybe you can point me to a
resource that would explain how to do this.
Does this procedure allow me to continue running RH9 or would I be taking a
step back to RH8 as others have needed to do?

----- Original Message -----

> Alex Davidson wrote:
> > /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
> > schedule_work
> > /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
> > /lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
> > /lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed
>
> Okay.
>
> depmod -a
>
> If this give a message like:
>
> depmod: *** Unresolved symbols in /lib/modules/...
>
> you may need to recompile ALSA with the same kernel source
> (/usr/src/linux/) as the kernel that is currently running.
>
> -- bjm

Alex Davidson wrote:

>I got the unresolved sumbols thing.
>
>I'm completely out of my depth with Linux so maybe you can point me to a
>resource that would explain how to do this.
>Does this procedure allow me to continue running RH9 or would I be taking a
>step back to RH8 as others have needed to do?
>
Note that I haven't reverted to RedHat 8.0. I installed RedHat 9, and
after having problems with installing ALSA, I took the
kernel-source-2.4.18-27.8.0 rpm for RedHat 8.0 and installed it under
RedHat 9. I then built and installed this kernel (I have to run a
custom compiled kernel due to some of the hardware I'm using). So I'm
running RedHat 9 with a RedHat 8.0 kernel.

You could probably just get the kernel-2.4.18-27.8.0 rpm and install it,
but I haven't tried that. It may be easier to step back to RedHat 8.0
if you aren't too comfortable with all this, but building your own
kernel isn't that bad (if indeed just installing the kernel rpm doesn't
work for you). If you've built ALSA (and it sounds like you actually
did that properly) you can probably handle the kernel build process as
well. If you can get away without building the kernel, you will still
need kernel-source-2.4.18-27.8.0 in order to build ALSA, since
kernel-source-2.4.18-27.8.0 has the headers you will need.

Mike

Unfortunately this problem doesn't appear to be something that can
easily be fixed by just recompiling your Redhat kernel ... I have heard
that you can recompile a stock 2.4.20 kernel and get it to work, but I
don't know what issues that introduces into your RH9 installation.
Incidentally I was able to do a one line change to one of the source
files in alsa to get it to compile/load properly, but I can't vouch for
whether or not it will cause terrible stability problems (which I have
had some of, though it seems pretty good now).... Basically if you do a
"grep schedule_work `find -type f`" on your alsa source, you'll see two
references -- one that is the function call that is causing this error
(in like snd.c perhaps?) and the other is a #define. All I did was
replace the function call in snd.c with the actual define value and
recompile ....... it seems to work........ you're kind of on your own
after that though.

ms


Alex Davidson wrote:

>I got the unresolved sumbols thing.
>
>I'm completely out of my depth with Linux so maybe you can point me to a
>resource that would explain how to do this.
>Does this procedure allow me to continue running RH9 or would I be taking a
>step back to RH8 as others have needed to do?
>
>----- Original Message -----
>
>
>
>>Alex Davidson wrote:
>>
>>
>>>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: unresolved symbol
>>>schedule_work
>>>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod
>>>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o failed
>>>/lib/modules/2.4.20-9/kernel/sound/acore/snd.o: insmod snd-sb16 failed
>>>
>>>
>>Okay.
>>
>> depmod -a
>>
>>If this give a message like:
>>
>> depmod: *** Unresolved symbols in /lib/modules/...
>>
>>you may need to recompile ALSA with the same kernel source
>>(/usr/src/linux/) as the kernel that is currently running.
>>
>>-- bjm
>>
>>
>
>_______________________________________________
>mythtv-users mailing list
>mythtv-users@snowman.net
>http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
>
>