All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Felix01 Fischer <felix01.fischer@iav.de>
Cc: meta-intel@yoctoproject.org, yocto@yoctoproject.org,
	genivi-meta-ivi@lists.genivi.org
Subject: Re: [meta-intel] Boot failure when using meta-intel and meta-ivi
Date: Thu, 25 Jul 2013 11:57:57 -0500	[thread overview]
Message-ID: <1374771477.6515.31.camel@empanada> (raw)
In-Reply-To: <OF4EE7C2B2.6E6969A5-ONC1257BB3.002ECED6-C1257BB3.00316E7B@retarus.de>

On Thu, 2013-07-25 at 11:00 +0200, Felix01 Fischer wrote:
> Hi, 
> I haven written regarding this issues before. So maybe it sounds
> familiar :-)
> 
> I'm unable to produce a booting image when combining a machine from
> the meta-intel layer with "DISTRO ?= "poky-ivi-systemd" from the
> meta-ivi layer.
> You will find a photograph of my screen attached, but I will describe
> the error anyway. 
> 
> 
> Which error do I get? 
> 
> When I'm booting my image the machine fails to boot. The relevant
> information (IMHO) are the lines:
>        /init: line 98: mount: not found 
>         /init: line 98: mount: not found 
>         /init: line 98: mount: not found 
> and 
>         cat: can't open '/proc/cmdline': No such file or directory 
>         Waiting for removable media... 
> 
> 
> When does the error occur?
> 
> Every image built with the local.conf options 
> MACHINE ?= "crownbay"        OR        MACHINE ?= "chiefriver" 
> AND 
> DISTRO ?= "poky-ivi-systemd" 
> 
> failed to boot. 
> 
I guess more information is needed to even build this.  Using the poky
commit id in the README, using either meta-intel/master or
meta-intel/dylan gives errors like this:

trz@elmorro:/usr/local/dev/yocto/ivi-test/build$ bitbake foton-image
Pseudo is not present but is required, building this first before the
main build
Loading cache: 100% |###########################################| ETA:
00:00:00
Loaded 1162 entries from dependency cache.
ERROR: No recipes available for:
  /usr/local/dev/yocto/ivi-test/meta-ivi/recipes-extended/common-api/dbus_1.6.10.bbappend
  /usr/local/dev/yocto/ivi-test/meta-ivi/recipes-core-ivi/dbus/dbus_1.6.10.bbappend
  /usr/local/dev/yocto/ivi-test/meta-ivi/recipes-connectivity/connman/connman_1.15.bbappend
  /usr/local/dev/yocto/ivi-test/meta-ivi/recipes-graphics/xorg-xserver/xserver-xorg_1.14.0.bbappend
  /usr/local/dev/yocto/ivi-test/meta-ivi/recipes-core-ivi/busybox/busybox_1.21.1.bbappend
  /usr/local/dev/yocto/ivi-test/meta-ivi/recipes-core-ivi/eglibc/eglibc_2.18.bbappend
  /usr/local/dev/yocto/ivi-test/meta-intel/meta-crownbay/recipes-kernel/linux/linux-yocto-rt_3.8.bbappend
  /usr/local/dev/yocto/ivi-test/meta-ivi/recipes-qt/qt4/qt4-embedded_4.8.5.bbappend
  /usr/local/dev/yocto/ivi-test/meta-intel/common/recipes-graphics/mesa/mesa_9.0.2.bbappend
  /usr/local/dev/yocto/ivi-test/meta-ivi/recipes-core-ivi/netbase/netbase_5.1.bbappend
ERROR: Command execution failed: Exited with 1

So, please supply the relevant commits for all layers used..

> I have tried builds with meta-ivi excalibur (not 100% sure) and foton
> releases and the master branch aswell 
> Similar applies to poky and meta-intel. I tried the danny and dylan
> releases and the master branch. 
> 
> The boot happens from an USB stick on which I dd'ed
> "foton-image-$MACHINE-$BUILDDATE.hddimg" 
> 
> All other builds are booting fine.
> 
> Addind "EXTRA_IMAGE_FEATURE = "udev-extraconf" did not change this
> behauviour. 
> 
> Building only with meta-intel OR meta-ivi results in a booting image.
> 
Not sure what this means - if using only meta-ivi, which machine are you
building?

Tom


> So, any ideas?
> 
> regards,
> 
> Viele Grüße
> 
> Felix Fischer
> 
> Studentischer Mitarbeiter (VC-D1)
> Vehicle Cockpit Electronics Devices
> 
> IAV GmbH
> Carnotstr. 1
> 10587 BERLIN
> GERMANY
> 
> Phone: +49 30 39978-9540
> Fax:      +49 30 39978-9411
> E-Mail:  <mailto:felix01.fischer@iav.de>
> Internet: http://www.iav.com
> 
> Sitz/Registered Office: Berlin, 
> Registergericht/Registration Court: Amtsgericht Charlottenburg, 
> Registernummer/Company Registration Number: HRB 21 280, 
> Geschäftsführer/Managing Directors: Kurt Blumenröder, Michael
> Schubert, Dr. Rüdiger Goyk
> _______________________________________________
> meta-intel mailing list
> meta-intel@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel




  reply	other threads:[~2013-07-25 16:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  9:00 Boot failure when using meta-intel and meta-ivi Felix01 Fischer
2013-07-25 16:57 ` Tom Zanussi [this message]
     [not found]   ` <OF9AE9D621.3F293DD7-ONC1257BB4.0029E8ED-C1257BB4.002AD720@retarus.de>
2013-07-27 14:17     ` Antwort: Re: [meta-intel] " Tom Zanussi
2013-07-29  6:54       ` Behrens, Holger
2013-07-29  8:05         ` Antwort: " Felix01 Fischer
2013-07-31  3:44           ` Tom Zanussi
2013-07-31  3:26         ` Tom Zanussi
2013-07-31 14:05           ` Behrens, Holger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1374771477.6515.31.camel@empanada \
    --to=tom.zanussi@intel.com \
    --cc=felix01.fischer@iav.de \
    --cc=genivi-meta-ivi@lists.genivi.org \
    --cc=meta-intel@yoctoproject.org \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.