got it , thanks sorry for the inconvenience caused Eddy Lai
Hi Eddy, I see Bruce has responded to your question. In the future, please provide a proper subject to your emails. We get *a lot* of email and we need the subject to help us filter as well as find your email later. Thanks, Darren On 12/21/2012 03:01 PM, Lai Eddy wrote:Thanks Bruce, how can I "check to see if the kernel options were picked up and made it to the build by looking at the linux build directory and the .config, are you options present in the final .config ?" have read the "development manual", in chap.4.1.2.2 said ".config file found in the Build Directory at tmp/sysroots/<machine-name>/kernel" but there's no "kernel" folder in my "tmp/sysroots/jasperforest" , nor in "tmp/sysroots/x86_64" Eddy Lai ------------------------------ Message: 2 Date: Fri, 21 Dec 2012 00:54:47 -0500 Message-ID: <[email protected] <mailto:[email protected]>> Content-Type: text/plain; charset="windows-1252"; format=flowed On 12-12-20 7:54 PM, Lai Eddy wrote: > Hi , I'm using yocto 1.3 on jasperforest BSP, have build the USB flash > drive and boot on target h/w successfully. > after trying to add "igb" for intel 82580DB network controller support > in jasperforst.conf +?KERNEL_FEATURES_append = "features/igb"?, build > done but after the target boot, there's no eth0 port present > how can I check if the igb driver is inclued and loaded in the target? I'm out of the office at the moment, and doing this from memory, so sorry for not being completely precise. You can check to see if the kernel options were picked up and made it to the build by looking at the linux build directory and the .config, are you options present in the final .config ? If they are, then you'll also see the .ko's in the build tree, and those same modules packaged in the linux-yocto deploy directory. That means the modules are available. But they won't be autoloaded on boot unless you have an init script that modprobes it, or you have a recipe that makes use of the oe-core module loading framework. So I'd suggest a build, boot and a manual modprobe of the igb module. That will check everything that I mention above, and you'll have the dmesg output to tell you if something has gone wrong while inserting the module (versus a build time issue). Cheers, Bruce > or where?s wrong with that igb driver?_____________________________________________ > linux-yocto mailing list > [email protected] <mailto:[email protected]> > https://lists.yoctoproject.org/listinfo/linux-yocto _______________________________________________ linux-yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/linux-yocto
_______________________________________________ linux-yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/linux-yocto
