Re: [Alsa-user] unresolved symbol schedule_work
Brought to you by:
perex
From: John C M. <joh...@co...> - 2003-04-12 06:22:07
|
Hello kmberry, thank you VERY MUCH for the information. It sounds like you solved the problem in two separate ways. I think I will go with the option of buying a soundblaster platinum card and disabling the C-MEDIA chip in BIOS. That approach sounds safer than replacing the kernel against which all the other rpm binaries were compiled, if I understand Linux and the RedHat distribution correctly. By the way, it is interesting that the pleasing human voice BIOS POST code completiion message "POST operations completed, booting operating system now" played from my speakers just fine, but then nothing else would after Linux booted. The BIOS must have a direct connection to the sound chip somehow. It would seem that I need to refer to a different sound module in my /etc/modules.conf file if I use the soundblaster card. What module does it use on your system? Thanks again. John Mann ----- Original Message ----- From: kmberry To: John C Mann ; als...@li... Sent: Friday, April 11, 2003 8:18 PM Subject: Re: [Alsa-user] unresolved symbol schedule_work John C Mann wrote: Hello. I am trying to get alsa to work with RedHat 9, sound chip being C-MEDIA CM8738 (a PCI device on motherboard). I did the Quick Install steps, but got the following error when attempting to load the module snd-cmipci: [root@localhost alsa-driver-0.9.2]# modprobe snd-cmipci /lib/modules/2.4.20-6/kernel/sound/acore/snd.o: unresolved symbol schedule_work /lib/modules/2.4.20-6/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.20-6/kernel/sound/acore/snd.o failed /lib/modules/2.4.20-6/kernel/sound/acore/snd.o: insmod snd-cmipci failed Any ideas as to what the problem might be? I saw a similar message to alsa-user on SourceForge, about an archive relating to this subject. Can someone direct me to that archive (I'm new to this list)? Thanks. John Mann I don't know about the archive, but I have a soundblaster platinum, midisport 2x2 and an intel8x0 onboard which I disabled in BIOS to use the wavetable synth in my soundblaster and alsa works. I got the same schedule_work problem and I read that redhat had put their own schedule queue in the redhat rpm kernel which caused the problem. Programmer types disabled the kernel schedule queue in the code and recompiled the redhat rpm kernel to eliminate the problem. I discovered that a tarball of 2.4.20 without redhat patches compiled on my rawhide on top of redhat-8.0 system and the schedule_work problem disappeared. Im am no programming expert so anybody that reads this will have some problem of my recollection of the terminology or even what a schedule queue does. kmberry Environmental Lab Tech |