• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 102 subscribers
  • Views 1515 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.

omap3530: error inserting dsplink, lpm and linuxutils modules

xpc
Prodigy 100 points
Other Parts Discussed in Thread: OMAP3530

Hi all,

 

I'm trying to run the omap-demo on beagleboard, but the modules cmemk.ko, lpm_omap3530.ko, dsplinkk.ko and sdmak.ko are unable to be inserted.

When the loadmodules.sh script is invoked the following error-messages appear:

cmemk: disagrees about version of symbol find_vma
cmemk: Unknown symbol find_vma
cmemk: disagrees about version of symbol __register_chrdev
cmemk: Unknown symbol __register_chrdev
insmod: error inserting 'cmemk.ko': -1 Unknown symbol in module
dsplinkk: disagrees about version of symbol set_user_nice
dsplinkk: Unknown symbol set_user_nice
dsplinkk: disagrees about version of symbol wake_up_process
dsplinkk: Unknown symbol wake_up_process
dsplinkk: disagrees about version of symbol filp_close
dsplinkk: Unknown symbol filp_close
dsplinkk: disagrees about version of symbol __register_chrdev
dsplinkk: Unknown symbol __register_chrdev
insmod: error inserting 'dsplinkk.ko': -1 Unknown symbol in module
BusyBox v1.13.2 (2009-12-02 19:10:22 EST) 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 or u: Make a character device
        p:      Make a named pipe (MAJOR and MINOR are ignored)

lpm_omap3530: Unknown symbol IPS_notify
lpm_omap3530: Unknown symbol IPS_register
lpm_omap3530: Unknown symbol IPS_unregister
lpm_omap3530: disagrees about version of symbol cdev_add
lpm_omap3530: Unknown symbol cdev_add
lpm_omap3530: Unknown symbol LDRV_PROC_setState
lpm_omap3530: Unknown symbol LDRV_PROC_getState
lpm_omap3530: Unknown symbol PMGR_PROC_getSymbolAddress
lpm_omap3530: disagrees about version of symbol cdev_init
lpm_omap3530: Unknown symbol cdev_init
lpm_omap3530: disagrees about version of symbol cdev_del
lpm_omap3530: Unknown symbol cdev_del
insmod: error inserting 'lpm_omap3530.ko': -1 Unknown symbol in module
sdmak: disagrees about version of symbol put_page
sdmak: Unknown symbol put_page
sdmak: disagrees about version of symbol __register_chrdev
sdmak: Unknown symbol __register_chrdev
insmod: error inserting 'sdmak.ko': -1 Unknown symbol in module
root@omap3evm:/opt/dvsdk/omap3530# Demo interface started at level 0.
CMEM Error: init: Failed to open /dev/cmem: 'No such file or directory'
Error: Failed to create display device instance
sh: can't create /sys/devices/platform/omapdss/overlay0/global_alpha: nonexistent directory
Error: Failed to execute: echo 0 > /sys/devices/platform/omapdss/overlay0/global_alpha

I'm using dvsdk-3.01.00.03 + am35x-omap35x-psp-sdk-03.00.00.03 / linux.-2.6.32-rc5.

Any ideas will be of use.

 

Thanks in advance.

 

 

  • 0
    TI__Expert 4930 points

    Hello,

    Are you using pre-built binaries? There could be a conflict in the Linux version used to build the binaries and the Linux version on the board. This conflict could be causing the errors that you see on insmod.

    The solution would be to ensure same Linux version for both board and binaries by either re-building binaries to use your Linux version or use the relevant Linux version on your board.

    Deepali

  • 0 in reply to Deepali Uppal
    Prodigy 100 points

    Hi,

     

    Actually I managed to solve the problem. Either I really messed up the build configuration or the problem was entirely in the cross-compiler, but when I switched from the last version of codesourcery toolchain - arm-2009q3-67-arm-none-linux-gnueabi-i686-pc-linux-gnu, that I used before, to the earlier arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu, everithing went fine.

  • 0 in reply to Deepali Uppal
    Prodigy 10 points

    Hi Deepali,

    I am also facing a similar problem. I built the whole dvsdk and linux psp using the instruction given in the TI wiki pages. But I get an error like this -

    cmemk: no symbol version for struct_module
    dsplinkk: no symbol version for struct_module
    lpm_omap3530: no symbol version for struct_module
    sdmak: no symbol version for struct_module

    I also get an error like this -

    Kernel panic - not syncing: No init found

    Please help me in this. I use an nfs mount procedure to mount the file system for the board. I suspect that the file system that gets copied to the workdir/filesys is not actually having all the contents. When I do "make modules_install" under the linux workdir, then some 5 to 6 module files etc get copied to the lib directory in the nfs mount target. When I do "make install" under the dvsdk workdir, then the /opt/dvsdk/omap3530 in the nfs mount target directory gets created and it has all the dvsdk binary files like dsplinkk.ko, sdmak.ko etc. I would like to know whether anything else needs to come under ths nfs target directory other than this. I have a strong feeling that a based linux root file system also needs to come under it. But I am not sure how to do that. I tried copying the overlay_#### binaries from the TI site in to the targetfs folder under dvsdk, and then doing "make targetfs" to create the nfs tar ball. Then I untarred the tar ball in to the nfs target directory. But the bootup still fails with similar errors of no symbol found or version etc which means that there is a difference in the binaries getting linked since the overlay file is a downloaded one and not a raw built one. But I am not sure how to make this overlay_#### tar ball from the sources. Any input is highly appreciated..Thanks in advance..

    Regards

    Saleem

  • 0 in reply to Saleem Rahim
    Intellectual 650 points

    Hello ,

    I have the same problem with DM355 and 2.6.10_mvl401_IPNCVCA1-2.1.0

    Thank you.

  • 0 in reply to rblode
    TI__Expert 3220 points

    If inserting the kernel modules failed with messages such as above, it typically means that they were compiled against a different Linux kernel than you are currently booting.

    Make sure you are booting the right kernel, and if you are make sure you rebuild the kernel modules against it.

    Regards, Niclas

  • 0 in reply to Niclas
    Intellectual 650 points

    Hello ,

    Thank you Niclas , it works .

    I compiled a new version of linux compatible with the modules.

    Regards , Rblode

     

     

  • 0
    Prodigy 40 points

    Hi xpc,

    I also got the same error initially.

    I had solved this and now I am able to load all these modules successfully.

    The following modifications are done to rectify this issue:

    1. maintaining the same toolchain to build your u-boot, kernel source and dvsdk.

    2. using the uImage from our kernel built source for booting.

    3. rebuild cmem, lpm, sdma and dsplink modules with your toolchain.

    Regards,

    Kumar HP