Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Erik Mouw <mouw@nl.linux.org>
To: Rajat Jain <rajat.noida.india@gmail.com>
Cc: kernelnewbies <kernelnewbies@nl.linux.org>,
	newbie <linux-newbie@vger.kernel.org>,
	linux-mips@linux-mips.org
Subject: Re: not getting command prompt at the console
Date: Thu, 22 Feb 2007 11:25:40 +0100	[thread overview]
Message-ID: <20070222102540.GB31252@gateway.home> (raw)
In-Reply-To: <b115cb5f0702220149wfbfc051qc8d0106b9e4ed98d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

On Thu, Feb 22, 2007 at 03:19:10PM +0530, Rajat Jain wrote:
> Hi All,
> 
> I just finished porting linux kernel 2.6.15 to a MIPS based board. The
> board now boots up beautifully ... and here is the console log:

[...]

> Next, I expected to see a command prompt which never comes. At this
> point if I debug, I find the processor executing the idle process.
> 
> I am successfully hable to telnet to the board and fire whatever
> commands I want though. How do I bring the prompt to the serial
> console?

Run a getty on the serial device (I suppose you're using a serial
port).

> My root FS seems OK since the same root FS is working for the same
> board for an ancient kernel (2.4.20)

Could be that the serial driver changed or that you forgot to compile a
driver for the serial device.


Erik

-- 
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-02-22 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22  9:49 not getting command prompt at the console Rajat Jain
2007-02-22 10:25 ` Erik Mouw [this message]
2007-02-22 10:50   ` Raseel Bhagat
2007-02-22 11:11     ` Erik Mouw
2007-02-22 11:25       ` Raseel Bhagat

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=20070222102540.GB31252@gateway.home \
    --to=mouw@nl.linux.org \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=rajat.noida.india@gmail.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