**** BEGIN LOGGING AT Sat Mar 07 02:59:58 2015 Mar 07 19:11:21 I've set up a new layer, and I added a machine definition which is getting loaded, but it seems to be ignoring my directive for PREFERRED_PROVIDER_virtual/kernel Mar 07 19:14:27 I've got a directory recipes-kernel/linux in there, and a file matching the name specied Mar 07 19:14:41 PREFERRED_PROVIDER_virtual/kernel = "linux-rom-7420" Mar 07 19:14:41 PREFERRED_VERSION_linux-rom-7420 = "3.0.35" Mar 07 19:14:56 ./recipes-kernel/linux: Mar 07 19:14:58 linux-rom-7420 linux-rom-7420_3.0.35.bb linux-rom-7420.inc Mar 07 19:15:52 it's recofnizing the PREFERRED_PROVIDER entry for u-boot just fine Mar 07 19:16:00 recognizing Mar 07 20:09:17 cyclist: is everything in your layer/machine config? Mar 07 20:09:53 cyclist: and what is in your bblayers.conf? Mar 07 20:10:26 maybe you have extra yocto bsp layer still in there? Mar 07 20:11:22 * nerdboy thinking maybe layer order or priority? Mar 07 21:09:25 Sorry. I was away Mar 07 21:11:05 cd I'm going to try to add a "SECTION 'kernel'" to my config Mar 07 21:13:00 actually "PROVIDES kernel" Mar 07 21:16:32 now it's asking for entries for kernel-base, kernel-image, and kernel-module-* Mar 07 21:17:37 I used the config files from meta-fsl-arm as a basis Mar 07 21:23:48 I added "inherit kernel". that fixed it Mar 07 22:02:24 can i safely change my build dirs name to beagle-build ? Mar 07 22:03:00 how do I fix the hwclock Mar 07 22:03:11 I cant build any npm modules because it thinks its janurary 1st 2015 **** ENDING LOGGING AT Sun Mar 08 02:59:58 2015