From: Daniel Ann <ktdann@gmail.com>
To: Josh Boyer <jwboyer@jdub.homelinux.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Serial console
Date: Sat, 30 Jul 2005 10:36:44 +0900 [thread overview]
Message-ID: <9b7ca6570507291836ac62600@mail.gmail.com> (raw)
In-Reply-To: <1122686376.4755.2.camel@yoda.jdub.homelinux.org>
I too have /dev/null
0 crw-rw-rw- 1 root root 1, 3 Aug 31 2001 null
However, Im not using initrd. null, and console devices are in my RAMDISK t=
ho.
On 7/30/05, Josh Boyer <jwboyer@jdub.homelinux.org> wrote:
> On Sat, 2005-07-30 at 10:06 +0900, 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 ?
> >
> > Is there anything I need to do on the kernel config ?
>=20
> Do you have a /dev/console device node in your initrd? If not, that is
> one of the reasons you could be seeing that problem. Make
> sure /dev/null is there too.
>=20
> josh
>=20
>=20
--=20
Daniel
next prev parent reply other threads:[~2005-07-30 1:36 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 [this message]
2005-07-30 5:46 ` Daniel Ann
2005-07-30 1:27 ` Ricardo Scop
2005-07-30 1:34 ` Daniel Ann
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=9b7ca6570507291836ac62600@mail.gmail.com \
--to=ktdann@gmail.com \
--cc=jwboyer@jdub.homelinux.org \
--cc=linuxppc-embedded@ozlabs.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).