I changed some of my 2.4.20-20.9 kernel options, compiled the new kernel, booted and ran it no problem. I followed the method at http://www.tldp.org/HOWTO/Kernel-HOWTO/index.html
Whenever my kernel changes, I have to reinstall my soundcard's drivers, which I've done several times following the recipe for my card at http://space.virgilio.it/[EMAIL PROTECTED]/ea.html as follows, using the patch provided from that web site: tar xjf alsa-driver-0.9.6.tar.bz2 cd alsa-driver-0.9.6 tar xjf ../eagd-0.6.0.tar.bz2 tar xjf ../ea-0.6.0.tar.bz2 patch -p0 < EchoaudioPatch.patch <edit pci/echoaudio/Makefile and put name of my card after the "EchoCard = "> ./cvscompile --with-cards=echoaudio --with-oss=yes <other options> make install All the make and compilation steps in the soundcard installation recipe complete as usual with no errors with my customized kernel. When I do the last step, however: modprobe snd-echoaudio I get the errors: /lib/modules/2.4.20-20.9custom/kernel/sound/acore/snd.o: unresolved symbol schedule_work /lib/modules/2.4.20-20.9custom/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.20-20.9custom/kernel/sound/acore/snd.o failed /lib/modules/2.4.20-20.9custom/kernel/sound/acore/snd.o: insmod snd-echoaudio failed I have no clue here. All I can think of is that something is disabled in my new kernel, but I built that by starting with the original config and only ADDING things to it. Any ideas? thanks, cyggie stardust ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
