Mailing List Archive

I was having intermittent problems with sound.
According to someone at work, he suggeseted to me that
I should disable ARTS, which is somewhere in the sound
mixer. That solved the problem for me.

BTW: I never got ALSA working either, but mine is
working just fine without it.

Leigh
--- "Jarod C. Wilson" <jcw@wilsonet.com> wrote:
> I'm having a real beast of a time with ALSA 0.9.4
> and RHL9. Nothing I
> can find browsing through the ALSA mailing lists or
> docs seems to help.
> I've got my PVR-250 working, my remote working, and
> all the other
> MythTV prerequisites installed and working, but I
> can't get ALSA to
> work.
>
>
> The latest thing I've tried is configuring like so:
>
> # cd /path/to/alsa-driver-0.9.4
> # ./configure
> --with-kernel=/usr/src/linux/2.4.20-18.9
> --with-moddir=/lib/modules/2.4.20-18.9custom/misc
> --with-cards=emu10k1
> --with-sequencer=yes --with-oss=yes
> # touch
> /usr/src/linux-2.4.20-18.9/include/linux/workqueue.h
> # make
> # make install
>
> All goes well until I 'depmod -a':
> # depmod -a
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.20-18.9custom/misc/snd.o
>
> And
> # modprobe snd-emu10k1
> /lib/modules/2.4.20-18.9custom/misc/snd.o:
> unresolved symbol
> schedule_work
> /lib/modules/2.4.20-18.9custom/misc/snd.o: insmod
> /lib/modules/2.4.20-18.9custom/misc/snd.o failed
> /lib/modules/2.4.20-18.9custom/misc/snd.o:
> unresolved symbol
> schedule_work
> /lib/modules/2.4.20-18.9custom/misc/snd.o: insmod
> /lib/modules/2.4.20-18.9custom/misc/snd.o failed
> /lib/modules/2.4.20-18.9custom/misc/snd.o: insmod
> snd-emu10k1 failed
>
> Anyone have any ideas? Am I all alone w/this
> problem? Should I just
> back off to ALSA 0.9.3c or the older Red Hat kernel?
> Help!
>
> TIA...
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@snowman.net
>
http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

I had exactly the same problem, and couldnt solve it. So i'm just using the
OSS drivers, which seem to work ok...

-----Original Message-----
From: mythtv-users-bounces@snowman.net
[mailto:mythtv-users-bounces@snowman.net]On Behalf Of Jarod C. Wilson
Sent: Thursday, 5 June 2003 5:52 AM
To: mythtv-users@snowman.net
Subject: [mythtv-users] RHL9 & alsa 0.9.4 snd.o problems


I'm having a real beast of a time with ALSA 0.9.4 and RHL9. Nothing I
can find browsing through the ALSA mailing lists or docs seems to help.
I've got my PVR-250 working, my remote working, and all the other
MythTV prerequisites installed and working, but I can't get ALSA to
work.


The latest thing I've tried is configuring like so:

# cd /path/to/alsa-driver-0.9.4
# ./configure --with-kernel=/usr/src/linux/2.4.20-18.9
--with-moddir=/lib/modules/2.4.20-18.9custom/misc --with-cards=emu10k1
--with-sequencer=yes --with-oss=yes
# touch /usr/src/linux-2.4.20-18.9/include/linux/workqueue.h
# make
# make install

All goes well until I 'depmod -a':
# depmod -a
depmod: *** Unresolved symbols in
/lib/modules/2.4.20-18.9custom/misc/snd.o

And
# modprobe snd-emu10k1
/lib/modules/2.4.20-18.9custom/misc/snd.o: unresolved symbol
schedule_work
/lib/modules/2.4.20-18.9custom/misc/snd.o: insmod
/lib/modules/2.4.20-18.9custom/misc/snd.o failed
/lib/modules/2.4.20-18.9custom/misc/snd.o: unresolved symbol
schedule_work
/lib/modules/2.4.20-18.9custom/misc/snd.o: insmod
/lib/modules/2.4.20-18.9custom/misc/snd.o failed
/lib/modules/2.4.20-18.9custom/misc/snd.o: insmod snd-emu10k1 failed

Anyone have any ideas? Am I all alone w/this problem? Should I just
back off to ALSA 0.9.3c or the older Red Hat kernel? Help!

TIA...

_______________________________________________
mythtv-users mailing list
mythtv-users@snowman.net
http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users

>>>>> On Wed, 4 Jun 2003 12:52:10 -0700, "Jarod C. Wilson" <jcw@wilsonet.com> said:

[...]

j> The latest thing I've tried is configuring like so:

j> # cd /path/to/alsa-driver-0.9.4
j> # ./configure --with-kernel=/usr/src/linux/2.4.20-18.9 --with-moddir=/lib/modules/2.4.20-18.9custom/misc --with-cards=emu10k1 --with-sequencer=yes --with-oss=yes
j> # touch /usr/src/linux-2.4.20-18.9/include/linux/workqueue.h

Are you sure about that "touch" command? I think the
workaround for newer RedHat kernels was to use the touch command to
create a dummy "workqueue.h" in include/linux of the alsa-driver
directory (not the kernel source directory). This forces ALSA to use
its own version of "schedule_work". However, that dummy workqueue.h
was already distributed with newer versions of alsa-driver (at least
in 0.9.3c -- I don't have a newer one to check). Does it exist in
your tree? The gcc command line should also be looking in the
alsa-driver include directory ahead of the kernel's. If you can't
make this work, you could also comment out the "#include
<linux/workqueue.h>" in include/adriver.h.

Anyway, you'll probably have better luck asking on the ALSA
mailing lists.

[...]

j> # modprobe snd-emu10k1
j> /lib/modules/2.4.20-18.9custom/misc/snd.o: unresolved symbol schedule_work

--
Gregorio Gervasio, Jr.
gtgj@pacbell.net

On Wednesday, Jun 4, Gregorio Gervasio wrote:

> j> # touch /usr/src/linux-2.4.20-18.9/include/linux/workqueue.h
>
> Are you sure about that "touch" command? I think the
> workaround for newer RedHat kernels was to use the touch command to
> create a dummy "workqueue.h" in include/linux of the alsa-driver
> directory (not the kernel source directory). This forces ALSA to use
> its own version of "schedule_work". However, that dummy workqueue.h
> was already distributed with newer versions of alsa-driver (at least
> in 0.9.3c -- I don't have a newer one to check). Does it exist in
> your tree? The gcc command line should also be looking in the
> alsa-driver include directory ahead of the kernel's. If you can't
> make this work, you could also comment out the "#include
> <linux/workqueue.h>" in include/adriver.h.

See, now this is what I get for working on this for too damned many
hours consecutively... My attention to detail wavers in the dead of
night, and I believe I was in fact touching the wrong place. I
re-traced my steps, touching like you (and others) suggested, and
everything looks to be just fine now. Gotta get more sleep... Thanks
for the help!