linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brian Waite <waite@skycomputers.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: NFS root woes: No init found
Date: Wed, 4 Dec 2002 16:35:31 -0500	[thread overview]
Message-ID: <200212041635.31861.waite@skycomputers.com> (raw)


Hi,
	I am attempting to boot up a custom PPC board and having problems with the
NFS Root. the board has a single 74xx PPC and Galileo memory controller. What
happens is everything looks good until I attempt to read init from the NFS
root. Then I get the message No init found. I have tried the obvious things
such as changing init for a staticly linked executable, to no avail. I have
enabled NFS debug and it looks like I have mounted the remote fs just fine.
In fact, I can remove /dev/console and watch console_init() throw a warning.
Has anyne seen problems with the Galileo's mii ports or any other boards
booting an NFS root filesystem? I am attaching the end of my log below.
Thanks
Brian


NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
gt64260_eth_open : Assigned IRQ 32 to gt64260_eth0
eth0:  link state:
  GT: 100: Link:FD:nFC
 mii:100: Link:FD:nFC ANnc:Manual
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 192.9.200.220, my address is 192.9.200.246
IP-Config: Complete:
      device=eth0, addr=192.9.200.246, mask=255.255.255.0, gw=255.255.255.255,
     host=seblade2, domain=, nis-domain=(none),
     bootserver=192.9.200.220, rootserver=192.9.200.220, rootpath=/home/ppc
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Root-NFS: Mounting /home/ppc on server 192.9.200.220 as root
Root-NFS:     rsize = 4096, wsize = 4096, timeo = 7, retrans = 3
Root-NFS:     acreg (min,max) = (3,60), acdir (min,max) = (30,60)
Root-NFS:     nfsd port = -1, mountd port = 0, flags = 00000200
Looking up port of RPC 100003/2 on 192.9.200.220
Root-NFS: Portmapper on server returned 2049 as nfsd port
Looking up port of RPC 100005/1 on 192.9.200.220
Root-NFS: mountd port is 32771
NFS:      nfs_mount(c009c8dc:/home/ppc)
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 188k init
Kernel panic: No init found.  Try passing init= option to kernel.
 <0>Rebooting in 180 seconds..

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

             reply	other threads:[~2002-12-04 21:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04 21:35 Brian Waite [this message]
2002-12-04 21:48 ` NFS root woes: No init found Dan Malek
2002-12-04 22:11   ` Brian Waite
2002-12-04 22:20     ` Wolfgang Grandegger
2002-12-04 22:30       ` Brian Waite
2002-12-04 22:47         ` Jerry Van Baren
2002-12-04 23:03           ` Brian Waite
2002-12-04 22:49         ` Roland Dreier
2002-12-04 22:52           ` Brian Waite
2002-12-04 22:27 ` Roland Dreier
2002-12-04 22:36   ` Brian Waite
2002-12-05  8:50     ` Dan Vatca
2002-12-05 15:20       ` Brian Waite
2002-12-05 15:58         ` Allen Curtis
  -- strict thread matches above, loose matches on Subject: below --
2002-12-07  1:36 Pagnotta, Chris
2002-12-07 11:02 ` Wolfgang Denk

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=200212041635.31861.waite@skycomputers.com \
    --to=waite@skycomputers.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).