ah, that explains it then. Okay, so I've made a bit more progress. I added some more packages to my build my appending this to my build/conf/local.conf
CORE_IMAGE_EXTRA_INSTALL += "wpa-supplicant" CORE_IMAGE_EXTRA_INSTALL += "wireless-tools" #CORE_IMAGE_EXTRA_INSTALL += "resolveconf" CORE_IMAGE_EXTRA_INSTALL += "openssl" CORE_IMAGE_EXTRA_INSTALL += "zeroconf" CORE_IMAGE_EXTRA_INSTALL += "modutils-initscripts" CORE_IMAGE_EXTRA_INSTALL += "update-modules" This gives me depmod and the rest. Now I can manually load drivers and depmod -a succeeds. However, I still can't activate the wlan0. ifup wlan0 gives me root@overo:~# ifup wlan0 Could not read interface wlan0 flags: No such device WEXT: Could not set interface 'wlan0' UP wlan0: Failed to initialize driver interface On a hunch I looked at /var/log/messages and it says near the end: Jul 30 23:17:03 overo user.info kernel: libertas_sdio: Libertas SDIO driver Jul 30 23:17:03 overo user.info kernel: libertas_sdio: Copyright Pierre Ossman Jul 30 23:17:03 overo user.err kernel: libertas_sdio: failed to find firmware (-2) You mentioned the firmware. Where do I get that? Incidentally, I don't get all of the kernel boot messages when my gumstix boots. It says Starting kernel ... Uncompressing Linux... done, booting the kernel. Yocto (Built by Poky 7.0) 1.2+snapshot-20120730 overo ttyO2 overo login: And then I'm at the login prompt. I'm assuming there is some boot setting which controls this? All of the messages are showing up in /var/log/messages, however. Thanks, Josh On Jul 30, 2012, at 12:42 PM, ext Denys Dmytriyenko wrote: > On Mon, Jul 30, 2012 at 07:10:23PM +0000, [email protected] wrote: >> Hmm. I don't see to have depmod installed. Perhaps that is part of my >> problem. What package would I need to add to the minimal-core-image to get >> that? > > Josh, > > core-image-minimal uses busybox for tools like insmod and modprobe. The > default configuration for busybox does not have depmod enabled. As of > module-init-tools, they are being built, but not installed on the filesystem. > So, you can either modify busybox config to enable depmod, or add > module-init-tools-depmod package to your filesystem. The new way is to use > kmod, which is available in oe-core master, or meta-oe in denzil. But oe-core > master setup is broken for me at the moment, so I can't verify that kmod is > included. At least it's not listed in the image/task... > > Denys > > >> On Jul 30, 2012, at 1:07 AM, ext Enrico wrote: >> >>> On Sat, Jul 28, 2012 at 9:30 PM, <[email protected]> wrote: >>>> This does work. When I boot the wpa stuff is included but I still don't >>>> have a network driver loaded. If I include the built >>>> modules-3.2.19-r0-overo.tgz in my rootfs I can cd into the directory with >>>> all of the modules. However insmod libertas.ko fails with >>>> >>>> insmod: can't insert 'libertas_tf_usb.ko': unknown symbol in module, >>>> or unknown parameter >>>> >>>> and modprobe fails with >>>> >>>> modprobe: module libertas not found in modules.dep >>>> >>>> >>>> So, what should I do to make sure the libertas module is compiled >>>> correctly, included in my kernel, and then actually used at runtime? >>> >>> try with "depmod -a" (this must be done only once after you untar the >>> modules) before modprobe libertas. >>> >>> I am not sure but i think it was "modprobe libertas_sdio", try that >>> too. And of course you will need the libertas firmware >>> (sd8686....bin). >>> >>> Enrico >> >> _______________________________________________ >> meta-ti mailing list >> [email protected] >> https://lists.yoctoproject.org/listinfo/meta-ti _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
