insmod problem with 0.9.7 but not 0.9.6

Help
2003-11-15
2004-09-16
  • Martin Weinberg

    Martin Weinberg - 2003-11-15

    Hi,

    I have a Debian/Woody system with kernel 2.4.20.  I find
    that 0.9.6 works perfectly but 0.9.7 fails on insmod with
    unresolved symbols.  0.9.6 works fine for me so this is not
    a problem, but I am curious about the cause.  Any insight?

    modprobe lufs
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol put_cmsg
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol generic_file_llseek/lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol generic_file_write
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol unlock_page
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol clear_inode
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol kmalloc
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol generic_read_dir
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol scm_detach_fds
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol unregister_filesystem
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol vfs_readlink
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol force_delete
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol find_inode_number
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol generic_file_mmap
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol is_bad_inode
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol d_rehash
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol make_bad_inode
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol generic_file_read
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol generic_file_open
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol register_filesystem/lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol zone_table
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol invalidate_inode_pages
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol d_alloc_root
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol kill_proc_info
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol kfree
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol iunique
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol get_empty_inode
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol vfs_follow_link
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol __scm_destroy
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol xtime
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol sock_release
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol simple_strtoul
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol sock_create
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol jiffies
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol d_instantiate
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol insert_inode_hash
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol __free_pages
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol strtok
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol printk
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved symbol __scm_send
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: insmod /lib/modules/2.4.20/kernel/fs/lufs/lufs.o failed
    /lib/modules/2.4.20/kernel/fs/lufs/lufs.o: insmod lufs failed

     
    • Amir

      Amir - 2003-12-01

      I am getting the same problem on Debian 3.0r0 with 2.4.20-grsec exact same insmod problems. I will try 0.9.6, however.

       
    • Martin Weinberg

      Martin Weinberg - 2003-12-06

      I had a chance to spend a little time looking into this.

      The problem is the configure script in this version (0.9.7).  The
      developer tests for the existence of:

      /lib/modules/<VERSION>/build/include/linux/modversions.h

      and then

      /lib/modules/<VERSION>/build/include/config/modversions.h

      It is the first one that is required but if the second one is found,
      then it is used, leading to the unresolved symbols.  I swapped the
      order of these tests and all was fine and the 0.9.7 module loaded
      and installed as it should.

      I don't understand what was intended by including the
      config/modversions.h so I didn't include a patch.  I hope the
      developers get a chance to read this.

       
    • Kapoor

      Kapoor - 2004-09-16

      I tried the above on a 2.4.20-8 kernel. And I still am getting the same issue.

      I know some ppl who have it working - what am I missing.

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks