From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Robert Zach" <rza1@so-logic.co.at>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: no login prompt with ml403 + uartlite-->major numbers?
Date: Wed, 28 Jun 2006 09:06:41 -0600 [thread overview]
Message-ID: <528646bc0606280806y2ec566b1rd0d5c07c9fcc0aaf@mail.gmail.com> (raw)
In-Reply-To: <200606281214.k5SCEQEf039728@webmail.so-logic.net>
On 6/28/06, Robert Zach <rza1@so-logic.co.at> wrote:
> Hello!
>
> I use the "Standart" ml403 Design with the uartlite instead of the
> uart16550...
>
> my kernel parameters are:
> "console=ttl0 ip=off root=/dev/xsysace/disc0/part3 rw"
>
> It boots correctly, but i got no login prompt!!
> getty is started with init.
> my inittab looks like:
> ...
> ::respawn:/sbin/getty 9600 ttl0
Looks ok. busybox I assume. You might try:
ttl0::respawn:/sbin/getty 9600 ttl0
You could try just launching a shell on the console. Then you can
look around and see what's there:
::respace:/bin/sh
> ...
>
> I use devfs.
Ugh. You should turn off devfs and build a static /dev folder for the
time being. Otherwise you've got no idea if devfs is putting the
right things into /dev. If you *really* want to, you can go back to
devfs later (but I don't recommend it).
> Is the inittab entry correct?
I think so
> Which device is the uartlite in devfs?
I don't know; read the source. Look for where it registers with devfs
to get the expected name. Does the uartlite driver you're using even
support devfs?
>
> Which major numbers uses the uartlite?
I don't know; it should be easy to find in the driver source
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2006-06-28 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 12:14 no login prompt with ml403 + uartlite-->major numbers? Robert Zach
2006-06-28 15:06 ` Grant Likely [this message]
[not found] <mailman.1193.1151524639.11183.linuxppc-embedded@ozlabs.org>
2006-06-28 20:14 ` T Ziomek
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=528646bc0606280806y2ec566b1rd0d5c07c9fcc0aaf@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rza1@so-logic.co.at \
/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).