Re: [OpenWrt-Devel] Unloadable modules generated for powerpc

2014-03-11 Thread Nils Rennebarth
On 11.03.2014 10:41, Felix Fietkau wrote: It may be better to send a patch to make the build fail early with a descriptive error message. You mean something like this? It is not pretty but appears to work. Kernels with CONFIG_MODVERSIONS set are not supported by openwrt, because the kernel is

Re: [OpenWrt-Devel] Unloadable modules generated for powerpc

2014-03-11 Thread Felix Fietkau
On 2014-03-11 10:26, Nils Rennebarth wrote: > On 11.03.2014 08:25, Felix Fietkau wrote: >> My guess is that you have module symbol versioning turned on in your >> kernel config for ppc. > Correct > >> This is incompatible with OpenWrt builds, because >> OpenWrt always builds the kernel modules bef

Re: [OpenWrt-Devel] Unloadable modules generated for powerpc

2014-03-11 Thread Nils Rennebarth
On 11.03.2014 08:25, Felix Fietkau wrote: My guess is that you have module symbol versioning turned on in your kernel config for ppc. Correct This is incompatible with OpenWrt builds, because OpenWrt always builds the kernel modules before the image. Could requirements like that be noted in a

Re: [OpenWrt-Devel] Unloadable modules generated for powerpc

2014-03-11 Thread Felix Fietkau
On 2014-03-11 02:48, Nils Rennebarth wrote: > Hello, > > We use our own kernel source (official linux 3.8.13 plus a drivers) and build > openwrt for x86 and powerpc 85xx. > Now the modules generated for powerpc don't load. When trying to insmod, then > the kernel message (e.g.) >xt_LOG: no s

[OpenWrt-Devel] Unloadable modules generated for powerpc

2014-03-10 Thread Nils Rennebarth
Hello, We use our own kernel source (official linux 3.8.13 plus a drivers) and build openwrt for x86 and powerpc 85xx. Now the modules generated for powerpc don't load. When trying to insmod, then the kernel message (e.g.) xt_LOG: no symbol version for module_layout is issued on the console.