From: Tom Zanussi <tom.zanussi@...> The BBFILES append in crownbay's layer.conf is too broad and causes the wrong init-install.sh to be picked up, causing a bad grub install. Narrow down the

From: Tom Zanussi <tom.zanussi@...> Fix for yocto bug #1257: broken grub due to wrong root path. The following changes since commit 96c247dad88b9fc0159b2a929216876d9fbb06dc: Tom Zanussi

Messages to the team:   * Thanks and kudos to the team, Yocto 1.1 has reached feature complete. The team is working on completing the build and bug fixes now. Many have been working really hard to

Interesting, since this is failing on multiple image types, there should be different init scripts at play, each with different requirements that should be met by the rootfs generation. Have you

Is the problem here that we need better documentation on using a prebuilt toolchain? I will have to learn more about the context of the problem from someone. The bug could just be against

I can, but not sure what the bug is. - k

Hi there, Git master as of that point. Revision 46cf540e63a848512617b20fd8492f81bfb2f704 I do have a tmp/sysroots/x86_64-linux/usr/bin/file.real -- although I'm building for BeagleBoard, and don't

Hello, When I mounted the root image on loop back device, I actually ran the init program. It executed and complained about missing params. I tried with the 5, like for network connected inittab.

Jeff, Which version of poky are you working with? There was a problem that we had with file at one point and thought was fixed. If you check in your tmp/sysroots directory for the host machine, do

The move originally scheduled for today will now happen on Wednesday August 3rd from 10pm to midnight PDT. For reference, we will move mailing lists and related services to new hardware hosted at the

On my host system I have the "file" utility version 5.05. The version in poky/in my build directories is version 5.04. I'm seeing a lot of builds fail with the following: | error: magic_load(ms,

Lianhao, For DISTRO_VERSION, we still need to use POKY_DISTRO_VERSION since our distro is "POKY" as to other rename to OECORE, are those variables that're distro neutral. Hope you get the idea.

Thank you very much, Bruce. The patch is now picked up, and the build runs successfully. cheers, Andre

Hi Jessica, I noticed the we still use POKY_DISTRO_VERSION in the environment while some other variables have changed their prefix to OECORE_ (e.g. OECORE_NATIVE_SYSROOT, etc.) Which prefix should

Nope. I don't think it's a red herring: Both of these: Freeing unused kernel memory: 720k freed Failed to execute /init Indicate that the device came up and init was loaded, the kernel passed

I'm also seeing this on both sugarbay and jasperforest with the latest master. rootwait doesn't help. rtc_cmos 00:07: setting system clock to 2010-01-02 05:35:34 UTC (1262410534) Freeing unused

Can you send a full bootlog, or paste it somewhere accessible ? It's hard to say what's with the information you've given. Is this the latest yocto master ? If you are seeing that message it

Hello, I probably miss something trivial. I cloned the git://git.yoctoproject.org/poky.git I build on a 64 bit machine a qemux86-64 (. ./oe-init-build-env qemux86-64 and changing the

Hello, My download directory is on a CIFS mounted drive. The idea was that other PCs could access the already downloaded files on the local network. The package libpam however failed

Hi all, Yocto 1.1 M2 released last week. The new-submit vs. fixed bug is 28 vs. 36. A lot of bugs are fixed, which make both open bug number and WDD number decreased a lot -- Open bug number from 185