[BusyBox] Problems with insmod and linux 2.6
wei gang
weiglink at gmail.com
Sun Jun 5 00:19:54 UTC 2005
All modules can't be loaded. I think part of the problem is caused by
insmod, but i don't know point of the problem.
when I do a 'uname -r', i get
2.6.9-hnx3
I use the MPU of Hynix's HMS30C7202 .
Best regards
> Is it just this module that fails, or all of them? Can you do a 'uname -r'
> and verify your kernel version?
>
>
> On 6/3/05, wei gang < weiglink at gmail.com> wrote:
> >
> > Hi,
> >
> > I built busybox with
> > #
> > CONFIG_INSMOD=y
> > #CONFIG_FEATURE_2_4_MODULES is not set
> > CONFIG_FEATURE_2_6_MODULES =y
> > #CONFIG_FEATURE_INSMOD_VERSION_CHECKING is not set
> > # CONFIG_FEATURE_INSMOD_KSYMOOPS_SYMBOLS is not set
> > # CONFIG_FEATURE_INSMOD_LOADINKMEM is not set
> > # CONFIG_FEATURE_INSMOD_LOAD_MAP is not set
> > CONFIG_LSMOD=y
> > CONFIG_FEATURE_QUERY_MODULE_INTERFACE=y
> > CONFIG_MODPROBE=y
> > CONFIG_RMMOD=y
> > # CONFIG_FEATURE_CHECK_TAINTED_MODULE is not set
> >
> > The kernel 2.6.9 was build with
> > #
> > # Loadable module support
> > #
> > CONFIG_MODULES=y
> > # CONFIG_MODVERSIONS is not set
> > CONFIG_KMOD=y
> >
> > But when I try to load an (external) module I get
> > # insmod g_multiser.ko
> > Using g_multiser.ko
> > insmod: Not configured to support old kernels
> >
> > I use buildroot to build toolchain for for a 2.6 kernel.
> >
> > Thanks!
> > _______________________________________________
> > busybox mailing list
> > busybox at mail.busybox.net
> > http://busybox.net/mailman/listinfo/busybox
> >
>
>
More information about the busybox
mailing list