I'm definitely using insmod and not modprobe to load these modules from
initramfs.  This is the snippet of ash script which does the loading:

MOD_DIR=/lib/modules/2.6.21.1

insmod ${MOD_DIR}/scsi_mod.ko
insmod ${MOD_DIR}/sd_mod.ko
insmod ${MOD_DIR}/libata.ko
insmod ${MOD_DIR}/ahci.ko
insmod ${MOD_DIR}/ide-core.ko
insmod ${MOD_DIR}/ehci-hcd.ko
insmod ${MOD_DIR}/uhci-hcd.ko
insmod ${MOD_DIR}/usb-storage.ko

insmod ${MOD_DIR}/via82cxxx.ko

insmod ${MOD_DIR}/ide-generic.ko
insmod ${MOD_DIR}/ide-disk.ko

insmod ${MOD_DIR}/mbcache.ko
insmod ${MOD_DIR}/jbd.ko
insmod ${MOD_DIR}/ext2.ko
insmod ${MOD_DIR}/ext3.ko

insmod ${MOD_DIR}/edd.ko

The exact error message I am getting on the target when it tries to load the
first module is:

insmod: module '/lib/modules/2.6.21.1/scsi_mod.ko' not found

It's going to take me some time to incorporate the strace utility into my
app so that we can see what's happening at the system level.  I'll report
that a bit later.  For now, please find my busybox config attached.

Thanks for the help!

~Dallas

On Thu, Mar 12, 2009 at 6:49 AM, Denys Vlasenko <[email protected]>wrote:

> 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
>

Attachment: config-busybox-1.12.1
Description: Binary data

_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to