• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 560 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

insmod: nvalid module format

Prad
Expert 1125 points

Other Parts Discussed in Thread: OMAP3530

 

Hi,

 

We are having trouble with porting the OMAP35x Linux DVSDK（01_31_01_001) into our SDK,

I have heard that "insmod: error inserting 'dsplinkk.ko': -1 Invalid module format" kind of 

error is something related to Linux version mismatch,

but I have crossed checked it and everything is latest version 

the problem might be something else.But dont understand what could be reason.

Kindly helps us to solve this error.

 

Error Details.

# ./loadmodules.sh 

CMEMK module: built on Jul 13 2010 at 09:03:04

  Reference Linux version 2.6.32

             .

             .

dsplinkk: disagrees about version of symbol module_layout

insmod: error inserting 'dsplinkk.ko': -1 Invalid module format

BusyBox v1.16.1 (2010-07-12 18:43:40 JST) multi-call binary.

Usage: mknod [OPTIONS] NAME TYPE MAJOR MINOR

Create a special file (block, character, or pipe)

Options:

        -m      Create the special file using the specified mode (default a=rw)

TYPEs include:

        b:      Make a block device

        c lpm_omap3530: Unknown symbol IPS_notify

or u:   Make a character device

        lpm_omap3530: Unknown symbol IPS_register

p:      Make a named pipe (MAJOR and lpm_omap3530: Unknown symbol IPS_unregister

MINOR are ignored)

lpm_omap3530: Unknown symbol LDRV_PROC_setState

lpm_omap3530: Unknown symbol LDRV_PROC_getState

lpm_omap3530: Unknown symbol PMGR_PROC_getSymbolAddress

insmod: error inserting 'lpm_omap3530.ko': -1 Unknown symbol in module

SDMAK module: built on Jul 13 2010 at 09:03:06

Reference Linux version 2.6.32

 

 

Thankyou in advance.

  • 0
    TI__Mastermind 41665 points

    Prad said:
    We are having trouble with porting the OMAP35x Linux DVSDK（01_31_01_001) into our SDK

    I am not sure exactly what you mean by this, are you moving to a different kernel version than the kernel that is associated with your old DVSDK?

    Prad said:

    I have heard that "insmod: error inserting 'dsplinkk.ko': -1 Invalid module format" kind of 

    error is something related to Linux version mismatch,

    but I have crossed checked it and everything is latest version 

    This is exactly what the message means, it is not a matter of using the latest version, but the specific kernel source tree that the DSPLink was built against. If you are moving to a different kernel than the one that came with the DVSDK out of the box than you will need to rebuild DSPLink against that new kernel, there are instructions for doing so on the wiki at http://processors.wiki.ti.com/index.php/Building_DSPLink. Once you have generated a new dsplinkk.ko file by building with the kernel sources you are using you should no longer get this error.

  • 0 in reply to Bernie Thompson TI
    Expert 1125 points

    Hi,

     

    Thankyou so much,

     

    I am sorry for the confusion,

    I mean we are trying to port it to our Platform SDK

    (even this is also based on TI's SDK with some modifications and additional drivers).

    And there is no difference in the kernel version.

    We are able to compile without errors but after loading dsplinkk.ko, lpm_omap3530.ko drivers

    on the target we get such error saying "Invalid module format".

    As you said I have cross-checked about Building DSPLink, but with no success.

     

    Please let me know if there are any suggestions.

     

    Regards.

     

    Prad

  • 0 in reply to Prad
    TI__Mastermind 41665 points

    Prad said:

    I mean we are trying to port it to our Platform SDK

    (even this is also based on TI's SDK with some modifications and additional drivers).

    And there is no difference in the kernel version.

    Just to be clear, since you have modified the kernel and rebuilt it, this means that DSP Link will also have to be rebuilt, it is not just a matter of official kernel versioning (i.e. 2.6.33...), but a matter of the kernel itself being different.

    Prad said:
    We are able to compile without errors but after loading dsplinkk.ko, lpm_omap3530.ko drivers

    When you say you are able to compile without errors, are you referring to the kernel, your applications, or the loadable module components like DSPLink? If you are rebuilding DSPLink than you may want to check that you are getting the right dsplinkk.ko file onto your target filesystem and you are not trying to load an older incompatible dsplinkk.ko.

    If you are still getting module loading errors even after building both the kernel and the DSPLink module against each other, than my next suspicion would be that something which was modified in your kernel is making it incompatible with DSPLink, so I would start looking at what has been changed.