All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Joe Berens <jberens@sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Installing linux on Indy
Date: Sat, 28 Oct 2000 05:13:26 +0200	[thread overview]
Message-ID: <20001028051326.B5764@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.SGI.4.10.10010271233390.241075-100000@jberens.americas.sgi.com>; from jberens@sgi.com on Fri, Oct 27, 2000 at 12:46:13PM -0500

On Fri, Oct 27, 2000 at 12:46:13PM -0500, Joe Berens wrote:

> I have followed the installation instructions and I think every thing is
> set up right.  When I do "boot -f bootp()<ipaddr of
> server>:/<hardhatdir>/vmlinux", the kernel seems to start booting and
> hangs after:
> 
> Partition check: sda1 sda2 sda3 sda4
> Looking up port of RPC 100003/2 on <ipaddr of server>
> RPC: sendmsg returned error 128
> RPC: sendmsg returned error 128
> RPC: sendmsg returned error 128
> RPC: sendmsg returned error 128
> portmap: server <ip addr of server> not responding, timed out
> Root-Nfs: Unable to get nfsd port number from server, using default
> Looking up port of RPC 100005/1 on <ipaddr of server>
> RPC: sendmsg returned error 128

128 = ENETUNREACH.  Sure your network configuration is correct and both
client and server are on the same subnet?

  Ralf

  reply	other threads:[~2000-10-28  3:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 17:46 Installing linux on Indy Joe Berens
2000-10-28  3:13 ` Ralf Baechle [this message]
2000-10-28  8:46 ` Erik Aderstedt
2000-10-28  8:46   ` Erik Aderstedt
  -- strict thread matches above, loose matches on Subject: below --
1999-01-19 14:11 Installing Linux " Trevor Jennings
1999-01-20 10:08 ` Tom Woelfel
1999-01-20 16:34   ` Eric Kimminau
1999-01-20 17:00   ` Alex deVries
1999-01-20 18:29   ` Dave Olson
1999-01-20 18:43     ` Eric Kimminau
1999-01-22  8:52     ` Tom Woelfel
1999-01-22  8:52       ` Tom Woelfel
1999-01-20 17:24 ` Honza Pazdziora

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=20001028051326.B5764@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=jberens@sgi.com \
    --cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.