From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Markus Volk <f_l_k@t-online.de>
Cc: yocto@yoctoproject.org
Subject: Re: some issues with current poky master
Date: Fri, 18 Aug 2017 09:03:10 -0500 [thread overview]
Message-ID: <1503064990.28682.24.camel@linux.intel.com> (raw)
In-Reply-To: <20170818013458.da848df3fac10ac277be82bb@t-online.de>
On Fri, 2017-08-18 at 01:34 +0200, Markus Volk wrote:
>
> > After sucessful build of the Image, my .iso has 38MB in size and seems to be missing the entire rootfs
> > The created hddimg has the right size of 4,3GB, but when i write it onto an usb drive (tried dd and gnome-disk-utility) it ends up with a big /boot partiton containing only the boot files
> >
>
> I still do not know if this is a homemade one, but i saw inside the do_bootimg log that isolevel 3 was missing for mkisofs because the rootfs is too big without.
>
> For me this here inside image-live.bbclass fails for some reason:
>
> # Check the size of ${ISODIR}/rootfs.img, use mkisofs -iso-level 3
> # when it exceeds 3.8GB, the specification is 4G - 1 bytes, we need
> # leave a few space for other files.
> mkisofs_iso_level=""
>
> if [ -n "${ROOTFS}" ] && [ -s "${ROOTFS}" ]; then
> rootfs_img_size=`stat -c '%s' ${ISODIR}/rootfs.img`
> # 4080218931 = 3.8 * 1024 * 1024 * 1024
> if [ $rootfs_img_size -gt 4080218931 ]; then
> bbnote "${ISODIR}/rootfs.img execeeds 3.8GB, using '-iso-level 3' for mkisofs"
> mkisofs_iso_level="-iso-level 3"
> fi
> fi
>
not really sure what you have changed in the code (better to send a diff
snippet), so proposed your change to the oe-core.
>
>
> hard coding mkisofs_iso_level to
>
> mkisofs_iso_level="-iso-level 3"
>
> fixes this up
> --
> Markus Volk <f_l_k@t-online.de>
next prev parent reply other threads:[~2017-08-18 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 8:00 some issues with current poky master Markus Volk
2017-08-17 23:34 ` Markus Volk
2017-08-18 14:03 ` Leonardo Sandoval [this message]
2017-08-19 18:36 ` Markus Volk
2017-08-21 11:24 ` Markus Volk
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=1503064990.28682.24.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=f_l_k@t-online.de \
--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.