Hi Gary, On 13 February 2014 14:36, Gary Thomas <g...@mlbassoc.com> wrote: > I had previously built core-image-sato-sdk with some extra packages: > CORE_IMAGE_EXTRA_INSTALL += "rsync openssh" > That worked fine, but core-image-weston fails as above. Is there a > reason I can't choose openssh instead of dropbear (and perhaps there > is some other way I am supposed to choose)?
You might find EXTRA_IMAGE_FEATURES += "ssh-server-openssh" better than CORE_IMAGE_EXTRA_INSTALL, because core-image-weston has the ssh-server-dropbear image feature. When specifying both the right thing happens (dropbear is dropped). > I removed the openssh from the extras and now it builds, but it doesn't > do anything [useful] - should it actually work? I don't see anything > that looks like 'weston' running. Looks like weston is crashing. There are known problems with Weston in qemu: https://bugzilla.yoctoproject.org/show_bug.cgi?id=5660 Valentin did the research here and I can't remember the details: Valentin, can you elaborate on the comments there about what is working/breaking? I remember there being a qemu option that changed behaviour too. Try changing the init script (or just running weston manually) to pick the fbdev backend. Note that right now this isn't enabled but there's a patch on the list to enable it by default, but it's just a PACKAGECONFIG away from being enabled. Ross _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
