From: Clemens Koller <clemens.koller@anagramm.de>
To: Mohammad Sadegh Sadri <mamsadegh@hotmail.com>
Cc: Linux PPC Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Re: ML403 2.6 kernel, root file system on NFS, stops after freeing unused kernel memory
Date: Sun, 27 May 2007 19:34:05 +0200 [thread overview]
Message-ID: <4659C10D.7070107@anagramm.de> (raw)
In-Reply-To: <BAY115-W15A8C3F50BF6AA5251BAB9B22A0@phx.gbl>
Hi, Mohammed!
Mohammad Sadegh Sadri schrieb:
> ok! problem solved
> problem was kernel command line
> mine was:
>
> CONFIG_CMDLINE="console=ttyS0,9600 console=tty0 root=/dev/nfs rw nfsroot=10.10.10.10:/home/sadri/hdl/eldk_rootfs/ppc_4xx ip=dhcp"
>
> by default 2.6.21 CMDLINE contains two console parameters,
> the correct one should be
>
> CONFIG_CMDLINE="console=ttyS0,9600 root=/dev/nfs rw nfsroot=10.10.10.10:/home/sadri/hdl/eldk_rootfs/ppc_4xx ip=dhcp"
>
> well , rootfs comes up until login prompt,
> I enter root as the password but it gives "incorrect login" message/
I have had the same symptoms.
Some device node was missing. I guess it was something like:
crw--w--w- 1 root tty 5, 1 May 1 09:30 console
crw-rw-rw- 1 root tty 5, 0 May 27 10:14 tty
Also check
-----8<-----
#
# /etc/securetty: defines which devices root can log in on
#
console
ttyS0
tty1
tty2
tty3
tty4
tty5
tty6
# End of file
-----8<-----
Greets,
Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany
http://www.anagramm-technology.com
Phone: +49-89-741518-50
Fax: +49-89-741518-19
next prev parent reply other threads:[~2007-05-27 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 13:46 ML403 2.6 kernel, root file system on NFS, stops after freeing unused kernel memory Mohammad Sadegh Sadri
2007-05-27 17:34 ` Clemens Koller [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-26 10:05 Mohammad Sadegh Sadri
2007-05-23 16:06 Mohammad Sadegh Sadri
2007-05-23 16:58 ` Grant Likely
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=4659C10D.7070107@anagramm.de \
--to=clemens.koller@anagramm.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mamsadegh@hotmail.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;
as well as URLs for NNTP newsgroup(s).