[Alsa-user] Re: Redhat 9.0 has snd.o unresolved symbol schedule_work
Brought to you by:
perex
From: Lance A. B. <la...@be...> - 2003-04-17 04:24:08
|
On Wed, 2003-04-16 at 17:15, Jonathan Ryshpan wrote: > This fix worked for me too with a Sound Blaster Live! card. However, > touch must be invoked **after** invoking configure. Otherwise configure > will remove include/linux/workqueue.h . Hmmm. I don't think I ran into that problem, but don't remember if I re-ran configure before or after I touched the file. > The alsa maintainers should get in touch with LAB, since (I suspect) > he knows exactly what's going on here. More systems will most likely > show this problem as more distros adopt the Native POSIX Thread Library. I think they need to get in touch with Red Hat and the other people modifying the stock linux kernel. I actually picked up this fix from a previous alsa-user mailing list post. Personally, I'm half-tempted to build a stock linux kernel on my system anyway... Some of the stuff Red Hat sticks in the kernel is kinda iffy, if you ask me. --[Lance] > > Lance A. Brown" <la...@be...> writes: > > A very simple work-around for the schedule_work symbol issue is to do > > the following: > > > > In the top level of the alsa-driver sources run this command: > > > > touch include/linux/workqueue.h > > > > This will cause schedule_work to not be used and the resulting alsa > > driver modules should load just fine in a default Red Hat RPM kernel for > > Red Hat 9. It worked very well for me with my Turtle Beach Santa Cruz > > (CS46xx) card. > > Jonathan Ryshpan <jo...@pa...> > > When You Drive Alone, You Drive With bin Laden. > -- Bill Maher -- Carolina Spirit Quest: http://www.carolinaspiritquest.org/ Celebrate The Circle: http://www.angelfire.com/nc/celebratethecircle/ My LiveJournal: http://www.livejournal.com/users/labrown/ |