From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Linux throwing "uncompression error" on rootfs.ext2.gz ?
Date: Tue, 3 Jul 2012 09:31:03 +0200 [thread overview]
Message-ID: <20120703093103.563a1876@skate> (raw)
In-Reply-To: <4FF24364.7010303@powerstandards.com>
Le Mon, 02 Jul 2012 17:57:08 -0700,
Judson Wilson <judson@powerstandards.com> a ?crit :
> Curious if anyone has run into an issue where their ext2.gz image causes
> linux boot to say "uncompression error", like this:
>
> ...
> RAMDISK: gzip image found at block 0
> uncompression error
> VFS: Mounted root (ext2 filesystem) on device 1:0.
> ...
Are you using this file as an initrd, or as the real root filesystem?
Could you share some details about your setup (where do you put the
ext2.gz image, what is your kernel command line, kernel configuration,
etc.).
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-03 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 0:57 [Buildroot] Linux throwing "uncompression error" on rootfs.ext2.gz ? Judson Wilson
2012-07-03 7:31 ` Thomas Petazzoni [this message]
2012-07-03 17:13 ` Judson Wilson
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=20120703093103.563a1876@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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