NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Issue with built modules on RN102/arm (no symbol version)
I would like to build a module for my DVB device so I can use TVHeadend on my RN102. I hope people can direct me in the right location to resolve this.
On my RN102 I did the following:
- I downloaded the ReadyNASOS_V6.2.3_WW_src.zip file and extracted the linux-3.0.101-0.46 folder
- I copied arch/arm/configs/readynas_defconfig to .config
- I installed the necessary items to compile a kernel
- I did a make menuconfig and enabled the DVB modules
- I removed "arm-marvell-linux-gnueabi-" from the CONFIG_CROSS_COMPILE option considering I'm compiling on the RN102 itself
- I saved the config and I did a make modules, installed them, did a depmod and rebooted the RN102.
Manually loading the newly compiled kernel module using insmod gives the message:
modprobe: can't load module media (kernel/drivers/media/media.ko): invalid module format
In dmesg I see the following error:
media: no symbol version for module_layout
Checking a working module and the non-working module with modinfo shows the same magicvers:
Working:
filename: /lib/modules/3.0.101.RN_ARM.4/kernel/fs/ufsd/ufsd.ko
license: Commercial product
author: Andrey Shedel & Alexander Mamaev
description: Paragon ufsd driver
depends:
vermagic: 3.0.101.RN_ARM.4 mod_unload modversions ARMv7
non-working:
filename: /lib/modules/3.0.101.RN_ARM.4/kernel/drivers/media/media.ko
license: GPL
author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
description: Device node registration for media drivers
depends:
vermagic: 3.0.101.RN_ARM.4 mod_unload modversions ARMv7
So, does anybody have an idea what's wrong?
On my RN102 I did the following:
- I downloaded the ReadyNASOS_V6.2.3_WW_src.zip file and extracted the linux-3.0.101-0.46 folder
- I copied arch/arm/configs/readynas_defconfig to .config
- I installed the necessary items to compile a kernel
- I did a make menuconfig and enabled the DVB modules
- I removed "arm-marvell-linux-gnueabi-" from the CONFIG_CROSS_COMPILE option considering I'm compiling on the RN102 itself
- I saved the config and I did a make modules, installed them, did a depmod and rebooted the RN102.
Manually loading the newly compiled kernel module using insmod gives the message:
modprobe: can't load module media (kernel/drivers/media/media.ko): invalid module format
In dmesg I see the following error:
media: no symbol version for module_layout
Checking a working module and the non-working module with modinfo shows the same magicvers:
Working:
filename: /lib/modules/3.0.101.RN_ARM.4/kernel/fs/ufsd/ufsd.ko
license: Commercial product
author: Andrey Shedel & Alexander Mamaev
description: Paragon ufsd driver
depends:
vermagic: 3.0.101.RN_ARM.4 mod_unload modversions ARMv7
non-working:
filename: /lib/modules/3.0.101.RN_ARM.4/kernel/drivers/media/media.ko
license: GPL
author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
description: Device node registration for media drivers
depends:
vermagic: 3.0.101.RN_ARM.4 mod_unload modversions ARMv7
So, does anybody have an idea what's wrong?
8 Replies
Replies have been turned off for this discussion
- What does the dmesg output have to say about the invalid module?
- I already gave that information:
nwagenaar wrote:
In dmesg I see the following error:
media: no symbol version for module_layout - No other errors like unknown symbol: .... ?
-Stefan - That's correct. That's the only message I see in dmesg. I tried verbose loading the module, but the message is the same.
- Niels - Well, as a quick test you could try to build from the plain sources without enabling the DVB stuff. Use any of the non-essentail compiled modules, copy it over to the ReadyNAS and check whether it exhibits the same problem.
-Stefan - I'll check that later today.
Just to make it clear; I'm compiling the kernel on the RN102 itself. I'm not using any cross-compile environment.
-Niels - I'm aware of that. What I'm trying to determine is (among other things) exactly that: whether building *on* the NAS is already sufficient to produce broken modules ;)
-Stefan - So I managed to get it working.
What doesn't work: compile modules only
What does work: compile the entire kernel
After this additional compile actions requiring the kernel source to be in place (for example the v4l git) can be compiled; just make sure you link the kernel source folder to /lib/modules/3.0.101.RN_ARM.4/build
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
