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 error

I am using RDK on DM8168. I have 2 questions:

1. What is the significance of vpss.ko, ti81xxfb.ko and ti81xxhdmi.ko

2. I am facing insmod error:

insmod: error inserting './kermod/vpss.ko': -1 Unknown symbol in module
insmod: error inserting './kermod/ti81xxfb.ko': -1 Unknown symbol in module
insmod: error inserting './kermod/ti81xxhdmi.ko': -1 Unknown symbol in module

How to fix this?

  • Hello,

    Are you rebuilt the kernel?
    If yes You should rebuild and cp the modules.

    host > make distclean
    host >  make CROSS_COMPILE=/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm ti8168_evm_defconfig
    host > make CROSS_COMPILE=/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm menuconfig
    host > make CROSS_COMPILE=/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-  ARCH=arm uImage
    host > make CROSS_COMPILE=/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-  ARCH=arm modules
    BR
    Margarita

  • Hi,
    Thanks for your quick answer. i will try your answer. Is there any answer for my first question?
    Thanks.
  • Hello,

    If I understand you right vpss.ko is the VPSS kernel driver module, ti81xxhdmi.ko on chip hdmi module, ti81xxfb.ko fbde module.


    BR
    Margarita
  • You should insert the kernel modules in a uImage with which they are build. If they are different, this problem could come..
    So either use released kernel modules and uImage or build both of them again.
    Rgds,Brijesh
  • After building the kernel and the modules, I am facing the same issue. Am I missing anything?

    insmod: error inserting './kermod/vpss.ko': -1 Unknown symbol in module
    [m3video] 8083: SYSTEM: Opening MsgQ [VPSS-M3_MSGQ] ...
    [m3vpss ] 8197: SYSTEM : FREE SPACE : Tiler 16-bit = 134217728 B (128 MB) - TILER ON
    [m3video] 8083: SYSTEM : FREE SPACE : Tiler 8-bit = 134217728 B (128 MB) - TILER Oti81xxhdmi: Unknown symbol TI81xx_un_register_displ)
    N
    [m3vpss ] ti81xxhdmi: Unknown symbol TI81xx_register_display_panel (err 0)
    8316: SYSTEM : Initializing Links ... DONE !!!
    [m3video] 8083: SYSTEM : FREE SPACE : Tiler 16-bit = 134217728 B (128 MB) - TILER ON
    [m3vpss ] 8316: SYSTEM : Set Static L3 pressure for HDVPSS as High
    [m3video] 8120: SYSTEM : Initializing Links ... DONE !!!
    insmod: error inserting './kermod/ti81xxfb.ko': -1 Unknown symbol in module
    insmod: error inserting './kermod/ti81xxhdmi.ko': -1 Unknown symbol in module
  • You will need compile these modules with the uImage, ie same configuration. If they are not compiled together, you could get this issue.
    So either use released uimage and kernel modules or rebuild both uimage and kernel modules together.
    Rgds,Brijesh
  • I have compiled using the following steps:

    host > make distclean
    host > make CROSS_COMPILE=/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm ti8168_evm_defconfig
    host > make CROSS_COMPILE=/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm menuconfig
    host > make CROSS_COMPILE=/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm uImage
    host > make CROSS_COMPILE=/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- ARCH=arm modules

    Still facing the issue. Any help?
  • Strange, it should have worked. Did you check if modules are from this build only? Also did you try using released modules and uImage?
    Rgds,Brijesh
  • Hello Brijesh,

    Maybe you can assist with the following simple question ?

    Can you please help understand what is the use of the following lines in script:

    ./wait_cmd.sh s m3vpss ${REMOTE_DEBUG_ADDR}
    ./wait_cmd.sh s m3video ${REMOTE_DEBUG_ADDR}
    ./wait_cmd.sh s c6xdsp ${REMOTE_DEBUG_ADDR}

    I see that even if I put it all inside comment, everything still works the same.

    Does it make sense ?

    Regards,
    Ran