From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: looking for .config file for RPXlite board for 2.6 kernel
Date: Wed, 30 Jun 2004 14:21:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0406301416270.511@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.60.0406301326160.10682@localhost.localdomain>
On Wed, 30 Jun 2004, Robert P. J. Day wrote:
> and i've selected:
>
> [*] CPM2 SCC/SMC serial port support
> [ ] Support for console on CPM2 SCC/SMC serial port (NEW)
> [*] Support for SCC1 serial port
> [ ] Support for SCC2 serial port (NEW)
> [ ] Support for SCC3 serial port (NEW)
> [ ] Support for SCC4 serial port (NEW)
> [*] Support for SMC1 serial port
> [ ] Support for SMC2 serial port (NEW)
as i just emailed tom on the side, duh, i took his previous note
stupidly literally, and selected *only* the options he listed. i
figured out pretty quickly to also select the "Support for console on
CPM2 ..." and, lo and behold, i have kernel boot output on my rpxlite
board. whew.
so now i get as far as:
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 72k init
Warning: unable to open an initial console.
Kernel panic: Attempted to kill init!
i suspect this is also some silly misconfiguration. off to track it
down.
rday
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-30 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 15:12 looking for .config file for RPXlite board for 2.6 kernel Robert P. J. Day
2004-06-30 17:14 ` Tom Rini
2004-06-30 17:35 ` Robert P. J. Day
2004-06-30 18:21 ` Robert P. J. Day [this message]
2004-06-30 19:42 ` Robert P. J. Day
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.0406301416270.511@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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