From: "Erik Aderstedt" <erik@ic.chalmers.se>
To: "Joe Berens" <jberens@sgi.com>, <linux-mips@oss.sgi.com>
Subject: Re: Installing linux on Indy
Date: Sat, 28 Oct 2000 10:46:00 +0200 [thread overview]
Message-ID: <007801c040bb$7fc5def0$a3291081@mc2.chalmers.se> (raw)
In-Reply-To: Pine.SGI.4.10.10010271233390.241075-100000@jberens.americas.sgi.com
Hi,
The portmapper isn't running on your system. I'm not an expert,
I just know that I got a lot of RPC-related errors due to
portmap not running.
If you are booting from a RedHat system please note that
due to some misconfiguration (at least in 6.1) portmap will
not be running after you've booted the system , even though
you may have installed it.
Finally, make sure that nfsd and mountd are both running on
your host.
/Erik
erik@ic.chalmers.se
----- Original Message -----
From: Joe Berens <jberens@sgi.com>
To: <linux-mips@oss.sgi.com>
Sent: Friday, October 27, 2000 7:46 PM
Subject: Installing linux on Indy
> Hello,
>
> 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
>
>
> Then it seems to hang for ever.
> Any help is greatly appreciated.
>
> Thank you,
>
> Joe
> ___________________________________
>
> Joe Berens
> SGI Customer Support Center
> Operating Systems Group
> Phone: 800-800-4744, Direct: 651-683-3254
> Email: jberens@sgi.com
>
> ___________________________________
>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "Erik Aderstedt" <erik@ic.chalmers.se>
To: Joe Berens <jberens@sgi.com>, linux-mips@oss.sgi.com
Subject: Re: Installing linux on Indy
Date: Sat, 28 Oct 2000 10:46:00 +0200 [thread overview]
Message-ID: <007801c040bb$7fc5def0$a3291081@mc2.chalmers.se> (raw)
Message-ID: <20001028084600.vrjP6aGwZgCPlmb__VMPjMih5ot8RPKoC4bohdCHNVc@z> (raw)
In-Reply-To: Pine.SGI.4.10.10010271233390.241075-100000@jberens.americas.sgi.com
Hi,
The portmapper isn't running on your system. I'm not an expert,
I just know that I got a lot of RPC-related errors due to
portmap not running.
If you are booting from a RedHat system please note that
due to some misconfiguration (at least in 6.1) portmap will
not be running after you've booted the system , even though
you may have installed it.
Finally, make sure that nfsd and mountd are both running on
your host.
/Erik
erik@ic.chalmers.se
----- Original Message -----
From: Joe Berens <jberens@sgi.com>
To: <linux-mips@oss.sgi.com>
Sent: Friday, October 27, 2000 7:46 PM
Subject: Installing linux on Indy
> Hello,
>
> 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
>
>
> Then it seems to hang for ever.
> Any help is greatly appreciated.
>
> Thank you,
>
> Joe
> ___________________________________
>
> Joe Berens
> SGI Customer Support Center
> Operating Systems Group
> Phone: 800-800-4744, Direct: 651-683-3254
> Email: jberens@sgi.com
>
> ___________________________________
>
>
>
next prev parent reply other threads:[~2000-10-28 8:44 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
2000-10-28 8:46 ` Erik Aderstedt [this message]
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='007801c040bb$7fc5def0$a3291081@mc2.chalmers.se' \
--to=erik@ic.chalmers.se \
--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.