[yocto] dizzy NUC missing wifi firmware
For the NUC, core-image-base seems to only include in /lib/firmware the ucode for the processor and the wifi firmware for the 6000 family of WiFi half-PCIe card adapters. I found with an n-135 wifi card there is no iwlwifi-135.6.ucode. I can manually add that firmware file or include all the linux-firmware in my build: IMAGE_INSTALL_append = linux-firmware What would be the correct way of including just the iwlwifi-135-ucode-18.168.6.1.tgz firmware?? Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] boot delay but recovery??
I'm booting Dizzy 1.7.1 on a Pandaboard (ARM). The image is core-image-base. My local.conf additions are : MACHINE ??= pandaboard IMAGE_INSTALL_append = oracle-jse-jre dropbear linux-firmware resolvconf LICENSE_FLAGS_WHITELIST += oracle_java I get a 30 second delay while the boot process hangs then kills a process. Not sure I know why. Can someone enlighten me. Below is the log showing what is happening before and after the delay: [6.087097] cfg80211: Calling CRDA to update world regulatory domain udevd[947]: worker [950] timeout, kill it udevd[947]: seq 1291 '/devices/platform/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' killed [ 36.711120] wl12xx: loaded udevd[947]: worker [950] terminated by signal 9 (Killed) Once the board is booted I have both LAN and WiFi and both are connected and working. It's just 30 seconds longer than it should be. Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ACPI powerbtn
Okay, I found a solution that works for core-image-base for NUC. 1. create /etc/acpi/events/powerbtn event=button[ /]power action=/etc/acpi/powerbtn.sh 2. create /etc/acpi/powerbtn.sh #!/bin/sh # /etc/acpi/powerbtn.sh # Initiates a shutdown when the power putton has been # pressed. /sbin/shutdown -h now Power button pressed 3. reboot From: jfaberna...@outlook.com Date: Wed, 4 Feb 2015 07:36:27 -0500 To: ross.bur...@intel.com CC: yocto@yoctoproject.org Subject: Re: [yocto] ACPI powerbtn On Feb 3, 2015, at 4:34 PM, Burton, Ross ross.bur...@intel.com wrote: On 3 February 2015 at 21:30, Jim Abernathy jfaberna...@outlook.com wrote: I need to add something that will 'shutdown -h now' when the power button is pressed. I would figure that ACPI is already included in the core-image-base of the NUC bsp. Do I need to include a new file in /etc/acpi/events or do I need to include some package? I'm literally signing off for the day but for what it's worth core-image-sato does that already on my NUC, so there must be something in that image that makes it work... maybe acpid or acpi-support isn't part of core-image-base? Ross I went back and built core-image-sato and the power button does nothing. I don’t see anything in the /etc/acpi/events directory. Same as core-image-base. Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] DNS nameservers in Yocto
I find that for Static IPs, I have to manually add my DNS name servers to /etc/resolv.conf instead of what I'm use to and that's put the line in /etc/network/interfaces with the dns-nameserver [IP] [IP]. My knowledge base comes from Ubuntu Server where putting everything in /etc/network/interfaces covers most things. Anyone know why? Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] DNS nameservers in Yocto
From: paul.eggle...@linux.intel.com To: d...@ripperd.com CC: jfaberna...@outlook.com; yocto@yoctoproject.org Subject: Re: [yocto] DNS nameservers in Yocto Date: Tue, 3 Feb 2015 18:11:12 + Hi Dean, On Tuesday 03 February 2015 11:20:01 Dean wrote: On 2/3/2015 9:43 AM, Jim Abernathy wrote: I find that for Static IPs, I have to manually add my DNS name servers to /etc/resolv.conf instead of what I'm use to and that's put the line in /etc/network/interfaces with the dns-nameserver [IP] [IP]. My knowledge base comes from Ubuntu Server where putting everything in /etc/network/interfaces covers most things. Anyone know why? Add resolvconf to your image. That being said, I'm using dora and the package there was very incomplete. I had to add quite a bit in a .bbappend to make it work properly. Would the issues you found have been fixed by this commit? http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=35e0a3eb6725781eb291b3fa90694a68c3b64c60 If not, we should really try to get these fixed in the original recipe - we'd certainly appreciate help there. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre Just adding 'resolvconf' fixed my issue on dizzy. Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ACPI powerbtn
I need to add something that will 'shutdown -h now' when the power button is pressed. I would figure that ACPI is already included in the core-image-base of the NUC bsp. Do I need to include a new file in /etc/acpi/events or do I need to include some package? Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Checksum failure encountered Java
Date: Mon, 2 Feb 2015 11:07:05 +0100 From: maxin.j...@enea.com To: jfaberna...@outlook.com CC: yocto@yoctoproject.org Subject: Re: [yocto] Checksum failure encountered Java Hi Jim, On Sun, Feb 01, 2015 at 10:58:02AM -0500, Jim Abernathy wrote: after I posted this issues, I tried to click on the link at the Oracle site and there is something about accepting a License. I have the LICENSE_FLAGS_WHITELIST += oracle_java which worked on the NUC build. I'm guessing that's not the issue. Since Oracle download webpage has an accept license button, the downloading process is on a best effort basis one. If the download fails for a particular binary, please go to the oracle download webpage and download the tarball. Move that binary to the bitbake download location as mentioned in local.conf file and build again. Sorry for the trouble and I think, we should update the README to reflect this process (again). Please note that the arm binary is pre-built for vfp-hflt (hard-float) and it may have troubles with root-filesystem built with soft-float support. Jim A Best Regards, Maxin thanks, but here's a dumb question for you. Since I'm using a Pandaboard, is it hard-float or soft-float? And are you referring to the oracle binary or the BSP I'm using. Jim A ━━━ From: jfaberna...@outlook.com To: yocto@yoctoproject.org Date: Sun, 1 Feb 2015 10:53:28 -0500 Subject: [yocto] Checksum failure encountered Java I tried to move a build from NUC to Pandaboard and the core-image-sato worked fine, well except the README.HARDWARE for arm didn't mention coping the uImage to /boot. Figured that out easy enough. But when I tried to add oracle-jse-jre that worked fine on NUC got the following errors: WARNING: Checksum failure encountered with download of http:// download.oracle.com/otn/java/ejre/7u60-b19/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz - will attempt other sources if available WARNING: Renaming /work/downloads/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz to / work/downloads/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz_bad-checksum_b72400960629e7403c4b579dada2a804 ERROR: Fetcher failure for URL: 'http://download.oracle.com/otn/java/ejre/ 7u60-b19/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'. Checksum mismatch! File: '/work/downloads/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz' has md5 checksum b72400960629e7403c4b579dada2a804 when b9b8f598b0a7f49e4d221f16ba25c6c0 was expected File: '/work/downloads/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz' has sha256 checksum c4a64be693e0e27ca95ffe3036c56156e3d75e07f620fd913308eb03cdf86779 when ed061060011d88efe5563c2949c00993db85db17ab94f18a78713007a2b90faf was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[md5sum] = b72400960629e7403c4b579dada2a804 SRC_URI[sha256sum] = c4a64be693e0e27ca95ffe3036c56156e3d75e07f620fd913308eb03cdf86779 Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified. ERROR: Function failed: Fetcher failure for URL: 'http://download.oracle.com/ otn/java/ejre/7u60-b19/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /work/pandaboard/tmp/work/ cortexa9t2hf-vfp-neon-poky-linux-gnueabi/oracle-jse-jre/1.7.0-u60r0/temp/ log.do_fetch.31677 ERROR: Task 231 (/home/jim/poky/meta-oracle-java/recipes-devtools/oracle-java/ oracle-jse-jre_1.7.0.bb, do_fetch) failed with exit code '1' Should I just change the checksum locally or what??? Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Checksum failure encountered Java
downloading the JRE file from the Oracle site to the working download directory solved my build problem. This image boots and now I'm testing java. So far so good. Since the Pandaboard uses an OMAP4430, I think it's hard-float. Jim A From: jfaberna...@outlook.com To: maxin.j...@enea.com Date: Mon, 2 Feb 2015 09:48:15 -0500 CC: yocto@yoctoproject.org Subject: Re: [yocto] Checksum failure encountered Java Date: Mon, 2 Feb 2015 11:07:05 +0100 From: maxin.j...@enea.com To: jfaberna...@outlook.com CC: yocto@yoctoproject.org Subject: Re: [yocto] Checksum failure encountered Java Hi Jim, On Sun, Feb 01, 2015 at 10:58:02AM -0500, Jim Abernathy wrote: after I posted this issues, I tried to click on the link at the Oracle site and there is something about accepting a License. I have the LICENSE_FLAGS_WHITELIST += oracle_java which worked on the NUC build. I'm guessing that's not the issue. Since Oracle download webpage has an accept license button, the downloading process is on a best effort basis one. If the download fails for a particular binary, please go to the oracle download webpage and download the tarball. Move that binary to the bitbake download location as mentioned in local.conf file and build again. Sorry for the trouble and I think, we should update the README to reflect this process (again). Please note that the arm binary is pre-built for vfp-hflt (hard-float) and it may have troubles with root-filesystem built with soft-float support. Jim A Best Regards, Maxin thanks, but here's a dumb question for you. Since I'm using a Pandaboard, is it hard-float or soft-float? And are you referring to the oracle binary or the BSP I'm using. Jim A ━━━ From: jfaberna...@outlook.com To: yocto@yoctoproject.org Date: Sun, 1 Feb 2015 10:53:28 -0500 Subject: [yocto] Checksum failure encountered Java I tried to move a build from NUC to Pandaboard and the core-image-sato worked fine, well except the README.HARDWARE for arm didn't mention coping the uImage to /boot. Figured that out easy enough. But when I tried to add oracle-jse-jre that worked fine on NUC got the following errors: WARNING: Checksum failure encountered with download of http:// download.oracle.com/otn/java/ejre/7u60-b19/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz - will attempt other sources if available WARNING: Renaming /work/downloads/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz to / work/downloads/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz_bad-checksum_b72400960629e7403c4b579dada2a804 ERROR: Fetcher failure for URL: 'http://download.oracle.com/otn/java/ejre/ 7u60-b19/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'. Checksum mismatch! File: '/work/downloads/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz' has md5 checksum b72400960629e7403c4b579dada2a804 when b9b8f598b0a7f49e4d221f16ba25c6c0 was expected File: '/work/downloads/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz' has sha256 checksum c4a64be693e0e27ca95ffe3036c56156e3d75e07f620fd913308eb03cdf86779 when ed061060011d88efe5563c2949c00993db85db17ab94f18a78713007a2b90faf was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[md5sum] = b72400960629e7403c4b579dada2a804 SRC_URI[sha256sum] = c4a64be693e0e27ca95ffe3036c56156e3d75e07f620fd913308eb03cdf86779 Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified. ERROR: Function failed: Fetcher failure for URL: 'http://download.oracle.com/ otn/java/ejre/7u60-b19/ ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /work/pandaboard/tmp/work/ cortexa9t2hf-vfp-neon-poky-linux-gnueabi/oracle-jse-jre/1.7.0-u60r0/temp/ log.do_fetch.31677 ERROR: Task 231 (/home/jim/poky/meta-oracle-java/recipes-devtools/oracle-java/ oracle-jse-jre_1.7.0.bb, do_fetch) failed with exit code '1' Should I just change the checksum locally or what??? Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-ti/pandaboard
I've noticed a few issues with the pandaboard image that builds. 1. core-image-sato does not have WiFi capability. I think it's missing firmware. 2. core-image-base is missing the linux-firmware. I added: IMAGE_INSTALL_append = linux-firmware. Now I have the necessary firmware to bring up the WiFi. 3. There is some delay cause in booting that affect the ability to have WiFi active after boot. I have to wait a few minutes until I see the error and recovery before doing the ifup wlan0. dmesg | grep wl12 gives me the following output: [0.396392] vwl1271: 1800 mV [ 67.167297] wl12xx: ERROR could not get nvs file ti-connectivity/wl1271-nvs.bin: -2 [ 67.181457] wl12xx: loaded (once I see the message above I can ifup wlan0 which produces this output below and WiFi now is working: [ 135.964355] wl12xx: firmware booted (Rev 6.3.5.0.98) [ 137.979522] wl12xx: Association completed. Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Checksum failure encountered Java
after I posted this issues, I tried to click on the link at the Oracle site and there is something about accepting a License. I have the LICENSE_FLAGS_WHITELIST += oracle_java which worked on the NUC build. I'm guessing that's not the issue. Jim A From: jfaberna...@outlook.com To: yocto@yoctoproject.org Date: Sun, 1 Feb 2015 10:53:28 -0500 Subject: [yocto] Checksum failure encountered Java I tried to move a build from NUC to Pandaboard and the core-image-sato worked fine, well except the README.HARDWARE for arm didn't mention coping the uImage to /boot. Figured that out easy enough. But when I tried to add oracle-jse-jre that worked fine on NUC got the following errors: WARNING: Checksum failure encountered with download of http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz - will attempt other sources if available WARNING: Renaming /work/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz to /work/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz_bad-checksum_b72400960629e7403c4b579dada2a804 ERROR: Fetcher failure for URL: 'http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'. Checksum mismatch! File: '/work/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz' has md5 checksum b72400960629e7403c4b579dada2a804 when b9b8f598b0a7f49e4d221f16ba25c6c0 was expected File: '/work/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz' has sha256 checksum c4a64be693e0e27ca95ffe3036c56156e3d75e07f620fd913308eb03cdf86779 when ed061060011d88efe5563c2949c00993db85db17ab94f18a78713007a2b90faf was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[md5sum] = b72400960629e7403c4b579dada2a804 SRC_URI[sha256sum] = c4a64be693e0e27ca95ffe3036c56156e3d75e07f620fd913308eb03cdf86779 Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified. ERROR: Function failed: Fetcher failure for URL: 'http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /work/pandaboard/tmp/work/cortexa9t2hf-vfp-neon-poky-linux-gnueabi/oracle-jse-jre/1.7.0-u60r0/temp/log.do_fetch.31677 ERROR: Task 231 (/home/jim/poky/meta-oracle-java/recipes-devtools/oracle-java/oracle-jse-jre_1.7.0.bb, do_fetch) failed with exit code '1' Should I just change the checksum locally or what??? Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Checksum failure encountered Java
I tried to move a build from NUC to Pandaboard and the core-image-sato worked fine, well except the README.HARDWARE for arm didn't mention coping the uImage to /boot. Figured that out easy enough. But when I tried to add oracle-jse-jre that worked fine on NUC got the following errors: WARNING: Checksum failure encountered with download of http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz - will attempt other sources if available WARNING: Renaming /work/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz to /work/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz_bad-checksum_b72400960629e7403c4b579dada2a804 ERROR: Fetcher failure for URL: 'http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'. Checksum mismatch! File: '/work/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz' has md5 checksum b72400960629e7403c4b579dada2a804 when b9b8f598b0a7f49e4d221f16ba25c6c0 was expected File: '/work/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz' has sha256 checksum c4a64be693e0e27ca95ffe3036c56156e3d75e07f620fd913308eb03cdf86779 when ed061060011d88efe5563c2949c00993db85db17ab94f18a78713007a2b90faf was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[md5sum] = b72400960629e7403c4b579dada2a804 SRC_URI[sha256sum] = c4a64be693e0e27ca95ffe3036c56156e3d75e07f620fd913308eb03cdf86779 Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified. ERROR: Function failed: Fetcher failure for URL: 'http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /work/pandaboard/tmp/work/cortexa9t2hf-vfp-neon-poky-linux-gnueabi/oracle-jse-jre/1.7.0-u60r0/temp/log.do_fetch.31677 ERROR: Task 231 (/home/jim/poky/meta-oracle-java/recipes-devtools/oracle-java/oracle-jse-jre_1.7.0.bb, do_fetch) failed with exit code '1' Should I just change the checksum locally or what??? Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding meta-oracle-java
Date: Wed, 28 Jan 2015 11:20:21 +0100 Subject: Re: [yocto] adding meta-oracle-java From: ma...@maxinbjohn.info To: paul.eggle...@linux.intel.com CC: jfaberna...@outlook.com; yocto@yoctoproject.org Hi Jim, On Wed, Jan 28, 2015 at 10:25 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: Hi Jim, On Tuesday 27 January 2015 15:24:09 James Abernathy wrote: In looking at the meta-oracle-java README, I see the notes about adding the License statement and switching to .deb packaging. With that done, I get a clean build, but my image boots and I can’t see any evidence that java was included. What am I missing. I have a web app server that in all inclusive and can be setup just by running “java -jar .jar”. But can’t run it without java installed. I assume you've just added the layer to your bblayers.conf - if so you've missed the next step of actually adding additional packages produced by recipes in the layer to your image. I haven't tried it but I assume the package to add would be oracle-jse-jre. As mentioned here, if you include oracle-jse-jre in the image, things should work as expected (IMAGE_INSTALL_append = oracle-jse-jre) root@qemux86:~# ls -la /usr/bin/java lrwxrwxrwx1 root root31 Jan 28 10:11 /usr/bin/java - /usr/share/jre1.7.0_67/bin/java root@qemux86:~# java -version java version 1.7.0_67 Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Java HotSpot(TM) Client VM (build 24.65-b04, mixed mode) Cheers, Paul Best Regards, Maxin Thanks, I guess the problem for me stems from not knowing the difference between, IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL, which I was using. Can you explain? Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding meta-oracle-java
From: paul.eggle...@linux.intel.com To: jfaberna...@outlook.com CC: ma...@maxinbjohn.info; yocto@yoctoproject.org Subject: Re: [yocto] adding meta-oracle-java Date: Wed, 28 Jan 2015 10:55:23 + On Wednesday 28 January 2015 05:44:47 Jim Abernathy wrote: Thanks, I guess the problem for me stems from not knowing the difference between, IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL, which I was using. Basically, the only difference is that CORE_IMAGE_EXTRA_INSTALL will only work with image recipes that inherit core-image. If the recipe inherits image, its value won't be used. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre thank, well I got the java included in my build, but I can't execute it. very strange! I see java is at /usr/share/java/bin and there's a link to java in the /usr/bin, but at the command line I can't run, java -version. I get java not found. It's like it a shell problem. I had the same issue when I just installed the tarball for JRE on a standard core-image-base before. I'm running as the only user on the system, root. Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding meta-oracle-java
Date: Wed, 28 Jan 2015 13:01:02 +0100 Subject: Re: [yocto] adding meta-oracle-java From: ma...@maxinbjohn.info To: jfaberna...@outlook.com CC: paul.eggle...@linux.intel.com; yocto@yoctoproject.org Hi Jim, On Wed, Jan 28, 2015 at 12:21 PM, Jim Abernathy jfaberna...@outlook.com wrote: From: paul.eggle...@linux.intel.com To: jfaberna...@outlook.com CC: ma...@maxinbjohn.info; yocto@yoctoproject.org Subject: Re: [yocto] adding meta-oracle-java Date: Wed, 28 Jan 2015 10:55:23 + On Wednesday 28 January 2015 05:44:47 Jim Abernathy wrote: Thanks, I guess the problem for me stems from not knowing the difference between, IMAGE_INSTALL_append and CORE_IMAGE_EXTRA_INSTALL, which I was using. Basically, the only difference is that CORE_IMAGE_EXTRA_INSTALL will only work with image recipes that inherit core-image. If the recipe inherits image, its value won't be used. Cheers, Paul thank, well I got the java included in my build, but I can't execute it. very strange! I see java is at /usr/share/java/bin and there's a link to java in the /usr/bin, but at the command line I can't run, java -version. I get java not found. It's like it a shell problem. I had the same issue when I just installed the tarball for JRE on a standard core-image-base before. This can also be related to the architecture difference of java binary. Can you share the output of file command on java binary along with MACHINE and other related details in local.conf file? I'm running as the only user on the system, root. Jim A Warm Regards, Maxin well the file command does not run on the target machine same as java, not found error. as to the local.conf file. The only changes are as follows: MACHINE ?= nuc IMAGE_INSTALL_append = oracle-jse-jre dropbear LICENSE_FLAGS_WHITELIST += oracle_java # DL_DIR ?= /work/downloads #PACKAGE_CLASSES ?= package_rpm PACKAGE_CLASSES = package_deb I build with bitbake core-image-base. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding meta-oracle-java
Date: Wed, 28 Jan 2015 15:26:24 +0100 Subject: Re: [yocto] adding meta-oracle-java From: ma...@maxinbjohn.info To: jfaberna...@outlook.com CC: paul.eggle...@linux.intel.com; yocto@yoctoproject.org Hi, On Wed, Jan 28, 2015 at 1:10 PM, Jim Abernathy jfaberna...@outlook.com wrote: snip well the file command does not run on the target machine same as java, not found error. as to the local.conf file. The only changes are as follows: MACHINE ?= nuc IMAGE_INSTALL_append = oracle-jse-jre dropbear LICENSE_FLAGS_WHITELIST += oracle_java # DL_DIR ?= /work/downloads #PACKAGE_CLASSES ?= package_rpm PACKAGE_CLASSES = package_deb I build with bitbake core-image-base. From the nuc image on qemu, I get this output for file command: # file bin/busybox.nosuid bin/busybox.nosuid: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=d87821503ef9cc2a5bed4a284cac138211a649ff, stripped # file /usr/share/jre1.7.0_67/bin/java /usr/share/jre1.7.0_67/bin/java: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.9, BuildID[sha1]=b82a586842f6da3df8a61093daadf0 / # java /bin/sh: java: not found Could be related to the library path. Continuing with investigation. Best Regards, Maxin I just created a qemux86 image for core-image-base with meta-java in it and after booting in the emulator, it, of course, gives the proper response to java -version. I'm going to try building a qemux86-64 to see if there's any difference. On real NUC hardware it will not, as mentioned, work correctly. Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding meta-oracle-java
Date: Wed, 28 Jan 2015 17:36:14 +0100 Subject: Re: [yocto] adding meta-oracle-java From: ma...@maxinbjohn.info To: jfaberna...@outlook.com CC: paul.eggle...@linux.intel.com; yocto@yoctoproject.org Hi Jim, On Wed, Jan 28, 2015 at 3:58 PM, Jim Abernathy jfaberna...@outlook.com wrote: snip I just created a qemux86 image for core-image-base with meta-java in it and after booting in the emulator, it, of course, gives the proper response to java -version. I'm going to try building a qemux86-64 to see if there's any difference. On real NUC hardware it will not, as mentioned, work correctly. In NUC, please execute these commands: # ln -s /lib /lib64 # export PATH=/usr/share/jre1.7.0_67/bin:$PATH # java Jim A Best Regards, Maxin Good, that fixes it. BTW, I found it also fails on qemux86-64, so this makes sense. Is this something that can be made part of the meta-java recipe?? Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding all the pieces of WiFi to core-image-minimal
From: thomas.moo...@atk.com To: jfaberna...@outlook.com CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal Date: Mon, 26 Jan 2015 21:04:54 + For now, I'd just get everything working with the local.conf: DISTRO_FEATURES += wifi bitbake core-image-base Ultimately, you may want to make a custom machine and distro config and incorporate all of the things you've specified in local.conf in those configs. For example, I have a system that's an intel-based single-board computer with several expansion cards. I've created a machine configuration to define the basic hardware components (features, drivers, etc). I've also created a custom distro because we prefer system over systemv and to include some other non-machine specific packages. Finally, I've created a custom image that includes some other extras. The power of local.conf is nice, but it's a little tricky transitioning from that to more of a BSP approach like I described above because most people just say to add it to your local.conf, but that's not really how it should be done at the end. Think global variables vs classes. P.S. Never edit anything in the poky folder. If you want to modify an existing recipe, create a new layer with a bbappend and modify away. Thomas I tried just adding DISTRO_FEATURES += wifi to the local.conf and bitbaking core-image-base, but I got a lot of errors: NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'glibc' ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in DISTRO_FEATURES) ERROR: Required build target 'core-image-base' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-base', 'glibc'] So I got it working with core-image-minimal as I mentioned earlier just before your reply. -Original Message- From: James Abernathy [mailto:jfaberna...@outlook.com] Sent: Monday, January 26, 2015 2:53 PM To: Moore, Thomas (FtWorth) Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth) thomas.moo...@atk.com wrote: Try building core-image-base or adding packagegroup-base-extended to your IMAGE_INSTALL. This should add the modules and firmware. core-image-minimal is just that and only includes just enough to boot the system. P.S. if you add wifi to your DISTRO_FEATURES, then packagegroup-base-wifi should automatically get added to the image. Checkout meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works. Thomas Interesting! are we talking about doing this in the local.conf? or are we talking about modifying existing recipes? I'd like to do this cleanly and not mess up what's in the default files. Maybe create my own layer?? Jim A From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Chris Tapp Sent: Monday, January 26, 2015 2:28 PM To: James Abernathy Cc: yocto@yoctoproject.org; Gary Thomas Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal On 26 Jan 2015, at 19:31, James Abernathy jfaberna...@outlook.com wrote: I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += packagegroup-base-wifi However, I have no wireless drivers. I must have to add something to add the drivers and firmware to the kernel. Not sure what though. I'm not an expert here, but I think that adding kernel-modules and linux-firmware to your extra_install should give you what you need. Jim A On Jan 26, 2015, at 11:09 AM, James Abernathy jfaberna...@outlook.com wrote: On Jan 26, 2015, at 10:52 AM, Gary Thomas g...@mlbassoc.com wrote: On 2015-01-26 08:26, James Abernathy wrote: On Jan 26, 2015, at 8:49 AM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2015-01-26 06:29, James Abernathy wrote: On Jan 23, 2015, at 12:37 PM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2015-01-23 10:24, Jim Abernathy wrote: I'm starting a project mostly for self-education. I have already done the project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as targets. Now I want to see how easy it is to move it to Yocto. Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and core-image-sato, both built with bitbake and not the prebuilt images. However, core-image-minimal doesn't have WiFi and core-image-sato does, but I don't need all the GUI stuff. It's a headless application. So what is recommended; eliminating the GUI from sato or adding wifi and wpa-supplicant, etc to minimal?? Also any pointers to how to do the adding/subtracting would be most helpful. Once
Re: [yocto] adding all the pieces of WiFi to core-image-minimal
I was just coming to the realization that core-image-minimal isn't what I wanted. So I'll experiment with core-image-base and a minimal set of local.conf statements that give me what I need. Thanks, Jim A From: thomas.moo...@atk.com To: jfaberna...@outlook.com CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal Date: Mon, 26 Jan 2015 22:23:12 + core-image-base installs packagegroup-base-extended, whereas core-image-minimal doesn’t. packagegroup-base-extended adds things like kernel modules and other package groups that you’ll want for a more full-featured system. Thomas From: Jim Abernathy [mailto:jfaberna...@outlook.com] Sent: Monday, January 26, 2015 3:54 PM To: Moore, Thomas (FtWorth) Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal From: thomas.moo...@atk.com To: jfaberna...@outlook.com CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal Date: Mon, 26 Jan 2015 21:51:47 + Looks like you also need to add ipv4 to the DISTRO_FEATURES: DISTRO_FEATURES += ipv4 wifi Might be worth trying. Thomas I'll test with it, but why core-image-base vs. core-image-minimal? Jim A From: Jim Abernathy [mailto:jfaberna...@outlook.com] Sent: Monday, January 26, 2015 3:38 PM To: Moore, Thomas (FtWorth) Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal From: thomas.moo...@atk.com To: jfaberna...@outlook.com CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal Date: Mon, 26 Jan 2015 21:04:54 + For now, I'd just get everything working with the local.conf: DISTRO_FEATURES += wifi bitbake core-image-base Ultimately, you may want to make a custom machine and distro config and incorporate all of the things you've specified in local.conf in those configs. For example, I have a system that's an intel-based single-board computer with several expansion cards. I've created a machine configuration to define the basic hardware components (features, drivers, etc). I've also created a custom distro because we prefer system over systemv and to include some other non-machine specific packages. Finally, I've created a custom image that includes some other extras. The power of local.conf is nice, but it's a little tricky transitioning from that to more of a BSP approach like I described above because most people just say to add it to your local.conf, but that's not really how it should be done at the end. Think global variables vs classes. P.S. Never edit anything in the poky folder. If you want to modify an existing recipe, create a new layer with a bbappend and modify away. Thomas I tried just adding DISTRO_FEATURES += wifi to the local.conf and bitbaking core-image-base, but I got a lot of errors: NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'glibc' ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in DISTRO_FEATURES) ERROR: Required build target 'core-image-base' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-base', 'glibc'] So I got it working with core-image-minimal as I mentioned earlier just before your reply. -Original Message- From: James Abernathy [mailto:jfaberna...@outlook.com] Sent: Monday, January 26, 2015 2:53 PM To: Moore, Thomas (FtWorth) Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth) thomas.moo...@atk.com wrote: Try building core-image-base or adding packagegroup-base-extended to your IMAGE_INSTALL. This should add the modules and firmware. core-image-minimal is just that and only includes just enough to boot the system. P.S. if you add wifi to your DISTRO_FEATURES, then packagegroup-base-wifi should automatically get added to the image. Checkout meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works. Thomas Interesting! are we talking about doing this in the local.conf? or are we talking about modifying existing recipes? I'd like to do this cleanly and not mess up what's in the default files. Maybe create my own layer?? Jim A From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Chris Tapp Sent: Monday, January 26, 2015 2:28 PM To: James Abernathy Cc: yocto@yoctoproject.org; Gary Thomas Subject: Re: [yocto] adding all the pieces of WiFi to core-image
Re: [yocto] adding all the pieces of WiFi to core-image-minimal
From: thomas.moo...@atk.com To: jfaberna...@outlook.com CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal Date: Mon, 26 Jan 2015 21:51:47 + Looks like you also need to add ipv4 to the DISTRO_FEATURES: DISTRO_FEATURES += ipv4 wifi Might be worth trying. Thomas I'll test with it, but why core-image-base vs. core-image-minimal? Jim A From: Jim Abernathy [mailto:jfaberna...@outlook.com] Sent: Monday, January 26, 2015 3:38 PM To: Moore, Thomas (FtWorth) Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal From: thomas.moo...@atk.com To: jfaberna...@outlook.com CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal Date: Mon, 26 Jan 2015 21:04:54 + For now, I'd just get everything working with the local.conf: DISTRO_FEATURES += wifi bitbake core-image-base Ultimately, you may want to make a custom machine and distro config and incorporate all of the things you've specified in local.conf in those configs. For example, I have a system that's an intel-based single-board computer with several expansion cards. I've created a machine configuration to define the basic hardware components (features, drivers, etc). I've also created a custom distro because we prefer system over systemv and to include some other non-machine specific packages. Finally, I've created a custom image that includes some other extras. The power of local.conf is nice, but it's a little tricky transitioning from that to more of a BSP approach like I described above because most people just say to add it to your local.conf, but that's not really how it should be done at the end. Think global variables vs classes. P.S. Never edit anything in the poky folder. If you want to modify an existing recipe, create a new layer with a bbappend and modify away. Thomas I tried just adding DISTRO_FEATURES += wifi to the local.conf and bitbaking core-image-base, but I got a lot of errors: NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'glibc' ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in DISTRO_FEATURES) ERROR: Required build target 'core-image-base' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-base', 'glibc'] So I got it working with core-image-minimal as I mentioned earlier just before your reply. -Original Message- From: James Abernathy [mailto:jfaberna...@outlook.com] Sent: Monday, January 26, 2015 2:53 PM To: Moore, Thomas (FtWorth) Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth) thomas.moo...@atk.com wrote: Try building core-image-base or adding packagegroup-base-extended to your IMAGE_INSTALL. This should add the modules and firmware. core-image-minimal is just that and only includes just enough to boot the system. P.S. if you add wifi to your DISTRO_FEATURES, then packagegroup-base-wifi should automatically get added to the image. Checkout meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works. Thomas Interesting! are we talking about doing this in the local.conf? or are we talking about modifying existing recipes? I'd like to do this cleanly and not mess up what's in the default files. Maybe create my own layer?? Jim A From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Chris Tapp Sent: Monday, January 26, 2015 2:28 PM To: James Abernathy Cc: yocto@yoctoproject.org; Gary Thomas Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal On 26 Jan 2015, at 19:31, James Abernathy jfaberna...@outlook.com wrote: I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += packagegroup-base-wifi However, I have no wireless drivers. I must have to add something to add the drivers and firmware to the kernel. Not sure what though. I'm not an expert here, but I think that adding kernel-modules and linux-firmware to your extra_install should give you what you need. Jim A On Jan 26, 2015, at 11:09 AM, James Abernathy jfaberna...@outlook.com wrote: On Jan 26, 2015, at 10:52 AM, Gary Thomas g...@mlbassoc.com wrote: On 2015-01-26 08:26, James Abernathy wrote: On Jan 26, 2015, at 8:49 AM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2015-01-26 06:29, James Abernathy wrote: On Jan 23, 2015, at 12:37 PM, Gary Thomas g...@mlbassoc.com
[yocto] adding all the pieces of WiFi to core-image-minimal
I'm starting a project mostly for self-education. I have already done the project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as targets. Now I want to see how easy it is to move it to Yocto. Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and core-image-sato, both built with bitbake and not the prebuilt images. However, core-image-minimal doesn't have WiFi and core-image-sato does, but I don't need all the GUI stuff. It's a headless application. So what is recommended; eliminating the GUI from sato or adding wifi and wpa-supplicant, etc to minimal?? Also any pointers to how to do the adding/subtracting would be most helpful. Once this is working all I have to do is put apache-tomcat, and openjdk-7-jre, then my application. thanks, JimA -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Recipe differences between Danny and Master
I have a recipe layers I use for test videos and audios that I included
in prior BSPs I've done. The last I tested it was Danny and it worked
fine. Today I tried to add it to a BSP that had previously built, using
the latest pull from Master, complete without errors and booted.
Once I added my layer, it built with a number of errors. So something
has changed, that I missed. Below is my one of my recipes and the
console log:
DESCRIPTION = my audio test files
SECTION = examples
LICENSE = CLOSED
MY_DESTINATION = /home/root/myaudios
SRC_URI = file://myaudios-1.0/myaudios-1.0.tar.gz
do_install_append() {
install -d ${D}${MY_DESTINATION}
install -m 0644 ${S}/* ${D}${MY_DESTINATION}
}
PR = r0
FILES_${PN} += ${MY_DESTINATION}/*
--
jim@jim-ubuntu-x64:/build/nuc-master$ bitbake core-image-sato
WARNING: Unable to get checksum for myvideos SRC_URI entry
myvideos-1.0.tar.gz: file could not be found
WARNING: Unable to get checksum for myaudios SRC_URI entry
myaudios-1.0.tar.gz: file could not be found
Parsing recipes: 100%
|###| Time: 00:00:11
Parsing of 842 .bb files complete (0 cached, 842 parsed). 1149 targets,
24 skipped, 0 masked, 0 errors.
Build Configuration:
BB_VERSION= 1.17.0
BUILD_SYS = x86_64-linux
NATIVELSBSTRING = Ubuntu-12.04
TARGET_SYS= x86_64-poky-linux
MACHINE = nuc
DISTRO= poky
DISTRO_VERSION= 1.3+snapshot-20121217
TUNE_FEATURES = m64
TARGET_FPU=
meta
meta-yocto
meta-yocto-bsp= master:958162e96b4a4f23bca94500b5f20975633dd5c6
meta-intel
meta-nuc = master:4122c514a22442a58b2f99e4ba9617ff219b3089
meta-jfa = unknown:unknown
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: Failed to fetch URL file://myaudios-1.0/myaudios-1.0.tar.gz,
attempting MIRRORS if available
WARNING: Failed to fetch URL file://myvideos-1.0/myvideos-1.0.tar.gz,
attempting MIRRORS if available
ERROR: Fetcher failure: Unable to find file
file://myaudios-1.0/myaudios-1.0.tar.gz anywhere. The paths that were
searched were:
/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios-1.0/x86-64
/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios-1.0/nuc
/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios-1.0/poky
/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios-1.0/
/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios/x86-64
/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios/nuc
/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios/poky
/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios/
/home/jim/meta-jfa/recipes-jfa/myaudio/files/x86-64
/home/jim/meta-jfa/recipes-jfa/myaudio/files/nuc
/home/jim/meta-jfa/recipes-jfa/myaudio/files/poky
/home/jim/meta-jfa/recipes-jfa/myaudio/files/
/home/jim/yocto-downloads
ERROR: Function failed: Fetcher failure for URL:
'file://myaudios-1.0/myaudios-1.0.tar.gz'. Unable to fetch URL from any
source.
ERROR: Logfile of failure stored in:
/build/nuc-master/tmp/work/x86_64-poky-linux/myaudios/1.0-r0/temp/log.do_fetch.29282
ERROR: Fetcher failure: Unable to find file
file://myvideos-1.0/myvideos-1.0.tar.gz anywhere. The paths that were
searched were:
/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos-1.0/x86-64
/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos-1.0/nuc
/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos-1.0/poky
/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos-1.0/
/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos/x86-64
/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos/nuc
/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos/poky
/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos/
/home/jim/meta-jfa/recipes-jfa/myvideos/files/x86-64
/home/jim/meta-jfa/recipes-jfa/myvideos/files/nuc
/home/jim/meta-jfa/recipes-jfa/myvideos/files/poky
/home/jim/meta-jfa/recipes-jfa/myvideos/files/
/home/jim/yocto-downloads
ERROR: Function failed: Fetcher failure for URL:
'file://myvideos-1.0/myvideos-1.0.tar.gz'. Unable to fetch URL from any
source.
ERROR: Logfile of failure stored in:
/build/nuc-master/tmp/work/x86_64-poky-linux/myvideos/1.0-r0/temp/log.do_fetch.29283
ERROR: Task 353 (/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios.bb,
do_fetch) failed with exit code '1'
ERROR: Task 341 (/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos.bb,
do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4122 tasks of which 4109 didn't need to
be rerun and 2 failed.
Waiting for 0 running tasks to finish:
Summary: 2 tasks failed:
/home/jim/meta-jfa/recipes-jfa/myaudio/myaudios.bb, do_fetch
/home/jim/meta-jfa/recipes-jfa/myvideos/myvideos.bb, do_fetch
Summary: There were 4 WARNING messages shown.
Summary: There were 4 ERROR messages shown, returni
Re: [yocto] Recipe differences between Danny and Master
On 12/17/2012 12:55 PM, Burton, Ross wrote:
On 17 December 2012 17:45, Jim Abernathy jfaberna...@gmail.com wrote:
SRC_URI = file://myaudios-1.0/myaudios-1.0.tar.gz
You don't need to specify the myaudios-1.0 section, that's implicit in
the search paths along with the unversioned ${BPN} and files/.
SRC_URI=file://myaudios-1.0.tar.gz will find it and also work with
every previous Yocto release.
This must have worked previously because the search path logic was
rather overcomplicated and unpredictable. It was recently cleaned up
but obviously you were unknowingly relying on undocumented behaviour.
I have not tested this back on Danny, but it seems to be past the point
where it couldn't find anything. I have no idea how it worked in the
past. I remember having to toy with it a lot. I'm still not clear about
all the paths in a recipe. So I just copy others and try things that
eventually work.
Thanks,
Jim A
Ross
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] problems adding extra packages
In the past on denzil, I'd get images working then start adding specific packages like this: LICENSE_FLAGS_WHITELIST = commercial CORE_IMAGE_EXTRA_INSTALL ?= gst-fluendo-mp3 CORE_IMAGE_EXTRA_INSTALL ?= web-webkit CORE_IMAGE_EXTRA_INSTALL ?= myvideos CORE_IMAGE_EXTRA_INSTALL ?= myaudios Today, I got chiefriver bsp working on my hardware and then wanted to add my video and audio files into the image along with extra software. It didn't get added and the image is basically the same size. No errors on just bitbaking again. I was trying to avoid deleting tmp and starting over again. Has something changed with Danny? Along with the CORE_IMAGE_EXTRA_INSTALL additions, I added my layer in bblayer.conf to pick up myvideos, etc. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] problems adding extra packages
On 12/05/2012 03:28 PM, Martin Jansa wrote: On Wed, Dec 05, 2012 at 03:25:52PM -0500, Jim Abernathy wrote: In the past on denzil, I'd get images working then start adding specific packages like this: LICENSE_FLAGS_WHITELIST = commercial CORE_IMAGE_EXTRA_INSTALL ?= gst-fluendo-mp3 CORE_IMAGE_EXTRA_INSTALL ?= web-webkit CORE_IMAGE_EXTRA_INSTALL ?= myvideos CORE_IMAGE_EXTRA_INSTALL ?= myaudios did you use '+=' before? Cheers, You'd think by now, my keyboard would know to put the + and not the ?. :-) Thanks for spotting that. I looked right past it. Jim A Today, I got chiefriver bsp working on my hardware and then wanted to add my video and audio files into the image along with extra software. It didn't get added and the image is basically the same size. No errors on just bitbaking again. I was trying to avoid deleting tmp and starting over again. Has something changed with Danny? Along with the CORE_IMAGE_EXTRA_INSTALL additions, I added my layer in bblayer.conf to pick up myvideos, etc. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] build failures after pull
I've reported this before, but it still happens. Today, I did a git pull into my local while master was checked out, both on poky and meta-intel. I then tried to rerun without cleaning or deleting anything for chiefriver. My last build had been successfully built, but didn't have audio. So when I saw patches, I thought I'd test again. I simply did source oe-init-build-env bitbake core-image-sato I got a failure in diffutils for some reason. I then did bitbake -c cleansstate diffutils bitbake core-image-sato. This time it worked. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build failure using Master branch for Crownbay
On 10/11/2012 11:10 AM, Jim Abernathy wrote: I just did a pull today and tried to rebuild Crownbay BSP which I successfully built yesterday. I'm looking for a case where the rebuild fails on a previously successful build with just running bitbake core-image-sato without deleting any files or cleaning anything, as I've been instructed previously. I got such a failure today and the console log is below. I'll hold off deleting the build directory and rebuilding as I usually do when this happens, until I hear from the experts on how to proceed. JIm A Since I didn't get any response, I went ahead and did bitbake -c cleansstate emgd-driver-bin and then did a bitbake core-image-sato. The image built fine and booted fine. Jim A Build Configuration: BB_VERSION= 1.16.0 TARGET_ARCH = i586 TARGET_OS = linux MACHINE = crownbay DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20121011 TUNE_FEATURES = m32 core2 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:df127c9cef334955e72420724fa6e1f6a6d44662 meta-intel meta-crownbay = master:5d8a05811101f7d69994f4028ec620c4480f6da4 meta-jfa = unknown:unknown NOTE: Resolving any missing task queue dependencies NOTE: preferred version 7.11 of mesa-dri not available (for item virtual/libgl) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri-dev) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_install (see /build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/temp/log.do_install.28628 for further information) ERROR: Logfile of failure stored in: /build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/temp/log.do_install.28628 Log data follows: | DEBUG: Executing shell function do_install | cpio: ./usr/lib/libgstvabuffer.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libgstvabuffer.so.0.10.8 not created: newer or same age version exists | 19 blocks | cpio: ./usr/lib/libmixcommon.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixcommon.so.0.10.8 not created: newer or same age version exists | 28 blocks | cpio: ./usr/lib/libmixvbp.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp.so.0.10.8 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_h264.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_h264.so.0.10.8 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_mpeg4.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_mpeg4.so.0.10.8 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_vc1.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_vc1.so.0.10.8 not created: newer or same age version exists | 358 blocks | cpio: ./usr/lib/libmixvideo.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvideo.so.0.10.9 not created: newer or same age version exists | 465 blocks | install: omitting directory `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/dri' | install: omitting directory `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/gstreamer-0.10' | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libEGL.so': No such file or directory | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libGLES_CM.so': No such file or directory | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libGLESv2.so': No such file or directory | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libOpenVG.so': No such file or directory | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libOpenVGU.so': No such file or directory | install: omitting directory `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/xorg
[yocto] Build failure using Master branch for Crownbay
I just did a pull today and tried to rebuild Crownbay BSP which I successfully built yesterday. I'm looking for a case where the rebuild fails on a previously successful build with just running bitbake core-image-sato without deleting any files or cleaning anything, as I've been instructed previously. I got such a failure today and the console log is below. I'll hold off deleting the build directory and rebuilding as I usually do when this happens, until I hear from the experts on how to proceed. JIm A Build Configuration: BB_VERSION= 1.16.0 TARGET_ARCH = i586 TARGET_OS = linux MACHINE = crownbay DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20121011 TUNE_FEATURES = m32 core2 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:df127c9cef334955e72420724fa6e1f6a6d44662 meta-intel meta-crownbay = master:5d8a05811101f7d69994f4028ec620c4480f6da4 meta-jfa = unknown:unknown NOTE: Resolving any missing task queue dependencies NOTE: preferred version 7.11 of mesa-dri not available (for item virtual/libgl) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri-dev) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_install (see /build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/temp/log.do_install.28628 for further information) ERROR: Logfile of failure stored in: /build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/temp/log.do_install.28628 Log data follows: | DEBUG: Executing shell function do_install | cpio: ./usr/lib/libgstvabuffer.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libgstvabuffer.so.0.10.8 not created: newer or same age version exists | 19 blocks | cpio: ./usr/lib/libmixcommon.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixcommon.so.0.10.8 not created: newer or same age version exists | 28 blocks | cpio: ./usr/lib/libmixvbp.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp.so.0.10.8 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_h264.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_h264.so.0.10.8 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_mpeg4.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_mpeg4.so.0.10.8 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_vc1.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvbp_vc1.so.0.10.8 not created: newer or same age version exists | 358 blocks | cpio: ./usr/lib/libmixvideo.so.0 not created: newer or same age version exists | cpio: ./usr/lib/libmixvideo.so.0.10.9 not created: newer or same age version exists | 465 blocks | install: omitting directory `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/dri' | install: omitting directory `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/gstreamer-0.10' | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libEGL.so': No such file or directory | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libGLES_CM.so': No such file or directory | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libGLESv2.so': No such file or directory | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libOpenVG.so': No such file or directory | install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libOpenVGU.so': No such file or directory | install: omitting directory `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/xorg' | ERROR: Function failed: do_install (see /build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/temp/log.do_install.28628 for further information) ERROR: Task 3814
[yocto] building under Centos 6.3
Just an FYI, following the Getting Started Guide for Centos prerequisites, I found one that was not listed that I needed: chrpath. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Building crownbay from master
I successfully build the meta-crownbay BSP using the latest pull from master branch. I did get some warning, that I wonder what they mean or the significance of them: NOTE: preferred version 7.11 of mesa-dri not available (for item virtual/libgl) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri-dev) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri) NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7 WARNING: bzip2: No generic license file exists for: bzip2 in any provider WARNING: bzip2-native: No generic license file exists for: bzip2 in any provider WARNING: emgd-driver-bin: No generic license file exists for: Intel-binary-only in any provider WARNING: busybox: No generic license file exists for: bzip2 in any provider Also a number of warning about the recipe trying to install files into a shared area when those files already existed. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] log
Build Configuration: BB_VERSION= 1.16.0 TARGET_ARCH = i586 TARGET_OS = linux MACHINE = crownbay DISTRO= poky DISTRO_VERSION= 1.2+snapshot-20121004 TUNE_FEATURES = m32 core2 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:ee76b805f96f00aec386a1c34d176eea7d66f526 meta-intel meta-crownbay = master:c4a86a2ad5df3a94b47e394090f67f7e324b1483 meta-jfa = unknown:unknown ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] log
On 10/04/2012 03:15 PM, Jim Abernathy wrote: Build Configuration: BB_VERSION= 1.16.0 TARGET_ARCH = i586 TARGET_OS = linux MACHINE = crownbay DISTRO= poky DISTRO_VERSION= 1.2+snapshot-20121004 TUNE_FEATURES = m32 core2 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:ee76b805f96f00aec386a1c34d176eea7d66f526 meta-intel meta-crownbay = master:c4a86a2ad5df3a94b47e394090f67f7e324b1483 meta-jfa = unknown:unknown My bad. meant to send this to my other computer. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] SATO video player app
Now that the Denzil branch supports the CDV 1.0.3 hardware accelerated video driver for Cedartrail, I would like to have the Video Player app play the mp4 videos accelerated by the hardware. The player currently does not accelerate the video. To play accelerated video, I need to run gst from the command line, for example: gst-launch filesrc location=myvideofile.mp4 ! qtdemux name=demux ! queue ! vaapidecode ! vaapisink demux. ! queue ! ffdec_aac ! alsasink. Is there a way to configure the GUI video player to include the right pipeline options? Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] configuring WiFi in Yocto
On 08/30/2012 07:41 AM, Burton, Ross wrote: On 29 August 2012 13:52, James Abernathy jfaberna...@gmail.com wrote: rtl8192ce:rtl92c_init_sw_vars():0-0 Failed to request firmware! You're missing firmware still. Ensure that you've installed every linux-firmware-* package first, and if that doesn't work dig around the logs and hopefully you'll find the file it's after. Ross Not sure I know how to force linux-firmware-* to be installed?? Also I replaced the WiFi card with an Intel Wireless-N 135, and I got a FW error using it as well. In this case it called out: lwlagn :02:00.0: request for firmware file 'iwlwifi-105-5-ucode' failed So if could just be I don't know how to force the firmware files to get included or the file does not exist in Yocto. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] configuring WiFi in Yocto
On 08/31/2012 03:22 PM, Burton, Ross wrote: Hi Jim, On 31 August 2012 19:05, Jim Abernathy jfaberna...@gmail.com wrote: Not sure I know how to force linux-firmware-* to be installed?? Personally I use DISTRO_EXTRA_RDEPENDS += in my local.conf for local changes like that. Also I replaced the WiFi card with an Intel Wireless-N 135, and I got a FW error using it as well. In this case it called out: That was probably a good move, I've not had good experience with realtek hardware. lwlagn :02:00.0: request for firmware file 'iwlwifi-105-5-ucode' failed So if could just be I don't know how to force the firmware files to get included or the file does not exist in Yocto. That's packaged in linux-firmware (in oe-core master at least, it appears the Denzil needs upgrading here), so adding DISTRO_EXTRA_RDEPENDS += linux-firmware will add it to all of your future images. the firmware I need must not be in the Denzil for Cedartrail BSP. It built fine with the DISTRO_EXTRA_RDEPENDS added, but both the Intel and Realtek cards can't load the firmware. Jim A Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] configuring WiFi in Yocto
When I configured WiFi with Yocto on a n450 based netbook, all I had to do was get the right drivers for the hardware included in the Yocto 3.2 kernel, then I could use the GUI Connection Manager to configure the WiFi so the hardware would connect to my WiFi network. However, I'm now trying to configure a different WiFi on a Cedartrail system. The card is a Realtek RTL8188CE and the hardware is a DN2800MT Cedartrail board. For Cedartrail the current BSP under Denzil is on kernel 3.0. Not sure what made the difference, but Connection Manager does not have an option for Wireless networks. iwconfig list both lo and eth0, both of course have no wireless extensions. I was expecting to see wlan0. If I do lspci -v, it shows I have my RTL8188CE hardware connected to the kernel module rtl8192ce, which was loaded in support of the wifi card along with the other modules I put into my config fragment file: CONFIG_RTL8192CE=m CONFIG_RTL8192C_COMMON=m CONFIG_RTLWIFI=m CONFIG_MAC80211=m CONFIG_CFG80211=m What does it take to get the wlan0 device so Connection Manger will recognize it? Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] adding drivers to the kernel
If I need to add a driver for a networking device that should be in the 3.0 kernel, but seems to be turned off, I usually follow the example in sections B.2.3 in the Development Manual. When I get to the stage of running bitbake linux-yocto -c menuconfig, I can search for my device with the / command and search for CONFIG_RTL8192CE and I find this: Symbol: RTL8192CE [=n] │ │ Type : tristate │ │ Prompt: Realtek RTL8192CE/RTL8188CE Wireless Network Adapter │ │ Defined at drivers/net/wireless/rtlwifi/Kconfig:1 │ │ Depends on: NETDEVICES [=y] WLAN [=y] MAC80211 [=n] PCI [=y] │ │ Location: │ │ - Device Drivers │ │ - Network device support (NETDEVICES [=y]) │ │ - Wireless LAN (WLAN [=y]) │ │ Selects: FW_LOADER [=y] RTLWIFI [=n] RTL8192C_COMMON [=n] However, I can't find this device where is should be or anywhere in the .config file. I've tried just adding the CONFIG_RTL8192CE=y to a config fragment file anyway and that didn't work. After building the image, the .config still didn't have the CONFIG_RTL8192CE=y. The 3.0 kernel should have support for the RTL8192CE devices. Also if I manual add CONFIG_RTL8192CE=y to the .config file and then compile and build the kernel, the RTL8192CE parameter is removed from the .config file after the kernel build. Any ideas? Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding drivers to the kernel
On 08/23/2012 08:35 AM, Marc Ferland wrote: Jim Abernathy jfaberna...@gmail.com writes: If I need to add a driver for a networking device that should be in the 3.0 kernel, but seems to be turned off, I usually follow the example in sections B.2.3 in the Development Manual. When I get to the stage of running bitbake linux-yocto -c menuconfig, I can search for my device with the / command and search for CONFIG_RTL8192CE and I find this: Symbol: RTL8192CE [=n] │ │ Type : tristate │ │ Prompt: Realtek RTL8192CE/RTL8188CE Wireless Network Adapter │ │ Defined at drivers/net/wireless/rtlwifi/Kconfig:1 │ │ Depends on: NETDEVICES [=y] WLAN [=y] MAC80211 [=n] PCI [=y] │ │ Location: │ │ - Device Drivers │ │ - Network device support (NETDEVICES [=y]) │ │ - Wireless LAN (WLAN [=y]) │ │ Selects: FW_LOADER [=y] RTLWIFI [=n] RTL8192C_COMMON [=n] However, I can't find this device where is should be or anywhere in the .config file. I've tried just adding the CONFIG_RTL8192CE=y to a config fragment file anyway and that didn't work. After building the image, the .config still didn't have the CONFIG_RTL8192CE=y. The 3.0 kernel should have support for the RTL8192CE devices. Also if I manual add CONFIG_RTL8192CE=y to the .config file and then compile and build the kernel, the RTL8192CE parameter is removed from the .config file after the kernel build. You probably need to enable MAC80211 first. Your RTL8192CE driver will be selectable afterwards. Marc You are correct. after I posted my question, I cheated and booted Ubuntu on the same hardware and saw the list of modules that lsmod showed were loaded to support my WiFi card. my config fragment files now has: CONFIG_RTL8192CE=y CONFIG_RTL8192C_COMMON=y CONFIG_RTLWIFI=y CONFIG_MAC80211=y CONFIG_CFG80211=y It's still building, but at least the .config file now has all the right parameters in it and they didn't get deleted by the bitbake linux-yocto -c compile -f Thanks, Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 08/02/2012 01:07 PM, maniacbug wrote: Got around this issue by checking out the denzil branch on meta-ti and poky. then my core-image-sato builds and boots. Right, that is what I was going to suggest. One of us should fix the pulseaudio issue on master and send in a patch. probably going to be you. that's a long ways away from my skill level. :-) Anyone know how to get the wireless and HW accelerated video playback to work with the pandaboard and Yocto? maybe a different image? meta-ti list is probably going to be the place to find this out. Or at least find clues. Unfortunately, it seems that there is not a pandaboard expert in the Yocto house. The meta-ti layer has been extracted from Angstrom, so there seem to be plenty dependencies directly on OE. Often when building more hardware-specific recipies, these dependencies crop up. So Yocto on Pandaboard is definitely still a work in progress. I have gotten video to work by porting the libav recipe from OE. Happy to send it to you if you want to try. There is no evidence to suggest this is hardware-accellerated. HOWEVER, it does play 2Mbps video without stuttering. So from my perspective, whether it's hw accellerated is not important :) I would say it's hardware accelerated because video under Ubuntu is like a slide show. 2-3 sections between frames. I don't think HW acceleration was working there either. The downside is that AUDIO is working hardly at all. This is my current challenge, and I'll definitely report progress to the meta-ti list. I need to test, but on Ubuntu 12.04 with the OMAP4 extras, I had audio only working via HDMI audio. I'll test to see what happens on Yocto. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/31/2012 08:14 AM, Gary Thomas wrote:
On 2012-07-31 06:00, Jim Abernathy wrote:
On 07/31/2012 07:53 AM, Gary Thomas wrote:
On 2012-07-31 05:49, Martin Jansa wrote:
On Tue, Jul 31, 2012 at 07:47:34AM -0400, Jim Abernathy wrote:
On 07/31/2012 07:25 AM, Gary Thomas wrote:
On 2012-07-30 13:11, Gary Thomas wrote:
On 2012-07-30 12:49, Jim Abernathy wrote:
On 07/30/2012 01:16 PM, Gary Thomas wrote:
On 2012-07-30 11:09, Jim Abernathy wrote:
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal
for the machine pandaboard. Besides the basics, I
put in
a license statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time
build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5:
Could not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto=
master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe =
master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti =
master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
BBMASK by itself didn't solve my particular problem. I'll
try the other suggestions and report back.
What other problem do you have? That BBMASK should keep
bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that
mask...
When I just used the statement:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
I got the same error as my original post.
The only way you could get that same error is if you already
have a BBMASK
statement somewhere and this one is being ignored because of
the ?= assignment.
So I started with a clean build again. This time I only added
the BBMASK statement you suggested. I got the following
error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by
your
yocto build.
Thanks, that makes more sense now. I removed the layer
meta-systemd from bblayers.conf and used the
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on
meta-systemd are there, but the mask removes that?? Why can you
remove a dependency?
The dependency on systemd comes from this recipe:
meta-ti/recipes-misc/payload/bonescript.bb
The BBMASK is making bitbake ignore that recipe (you don't need
it), hence no dependency.
I got core-image-minimal built without errors, Thanks, now I
need to
ask some questions about booting that image. I'm assuming that I
can follow the instructions on pandaboard.org
for creating the SD card format and just copy the deploy/image/
u-boot, MLO, uImage, and rootfs to the right places and boot the
sdcard in the pandaboard. Anyway, that's what I
tried. I'm connected to the panadboard via serial port and the
U-Boot works and the uImage seems to be found, but I don't get a
login console on the serial port:
U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03)
Texas Instruments OMAP4430 ES2.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03)
CPU : OMAP4430 ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
In:serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read boot.scr from mmc 0:1 **
reading uImage
4176404 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4176340 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
[yocto] build error pandaboard on master
I'm on master branch trying to build core-image-minimal for the machine
pandaboard. Besides the basics, I put in a license statement for
cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could not
inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto= master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe = master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti = master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/30/2012 09:00 AM, Martin Jansa wrote:
On Mon, Jul 30, 2012 at 08:53:50AM -0400, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal for the machine
pandaboard. Besides the basics, I put in a license statement for
cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could not
inherit file classes/systemd.bbclass
add meta-openembedded/meta-systemd to your BBLAYERS
When I do that I get the errors:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
Jim A
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto= master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe = master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti = master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal for the
machine pandaboard. Besides the basics, I put in a license
statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could not
inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto= master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe = master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti = master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
BBMASK by itself didn't solve my particular problem. I'll try the other
suggestions and report back.
Jim A
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/30/2012 09:19 AM, Martin Jansa wrote:
On Mon, Jul 30, 2012 at 09:06:23AM -0400, Jim Abernathy wrote:
On 07/30/2012 09:00 AM, Martin Jansa wrote:
On Mon, Jul 30, 2012 at 08:53:50AM -0400, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal for the machine
pandaboard. Besides the basics, I put in a license statement for
cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could not
inherit file classes/systemd.bbclass
add meta-openembedded/meta-systemd to your BBLAYERS
When I do that I get the errors:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
Add BB_DANGLINGAPPENDS_WARNONLY to
meta-openembedded/meta-systemd/conf/layer.conf
BB_DANDLINGAPPENDS_WARNONLY = yes seems to have gotten me past the
build errors for now.
I'll look at the BBMASK some more since it looks cleaner to just modify
the local.conf file.
Jim A
or add meta-gnome/meta-efl layers if you would use them..
Cheers,
Jim A
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto= master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe = master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti = master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal for the
machine pandaboard. Besides the basics, I put in a license
statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could not
inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto= master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe = master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti = master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
BBMASK by itself didn't solve my particular problem. I'll try the
other suggestions and report back.
What other problem do you have? That BBMASK should keep bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that mask...
When I just used the statement:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
I got the same error as my original post.
Jim A
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal for the
machine pandaboard. Besides the basics, I put in a license
statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could not
inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto=
master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe =
master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti =
master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
BBMASK by itself didn't solve my particular problem. I'll try the
other suggestions and report back.
What other problem do you have? That BBMASK should keep bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that mask...
When I just used the statement:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
I got the same error as my original post.
The only way you could get that same error is if you already have a
BBMASK
statement somewhere and this one is being ignored because of the ?=
assignment.
hmm..
right now I have the build running by using the
BB_DANGLINGAPPENDS_WARNONLY = yes statement.
When that is done, I'll test the BBMASK on a completely new build from
scratch and see what I get.
Jim A
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal for the
machine pandaboard. Besides the basics, I put in a license
statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could not
inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto=
master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe =
master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti =
master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
BBMASK by itself didn't solve my particular problem. I'll try the
other suggestions and report back.
What other problem do you have? That BBMASK should keep bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that mask...
When I just used the statement:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
I got the same error as my original post.
The only way you could get that same error is if you already have a
BBMASK
statement somewhere and this one is being ignored because of the ?=
assignment.
So I started with a clean build again. This time I only added the BBMASK
statement you suggested. I got the following error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Jim A
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal for the
machine pandaboard. Besides the basics, I put in a license
statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time
build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could
not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto=
master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe =
master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti =
master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
BBMASK by itself didn't solve my particular problem. I'll try the
other suggestions and report back.
What other problem do you have? That BBMASK should keep bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that mask...
When I just used the statement:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
I got the same error as my original post.
The only way you could get that same error is if you already have a
BBMASK
statement somewhere and this one is being ignored because of the ?=
assignment.
So I started with a clean build again. This time I only added the
BBMASK statement you suggested. I got the following error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by your
yocto build.
Thanks, that makes more sense now. I removed the layer meta-systemd
from bblayers.conf and used the
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on
meta-systemd are there, but the mask removes that?? Why can you remove
a dependency?
Jim A
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/30/2012 01:16 PM, Gary Thomas wrote:
On 2012-07-30 11:09, Jim Abernathy wrote:
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal for
the machine pandaboard. Besides the basics, I put in a
license statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time
build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 5
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could
not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= 1.15.3
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = pandaboard
DISTRO= poky
DISTRO_VERSION= 1.2+snapshot-20120730
TUNE_FEATURES = armv7a vfp neon cortexa9
TARGET_FPU= vfp-neon
meta
meta-yocto=
master:7411158e1f980cd71c432026fa2f68ab80e3541e
meta-oe =
master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb
meta-ti =
master:9bc77dff5f84578e259f8225bfa0656d94a2a60a
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
BBMASK by itself didn't solve my particular problem. I'll try
the other suggestions and report back.
What other problem do you have? That BBMASK should keep bitbake
from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that mask...
When I just used the statement:
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
I got the same error as my original post.
The only way you could get that same error is if you already have
a BBMASK
statement somewhere and this one is being ignored because of the
?= assignment.
So I started with a clean build again. This time I only added the
BBMASK statement you suggested. I got the following error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by your
yocto build.
Thanks, that makes more sense now. I removed the layer meta-systemd
from bblayers.conf and used the
BBMASK ?= .*/meta-ti/recipes-(misc|bsp/formfactor)/
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on
meta-systemd are there, but the mask removes that?? Why can you
remove a dependency?
The dependency on systemd comes from this recipe:
meta-ti/recipes-misc/payload/bonescript.bb
The BBMASK is making bitbake ignore that recipe (you don't need it),
hence no dependency.
I got core-image-minimal built without errors, Thanks, now I need to ask
some questions about booting that image. I'm assuming that I can follow
the instructions on pandaboard.org for creating the SD card format and
just copy the deploy/image/ u-boot, MLO, uImage, and rootfs to the right
places and boot the sdcard in the pandaboard. Anyway, that's what I
tried. I'm connected to the panadboard via serial port and the U-Boot
works and the uImage seems to be found, but I don't get a login console
on the serial port:
U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03)
Texas Instruments OMAP4430 ES2.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03)
CPU : OMAP4430 ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
In:serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read boot.scr from mmc 0:1 **
reading uImage
4176404 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4176340 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] creating SD card for booting Yocto image on Pandaboard
I have not seem a procedure documented for creating an SD card with the Yocto image that works in a Pandaboard Rev A2. I have created a core-image-minimal and core-image-sato successfully. I followed the basic procedures on pandaboard wiki to format the SD card. After formating the card, I can insert it into an Ubuntu 12.04 system and the /media/boot and /media/rootfs devices are mounted automatically. Using the files in tmp/deploy/images, I copy the files as below: cp MLO-pandaboard-2012.12 /media/boot/MLO cp u-boot-pandaboard-2011.12-r8.img /media/boot/u-boot.img cp uImage-3.1.0-r0-pandaboard-201207300170622.bin /media/boot/uImage tar -xjf core-image-minimal-pandaboard.tar.bz2 -C /media/rootfs/ Am I missing a step? It starts booting the kernel, but that's is, no more output on the console. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/21/2012 07:47 PM, Tom Zanussi wrote: On Sat, 2012-07-21 at 09:58 -0400, Jim Abernathy wrote: On 07/21/2012 12:06 AM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:55 -0500, Tom Zanussi wrote: On Fri, 2012-07-20 at 15:39 -0500, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? As a sanity check, I just now downloaded the denzil-7.0.1 tarball and the denzil sugarbay tarball and built successfully without any problems. Also did a fresh clone of meta-intel, checked out meta-intel/denzil and successfully built n450 with the denzil-7.0.1 tarball here with no problems. Tom I can confirm I had no issues doing just what you did. tarball for denzil-7.0.1 and denzil clone for meta-intel and default core-image-sato for n450. Next, I cloned poky and checked out the tag denzil-7.0.1, which in theory should match the tarball I ran with in the above test. I cloned meta-intel and checked out the branch denzil, just as above. So this good news is that worked as expected. The denzil-7.0.1 tag equals the tarball. So the only problem is the denzil branch of poky has some problem that's seen in denzil-7.0.1 as it relates to n450. I'm not sure what you mean by this - I just did a build of poky/denzil with meta-intel/denzil and again, didn't see any problems with that permutation either. Tom What I meant by my statement was I could only build n450 while I use the tarball of poky denzil-7.0.1 with the denzil tracking branch of meta-intel, or the equivalent git repository tag of poky denzil-7.0.1. I couldn't build the n450 from the tracking branch of poky denzil and the tracking branch of meta-intel denzil. To me that just meant that something changed in denzil since the tag denzil 7.0.1 was established. I retest again and can confirm that my retest was successful. Here are the steps I used for both test. Not sure what changed, but at least it works now: git clone git://git.yoctoproject.org/poky cd poky git clone git://git.yoctoproject.org/meta-intel.git git checkout -b denzil origin/denzil cd meta-intel git checkout -b denzil origin/denzil cd .. . oe-init-build-env /build/n450-new (edit local.conf for parallel options, machine= n450, and DL_DIR) (edit bblayer.conf for meta-intel and meta-intel/meta-n450 layer) bitbake core-image-sato Jim A Jim A Tom Tom Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/21/2012 12:06 AM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:55 -0500, Tom Zanussi wrote: On Fri, 2012-07-20 at 15:39 -0500, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? As a sanity check, I just now downloaded the denzil-7.0.1 tarball and the denzil sugarbay tarball and built successfully without any problems. Also did a fresh clone of meta-intel, checked out meta-intel/denzil and successfully built n450 with the denzil-7.0.1 tarball here with no problems. Tom I can confirm I had no issues doing just what you did. tarball for denzil-7.0.1 and denzil clone for meta-intel and default core-image-sato for n450. Next, I cloned poky and checked out the tag denzil-7.0.1, which in theory should match the tarball I ran with in the above test. I cloned meta-intel and checked out the branch denzil, just as above. So this good news is that worked as expected. The denzil-7.0.1 tag equals the tarball. So the only problem is the denzil branch of poky has some problem that's seen in denzil-7.0.1 as it relates to n450. Jim A Tom Tom Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/21/2012 09:58 AM, Jim Abernathy wrote: On 07/21/2012 12:06 AM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:55 -0500, Tom Zanussi wrote: On Fri, 2012-07-20 at 15:39 -0500, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? As a sanity check, I just now downloaded the denzil-7.0.1 tarball and the denzil sugarbay tarball and built successfully without any problems. Also did a fresh clone of meta-intel, checked out meta-intel/denzil and successfully built n450 with the denzil-7.0.1 tarball here with no problems. Tom I can confirm I had no issues doing just what you did. tarball for denzil-7.0.1 and denzil clone for meta-intel and default core-image-sato for n450. Next, I cloned poky and checked out the tag denzil-7.0.1, which in theory should match the tarball I ran with in the above test. I cloned meta-intel and checked out the branch denzil, just as above. So this good news is that worked as expected. The denzil-7.0.1 tag equals the tarball. So the only problem is the denzil branch of poky has some problem that's seen in denzil-7.0.1 as it relates to n450. Jim A FYI, I added the meta-baryon layer after I got the n450 straightened out. It's fine as well. Jim A Tom Tom Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] nothing building under denzil-7.0.1
There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 04:39 PM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? Tom I should know shortly. I patched the n450 like I did before. I forgot that BSP didn't get updated when denzil 7.0.1 came out. Duh! If you have it fixed in Denzil and master branch, I'll test that as well. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 04:48 PM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:42 -0400, Jim Abernathy wrote: On 07/20/2012 04:39 PM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? Tom I should know shortly. I patched the n450 like I did before. I forgot that BSP didn't get updated when denzil 7.0.1 came out. Duh! If you have it fixed in Denzil and master branch, I'll test that as well. Yes, you should be fine using the BSP branches from the git repo, but steer clear of the tarball until it gets updated... Tom I don't have something right yet. on poky, I'm up to date on denzil branch. Also denzil branch on meta-intel. I'm getting a build failure on the yocto kernel. Log file below: DEBUG: Trying Upstream DEBUG: Running export HOME=/home/jim; export SSH_AGENT_PID=1456; export SSH_AUTH_SOCK=/tmp/keyring-aKbQKk/ssh; export GIT_CONFIG=/build/n450-denzil/tmp/sysroots/x86_64-linux/etc/gitconfig; export PATH=/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/build/n450-denzil/tmp/sysroots/n450/usr/bin/crossscripts:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin:/build/n450-denzil/tmp/sysroots/x86_64-linux/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux//bin:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jim/poky/scripts; git log --pretty=oneline -n 1 8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c -- 2 /dev/null | wc -l DEBUG: Running export HOME=/home/jim; export SSH_AGENT_PID=1456; export SSH_AUTH_SOCK=/tmp/keyring-aKbQKk/ssh; export GIT_CONFIG=/build/n450-denzil/tmp/sysroots/x86_64-linux/etc/gitconfig; export PATH=/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/build/n450-denzil/tmp/sysroots/n450/usr/bin/crossscripts:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin:/build/n450-denzil/tmp/sysroots/x86_64-linux/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux//bin:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jim/poky/scripts; git log --pretty=oneline -n 1 49f931bc294d5b6be60502bbd448cff5aa766235 -- 2 /dev/null | wc -l DEBUG: Running export HOME=/home/jim; export SSH_AGENT_PID=1456; export SSH_AUTH_SOCK=/tmp/keyring-aKbQKk/ssh; export GIT_CONFIG=/build/n450-denzil/tmp/sysroots/x86_64-linux/etc/gitconfig; export PATH=/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/build/n450-denzil/tmp/sysroots/n450/usr/bin/crossscripts:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin:/build/n450-denzil/tmp/sysroots/x86_64-linux/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux//bin:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 07:02 PM, Darren Hart wrote: On 07/20/2012 03:12 PM, Jim Abernathy wrote: git://git.yoctoproject.org/linux-yocto-3.2 could not be run: None ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/common-pc/atom-pc,meta;name=machine,meta'. Unable to fetch URL from any source. Can you clone this from the shell? Okay, I blew away my poky and build directories, but keep my download central directory. Here are the steps. git clone git://git.yoctoproject.org/poky cd poky git clone git://git.yoctoproject.org/meta-intel.git git checkout -b denzil origin/denzil cd meta-intel git checkout -b denzil origin/denzil cd .. . oe-init-build-env /build/n450-new (edit local.conf for parallel options, machine= n450, and DL_DIR) (edit bblayer.conf for meta-intel and meta-intel/meta-n450 layer) bitbake core-image-sato Error console: NOTE: Running task 687 of 4920 (ID: 69, virtual:native:/home/jim/poky/meta/recipes-devtools/prelink/prelink_git.bb, do_unpack) WARNING: Failed to fetch URL git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/common-pc/atom-pc,meta;name=machine,meta ERROR: Fetcher failure: Fetch command export HOME=/home/jim; export SSH_AGENT_PID=1456; export SSH_AUTH_SOCK=/tmp/keyring-aKbQKk/ssh; export GIT_CONFIG=/build/n450-new/tmp/sysroots/x86_64-linux/etc/gitconfig; export PATH=/build/n450-new/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/build/n450-new/tmp/sysroots/n450/usr/bin/crossscripts:/build/n450-new/tmp/sysroots/x86_64-linux/usr/sbin:/build/n450-new/tmp/sysroots/x86_64-linux/usr/bin:/build/n450-new/tmp/sysroots/x86_64-linux/sbin:/build/n450-new/tmp/sysroots/x86_64-linux//bin:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jim/poky/scripts; git remote add --mirror=fetch origin git://git.yoctoproject.org/linux-yocto-3.2 could not be run: None ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/common-pc/atom-pc,meta;name=machine,meta'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /build/n450-new/tmp/work/n450-poky-linux/linux-yocto-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c-r1/temp/log.do_fetch.12200 NOTE: package linux-yocto-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c-r1: task do_fetch: Failed ERROR: Task 705 (/home/jim/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb, do_fetch) failed with exit code '1' ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] build failures after recent pull
Something that got pushed recently has broken the tools. To keep the debug simple, I went back and tried to just build an old stable platform, the n450. Below is the error: NOTE: Unpacking home/jim/yocto-downloads/gnu-config-yocto-2011.tgz to /build/baryon-denzil/tmp/work/x86_64-linux/gnu-config-native-2011-r1/ tar (child): home/jim/yocto-downloads/gnu-config-yocto-2011.tgz: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now ERROR: Function failed: Unpack failure for URL: 'http://downloads.yoctoproject.org/releases/gnu-config/gnu-config-yocto-2011.tgz'. Unpack command PATH=/build/baryon-denzil/tmp/sysroots/x86_64-linux/usr/bin/core2-linux:/build/baryon-denzil/tmp/sysroots/x86_64-linux/usr/bin:/build/baryon-denzil/tmp/sysroots/x86_64-linux/usr/sbin:/build/baryon-denzil/tmp/sysroots/x86_64-linux/usr/bin:/build/baryon-denzil/tmp/sysroots/x86_64-linux/sbin:/build/baryon-denzil/tmp/sysroots/x86_64-linux//bin:/home/jim/poky/scripts/native-intercept:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jim/poky/scripts tar xz --no-same-owner -f home/jim/yocto-downloads/gnu-config-yocto-2011.tgz failed with return value 2 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-baryon flexibility
In an effort to explore how independent a layer could be to the
underlying hardware, I took the meta-baryon NAS layer and got it built
from master using the n450 BSP. With that working I decided to replace
the n450 with sugarbay. While the n450 can support X11 and sato, it was
not generated by design in the baryon build.
However, when I changed to sugarbay, the build stops because X11 is
needed. To get around this I had to comment out some things in the
conf/machine/sugarbay.conf file in the BSP.
#XSERVER ?= ${XSERVER_IA32_BASE} \
# ${XSERVER_IA32_EXT} \
# ${XSERVER_IA32_I965} \
#
#VA_FEATURES ?= gst-va-intel va-intel
#MACHINE_EXTRA_RRECOMMENDS += ${VA_FEATURES}
Why didn't I have to do this in the n450??
JIm A
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Is it just me? Can't get 'Atom-PC' to boot.
On 07/16/2012 04:25 PM, Chris Tapp wrote: I've built the 'atom-pc' kernel as follows: 1) git clone git://git.yoctoproject.org/poky.git 2) git checkout denzil 3) source poky/oe-init-build-env work-area 4) Edit local.conf so that threads/parallel make are both 16 and MACHINE is 'atom-pc' 8) bitbake virtual/kernel. However, the kernel that gets produced fails to boot. All I get is a screen full of random characters and nothing comes out of the serial port (configured for kernel messages). I don't get any 'Loading...' or 'Uncompressing...' messages either. Using a kernel image from else where (e.g. Voyage Linux) works as expected. What do I need to do differently to get the above to build a bootable image? I'm assuming that 'atom-pc' works for others? When I build for Atom PCs, I'm usually targeting a specific BSP like CrownBay, n450, Cedartrail. All of those require the meta-intel layer. So you need to edit the local.conf with a machine like n450, crownbay, cedartrail, etc. and you need to edit bblayer.conf to add the meta-intel layer and the meta-intel/meta/crownbay, etc. I always bitbake core-image minimal or core-image-sato. Jim A Chris Tapp opensou...@keylevel.com www.keylevel.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] switch between denzil and edison
I just build an Ubuntu 12.04 LTS development system and installed the required packages based on the current 1.2 QS Guide. On Denzil based BSP that works as expected. However, I needed to switch back to edison. When I tried to bitbake an image I received errors that stated a need for bash and not dash (just like the old days). Also it needed a package 'cvs'. Can I assume that bash is supported if I move back to working on the denzil release?? Can I assume installing cvs will not interfere with the denzil release? Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-baryon
On 07/10/2012 03:47 PM, Jim Abernathy wrote: I took at look at the meta baryon NAS project and thought it was interesting and decided to build it on a n410 based miniITX motherboard. I think I guessed correctly on how to integrate it in. 1. make the machine = n450 in local.conf 2. make distro = baryon in local.conf 3. add meta-baryon and meta-n450 layers to bblayer.conf 4. put the commercial license flag in local.conf. This is an issues with Denzil. I went back and built it on edison branch and it built clean and boots on a D510MO board. Jim A The build was going good until I got into the webmin section below is the error. I don't see an obvious problem (to me): DEBUG: No locale files in this package DEBUG: adding update-rc.d calls to postinst/postrm for webmin DEBUG: LIBNAMES: pkg webmin-staticdev libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-zones libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-xinetd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-webminlog libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-webmincron libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-webmin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-usermin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-useradmin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-updown libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-tunnel libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-time libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-tcpwrappers libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-system-status libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-syslog-ng libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-syslog libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-status libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-sshd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-software libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-smf libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-smart-status libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-shell libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-sgiexports libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-servers libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-samba libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-rbac libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-raid libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-quota libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-proftpd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-proc libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ppp-client libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-postgresql libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-phpini libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-passwd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-pam libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-package-updates libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-nis libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-net libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-mysql libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-mount libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-mon libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-mediatomb libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-man libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-lvm libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-lpadmin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-logrotate libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ldap-useradmin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ldap-server libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ldap-client libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-krb5 libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ipsec libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ipfw libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ipfilter libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-inittab libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-init libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-inetd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-idmapd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-htaccess-htpasswd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-hpuxexports libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-grub libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-format libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-firewall libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-file libs 0 bins 0 sonames
Re: [yocto] meta-baryon
On 07/11/2012 11:47 AM, Paul Eggleton wrote: On Wednesday 11 July 2012 11:39:24 Jim Abernathy wrote: On 07/10/2012 03:47 PM, Jim Abernathy wrote: I took at look at the meta baryon NAS project and thought it was interesting and decided to build it on a n410 based miniITX motherboard. I think I guessed correctly on how to integrate it in. 1. make the machine = n450 in local.conf 2. make distro = baryon in local.conf 3. add meta-baryon and meta-n450 layers to bblayer.conf 4. put the commercial license flag in local.conf. This is an issues with Denzil. I went back and built it on edison branch and it built clean and boots on a D510MO board. OK, thanks. FYI I'm just running through a fresh build with it now with master, and have hit a few unrelated issues, so I haven't quite got to the one you found yet. When I do I'll certainly investigate and let you know what I find. When you do have time, let me know if my assumptions above were correct. I must be missing something because I can't find any evidence of webmin in the file system. So while my board boots Yocto, I can't see any of the baryon layer. Could a CORE-IMAGE-EXTRA-INSTALL or something be needed to force the inclusion into the file system?? Jim A Cheers, Paul ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-baryon
I took at look at the meta baryon NAS project and thought it was interesting and decided to build it on a n410 based miniITX motherboard. I think I guessed correctly on how to integrate it in. 1. make the machine = n450 in local.conf 2. make distro = baryon in local.conf 3. add meta-baryon and meta-n450 layers to bblayer.conf 4. put the commercial license flag in local.conf. The build was going good until I got into the webmin section below is the error. I don't see an obvious problem (to me): DEBUG: No locale files in this package DEBUG: adding update-rc.d calls to postinst/postrm for webmin DEBUG: LIBNAMES: pkg webmin-staticdev libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-zones libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-xinetd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-webminlog libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-webmincron libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-webmin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-usermin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-useradmin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-updown libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-tunnel libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-time libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-tcpwrappers libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-system-status libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-syslog-ng libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-syslog libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-status libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-sshd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-software libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-smf libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-smart-status libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-shell libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-sgiexports libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-servers libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-samba libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-rbac libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-raid libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-quota libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-proftpd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-proc libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ppp-client libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-postgresql libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-phpini libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-passwd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-pam libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-package-updates libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-nis libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-net libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-mysql libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-mount libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-mon libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-mediatomb libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-man libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-lvm libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-lpadmin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-logrotate libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ldap-useradmin libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ldap-server libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ldap-client libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-krb5 libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ipsec libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ipfw libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-ipfilter libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-inittab libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-init libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-inetd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-idmapd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-htaccess-htpasswd libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-hpuxexports libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-grub libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-format libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-firewall libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-file libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-fdisk libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-exports libs 0 bins 0 sonames [] DEBUG: LIBNAMES: pkg webmin-module-dnsadmin libs 0
Re: [yocto] Deploy to a hard drive
Need mkdir /mnt/target and mnt/target-ext before step 4 Sent from my Kindle Fire _ From: Sean Liming sean_lim...@sjjmicro.com Sent: Sat Feb 11 16:13:33 EST 2012 To: yocto@yoctoproject.org Subject: [yocto] Deploy to a hard drive Follow the Wiki instructions: 1) have a suitable partition on the disk - say partition #3 2) this partition will show up as sde3 on my host machine and sda3 on the atom 3) mkfs.ext3 /dev/sde3 4) mount /dev/sde3 /mnt/target 5) mount -o loop tmp/deploy/images/core-image-sato-sdk.ext3 /mnt/target-text3 6) cp -a /mnt/target-ext3/* /mnt/target 7) grub-install --recheck --root-directory=/mnt/target /dev/sde When I do step 4, I get “mount: mount point /mnt/target does not exist” What am I missing? I am using Ubuntu 10.4 LTS 32-bit. Regards, Sean ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] core-image-sato-directdisk
On 01/20/2012 09:16 AM, autif khan wrote:
I have been using core-image-sato and core-image-sato-sdk on the hard
disk on Intel Atom (crownbay in my case).
I perform the following broad steps:
1) have a suitable partition on the disk - say partition #3
2) this partition will show up as sde3 on my host machine and sda3 on the atom
3) mkfs.ext3 /dev/sde3
4) mount /dev/sde3 /mnt/target
5) mount -o loop tmp/deploy/images/core-image-sato-sdk.ext3 /mnt/target-text3
6) cp -a /mnt/target-ext3/* /mnt/target
7) grub-install --recheck --root-directory=/mnt/target /dev/sde
If grub install passed, I copy the following to /mnt/target/boot/grub/grub.cfg
set default=0
set timeout=30
menuentry 'Yocto SDK' {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
linux /boot/bzImage root=/dev/sda3
}
Thats it - this boots for me.
Eventually, when I move to some other media, I will have to
investigate other bootloaders - like syslinux.
All the best, do tell if this works.
This worked fine for me. one typo in step (5) ext3 and not text3, but
these are good instructions. How do we get them put into the
README.hardware instead of the directdisk section that doesn't work anymore.
Did you file a bug on this?
Thanks,
Jim Abernathy
On Thu, Jan 19, 2012 at 7:51 PM, James Abernathyjfaberna...@gmail.com wrote:
The README.hardware file in the poky directory talks about creating images
on 2 types of disk for the Atom based PCs like the n450. The one I've
successfully tested is the core-image-sato on a USB key. I have no luck
with the directdisk method because the image recipe doesn't exist for
core-image-minimal-directdisk or core-image-sato-directdisk.
Is there a way to put Yocto on the hard drive on a Atom PC?
Jim A
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] core-image-sato-directdisk
Jim Abernathy Sent from my iPhone On Jan 20, 2012, at 1:00 PM, autif khan autif.ml...@gmail.com wrote: On Fri, Jan 20, 2012 at 12:15 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Friday 20 January 2012 11:54:44 autif khan wrote: Did you file a bug on this? I have not. I am not sure I should. I am not even sure whoose call it should be weather or not this goes in README.hardware. I hope someone chimes in So I would say if any of our documentation is out-of-date or unclear, it should be fixed, no deliberation needed :) However, in Poky master, README.hardware has now been updated to remove references to the old directdisk images. It could be that we need to explicitly add something like what you have written about writing the image to a hard disk, but for the moment it is at least no longer out-of-date. At the very least a great start would be to put your instructions up as a page on the Yocto Project wiki. I have created a new link titled How Do I on the main page and for now, this is the only entry. Please take a look. https://wiki.yoctoproject.org/wiki/Main_Page https://wiki.yoctoproject.org/wiki/How_do_I Looks good to me. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: build failure on ubuntu 64bits development system
On 01/18/2012 04:34 PM, Darren Hart wrote: On 01/18/2012 09:05 AM, Jim Abernathy wrote: FYI for those wanting to use Soft RAID, make sure you create one very small primary partition for GRUB2 to put the second part of the boot-loader in. Can't use the old process. I strongly recommend using a separate DISK for your OS installation. Yocto builds are hard on disks, and RAID 0 increases your risk of failure in exchange for the added performance. I use a small SSD for my OS disk and a large RAID0 array of spinning disks for /build and another array for /virt (where my VM images live - easily recreated). Learned a few things in this process. I appreciate all the help and advice. 1. So we know that at least with Edison, btrfs does not work with bitbake. 2. When I rebuilt the system, this time I put the Linux root directory on an 80GB SSD. That is where I also have my clone of Linux-Yocto repository, poky, and download directory , DL_DIR. 3. I have create /build with EXT4 format on a Software RAID 0 (striped) partition, using 2 separate hard drives, to use as the working build directory for bitbake. I have a striped swap file on the same two drives. But with 8GB or RAM, I shouldn't be using that much. My build times for some of the basic meta-intel BSPs is around 103 minutes. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] using the same download directory multiple times
After reading the comments in the local.conf file about the download directory (DL_DIR), I experimented with creating it outside of the normal build dir directory used by source oe-init-build-env build dir command. After completing a build successfully, I examined the download directory and I'm trying to figure out what is in there besides the tarballs that were downloaded and the .done files for the matching tarball. There also appear to be .done files that are not related to any tarball in the download directory. What is the purpose of these files? Apparently, all this works because I've recreated the same BSP in two different build directories with a common DL_DIR outside the build directory successfully. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: build failure on ubuntu 64bits development system
On 01/19/2012 12:44 PM, Darren Hart wrote: On 01/19/2012 05:55 AM, Jim Abernathy wrote: On 01/18/2012 04:34 PM, Darren Hart wrote: On 01/18/2012 09:05 AM, Jim Abernathy wrote: FYI for those wanting to use Soft RAID, make sure you create one very small primary partition for GRUB2 to put the second part of the boot-loader in. Can't use the old process. I strongly recommend using a separate DISK for your OS installation. Yocto builds are hard on disks, and RAID 0 increases your risk of failure in exchange for the added performance. I use a small SSD for my OS disk and a large RAID0 array of spinning disks for /build and another array for /virt (where my VM images live - easily recreated). Learned a few things in this process. I appreciate all the help and advice. 1. So we know that at least with Edison, btrfs does not work with bitbake. 2. When I rebuilt the system, this time I put the Linux root directory on an 80GB SSD. That is where I also have my clone of Linux-Yocto repository, poky, and download directory , DL_DIR. 3. I have create /build with EXT4 format on a Software RAID 0 (striped) partition, using 2 separate hard drives, to use as the working build directory for bitbake. I have a striped swap file on the same two drives. But with 8GB or RAM, I shouldn't be using that much. My build times for some of the basic meta-intel BSPs is around 103 minutes. You may be able to improve upon that with the following in /etc/fstab: /dev/md0 /build ext4 noauto,noatime,nodiratime,commit=6000 0 2 This reduces the number of writes due to updated access time and increases the commit interval so it doesn't stall while writing out every 5 minutes per default. NOTE: THIS INCREASES YOUR RISK OF DATA LOSS If your machine goes down during a build, you should plan on formatting that drive. If you only keep builds on it, they easily recreateable and you may find the performance boost is worth the risk. I'll test this out and see. I'm plan on keeping this system on a UPS anyway. Jim S ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: build failure on ubuntu 64bits development system
On 01/18/2012 11:32 AM, Saul Wold wrote:
On 01/18/2012 08:17 AM, Jim Abernathy wrote:
On 01/18/2012 11:06 AM, William Mills wrote:
On 01/18/2012 10:25 AM, James Abernathy wrote:
On Wed, Jan 18, 2012 at 10:15 AM, William Mills wmi...@ti.com
mailto:wmi...@ti.com wrote:
On 01/18/2012 10:04 AM, James Abernathy wrote:
-- Forwarded message --
From: *William Mills* wmi...@ti.com mailto:wmi...@ti.com
mailto:wmi...@ti.com mailto:wmi...@ti.com
Date: Wed, Jan 18, 2012 at 9:57 AM
Subject: Re: [yocto] build failure on ubuntu 64bits development
system
To: Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com
mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com
Cc: yocto@yoctoproject.org mailto:yocto@yoctoproject.org
mailto:yocto@yoctoproject.org mailto:yocto@yoctoproject.org__
On 01/18/2012 09:51 AM, Gary Thomas wrote:
On 2012-01-18 07 tel:2012-01-18%2007 tel:2012-01-18%2007:42,
James Abernathy wrote:
On Wed, Jan 18, 2012 at 9:30 AM, James Abernathy
jfaberna...@gmail.com mailto:jfaberna...@gmail.com
mailto:jfaberna...@gmail.com mailto:jfaberna...@gmail.com
mailto:jfaberna...@gmail.com mailto:jfaberna...@gmail.com
mailto:jfaberna...@gmail.com mailto:jfaberna...@gmail.com
wrote:
On Wed, Jan 18, 2012 at 7:55 AM, James Abernathy
jfaberna...@gmail.com mailto:jfaberna...@gmail.com
mailto:jfaberna...@gmail.com mailto:jfaberna...@gmail.com
mailto:jfaberna...@gmail.com mailto:jfaberna...@gmail.com
mailto:jfaberna...@gmail.com mailto:jfaberna...@gmail.com
wrote:
I just built a new development pc and installed Ubuntu 11.10
x64. I wonder if there are any new requirements to building
Yocto in that environment? I got an error right
off, but then it complete the first 63 task and stopped
successfully. error below:
jim@ubuntu:~/poky/build-cdv$ bitbake core-image-sato
Pseudo is not present but is required, building this first
before the main build
Parsing recipes: 100%
|#| Time:
00:00:25
Parsing of 797 .bb files complete (0 cached, 797 parsed). 1037
targets, 22 skipped, 0 masked, 0 errors.
ERROR: Execution of event handler 'run_buildstats' failed
Traceback (most recent call last):
File run_buildstats(e), line 18, in
run_buildstats(e=bb.event.BuildStarted object at 0x4c338d0)
File buildstats.bbclass, line 21, in
set_device(e=bb.event.BuildStarted object at 0x4c338d0)
UnboundLocalError: local variable 'rdev' referenced before
assignment
Any ideas?
JIm A
I went back and tried using the tarballs for poky edison and
cedartrail bsp and the errors don't occur. So I'm guessing the
issue isn't related to Ubuntu 32 vs. 64 bit.
I spoke too soon. Same error in edison tarballs. I looked at the
code and I can see an place were rdev could go un assigned. If
you fell out of the for loop without passing any of
the if conditions, rdev would be unassigned. That must be what
is happening in Ubuntu 11.10 x64
Anybody building with Ubuntu 11.10 x64? This doesn't happen on x32
Jim A
def set_device(e):
tmpdir = bb.data.getVar('TMPDIR', e.data, True)
try:
os.remove(bb.data.getVar('DEVFILE', e.data, True))
except:
pass
##__##__
# We look for the volume TMPDIR lives on. To do all disks would
make little
# sense and not give us any particularly useful data. In theory
we could do
# something like stick DL_DIR on a different partition and this
would
# throw stats gathering off. The same goes with SSTATE_DIR.
However, let's
# get the basics in here and work on the cornercases later.
##__##__
device=os.stat(tmpdir)
majordev=os.major(device.st_dev)
minordev=os.minor(device.st_dev)
for line in open(/proc/diskstats, r):
if majordev == int(line.split()[0]) and minordev ==
int(line.split()[1]):
rdev=line.split()[2]
file = open(bb.data.getVar('DEVFILE', e.data, True), w)
file.write(rdev)
file.close()
Can you show what the differences are between /proc/diskstats
on the two systems? That's obviously what's causing the error.
If your build dir is encyptfs or a fuse device or anything that
is not a
direct block device you will get this error. This is to be fixed in
1.1.1 but encyptfs will still have other problems.
I build the Ubuntu 11.10 x64 system with 2 drives setup as Soft
RAID 0.
I picked btrfs as the file system for no particular reason.
Should I go
back to ext4 or is RAID 0 the problem?
No, I would not do that yet. I would think software RAID would
present a block device so would not trigger this error.
I was hoping to use RAID 0 for speed. I have a I7 2700K on a DZ68DB
with
2 6Gb/s ports matched to 2 6Gb/s 7200 hard drives. Since the builds
take
so long, I was looking for an edge.
So are there any recommendations at this point? I'm assuming that the
default ext4 directly on the SATA drive is a fall back position.
Advice?
If it were me, I would instrument (hack
[yocto] Serial consoles
I'm using a Marshalltown Cedarview board and it's serial ports are standard PC com1 and com2 so I put the following in my conf/machine/mycdv.conf file, where mycdv is the name of my machine/bsp, i.e. meta-mycdv. SERIAL_CONSOLE = 115200 ttyS0 SYSLINUX_OPTS = serial 0 115200 APPEND = console=ttyS0,115200 console=tty0 When the system booted, I have the kernel console on com1 and I also got a login prompt on com1. However, the syslinux output was only displayed on the VGA monitor. Anyone know why? Maybe SYSLINUX_OPTS goes somewhere else? I noticed in the n450 release notes that they accomplish this with the following in the local.conf file: # Serial Port Setup for Intel Embedded Development Board 1-N40\ SYSLINUX_OPTS_atom-pc = serial 0 115200 SERIAL_CONSOLE_atom-pc = 115200 ttyS0 APPEND_atom-pc = console=ttyS0,115200 console=tty0 This does work for the N450, but the cedartrail bsp is not under standard/common-pc/atom-pc. It's under standard/cedartrail. If I have to put SYSLINUX_OPTS in local.conf, what is the suffix and why??? JIm A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] question on poky and git interaction
under the poky directory you git checkout of the branch you want to work with, then you clone meta-intel and within that directory you checkout a branch. if you needed to use git for you personal project, you can't put it at the same meta-intel level, right? Only one per directory??? I would guess that you'd need to create your personal git clone below meta-intel; something like meta-jima. Does this sound correct?? Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] where to put IMAGE_INSTALL??
There seems to be some sensitivity to where I put the statement IMAGE_INSTALL += web-webkit. At first I just modifed the meta/receipes-sato/image/core-image-sato.bb file to include it. That caused the webkit to be built. Since that is not an ideal location, I removed it and put it into the local.conf file. That also caused the webkit to be built, but I wanted it to be part of my BSP permanently. I thought about creating a core-image-sato.bbappend file with the IMAGE_INSTALL += web-webkit in it and put that into the BSP, but that didn't cause the webkit to be built. Under the meta-intel/meta-n450 directory, I created a receipes-jfa directory and put the core-image-sato.bbappend file there. I must be missing a key rule about directory parsing and .bbappend files. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] where to put IMAGE_INSTALL??
On 01/12/2012 08:06 AM, Gary Thomas wrote:
On 2012-01-12 05:53, Jim Abernathy wrote:
There seems to be some sensitivity to where I put the statement
IMAGE_INSTALL += web-webkit.
At first I just modifed the
meta/receipes-sato/image/core-image-sato.bb file to include it. That
caused the webkit to be built.
Since that is not an ideal location, I removed it and put it into the
local.conf file. That also caused the webkit to be built, but I
wanted it to be part of my BSP permanently.
I thought about creating a core-image-sato.bbappend file with the
IMAGE_INSTALL += web-webkit in it and put that into the BSP, but
that didn't cause the webkit to be built. Under
the meta-intel/meta-n450 directory, I created a receipes-jfa
directory and put the core-image-sato.bbappend file there.
I must be missing a key rule about directory parsing and .bbappend
files.
Look at the how the layers are parsed - this info is in
layer/conf/layer.conf
Try putting your .bbappend file in
.../meta-intel/meta-n450/recipes-jfa/images/core-image-sato.bbappend
I think you are correct now that I look more closely at the
meta-n450/conf/layer.conf file.
It has:
BBFILES := ${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend
which tells me that it will not find
recipes-jfa/core-image-sato.bbappend, but will find
meta-n450/recipes-jfa/images/core-image-sato.bbappend
Thanks,
JIm A
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] where to put IMAGE_INSTALL??
On 01/12/2012 08:06 AM, Gary Thomas wrote: On 2012-01-12 05:53, Jim Abernathy wrote: There seems to be some sensitivity to where I put the statement IMAGE_INSTALL += web-webkit. At first I just modifed the meta/receipes-sato/image/core-image-sato.bb file to include it. That caused the webkit to be built. Since that is not an ideal location, I removed it and put it into the local.conf file. That also caused the webkit to be built, but I wanted it to be part of my BSP permanently. I thought about creating a core-image-sato.bbappend file with the IMAGE_INSTALL += web-webkit in it and put that into the BSP, but that didn't cause the webkit to be built. Under the meta-intel/meta-n450 directory, I created a receipes-jfa directory and put the core-image-sato.bbappend file there. I must be missing a key rule about directory parsing and .bbappend files. Look at the how the layers are parsed - this info is in layer/conf/layer.conf Try putting your .bbappend file in .../meta-intel/meta-n450/recipes-jfa/images/core-image-sato.bbappend I just tested your method of putting the .bbappend file in the directory above and it work just fine. I also found out that you should not put the IMAGE_INSTALL in the local.conf. It builds okay, but the resulting image will not boot. Tom pointing me the a statement in the Poky reference manual about not doing this as well. JIm A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] understanding what's in an image
On 01/09/2012 09:07 PM, Christopher Larson wrote: Read layer.conf in each layer. See the BBFILES variable. -- Christopher Larson On Monday, January 9, 2012 at 5:51 PM, James Abernathy wrote: I'm trying to understand how bitbake parses the poky directory tree a little better. The best I can figure all .bb files are NOT included. Just some of them are. I'm guessing that the .bb in the meta/recipe-sato named core-image-sato.bb is the one that is used to start the parsing if bitbake core-image-sato is executed. I originally thought all subdirectories of a path included in BBLAYER were parsed looking for .bb files, but now I know that is not true, but not sure why. For example, it does not appear that webkit is included in the core-image-sato even though the recipe-sato directory includes the webkit subdirectory with it's recipe. What would be the proper way of adding the webkit to core-image-sato?? Jim A ___ yocto mailing list yocto@yoctoproject.org mailto:yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto the layer.conf in meta/conf includes and covers all .bb files under it like receipe-sato, which includes web-webkit. So does this say that the web-webkit get's built by bitbake, but the images does not contain web-webkit until you put in the IMAGE_INSTALL += web-webit??? Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] understanding what's in an image
On 01/10/2012 09:57 AM, Gary Thomas wrote: On 2012-01-10 07:48, Jim Abernathy wrote: On 01/09/2012 09:07 PM, Christopher Larson wrote: Read layer.conf in each layer. See the BBFILES variable. -- Christopher Larson On Monday, January 9, 2012 at 5:51 PM, James Abernathy wrote: I'm trying to understand how bitbake parses the poky directory tree a little better. The best I can figure all .bb files are NOT included. Just some of them are. I'm guessing that the .bb in the meta/recipe-sato named core-image-sato.bb is the one that is used to start the parsing if bitbake core-image-sato is executed. I originally thought all subdirectories of a path included in BBLAYER were parsed looking for .bb files, but now I know that is not true, but not sure why. For example, it does not appear that webkit is included in the core-image-sato even though the recipe-sato directory includes the webkit subdirectory with it's recipe. What would be the proper way of adding the webkit to core-image-sato?? Jim A ___ yocto mailing list yocto@yoctoproject.org mailto:yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto the layer.conf in meta/conf includes and covers all .bb files under it like receipe-sato, which includes web-webkit. So does this say that the web-webkit get's built by bitbake, but the images does not contain web-webkit until you put in the IMAGE_INSTALL += web-webit??? No, only packages which are needed to satisfy the needs of the given image are built. So, if your image does not include web-webkit, it won't be built even though there is a recipe for it. When building an image, bitbake looks at the image recipe and figures out what packages are needed (these are listed explicitly). Then any additional packages which are needed (DEPENDS, RDEPENDS, etc) will be added to the list. This process continues until all dependencies are met, yielding the final package set. Out of the 1000 or so possible recipes, you may end up only building a few hundred and many of these are support - i.e. only used for the build process itself. This makes sense now, thanks. I did this via hob this morning and it become more obvious because hob approaches this process as all about the package. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto on Acer Aspire One NAV50
On 01/10/2012 10:50 AM, Bruce Ashfield wrote: On 12-01-10 10:47 AM, James Abernathy wrote: I created a core-image-sato using the meta-n450 BSP hoping I could work with it on the Acer Aspire One 532h-2588. However, that netbook uses the Atheros AR5B95 wireless NIC and the Atheros AR8132 wired NIC, which are not recognized. Is there anything already in Yocto that could be turned on to support these devices, or am I left with porting the drives? Since Ubuntu 11.10 with it's kernel 3.0.0 supports these devices and runs on the netbook, I'm guessing it's a matter of configuring the kernel to include these modules. Does this sound right?? That should be all that is required. If the drivers you need are indeed in 3.0 (I didn't go check explicitly), then you can create a bbappend for the BSP in a layer, and add a configuration fragment that enables the drivers you need (as modules or builtin, your choice). Examples of config fragments are in the BSP/kernel guides found on the yocto project pages. If I'm only making changes to the .config parameters, do I still need to create a local bare clone of the yocto kernel and also git the poky-extras repository as mentioned in the Developers Manual appendix B? Jim A Cheers, Bruce Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] hob usage
I have a question about hob usage. I understand the basics of hob and how it adds packages. I also understand how it will parse through my local.conf and include any extra packages that I may have included by using IMAGE_INSTALL += package. I've found that if I start with a clean BSP and use hob to add a package, it will allow me to save that configuration anywhere. I'm not sure where I should save it. It contains the IMAGE_INSTALL for the packages I've selected, but is also includes a 'require' statement, which seems to have a relative path, like: require recipes-sato/images/core-image-sato.bb Where is the location I should save the hob configuration file? I know that if I save it outside my poky directory, the package will not be included, so it's important where it goes. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] builds failing
Starting Friday, I noticed builds(n450) failing due to files not being found. This morning it's still failing on 4 kernel.org modules: i.e. http://kernel.org/pub/linux/utils/kernel/module-init-tools/module-init-tools-3.16.tar.bz2 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] building Yocto on Fedora 14 vs. Ubuntu 11.10
I'm finding differences between the number of task for building meta-cedartrail on ubuntu 11.10 vs. doing the same thing on Fedora 14 and wondered if this is a problem. On a clean build of core-image-sato, the first section has 63 tasks on Ubuntu 11.10, but 126 tasks on Fedora 14. 126 is the number I remember seeing for the first section of the build on other Sato builds. Is this an issue? is this caused by the different development O/S's? BTW the second part of the build has 4426 tasks on Ubuntu 11.10 and also on Fedora 14. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error on meta-cedarview
On 01/03/2012 11:59 PM, Khem Raj wrote: On (03/01/12 12:26), Jim Abernathy wrote: On 12/29/2011 11:37 AM, Saul Wold wrote: On 12/28/2011 09:26 PM, Andrew Schweitzer wrote: Jim Abernathyjfabernathy@... writes: While running a build of the core-image-sato using the edison latest commits and the meta-cedartrail bsp, I notices some errors fly by and thought I'd see if anyone knows the reason. The build is just to test the bsp with no changes. Basically, doing the Appendix A of the Development manual substituting cedartrail for crownbay. snippet of the console log below: NOTE: package icon-naming-utils-native-0.8.7-r3: task do_unpack: Started ERROR: Function 'Unpack failure for URL: 'http://tango.freedesktop.org/releases/icon-naming-utils-0.8.7.tar.gz'. I don't know the reason, but I did get the same error when trying to build yocto per the getting started page, changing local.conf to create qemuarm I would be interested in knowing the reason too. There has been a bug filed against this issue, it seems that the tarballs have moved or are unavailable from that location for some reason. You are getting a download page, and I believe that the failure should occur earlier with a checksum mismatch, but is not. You can fetch this file from our mirror at: http://downloads.yoctoproject.org/mirror/sources/icon-naming-utils-0.8.7.tar.gz Saul, Sorry for the dumb question, but how do I download the file and fool bitbake into not trying to download it from the invalid site? Or do I need to change a file somewhere to specific our mirror URL instead?? cd into DL_DIR wget thetar then touchtar.done You can add http://downloads.yoctoproject.org/mirror/sources/ to MIRRORS something like MIRRORS =+ http://downloads.yoctoproject.org/mirror/sources/; to the concerned recipe. I went back and had a number of issues so I just deleted the current ~/poky/build directory and restarted the process including editing the conf/local.conf, etc. The only change I made to the recipes was to put in the reference to the Yocto mirror for icon-naming-utils. I got a fair way down into the build(2358 of 4426) before I got a new error. The step is related to initramfs-live-boot_1.0.bb do_package_write_rpm the log is below: NOTE: Creating RPM package for initramfs-live-boot-dbg NOTE: Creating RPM package for initramfs-live-boot NOTE: Creating RPM package for initramfs-live-boot NOTE: Not creating empty RPM package for initramfs-live-boot-doc NOTE: Creating EMPTY RPM Package for initramfs-live-boot-dev NOTE: Not creating empty RPM package for initramfs-live-boot-staticdev NOTE: Not creating empty RPM package for initramfs-live-boot-locale Building target platforms: all-poky-linux Processing files: initramfs-live-boot-1.0-r6.all Finding Provides: /home/jim/poky/build/tmp/work/all-poky-linux/initramfs-live-boot-1.0-r6/initramfs-live-boot.provides Finding Requires: /home/jim/poky/build/tmp/work/all-poky-linux/initramfs-live-boot-1.0-r6/initramfs-live-boot.requires Requires: /bin/sh Requires: /bin/sh Processing files: initramfs-live-boot-dbg-1.0-r6.all Finding Provides: /home/jim/poky/build/tmp/work/all-poky-linux/initramfs-live-boot-1.0-r6/initramfs-live-boot.provides Finding Requires: /home/jim/poky/build/tmp/work/all-poky-linux/initramfs-live-boot-1.0-r6/initramfs-live-boot.requires Processing files: initramfs-live-boot-dev-1.0-r6.all Checking for unpackaged file(s): /home/jim/poky/build/tmp/sysroots/i686-linux/usr/lib/rpm/check-files /home/jim/poky/build/tmp/work/all-poky-linux/initramfs-live-boot-1.0-r6/package error: Unable to open temp file. RPM build errors: Unable to open temp file. ERROR: Function 'BUILDSPEC' failed (see /home/jim/poky/build/tmp/work/all-poky-linux/initramfs-live-boot-1.0-r6/temp/log.do_package_write_rpm.27564 for further information) Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-ti?????
I know the examples in the documentation of Yocto use meta-intel a lot to get the board specific BSPs like meta-crownbay or meta-n450. Is there a meta-ti or similar that gets you the meta-beagleboard and meta-pandaboard? If not how do you clone and checkout the pandaboard BPS? Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] build error on meta-cedarview
While running a build of the core-image-sato using the edison latest commits and the meta-cedartrail bsp, I notices some errors fly by and thought I'd see if anyone knows the reason. The build is just to test the bsp with no changes. Basically, doing the Appendix A of the Development manual substituting cedartrail for crownbay. snippet of the console log below: NOTE: package icon-naming-utils-native-0.8.7-r3: task do_unpack: Started ERROR: Function 'Unpack failure for URL: 'http://tango.freedesktop.org/releases/icon-naming-utils-0.8.7.tar.gz'. Unpack command PATH=/home/jim/poky/build/tmp/sysroots/i686-linux/usr/bin/perl-native:/home/jim/poky/build/tmp/sysroots/i686-linux/usr/bin/core2-linux:/home/jim/poky/build/tmp/sysroots/i686-linux/usr/bin:/home/jim/poky/build/tmp/sysroots/i686-linux/usr/sbin:/home/jim/poky/build/tmp/sysroots/i686-linux/usr/bin:/home/jim/poky/build/tmp/sysroots/i686-linux/sbin:/home/jim/poky/build/tmp/sysroots/i686-linux//bin:/home/jim/poky/scripts/native-intercept:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jim/poky/scripts tar xz --no-same-owner -f /home/jim/poky/build/downloads/icon-naming-utils-0.8.7.tar.gz failed with return value 2' failed ERROR: Logfile of failure stored in: /home/jim/poky/build/tmp/work/i686-linux/icon-naming-utils-native-0.8.7-r3/temp/log.do_unpack.19392 Log data follows: | NOTE: Unpacking /home/jim/poky/build/downloads/icon-naming-utils-0.8.7.tar.gz to /home/jim/poky/build/tmp/work/i686-linux/icon-naming-utils-native-0.8.7-r3/ | | gzip: stdin: not in gzip format | tar: Child returned status 1 | tar: Error is not recoverable: exiting now | ERROR: Function 'Unpack failure for URL: 'http://tango.freedesktop.org/releases/icon-naming-utils-0.8.7.tar.gz'. Unpack command PATH=/home/jim/poky/build/tmp/sysroots/i686-linux/usr/bin/perl-native:/home/jim/poky/build/tmp/sysroots/i686-linux/usr/bin/core2-linux:/home/jim/poky/build/tmp/sysroots/i686-linux/usr/bin:/home/jim/poky/build/tmp/sysroots/i686-linux/usr/sbin:/home/jim/poky/build/tmp/sysroots/i686-linux/usr/bin:/home/jim/poky/build/tmp/sysroots/i686-linux/sbin:/home/jim/poky/build/tmp/sysroots/i686-linux//bin:/home/jim/poky/scripts/native-intercept:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jim/poky/scripts tar xz --no-same-owner -f /home/jim/poky/build/downloads/icon-naming-utils-0.8.7.tar.gz failed with return value 2' failed NOTE: package icon-naming-utils-native-0.8.7-r3: task do_unpack: Failed ERROR: Task 2395 (/home/jim/poky/meta/recipes-devtools/icon-naming-utils/icon-naming-utils-native_0.8.7.bb http://icon-naming-utils-native_0.8.7.bb, do_unpack) failed with exit code '1' Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where is the emgd.ko module?
On Tue, 2011-12-13 at 11:13 -0500, autif khan wrote: I built the crownbay (not crownbay-noemgd) image as outlined in the E660 development kit (link http://www.yoctoproject.org/download/bsp/intel-atom-processor-e660-intel-platform-controller-hub-eg20t-development-kit-1) I used poky-edison-6.0.tar.bz2 and crownbay-edison-6.0.0.tar.bz2 and followed the instructions (short version - extract, move, add meta-intel/meta-crownbay to bblayers.conf, add MACHINE=crownbay to local.conf, bitbake core-image-sato) The result was the expected set of images in tmp/deploy/images I loop mounted the core-image-sato-crownbay.ext3 and tried to find emgd.ko in the file system - I could not find it. (find output attached - notice that there is no emgd.ko) Here is the kicker - crownbay-edison-6.0.0.tar.bz2 has a directory called binary which contains core-image-sato-crownbay.hddimg, which contains rootfs.img, which I also loop mounted and was able to find the emgd.ko (however this image does not work with my hardware, I am not sure why). Find output for this is also included below. I very much doubt that it is included as a part of the kernel, I looked at the kernel's .config (in tmp/work/crownbay-poky-linux/linux-yocto-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+2247da9131ea7e46ed4766a69bb1353dba22f873-r2/linux-crownbay-standard-build) and could not find emgd there either. So, my questions is if I am doing something wrong? Do I need to do something to get the emgd.ko to build? I am using the latest release (6.0 Edison (released on October 17th, 2011)). Please advise. Check out the README file in the meta-crownbay directory. There are instructions on integrating the EMGD driver files into the build. Jim A Thanks Autif autif@xu:~/data/dev/yocto/emgd/tmp/deploy/images/1$ sudo find . | grep emgd ./usr/lib/libemgdsrv_um.so.1.5.15.3226 ./usr/lib/libemgdsrv_um.so ./usr/lib/libemgdglslcompiler.so.1.5.15.3226 ./usr/lib/libemgdPVR2D_DRIWSEGL.so ./usr/lib/xorg/modules/drivers/emgd_drv.so ./usr/lib/libemgdPVR2D_DRIWSEGL.so.1.5.15.3226 ./usr/lib/libemgdsrv_init.so ./usr/lib/libemgdsrv_init.so.1.5.15.3226 ./usr/lib/libemgdglslcompiler.so ./usr/lib/dri/emgd_dri.so autif@xu:~/data/dev/yocto/emgd/tmp/deploy/images/1$ autif@xu:~/data/dev/yocto/poky-edison-6.0/meta-intel/meta-crownbay/binary/2$ sudo find . | grep emgd ./usr/lib/libemgdsrv_um.so ./usr/lib/dri/emgd_dri.so ./usr/lib/libemgdsrv_init.so.1.5.15.3226 ./usr/lib/libemgdsrv_init.so ./usr/lib/xorg/modules/drivers/emgd_drv.so ./usr/lib/libemgdPVR2D_DRIWSEGL.so.1.5.15.3226 ./usr/lib/libemgdglslcompiler.so.1.5.15.3226 ./usr/lib/libemgdsrv_um.so.1.5.15.3226 ./usr/lib/libemgdPVR2D_DRIWSEGL.so ./usr/lib/libemgdglslcompiler.so ./lib/modules/3.0.4-yocto-standard+/kernel/drivers/gpu/drm/emgd ./lib/modules/3.0.4-yocto-standard+/kernel/drivers/gpu/drm/emgd/emgd.ko ./etc/rpm-postinsts/kernel-module-emgd.sh.done autif@xu:~/data/dev/yocto/poky-edison-6.0/meta-intel/meta-crownbay/binary/2$ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ADT installer
I was following the ADT manual online, section 2.1.1.1, and everything seemed to complete as expected, but adt_installer.tar.bz2 was not created in the /build/tmp/deploy/sdk direction as documented. In fact, there is no sdk directory in deploy. Is this a documentation issue or is this not working. BTW, I could not find the tarball anywhere on my Ubuntu development system. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ADT installer
On Wed, 2011-11-23 at 18:22 +, Rifenbark, Scott M wrote: Jim, My machine finished and it built the adt_installer.tar.bz2 in ~/yocto-project/build/tmp/deploy/sdk as advertised. The only change I made was the URL change to get the Edison tarball using wget. Scott Okay, I see my problem. If you look at the instructions in the manual, $ source poky-edison-6.0/oe-init-build-env $ bitbake adt-installer it does not start with cd'ing into the poky directory as other bitbake sessions do. This sequence creates the build directory at the same directory level as the poky-edison-6.0 directory. I was looking down in poky-edison-6.0. What happened is the build directory was created at the correct level for the way the command was spelled out. I just had my head up my Jim A -Original Message- From: James Abernathy [mailto:jfaberna...@gmail.com] Sent: Wednesday, November 23, 2011 9:28 AM To: Rifenbark, Scott M Cc: yocto@yoctoproject.org Subject: Re: [yocto] ADT installer On Nov 23, 2011, at 11:55 AM, Rifenbark, Scott M wrote: Jim, Let me try and replicate this from the manual. I will get back momentarily. Scott -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Jim Abernathy Sent: Wednesday, November 23, 2011 8:45 AM To: yocto@yoctoproject.org Subject: [yocto] ADT installer I was following the ADT manual online, section 2.1.1.1, and everything seemed to complete as expected, but adt_installer.tar.bz2 was not created in the /build/tmp/deploy/sdk direction as documented. In fact, there is no sdk directory in deploy. Is this a documentation issue or is this not working. BTW, I could not find the tarball anywhere on my Ubuntu development system. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto The instructions don't have you cd into the directory to execute the source oe-. Not sure if that's a problem. I can rerun. I use the Edison Poky tarball and not the git. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build error while following Appendix A. Yocto Project Development manual
okay, what you mentioned as the steps below, I agree with, but a couple
I don't understand. first, in the linux-yocto_3.0.bbappend file, why is
the KMACHINE statement changed to common-pc/atom-pc? If I look st eh
section of the doc in A.5.2.4 talking about going to
cgit/cgit.cgi/linux-yocto-3.0 to get the latest commit strings, I see
that it agrees with the path in #2, but not sure why??
Second, I looked at your cat of the same file containing the SRCREV
commit strings and I don't see that they agree with the commits on the
website even just this morning. Can you explain that? Should I just use
the ones in your cat output or eventually the corrected Dev. Manual?
Jim A
On Tue, 2011-11-01 at 19:45 -0500, Tom Zanussi wrote:
Hi James,
I'm still not sure what happened in your case to cause this problem, but
I just went through the Appendix A example pretty much as described, and
got a good build out of it. There was one particular part of the
example that wasn't exactly clear and that could definitely cause some
build problems if you did it incorrectly (the section that makes changes
to linux-yocto_3.0.bbappend, which in the example has a custom branch in
the .bbappend file, but has the explanation using atom-pc).
I'll work with Scott to make sure that part gets cleaned up, along with
the other comments that should get pulled in, but in the meantime, I
captured the steps I used below, which should work in the same way for
you.
trz@elmorro:/usr/local/dev/yocto$ mkdir bsp-test; cd bsp-test
trz@elmorro:/usr/local/dev/yocto/bsp-test$ git clone
git://git.yoctoproject.org/poky
trz@elmorro:/usr/local/dev/yocto/bsp-test$ cd poky
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky$ git checkout -b edison
origin/edison
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky$ git clone
git://git.yoctoproject.org/meta-intel.git
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky$ cd meta-intel
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ git checkout -b
edison origin/edison
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ cp -a
meta-crownbay/ meta-mymachine
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ rm
meta-mymachine/conf/machine/crownbay.conf
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ mv
meta-mymachine/conf/machine/crownbay-noemgd.conf
meta-mymachine/conf/machine/mymachine.conf
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ rm -rf
meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay/
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ mv
meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay-noemgd
meta-mymachine/recipes-bsp/formfactor/formfactor/mymachine
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ rm -rf
meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay
The Developer's Manual seems to want to base the BSP on atom-pc for
this example, so we need to specify the atom-pc branch and get the
SRCREVs for atom-pc or the step that modifies the
linux-yocto_3.0.bbappend. So in
meta-yocto/recipes-kernel/linux/linux-yocto_3.0.bbappend, we find both
the KMACHINE branch we need, and the SRCREV on that branch we need for
edison. Since that doesn't specify the meta branch, but the base
recipe does, we can look at the SRCREV_meta there
(meta/recipes-kernel/linux/linux-yocto_3.0.bb) for the SRCREV of the
meta branch, which already matches what we're using, so no change
needed there.
Here's the resulting linux-yocto_3.0.bbappend:
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ cat
meta-mymachine/recipes-kernel/linux/linux-yocto_3.0.bbappend
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
COMPATIBLE_MACHINE_mymachine = mymachine
KMACHINE_mymachine = yocto/standard/common-pc/atom-pc
KERNEL_FEATURES_append_mymachine += cfg/smp.scc
SRCREV_machine_pn-linux-yocto_mymachine ?=
1e18e44adbe79b846e382370eb29bc4b8cd5a1a0
SRCREV_meta_pn-linux-yocto_mymachine ?=
d05450e4aef02c1b7137398ab3a9f8f96da74f52
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky$ source oe-init-build-env
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky$ bitbake core-image-sato
NOTE: Tasks Summary: Attempted 4426 tasks of which 247 didn't need to be
rerun and 0 failed.
trz@elmorro:/usr/local/dev/yocto/bsp-test/poky/build
Tom
On Tue, 2011-11-01 at 12:48 -0700, James Abernathy wrote:
Just to clear up the basics, Prior to following Appendix A verbatim, I
did the following
1. install prerequisites from GS guide
2. git clone git://git.yoctoproject.org/poky
3. cd poky
4. git clone git://git.yoctoproject.org/meta-intel.git
I did not install the poky-extras. I assumed it only had to be
installed if you installed the kernel source for modification like in
Appendix b
Jim a
On Tue, Nov 1, 2011 at 3:40 PM, Tom Zanussi tom.zanu...@intel.com
wrote:
Hi,
On Tue, 2011-11-01 at 11:37
Re: [yocto] Build error while following Appendix A. Yocto Project Development manual
Well, I finally got a successful build without erros of the Appendix A example for Crownbay, but the image created was only 216MB in size and kernel panic'ed because it couldn't find a valid root file system. I'm going to try again from scratch and see if I missed anything. If that fails, I'll report out. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build error while following Appendix A. Yocto Project Development manual
I'm noticing fetcher failures while my bitbake is working. They are listed as warning. Do I ignore these?? WARNING: Fetcher failure for URL: 'None'. Fetch command export HOME=/home/jim; export SSH_AGENT_PID=1500; export SSH_AUTH_SOCK=/tmp/keyring-Zcbzax/ssh; export GIT_CONFIG=/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/usr/etc/gitconfig; export PATH=/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/usr/bin/core2-poky-linux:/home/jim/bsp-test/poky/build/tmp/sysroots/mymachine/usr/bin/crossscripts:/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/usr/sbin:/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/usr/bin:/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/sbin:/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux//bin:/home/jim/bsp-test/poky/scripts:/home/jim/bsp-test/poky/bitbake/bin/:/home/jim/bsp-test/poky/scripts:/home/jim/bsp-test/poky/bitbake/bin/:/home/jim/bsp-test/poky/scripts:/home/jim/bsp-test/poky/bitbake/bin/:/home/jim/bsp-test/poky/scripts:/home/jim/bsp-test/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/CodeSourcery/Sourcery_G++_Lite/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games: /home/jim/bsp-test/poky/scripts; /usr/bin/env wget -t 5 -q --passive-ftp --no-check-certificate -P /home/jim/bsp-test/poky/build/downloads 'https://fedorahosted.org/releases/l/i/liberation-fonts/liberation-fonts-1.04.tar.gz' failed with signal 4, output: ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
