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 20:00:35 +0200	[thread overview]
Message-ID: <4C34C0C3.4000500@gmx.net> (raw)
In-Reply-To: <87pqyz6dpa.fsf@macbook.be.48ers.dk>

Am 07.07.2010 07:52, schrieb Peter Korsgaard:
>>>>>> "Ossy" == Ossy<ossy1980@gmx.net>  writes:
>
>   Ossy>  Hi buildroot mailinglist,
>   Ossy>  After successfully compiling a whole rootfs and mounting it via loop
>   Ossy>  on some nfs export I started my arm ebedded device and ran into tho
>   Ossy>  following error after booting the image via tftp.
>
>   Ossy>  "init: I won't write compressed data to a terminal."
>
> What .config are you using? That string doesn't exist in the busybox
> init (or anywhere in busybox).

I'm using the configuration attached (you may need to ignore my custom 
settings for the sheevaplugbased DockStar).

I mount the generated rootfs with
mount -o loop,ro br_dist/dev/rootfs.ext2 /exports/rootfs/rfs1
and export it via nfs. The Kernel supports rootfs over nfs and was able 
to mount the filesystem via nfs. After that I get the above mentioned error.
As Mitch already mentioned, this error comes from bzip2 (or maybe gzip). 
So I guess there is some ext2 inline compression, which is not 
compatibel with the serial console?
I need to add, that I connect passing console=ttyS0,115200 to the kernel.

The cat of /exports/rootfs/rfs1/etc/inittab looks good to me:
debian-virtual:/exports/rootfs/rfs1# cat etc/inittab
# /etc/inittab
[...]
#

# Startup the system
null::sysinit:/bin/mount -o remount,rw /
null::sysinit:/bin/mount -t proc proc /proc
null::sysinit:/bin/mkdir -p /dev/pts
null::sysinit:/bin/mount -a
null::sysinit:/bin/hostname -F /etc/hostname
# now run any rc scripts
::sysinit:/etc/init.d/rcS

# Set up a couple of getty's
tty1::respawn:/sbin/getty 38400 tty1
tty2::respawn:/sbin/getty 38400 tty2

# Put a getty on the serial port
ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL

# Logging junk
null::sysinit:/bin/touch /var/log/messages
null::respawn:/sbin/syslogd -n -m 0
null::respawn:/sbin/klogd -n
tty3::respawn:/usr/bin/tail -f /var/log/messages

# Stuff to do for the 3-finger salute
::ctrlaltdel:/sbin/reboot

# Stuff to do before rebooting
null::shutdown:/usr/bin/killall klogd
null::shutdown:/usr/bin/killall syslogd
null::shutdown:/bin/umount -a -r
null::shutdown:/sbin/swapoff -a

Maybe it would work, if I do not watch the bootingprocess on the serial 
console, but I won't be able to verify if the system comes up without 
serialconsole output.

Regards for now,
Marcus
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: buildroot-config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100707/fc6b6b79/attachment-0002.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: uClibc-config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100707/fc6b6b79/attachment-0003.ksh>

  parent reply	other threads:[~2010-07-07 18:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 22:16 [Buildroot] init: I won't write compressed data to a terminal Ossy
2010-07-07  0:35 ` 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 [this message]
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=4C34C0C3.4000500@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.