On Tue, 2 Jul 2002 12:01:38 +0300 Martins Medens <[EMAIL PROTECTED]> wrote: >I have had somthing like this happen while compiling >modules for 3COMs >megabit NIC. The module would compile but would not load. >In my case >the problem was solved by using the right includes from >the same kernel >that was used on the box. The steps were like - > >1. Compile and install the kernel. > Do not make 'make clean' for kernel source! >2. Compile and install the modules giving the include >path for kernel > source of the just compiled kernel. Also take care >not to leave the > previous modules around. Be sure to move old >/lib/modules/2.4.18 out of > the way before installing new ones. > >Btw preemptive patch is of no concern here. I am using >alsa 0.9.0rc2 with >preemptive 2.4.18 kernel on several machines with no >problem at all. > > Martins
Martins, Thanks for your reply. So, in your opinion, what I need to do is 1.-remove my current modules dir 2.- go into /usr/src/linux recompile and reinstall my kernel. 3.- configure, compile and install ALSA Step 2 is what intrigues me, normally I'd do: # make dep clean bzImage but, as you say, I shouldn´t do 'make clean' in order to avoid wiping off my current kernel source tree setup. So, would 'make dep bzImage' be correct? or only 'make bzImage' Thanks again. And Btw, I supposed preemptibility would be of no concern, since it has been of no concern for every other piece of software compiling against kernel sources :-) Cheers Oscar Ross Junior SysAdmin __________________________________________________ "... all you touch and all you see, is all your life will ever be." __________________________________________________ ------------------------------------------------------- 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
