#54 can't insmod.

open
nobody
None
5
2003-06-02
2003-06-02
Anonymous
No

/bin/sh ../../../config/mkinstalldirs
/lib/modules/2.4.20/kernel/fs/lufs
/bin/sh ../../../libtool --mode=install
/usr/bin/install -c lufs.o /lib/modu
es/2.4.20/kernel/fs/lufs/lufs.o
/usr/bin/install -c lufs.o
/lib/modules/2.4.20/kernel/fs/lufs/lufs.o
make install-data-hook
make[5]: Entering directory
`/usr/src/lufs2/kernel/Linux/2.4'
depmod -aq
if [ "`lsmod | grep lufs`" ]; then rmmod lufs; fi
modprobe lufs
/lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved
symbol __write_lock_faile
/lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved
symbol kernel_flag_cachel
ne
/lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved
symbol __read_lock_failed
/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
make[5]: *** [install-data-hook] Error 255
make[5]: Leaving directory
`/usr/src/lufs2/kernel/Linux/2.4'
make[4]: *** [install-data-am] Error 2
make[4]: Leaving directory
`/usr/src/lufs2/kernel/Linux/2.4'
make[3]: *** [install-am] Error 2
make[3]: Leaving directory
`/usr/src/lufs2/kernel/Linux/2.4'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/usr/src/lufs2/kernel/Linux'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/usr/src/lufs2/kernel'
make: *** [install-recursive] Error 1
debian:/usr/src/lufs2# insmod lufs
Using /lib/modules/2.4.20/kernel/fs/lufs/lufs.o
/lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved
symbol __write_lock_failed
/lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved
symbol kernel_flag_cacheline
/lib/modules/2.4.20/kernel/fs/lufs/lufs.o: unresolved
symbol __read_lock_failed
debian:/usr/src/lufs2#

Discussion

  • manuel wolfshant

    Logged In: YES
    user_id=659510

    I was hit by the same problem. I am using RH 7.3. lufs did not like my
    versions of autoconf and automake, so I upgraded to those from rawhide
    (autoconf-2.57-3.noarch.rpm recompiled, automake-1.7.5-1.noarch.rpm
    as downloaded from the ftp). Near the end of rpmbuild --rebuild lufs-0.9.
    6 I get
    /usr/bin/install -c lufs.o /tmp/buildroot-lufs-0.9.6/lib/modules/2.4.20-18.
    7/kernel/fs/lufs/i686-redhat-linux-lufs.o
    /usr/bin/make install-data-hook
    make[5]: Entering directory `/usr/src/redhat/BUILD/lufs-0.9.
    6/kernel/Linux/2.4'
    depmod -aq
    if [ "`lsmod | grep lufs`" ]; then rmmod lufs; fi
    modprobe lufs
    modprobe: Can't locate module lufs
    make[5]: *** [install-data-hook] Error 255
    make[5]: Leaving directory `/usr/src/redhat/BUILD/lufs-0.9.
    6/kernel/Linux/2.4'
    make[4]: *** [install-data-am] Error 2
    make[4]: Leaving directory `/usr/src/redhat/BUILD/lufs-0.9.
    6/kernel/Linux/2.4'
    make[3]: *** [install-am] Error 2
    make[3]: Leaving directory `/usr/src/redhat/BUILD/lufs-0.9.
    6/kernel/Linux/2.4'
    make[2]: *** [install-recursive] Error 1
    make[2]: Leaving directory `/usr/src/redhat/BUILD/lufs-0.9.
    6/kernel/Linux'
    make[1]: *** [install-recursive] Error 1
    make[1]: Leaving directory `/usr/src/redhat/BUILD/lufs-0.9.6/kernel'
    make: *** [install-recursive] Error 1
    error: Bad exit status from /var/tmp/rpm-tmp.32232 (%install)

     
  • Marcelo Matus

    Marcelo Matus - 2003-06-26

    Logged In: YES
    user_id=246059

    Similar problems here until I did the following:

    1.- save your .config file from the /usr/src/linux directory
    cd /usr/src/linux
    cp .config ../config
    2.- use make mrproper inside the linux kernel
    3.- put back the .config file and do the routine make
    xconfig; make dep
    4.- clean, reconfigure and recompile lufs.

    if you still have problems, then you will need to complete
    the installation
    of the kernel, ie, the usual make bzlilo; make modules; make
    modules_install, etc.

    Then reboot and go back to step 4.

    all this mess seems to occur because slitghtly different gcc
    versions
    between the one use to compile the kernel, and the use for
    lufs, product
    (in my case) of the redhat compiler updates.

     

Log in to post a comment.

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

Sign up for the SourceForge newsletter:





No, thanks