From: Falco Hyfing <hyfinglists@gmail.com>
To: barebox@lists.infradead.org
Subject: Re: squashfs: corrupted kernel image when booting/reading from squashfs
Date: Tue, 7 Feb 2017 13:25:04 +0100 [thread overview]
Message-ID: <CAChPQeCo18tLMJTYE8cJ43=3Nnw=PeOi-iOBH3g-5RDWjfhVcA@mail.gmail.com> (raw)
In-Reply-To: <20170204113525.rkyuqe6uvtjachnz@pengutronix.de>
Hi,
I've found what causes my problems with the squashfs volume. The
standard block size using mksquashfs is 128KiB, but OpenWrt's default
is 256KiB (-b 256k) causing the failure:
mksquashfs openwrt/build_dir/target-arm_xscale_musl-1.1.15_eabi/root-baltosopenwrt/build_dir/target-arm_xscale_musl-1.1.15_eabi/linux-baltos/root.squashfs
-root-owned -noappend -comp xz -b 256k -p '/dev d 755 0 0' -p
'/dev/console c 600 0 0 5 1' -processors 1
Setting -b 128k works.
Also OpenWrt uses bcj filters (-Xbcj arm) for xz which don't work
either. I had commented out this option earlier.
Best wishes,
Falco Hyfing
On Sat, Feb 4, 2017 at 12:35 PM, Ulrich Ölmann <u.oelmann@pengutronix.de> wrote:
> Hi Falco,
>
> On Fri, Feb 03, 2017 at 12:24:47PM +0100, Falco Hyfing wrote:
>> I try to boot a kernel-fit.itb from squashfs (xz compressed) volume while the
>> same kernel-fit.itb is bootable from a fat volume:
>
> currently barebox' squashfs driver seems to be broken if not used with lzo
> compression: the symptom is barebox only reading the first squashfs block
> correctly.
>
> I looked into this some months ago, but did not manage to find and fix the bug
> in reasonable time. As the barebox driver has been ported from the linux kernel,
> the latter is a working reference to look at when debugging.
>
> So you are welcome to hack on it and send patches. :)
>
> Best regards
> Ulrich
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-02-07 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAChPQeC3-EsvZ2s35qcVZL=gusSJf1FKivKjB=LR8LHR1F3POA@mail.gmail.com>
2017-02-03 11:24 ` Falco Hyfing
2017-02-04 11:35 ` Ulrich Ölmann
2017-02-07 12:25 ` Falco Hyfing [this message]
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='CAChPQeCo18tLMJTYE8cJ43=3Nnw=PeOi-iOBH3g-5RDWjfhVcA@mail.gmail.com' \
--to=hyfinglists@gmail.com \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox