linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Mark Hatle <fray@mvista.com>
Cc: Phill Treddenick <Phillip.Treddenick@colorado.edu>,
	"linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problem booting kernel on EP405
Date: Wed, 28 May 2003 09:57:52 +1000	[thread overview]
Message-ID: <20030527235752.GB21036@zax> (raw)
In-Reply-To: <3ED392E0.7060101@mvista.com>


On Tue, May 27, 2003 at 11:31:28AM -0500, Mark Hatle wrote:
>
> Phill Treddenick wrote:
> >Hi,
> >  I am trying to run Monta Vista Linux PE 2.1 on an EP405 with Solaris 2.7
> >  as
> >the host.  When I boot the kernel on the EP405 though, I get a couple of
> >boot
> >error messages.  The kernel continues booting however and gets to a login
> >prompt, if I try to login though it fails.  Can anyone provide me with
> >information about the errors I'm getting.  Specifically, the "modprobe:
> >modprobe: Can't locate module char-major-4" and the "mknod: `/dev/ptmx':
> >Operation not permitted" errors.  I would like to know where I would find
> >the
> >char-major-4 module or why the kernel can't find it.  Here are the boot
> >messages
> >and a failed login attempt. Thanks guys.
>
> You can safely ignore the modprobe message.. it's not an error bug really a
> warning. Now for the other issue.. the mknod error and the unable to
> login.. See
> below:
>
> >IP-Config: Complete:
> >      device=eth0, addr=128.138.189.65, mask=255.255.255.0,
> >      gw=255.255.255.255,
> >     host=sme, domain=, nis-domain=colorado.edu,
> >     bootserver=128.138.189.51, rootserver=128.138.189.51, rootpath=
>
> >VFS: Mounted root (nfs filesystem).
>
> >mknod: `/dev/ptmx': Operation not permitted
>
> >login[82]: unable to change tty `/dev/console' for user `root'
> >
> >Unable to change tty /dev/console: Illegal seek
>
> The above shows that you are NFS rooted.  On your NFS root, it was unable to
> mknod /dev/ptmx.  Either you have a RO NFS export on your slowlaris box, or
> somehow you are exporting a system in which you are unable to create device
> nodes.  /dev/ptmx is required for the multi-user login to work.  It
> controls the
> PTYs.
>
> The second error if that it is unable to change the tty for /dev/console to
> root.  This again indicates that there is a problem with device nodes over
> your
> NFS mount.  Make sure the NFS mount is RW.

And make sure it doesn't have root_squash enabled.

--
David Gibson			| For every complex problem there is a
david@gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-05-27 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 16:23 Problem booting kernel on EP405 Phill Treddenick
2003-05-27 16:31 ` Mark Hatle
2003-05-27 23:57   ` David Gibson [this message]

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=20030527235752.GB21036@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=Phillip.Treddenick@colorado.edu \
    --cc=fray@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).