I set the sysmbolic link at the right direction, as well recompiled the entire kernel with the matched linux-headers.
I have only 1 kernel, built with the same compiler I build the wanpipe module. Nividia Drivers are being compiled out of the box, and are running ou tof the box without errors. Am 21.08.2012 11:14, schrieb Hinnerk van Bruinehsen: > On 20.08.2012 18:14, Tamer Higazi wrote: >> Hi Hinnerk! I did what you say, now the magic issue comes, the >> kernel drivers ARE BUILT for this kernel, here the modinfo output: > >> tamer@office ~ $ sudo modinfo >> /lib/modules/3.3.8-gentoo/kernel/drivers/net/wan/wanpipe.ko >> +filename: >> /lib/modules/3.3.8-gentoo/kernel/drivers/net/wan/wanpipe.ko >> license: GPL description: Sangoma WANPIPE: WAN >> Multi-Protocol Driver author: Nenad Corbic >> <ncor...@sangoma.com> depends: sdladrv,wanrouter vermagic: >> 3.3.8-gentoo SMP mod_unload modversions tamer@office ~ $ sudo >> modinfo >> /lib/modules/3.3.8-gentoo/kernel/drivers/net/wan/wanrouter.ko > > >> tamer@office ~ $ sudo modinfo >> /lib/modules/3.3.8-gentoo/kernel/net/wanrouter/wanrouter.ko >> filename: >> /lib/modules/3.3.8-gentoo/kernel/net/wanrouter/wanrouter.ko >> license: GPL description: Sangoma WANPIPE: Proc & User >> Interface author: Nenad Corbic <ncor...@sangoma.com> >> depends: sdladrv vermagic: 3.3.8-gentoo SMP mod_unload >> modversions > > >> tamer@office ~ $ sudo modprobe sdladrv WARNING: Deprecated config >> file /etc/modprobe.conf, all config files belong into >> /etc/modprobe.d/. FATAL: Error inserting sdladrv >> (/lib/modules/3.3.8-gentoo/kernel/drivers/net/wan/sdladrv.ko): >> Invalid module format tamer@office ~ $ sudo modinfo >> /lib/modules/3.3.8-gentoo/kernel/drivers/net/wan/sdladrv.ko >> filename: >> /lib/modules/3.3.8-gentoo/kernel/drivers/net/wan/sdladrv.ko >> license: GPL description: Sangoma WANPIPE: HW Layer >> author: Alex Feldman <al.feld...@sangoma.com> depends: >> vermagic: 3.3.8-gentoo SMP mod_unload modversions > > >> I am running the 3.3.8 SMP kernel, and I don't know why he doesn't >> load the modules. This is what droves me crazy about it.... > > >> any other ideas?! > > <SNIP> > > > > I would try to recompile the kernel. You should also set the > /usr/src/linux symlink accordingly (to your actual kernel sources). > Reboot to machine after rebuilding the kernel and then rebuild the > module itself. > Maybe try - as Wonko stated in another mail - module versioning support. > > For the whole process make sure that you use a consistent toolchain > (gcc, linux-headers, kernel-sources, glibc, binutils come to mind) > > WKR > Hinnerk >
