On Thursday 12 March 2009 06:06:55 am Dallas Clement wrote: > I have been using busybox 1.12.1 for some time now and have been > successfully using the 'insmod' command to load certain kernel modules. > Everything was working great until I upgraded my cross-compiler toolchain > from gcc 4.1.1 and glibc 2.3.6 to gcc 4.2.4 and glibc 2.8. Everything else, > including kernel version remained unchanged. > > My application builds just fine with the new toolchain, however when I run > the application on the target, insmod is failing with the following error > message: > > "insmod: module <module name> not found"
insmod.c does not have such message. Are you sure you are using insmod and not modprobe? > Now I have checked and re-checked that the kernel modules I am trying to > load exist in this file system. They are definitely there. Yet insmod is > no longer able to find them or this error message is misleading and simply > masking another problem. Run "strace -o LOGFILE <your command here>" and post LOGFILE. Also post your busybox .config -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
