From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: 2.5 bk tree on 8xx board ... so close
Date: Mon, 28 Jun 2004 17:48:07 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0406281743170.4213@localhost.localdomain> (raw)
after messing with the kernel config of the latest "bk pull", and
building a new kernel and ramdisk, i got:
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 60k init
Configuring localhost networking ...
SIOCSIFADDR: No such device (ignore, i tried to configure eth0)
Mounting /proc filesystem ...
Mounting /tmp filesystem ...
There are no /dev/mtdblock devices here, aborting. (no, not really)
Clearing /var/log/msgs and starting syslogd ...
I found portmap, so I'll start it now ...
I found telnetd, so I'll start it now ...
Bailing for testing purposes.
BusyBox v1.00-pre10 (2004.06.24-
... and hang.
so, from the above, i got
1) localhost networking configured
2) /proc mounted
3) /tmp (tmpfs) mounted
4) syslog, portmap and telnet starting
5) an exit from the startup script since i wanted to keep things
simple
at that point, /etc/inittab has the line:
::respawn:-/bin/sh
/bin/sh being, of course, a link to busybox. i'm not sure what to
make of the partial output, perhaps some problem with the serial or
console port that the shell is trying to use. so i guess it's on to
poking around the console port, see if that's the issue.
getting so close ...
rday
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-06-28 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 21:48 Robert P. J. Day [this message]
2004-06-28 23:31 ` 2.5 bk tree on 8xx board ... so close Tom Rini
2004-06-29 9:53 ` Robert P. J. Day
2004-06-29 15:16 ` Tom Rini
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=Pine.LNX.4.60.0406281743170.4213@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).