• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Compiled module won't load- unknown relocation: 3  (Read 3599 times)
johnsoftek
Newbie
*

Karma: 0
Posts: 5


View Profile
« on: February 21, 2011, 03:27:21 AM »

Module mcs78830.ko (usb/ethernet adapter) was disabled in the standard http://sheeva.with-linux.com 2.6.35.10 build. So I compiled and installed all modules from source. Now modules won't load: error 'unknown relocation: 3'.

I get the same result compiling on the plug and via scratchbox2 cross-compilation.

Can anyone help?
Logged

johnsoftek
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #1 on: February 21, 2011, 03:49:55 PM »

Failing a solution, would it be okay to add mcs7830 to the standard kernel modules?
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #2 on: February 21, 2011, 04:36:43 PM »

Failing a solution, would it be okay to add mcs7830 to the standard kernel modules?

I just added support for that in 2.6.35.11 RELEASE 3.  Support will be in 2.6.36.X and 2.6.37.X the next time I rebuild those.
Logged

johnsoftek
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #3 on: February 21, 2011, 06:48:51 PM »

Many thanks!
Logged

johnsoftek
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #4 on: March 20, 2011, 04:41:04 AM »

SOLVED!

One cause of this error ("unknown relocation: 3") when loading a kernel module on an arm machine is the GCC 4.4 compiler. See this post: http://forums.arm.com/index.php?/topic/8122-kernel-modulec-not-handling-r-arm-rel32/

The fix involves adding a few lines to the kernel Makefile.
Logged

Pages: [1]
Print
Jump to: