All of lore.kernel.org
 help / color / mirror / Atom feed
From: "JH" <jupiter.hce@gmail.com>
To: Mikko.Rapeli@bmw.de
Cc: marek.belisko@gmail.com, yocto@yoctoproject.org,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts
Date: Tue, 18 Feb 2020 20:43:01 +1100	[thread overview]
Message-ID: <CAA=hcWREdVeYqnOs-3aSFOhobaQWvLoaEU8Rdku_RM=Q5q2Ruw@mail.gmail.com> (raw)
In-Reply-To: <20200218085848.GA104502@korppu>

Hi Mikko,

On 2/18/20, Mikko.Rapeli@bmw.de <Mikko.Rapeli@bmw.de> wrote:
> I think you may be missing volatile-binds package and service from your
> image.
> See poky/meta/recipes-core/volatile-binds/volatile-binds.bb

I got the source in my build system, it is zeus:

oe-core/meta/recipes-core/volatile-binds/volatile-binds.bb

./all-oe-linux/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/packages-split/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/sysroot-destdir/sysroot-providers/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata-pdata-input/runtime/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata-pdata-input/runtime-reverse/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata-pdata-input/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata/runtime/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata/runtime-reverse/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/license-destdir/volatile-binds

Are there correct?

> It may be missing /var/log but with systemd there should not be needs to
> write
> to that location after image builds...

The volatile did not have the log, so /var/log -> volatile/log was an
invalid link, should I manually create it?

Thanks Mikko,

- jh

WARNING: multiple messages have this Message-ID (diff)
From: JH <jupiter.hce@gmail.com>
To: Mikko.Rapeli@bmw.de
Cc: openembedded-core@lists.openembedded.org, yocto@yoctoproject.org
Subject: Re: [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts
Date: Tue, 18 Feb 2020 20:43:01 +1100	[thread overview]
Message-ID: <CAA=hcWREdVeYqnOs-3aSFOhobaQWvLoaEU8Rdku_RM=Q5q2Ruw@mail.gmail.com> (raw)
In-Reply-To: <20200218085848.GA104502@korppu>

Hi Mikko,

On 2/18/20, Mikko.Rapeli@bmw.de <Mikko.Rapeli@bmw.de> wrote:
> I think you may be missing volatile-binds package and service from your
> image.
> See poky/meta/recipes-core/volatile-binds/volatile-binds.bb

I got the source in my build system, it is zeus:

oe-core/meta/recipes-core/volatile-binds/volatile-binds.bb

./all-oe-linux/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/packages-split/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/sysroot-destdir/sysroot-providers/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata-pdata-input/runtime/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata-pdata-input/runtime-reverse/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata-pdata-input/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata/runtime/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata/runtime-reverse/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/pkgdata/volatile-binds
./all-oe-linux/volatile-binds/1.0-r0/license-destdir/volatile-binds

Are there correct?

> It may be missing /var/log but with systemd there should not be needs to
> write
> to that location after image builds...

The volatile did not have the log, so /var/log -> volatile/log was an
invalid link, should I manually create it?

Thanks Mikko,

- jh


  reply	other threads:[~2020-02-19 21:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18  1:00 Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts JH
2020-02-18  1:00 ` JH
2020-02-18  1:00 ` JH
2020-02-18  1:00 ` JH
2020-02-18  4:35 ` JH
2020-02-18  4:35   ` JH
2020-02-18  4:35   ` JH
2020-02-18  4:35   ` JH
2020-02-18  6:37 ` [yocto] " Belisko Marek
2020-02-18  6:37   ` Belisko Marek
2020-02-18  6:37   ` Marek Belisko
2020-02-18  6:37   ` Belisko Marek
2020-02-18  7:20   ` JH
2020-02-18  7:20     ` JH
2020-02-18  7:20     ` JH
2020-02-18  7:20     ` JH
2020-02-18  8:58     ` [OE-core] " Mikko Rapeli
2020-02-18  8:58       ` Mikko.Rapeli
2020-02-18  9:43       ` JH [this message]
2020-02-18  9:43         ` JH
2020-02-18 10:11         ` [OE-core] " Mikko Rapeli
2020-02-18 10:11           ` Mikko.Rapeli
2020-02-18 11:30           ` [OE-core] " JH
2020-02-18 11:30             ` JH

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='CAA=hcWREdVeYqnOs-3aSFOhobaQWvLoaEU8Rdku_RM=Q5q2Ruw@mail.gmail.com' \
    --to=jupiter.hce@gmail.com \
    --cc=Mikko.Rapeli@bmw.de \
    --cc=marek.belisko@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.