× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Issue with built modules on RN102/arm (no symbol version)

nwagenaar
Aspirant

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?
Message 1 of 9
mdgm-ntgr
NETGEAR Employee Retired

Re: Issue with built modules on RN102/arm (no symbol version

What does the dmesg output have to say about the invalid module?
Message 2 of 9
nwagenaar
Aspirant

Re: Issue with built modules on RN102/arm (no symbol version

I already gave that information:

nwagenaar wrote:

In dmesg I see the following error:

media: no symbol version for module_layout
Message 3 of 9
WhoCares_
Mentor

Re: Issue with built modules on RN102/arm (no symbol version

No other errors like unknown symbol: .... ?
-Stefan
Message 4 of 9
nwagenaar
Aspirant

Re: Issue with built modules on RN102/arm (no symbol version

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
Message 5 of 9
WhoCares_
Mentor

Re: Issue with built modules on RN102/arm (no symbol version

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
Message 6 of 9
nwagenaar
Aspirant

Re: Issue with built modules on RN102/arm (no symbol version

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
Message 7 of 9
WhoCares_
Mentor

Re: Issue with built modules on RN102/arm (no symbol version

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
Message 8 of 9
nwagenaar
Aspirant

Re: Issue with built modules on RN102/arm (no symbol version

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
Message 9 of 9
Top Contributors
Discussion stats
  • 8 replies
  • 4644 views
  • 0 kudos
  • 3 in conversation
Announcements