From: Pete Popov <ppopov@mvista.com>
To: Wayne Gowcher <wgowcher@yahoo.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: serial console, have linefeed but no command prompt
Date: Wed, 25 Apr 2001 10:25:26 -0700 [thread overview]
Message-ID: <3AE70886.AEEC48D3@mvista.com> (raw)
In-Reply-To: 20010425150258.11719.qmail@web11901.mail.yahoo.com
Wayne Gowcher wrote:
>
> I am trying to bring up a mips based board using the
> serial console outputing to a serial terminal.
> Everything seems to boot OK, I see the various printk
> messages of the kernel booting right up until the
> execve calls in init/main.c init().
> After this point the board stops printing to the
> serial console, but if I hit return at the terminals
> keyboard, the terminal's cursor moves down one line.
> But I still have no command prompt.
>
> Up until now I have been successfully booting the
> board with the 2.2.13 kernel using nfs as the file
> system. The problem kernel is my attempt at porting
> 2.4.0 test 9 to the same board, using the same nfs.
>
> I suspect I have a setup problem with the serial
> configuration in the kernel ( not the filesystem since
> 2.2.13 is OK ), maybe it's not selecting the right
> terminal or not directing output correctly ? But I am
> not sure how to fix it and would appreciate any help,
> references to texts that would help me.
I would suggest you first start by loading ash.static or some other
statically compiled shell (boot with "init=/bin/bash or
init=/bin/ash.static, depending on what shell you have) and then go from
there. If even that doesn't work, try cross compiling a static hello
world and load that as the init (something like "init=/bin/hello").
What does you /etc/inittab look like?
Pete
next prev parent reply other threads:[~2001-04-25 17:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 7:28 usermode gdb / remote gdb Michael Shmulevich
2001-04-25 9:36 ` Ian Soanes
2001-04-25 10:31 ` Michael Shmulevich
2001-04-25 11:13 ` Ian Soanes
2001-04-25 17:39 ` Jun Sun
2001-04-26 4:04 ` Ralf Baechle
2001-05-02 14:12 ` Maciej W. Rozycki
2001-04-26 18:05 ` Michael Shmulevich
2001-04-26 17:03 ` Jun Sun
2001-04-26 18:05 ` Michael Shmulevich
2001-04-29 9:47 ` Michael Shmulevich
2001-04-30 17:40 ` Jun Sun
2001-05-07 20:40 ` Wayne Gowcher
2001-05-07 20:40 ` Wayne Gowcher
2001-04-25 15:02 ` serial console, have linefeed but no command prompt Wayne Gowcher
2001-04-25 17:25 ` Pete Popov [this message]
2001-04-25 18:38 ` Wayne Gowcher
2001-04-25 19:50 ` Scott A McConnell
2001-04-27 15:40 ` load_elf_binary problems ? Wayne Gowcher
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=3AE70886.AEEC48D3@mvista.com \
--to=ppopov@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=wgowcher@yahoo.com \
/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