Subject: Re: bootparam/whoami RPC failed?
To: Jeremy D. Worrells - 4097358 <jworrell@nunic.nu.edu>
From: Matt Thompson <bl514@smt.net>
List: port-sun3
Date: 05/07/1997 17:31:49
--------------02F1637E0279AC435BF69C3F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Jeremy D. Worrells - 4097358 wrote:
> Henry W Miller wrote:
> >
> >
> >
> > On Fri, 23 May 1997, Jeremy D. Worrells - 4097358 wrote:
> >
> > > I finally got my Sun3 to work and am trying to get it to boot
> off my Linux
> > > box so I can install NetBSD. I get the right IP address and gets
> the netboot
> > > alright, but fails on bootparam. The following error message
> appears:
> > >
> > > >> NetBSD netboot [$Revision: 1.5 $]
> > > Using IP addresss xxx.xxx.xxx.xxx = xxxxxxxx
> > > boot: client addr: xxx.xxx.xxx.xxx
> > > bootparamd: 'whoami' call failed
> > > net_open: bootparam/whoami RPC failed
> > > boot: netbsd: Input/output error
> > > boot:
> > >
> > > Arrgh!
> > > I ran callbootd from my Linux box and got all the right info:
> > >
> > > # callbootd <server IP> <client IP>
> > > Whoami returning:
> > > client_name: goofert
> > > domain_name: (none)
> > > router: 127.0.0.1
> >
> > I don't know what callbootd is, but I think you are looking in the
> wrong
> > place. You need to check bootparamd, NOT bootd.
> >
> > do a 'ps -a' and make sure bootparamd is running.
> > make sure that /etc/bootparamd (or similer filename) has the
> needed entries.
> >
> > feel stupid like most of the rest of use when we suddenly realise
> that
> > bootp is a different beast from bootparamd.
> >
>
> callbootd is a test facility for bootparamd. You issue it from the
> server and
> it gives you back any info that bootparamd would return. callbootd
> issues the
> request and bootparamd gives the info. It is the right stuff, as you
> can see
> above.
>
> bootparamd is running. Checked and doublechecked.
>
> /etc/bootparams has the following entry:
>
> goofert root=kumonojo:/usr/export/root
>
> Everything looks kosher. /etc/bootparams is mode 600, owner root,
> group wheel.
> If I change the mode to 644, still nothing.
>
> Any more ideas?
>
> --
> Jeremy Worrells Undergraduate - Computer Science
> jworrell@nunic.nu.edu National University
> jworrell@priacc.com http://nunic.nu.edu/~jworrell
bootparamd is a bitch in Linux, I had a LOT of trouble with it. Run
it with the -d switch to see if it is getting the request. I had the
same problem with a Sun3 and VAX from a Linux bootparamd server , but
FreeBSD's bootparamd works fine .. just keep trying to boot the sun, if
it doesn't work, kill the bootparamd , reload it, and try booting again
.. it should work eventually.
Ttyl
Matt
--------------02F1637E0279AC435BF69C3F
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<HTML><BODY>
Jeremy D. Worrells - 4097358 wrote:
<BLOCKQUOTE TYPE=CITE>Henry W Miller wrote:
<BR><I>></I>
<BR><I>></I>
<BR><I>></I>
<BR><I>> On Fri, 23 May 1997, Jeremy D. Worrells - 4097358 wrote:</I>
<BR><I>></I>
<BR><I>> > I finally got my Sun3 to work and am trying to get it to boot off
my Linux</I>
<BR><I>> > box so I can install NetBSD. I get the right IP address and gets
the netboot</I>
<BR><I>> > alright, but fails on bootparam. The following error message appears:</I>
<BR><I>> ></I>
<BR><I>> > >> NetBSD netboot [$Revision: 1.5 $]</I>
<BR><I>> > Using IP addresss xxx.xxx.xxx.xxx = xxxxxxxx</I>
<BR><I>> > boot: client addr: xxx.xxx.xxx.xxx</I>
<BR><I>> > bootparamd: 'whoami' call failed</I>
<BR><I>> > net_open: bootparam/whoami RPC failed</I>
<BR><I>> > boot: netbsd: Input/output error</I>
<BR><I>> > boot:</I>
<BR><I>> ></I>
<BR><I>> > Arrgh!</I>
<BR><I>> > I ran callbootd from my Linux box and got all the right info:</I>
<BR><I>> ></I>
<BR><I>> > # callbootd <server IP> <client IP></I>
<BR><I>> > Whoami returning:</I>
<BR><I>> > client_name: goofert</I>
<BR><I>> > domain_name: (none)</I>
<BR><I>> > router: 127.0.0.1</I>
<BR><I>></I>
<BR><I>> I don't know what callbootd is, but I think you are looking in the
wrong</I>
<BR><I>> place. You need to check bootparamd, NOT bootd.</I>
<BR><I>></I>
<BR><I>> do a 'ps -a' and make sure bootparamd is running.</I>
<BR><I>> make sure that /etc/bootparamd (or similer filename) has the needed
entries.</I>
<BR><I>></I>
<BR><I>> feel stupid like most of the rest of use when we suddenly realise
that</I>
<BR><I>> bootp is a different beast from bootparamd.</I>
<BR><I>></I>
<BR>
<BR>callbootd is a test facility for bootparamd. You issue it from the server
and
<BR>it gives you back any info that bootparamd would return. callbootd issues
the
<BR>request and bootparamd gives the info. It is the right stuff, as you can
see
<BR>above.
<BR>
<BR>bootparamd is running. Checked and doublechecked.
<BR>
<BR>/etc/bootparams has the following entry:
<BR>
<BR>goofert root=kumonojo:/usr/export/root
<BR>
<BR>Everything looks kosher. /etc/bootparams is mode 600, owner root, group
wheel.
<BR>If I change the mode to 644, still nothing.
<BR>
<BR>Any more ideas?
<BR>
<BR>--
<BR>Jeremy Worrells
Undergraduate - Computer Science
<BR>jworrell@nunic.nu.edu
National University
<BR>jworrell@priacc.com
">http://nunic.nu.edu/~jworrell
</BLOCKQUOTE>
bootparamd is a bitch in Linux, I had a LOT of trouble with it.
Run it with the -d switch to see if it is getting the request. I
had the same problem with a Sun3 and VAX from a Linux bootparamd server
, but FreeBSD's bootparamd works fine .. just keep trying to boot the sun,
if it doesn't work, kill the bootparamd , reload it, and try booting again
.. it should work eventually.
<BR>
<BR>Ttyl
<BR>Matt
<BR>
</BODY>
</HTML>
--------------02F1637E0279AC435BF69C3F--