**** BEGIN LOGGING AT Sun Nov 09 03:00:00 2014 Nov 09 13:58:28 Hi guys, I am having a bit of a problem here. I want to build an image using yocto which would consist of cryptodev_linux.1.6. To build image I am following steps from quick guide provided by yocto project. in menuconfig of kernel, i enable cryptodev, however after build I cannot see a module, nor I can modprobe it. Anyone with solution here? Nov 09 13:59:11 and if I want to build from sources it is missing some unknown headers Nov 09 13:59:49 target machine - beaglebone black Nov 09 14:23:15 JustasMika: do you see any other modules in the rootfs? (/lib/modules// Nov 09 14:24:47 JustasMika: make sure that the conf/machine/ contains: IMAGE_INSTALL_append += " kernel-modules" Nov 09 14:45:34 in /lib/modules i see 1 folder, the kernel version named folder. I will try out kernel-modules, that most likely will solve Nov 09 16:35:06 okay, as I see this night somebody published same problem as I have https://bugzilla.yoctoproject.org/show_bug.cgi?id=6948 Nov 09 16:35:07 Bug 6948: normal, Undecided, ---, dvhart, NEW , cryptodev-linux depends on host kernel headers/build being present Nov 09 16:39:09 if anyone has some ideas for this one, would be nice :) Nov 09 20:45:44 ->> T0mW look, in /lib/module// there is missing build folder with rules, any ideas how to get it? which module is missing for that? Nov 09 21:03:33 RP, +1 on the ride Nov 09 21:05:46 sorry, can you direct me more detailed Nov 09 21:21:12 okay, I will ask again, getting desperate, trying to get cryptodev modules for several weeks know on beaglebone black and no success. building standard setup from yocto quick start, enabling in menuconfig the cryptodev module, everything goes fine, building with core-image-base aaaand no cryptodev in image, any ideas why? Nov 09 21:31:49 and the thing is during baking process i can see cryptodev being proccesed but its not being added to image Nov 09 21:38:15 well, that is a clue Nov 09 21:38:31 sound like you need to add that module to the image Nov 09 21:38:42 IMAGE_EXTRA_INSTALL or seomthing like that Nov 09 21:40:38 into imageextrainstall it gives error that there is no such package. in meta/recipes-kernel/cryptodev there is everything needed to cryptodev so it should add to image if I enable it through menuconfig, however it doesnt Nov 09 21:41:20 another weird thing, it create .ko files, but they are separate for each function like aes.ko, cbc.ko md5.ko Nov 09 21:41:28 should be only one cryptodev.ko Nov 09 21:46:11 will try clean build, maybe smth went wrong on the way :) Nov 09 22:17:50 stupid question, but never before tried building images and not too familiar with linux in that way.... anyway, what the difference between standard package and native? Nov 09 22:53:04 JustasMika: a "native" package is one that runs on the development host. Nov 09 22:54:15 okay, that makes sense, thank you Nov 09 22:54:41 JustasMika: try this, run 'bitbake -c devshell linux'. That will open a terminal and drop you onto a command line inside the linux build directory (for your TARGET). From there, you can work at '../temp/do_compile' or '../temp/do_compile_modules' Nov 09 22:55:10 JustasMika: umm, ../temp/run.do_compile, etc. Nov 09 22:56:29 You can work at resolving the linux build and modules build. Those go into ../image/ output directory within that recipe build tree. Nov 09 22:57:49 will try after image will be built! I will let you know most likely tmr how it went Nov 09 22:57:54 takes time :) Nov 09 22:59:08 JustasMika: this is what my kernel build tree looks like under devshell (tree -d -L 2): http://pastebin.com/jKs1mAyt Nov 09 23:00:24 JustasMika: take note of the kernel-module- (my modules to poplulate the rootfs), temp (where the logs and run tasks are located), image (result of the do_compile, do_compile_moudules). **** ENDING LOGGING AT Mon Nov 10 02:59:59 2014