Results 1 to 2 of 2

Thread: Kernel Module Devlopment insmod issues

  1. #1

    Default Kernel Module Devlopment insmod issues

    I'm getting this error when trying to run insmod xx.ko on a module I wrote: -1 Invalid module format

    dmesg: no symbol version for module_layout

    If anyone would have some time to just point me in the proper direction, I would appreciate it. I've spent the last two days searching the net looking for an answer, and it has been rather frustrating. I have found lots of data on nvidia drivers and other modules and the answers do not relate to my problem. I have dumbed my driver down to a basic helloworld type module.

    I would be happy to provide any additional information that would be helpful - here is what I have so far:

    openSUSE 11.2

    relevant info from uname -a
    Code: #1 SMP
    output from modinfo
    filename:       helloworld.ko
    srcversion:     ED991015B68E7E20B0283E6
    vermagic: SMP mod_unload modversions 586TSC
    relevant output from zypper se kernel
    S | Name                 | Summary                                                 | Type
    i | kernel-default       | The Standard Kernel                                     | package
    i | kernel-default-base  | The Standard Kernel - base modules                      | package
    i | kernel-default-devel | Development files necessary for building kernel modules | package
    i | kernel-source        | The Linux Kernel Sources                                | package
    Thank you for your help.

  2. #2

    Default Re: Kernel Module Devlopment insmod issues<SOLVED>

    The answer..... incorrect information to begin with.

    The instructions I followed used the following make command:
    make -C /usr/src/`uname -r` M=`pwd` modules
    the code compiled... but I had the issues I reported.

    using this:
    make -C /lib/modules/`uname -r`/build M=`pwd` modules
    allowed me to compile and insert my module with out any issues.

    So apparently there is some difference in the configuration information provided in the modules/build directory ... when I have time I will investigate more.

    I would still like to know what "no symbol version for module_layout" means... I'm curious that way, but I will take this as a small success and move on.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts