All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] init: I won't write compressed data to a terminal.
Date: Wed, 07 Jul 2010 00:16:46 +0200	[thread overview]
Message-ID: <4C33AB4E.9050604@gmx.net> (raw)

Hi buildroot mailinglist,

After successfully compiling a whole rootfs and mounting it via loop on 
some nfs export I started my arm ebedded device and ran into tho 
following error after booting the image via tftp.

"init: I won't write compressed data to a terminal."

The bootargs include a console=ttyS0,115200 and rootfs over nfs options.
I guess there is is an issue with the built in zip/bzip compression.
But why is the init process not able to output to the terminal?
After that error, the kernel panics, so I can't boot into my brand new 
rootfs. (The search function of the mailinglist didn't give a hint...)

Thanks for your help,
Marcus

             reply	other threads:[~2010-07-06 22:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 22:16 Ossy [this message]
2010-07-07  0:35 ` [Buildroot] init: I won't write compressed data to a terminal Mitch Davis
2010-07-07 20:20   ` Ossy
2010-07-07 20:33     ` Peter Korsgaard
2010-07-07 20:41       ` Ossy
2010-07-07 20:49         ` Peter Korsgaard
2010-07-07 21:39           ` Peter Korsgaard
2010-07-09 19:46             ` Ossy
2010-07-11 18:52               ` Peter Korsgaard
2010-07-07 20:45       ` Peter Korsgaard
2010-07-07  5:52 ` Peter Korsgaard
2010-07-07  6:14   ` Mitch Davis
2010-07-07 18:00   ` Ossy
2010-07-07 18:59     ` Peter Korsgaard
2010-07-07 20:14       ` Ossy

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=4C33AB4E.9050604@gmx.net \
    --to=ossy1980@gmx.net \
    --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 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.