[BusyBox] insmod problem with 2.4.4 kernel

[Andreas Neuhaus]

well, of course i compiled everything (uclibc and busybox) against the i was
testing. a few minutes ago i completely checked out uclibc and busybox again
and recompiled everything: still the same strange thing.

because my build system has a 2.4.2 kernel i guess somewhere is something
included from my running kernel. i don't install uclibc on my build system
because i only want to run busybox on a little (embedded) i386 machine (and
not on my build machine!).

i traced parameters i386-uclibc-gcc passes to gcc but i cannot find any
mistake. of course i set KERNEL_SOURCE in uClibc/Config to the right path,
but there must be some place where it takes something from my running
kernel. any hints?

regards,
andreas neuhaus

> My suggestion would be to re-compile the uClibc libraries, and
> BusyBox against the new kernel code.  Make sure that the libraries and
> binaries are installing correctly, and you should be all set.  I have been
> using the 2.4.4 kernel for a while now (since just after it was released),
> and have had no problems with modules with CVS since the middle of last
> week.  That would be my second guess, is to update your version against
CVS.
> There were some issues with symlinks and search paths last week that were,
> thankfully, resolved.  BTW...Did I mention what Excellent work you all
have
> done?  ; ) Anyway, good luck, and keep us posted!
> > when i recently switched from kernel 2.4.2 to kernel 2.4.4 on my
embedded
> > system (using uClibc and busybox latest cvs version) i encountered a new
> > problem:
> > module msdos.o (msdos filesystem) needs to have fat.o loaded. when i
load
> > fat.o with busybox insmod, it shows up as (uninitialized) in lsmod and
> > when
> > trying insmod msdos.o, it complains about various unresolved symbols
> > (insmod: unresolved symbol fat_*). when using insmod from modutils
> > (statically linked to glibc), everything works (fat.o shows up as
(unused)
> > after doing insmod and insmod msdos.o works fine).
> > my busybox Config.h has BB_FEATURE_NEW_MODULE_INTERFACE and
> > BB_FEATURE_INSMOD_VERSION_CHECKING set. the kernel has CONFIG_MODULES
and
> > CONFIG_MODVERSIONS set.
> > did anybody else run into similar problems? i used an older busybox with
a
> > 2.4.2 kernel before and right now i don't know if my problem is related
to
> > the kernel update from 2.4.2 to 2.4.4 or because i'm now using a new
> > busybox
> > and uClibc version. i'll try to find out later today...