linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Ann <ktdann@gmail.com>
To: Ricardo Scop <scop@digitel.com.br>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Serial console
Date: Sat, 30 Jul 2005 10:34:23 +0900	[thread overview]
Message-ID: <9b7ca657050729183410394f8d@mail.gmail.com> (raw)
In-Reply-To: <200507292227.45626.scop@digitel.com.br>

Looks like I have /dev/console
0 crw-------  1 root root 5, 1 Sep 26  2002 console
0 crw-rw-rw-  1 root root 4, 64 Jun 17  2004 ttyS0

I havent yet figured out how I should go about seeing if init is
correctly accessing it tho. Let me take a look at busybox init part.
BTW, any more reasons why this problem might exist ?



On 7/30/05, Ricardo Scop <scop@digitel.com.br> wrote:
> Hi Daniel,
>=20
> On Friday 29 July 2005 22:06, Daniel Ann wrote:
> > Hi folks,
> >
> > Just wondering if anyone could lend a hand with this problem I have
> > with serial console. I'm trying to boot up my board (very similar to
> > sandpoint using MPC8245) with kernel 2.6.12.3, and most of it is
> > working but console will display up to,
> > [snip]
> > RAMDISK: Compressed image found at block 0
> > VFS: Mounted root (ext2 filesystem) readonly.
> > Freeing unused kernel memory: 112k init
> >
> > I've done series of printk in sys_execve() to see if /sbin/init is
> > working, and found out it went thru the whole rcS file okay. Mind you,
> > printk is successfully displaying the output on the console while I'm
> > still not getting anything from the user processes.
> >
> > Having all the kernel boot up log on console means that I've done some
> > part right. But why am I not getting anything from the user processes
> > on the console screen ?
> >
> Please verify that you have a /dev/console in your rootfs, and that it's =
being
> correctly acessed by the init process.
>=20
> HTH,
>=20
> --
> Ricardo Scop.
>=20
>        \|/
>    ___ -*-
>   (@ @)/|\
>  /  V  \|  R SCOP Consult.
>  /(     )\  Linux-based communications
> --^^---^^+------------------------------
> rscop@matrix.com.br
> +55 51 999-36-777
> Porto Alegre, RS - BRazil
>=20
>=20


--=20
Daniel

  reply	other threads:[~2005-07-30  1:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-30  1:06 Serial console Daniel Ann
2005-07-30  1:19 ` Josh Boyer
2005-07-30  1:36   ` Daniel Ann
2005-07-30  5:46     ` Daniel Ann
2005-07-30  1:27 ` Ricardo Scop
2005-07-30  1:34   ` Daniel Ann [this message]
2005-07-30 10:37 ` Anton Wöllert
2005-08-01  1:27   ` Daniel Ann
2005-08-02  3:38     ` JohnsonCheng
2005-08-02 13:39       ` Kumar Gala
2005-08-03  0:16         ` Daniel Ann
  -- strict thread matches above, loose matches on Subject: below --
2005-10-05  2:36 serial console KokHow Teh
2005-10-05 12:23 ` Vitaly Bordug
2005-10-05  2:32 KokHow Teh
2005-10-04  6:54 KokHow Teh
2005-10-04 15:11 ` David Jander
2005-10-04 15:16   ` Vitaly Bordug
2005-10-05  9:16     ` David Jander
2003-03-04 14:53 Serial Console Aman
2003-03-04 15:40 ` Mark Hatle
2003-03-04 17:06   ` Ibon Gotxi Garcia
2003-03-04 19:09     ` Dave Wolfe
2003-01-16 21:06 Aman

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=9b7ca657050729183410394f8d@mail.gmail.com \
    --to=ktdann@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=scop@digitel.com.br \
    /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).