• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 2079 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

module insert error: disagrees about version of symbol module_layout, but same release kernel number

Jeff Wong1
Expert 1305 points

Hi,

After I modify a few kernel options through menuconfig, kernel is rebuilt, copied (not quite sure as source and destin SD-card not the same name, zImage vs.

As with suggestions of running modinfo for the module at the target, it is found that the same release number with the target kernel after running 'uname -r'.

It is puzzling that insmod fails (for disagree about version of symbol module_layout) but it has the same release number with the target kernel. Please see the screen shot. What is wrong for the kernel? Thanks,

  • 0
    Expert 1305 points

    I just realize that the version number on the row of 'vermagic:' does not relate to the device driver. Then, the zImage and the driver against may not be the same.

    When I run the command:

    root@am335x-evm:~# cat /proc/cmdline
    console=ttyO0,115200n8 root=/dev/nfs nfsroot=192.168.0.109:/home/u64rj/ti-processor-sdk-linux-am335x-evm-01.00.00.03/targetNFS,nolock rw ip=dhcp

    Even though I use 'sudo cp command' the boot folder of SD-card has a link type zImage. Is it wrong for using the new zImage on the SD-card? The top is the rebuild zImage

    How to get a true zImage at SD-card? Thanks,

  • 0 in reply to Jeff Wong1
    Expert 1305 points

    Here is the screen shot of cp command and SD-card file list:

    It looks like zImage is still a link, not a true zImage file. How to correct it?

    Thanks,

  • 0 in reply to Jeff Wong1
    TI__Guru**** 393215 points
    Hi,

    I will forward this to the SW team.
  • 0 in reply to Jeff Wong1
    TI__Guru**** 161600 points
    Hi Jeff,

    Here is what I usually do when I want to copy my customized kernel:
    $ sudo rm /media/rootfs/boot/zImage-3.14.43-g875c69b
    $ sudo cp ~/ti-processor-sdk-linux-am335x-evm-01.00.00.03/board-support/linux-3.14.43+gitAUTOINC+875v69b2c3-g875c69b/arch/arm/boot/zImage /media/rootfs/boot/zImage-3.14.43-g875c69b

    This way the zImage symlink will point to your customized kernel.

    As for the insmod error, this is because your hello_prink kernel object is built against the customized kernel. And failing to copy your custom kernel (against which the hellow_printk.ko was built) to the sd card is the rootcause of the version misalignment in insmod.

    Best Regards,
    Yordan