headers
Chris Ross | 7 May 2010 20:45

Netbooting a sparc64


 [- apologies for this near-duplicate of an earlier current-users post -]

 I have previously booted sparc64 machines from the same i386 I'm trying to use now, although it has been
quite a while.  I think I must be doing something wrong, however.  I backed the i386 back down to netbsd-5
(5.1_RC1) and am having the same problems, so I now don't worry that it's a -current bug.

  I'm trying to netboot a Sun Netra X1.  rarpd is giving my host an address, and tftp is retrieving the
ofwboot.net file from the i386 host.  The next step, however, is a sunrpc (udp/111) request so that it can
NFS mount root, and the i386 host seems never to respond.  I can see the incoming packets on the wire, but no
responses going out.  rpcinfo on the i386 host shows many things, including nfs and mountd.

  Anyone have any idea what step I missed?

  Thanks...

                  - Chris
Permalink | Reply | 21 comments |
headers
rjs | 7 May 2010 20:59
Picon
Picon

Re: Netbooting a sparc64


Chris Ross wrote:
> [- apologies for this near-duplicate of an earlier current-users post -]
>
> I have previously booted sparc64 machines from the same i386 I'm
>trying to use now, although it has been quite a while.  I think I must
>be doing something wrong, however.  I backed the i386 back down to
>netbsd-5 (5.1_RC1) and am having the same problems, so I now don't
>worry that it's a -current bug.
>
>  I'm trying to netboot a Sun Netra X1.  rarpd is giving my host an
>address, and tftp is retrieving the ofwboot.net file from the i386
>host.  The next step, however, is a sunrpc (udp/111) request so that
>it can NFS mount root, and the i386 host seems never to respond.  I
>can see the incoming packets on the wire, but no responses going out.
>rpcinfo on the i386 host shows many things, including nfs and mountd.
>
>  Anyone have any idea what step I missed?

You haven't described how the sparc64 system is told where to look for the
NFS root. Are you using DHCP or rpc.bootparamd ?

Checking /etc/exports is probably a good idea too. You may need to add
the -alldirs and -maproot=root options.

Robert Swindells
Permalink | Reply | 20 comments |
headers
Chris Ross | 7 May 2010 21:05

Re: Netbooting a sparc64


On May 7, 2010, at 2:59 PM, <rjs <at> fdy2.demon.co.uk> wrote:
> You haven't described how the sparc64 system is told where to look for the
> NFS root. Are you using DHCP or rpc.bootparamd ?

  You're right.  Apologies for various lacks of information.

  I'm using rarp, tftp, and dhcp.  Or at least, that's what I mean to be doing.  rarp is working, and tftp seems to
be working.  I'm not 100% sure how the sparc knows who to contact for the NFS root, though.  That's likely my
problem.  How is that normally done?

  This host doesn't have a bootparams file, and as I've done this sort of booting from this server before, I
assume that I wasn't using rpc.bootparamd.  My DHCP server has the following block in it, which I believe is
what I was using to specify this:

# A diskless boot host
group {
  # server to NFS from, and path to mount as root...
  next-server 206.138.151.36;
  host diskless-sparc64 {
#    hardware ethernet 08:00:20:a1:8b:f8;
    hardware ethernet 00:03:ba:05:e4:7a;
    fixed-address 206.138.151.49;
    option root-path "/export/sparc64/nfsroot";
  }
}

  The sparc boot, which I also should've included in my earlier email, shows:

Executing last command: boot net
(Continue reading)

Permalink | Reply | 19 comments |
headers
Martin Husemann | 7 May 2010 21:17
Picon

Re: Netbooting a sparc64

If your PROM is new enough, try:

  boot net:dhcp

This is always a lot easier to get working than the legacy stuff.

Martin
Permalink | Reply | 18 comments |
headers
Chris Ross | 7 May 2010 21:31

Re: Netbooting a sparc64


On May 7, 2010, at 3:17 PM, Martin Husemann wrote:
> If your PROM is new enough, try:
> 
>  boot net:dhcp
> 
> This is always a lot easier to get working than the legacy stuff.

  I had tried that at one point, but it seemed to work less well.  Looking into it a little more, I think I see a
problem that I've now fixed, and I can get as far with boot net:dhcp.  (I had a duplicate definition in my
dhcpd.conf for the same hardware address.)  tftp loads a different file name this way, but that was easy
enough to find/fix.  And should tftp still be loading the ofwboot.net?

  So, now that I fixed that dhcpd.conf error, I am still seeing the following on my sparc:

Executing last command: boot net:dhcp                                 
Boot device: /pci <at> 1f,0/ethernet <at> c:dhcp  File and args: 
Timeout waiting for BOOTP/DHCP reply. Retrying ... 
Timeout waiting for BOOTP/DHCP reply. Retrying ... 
Timeout waiting for BOOTP/DHCP reply. Retrying ... 
>> NetBSD/sparc64 OpenFirmware Boot, Revision 1.13
bootp: no reply
Using BOOTPARAMS protocol: ip address: 206.138.151.49bootparamd: 'whoami' call failed
open netbsd: Unknown error: code 60
Failed to load 'netbsd'.
: trying netbsd.gz...
bootp: no reply
Using BOOTP protocol: ip address: 206.138.151.49, netmask: 255.255.255.0
root addr=0.0.0.0 path=
Fast Data Access MMU Miss
(Continue reading)

Permalink | Reply | 17 comments |
headers
Martin Husemann | 7 May 2010 21:35
Picon

Re: Netbooting a sparc64

On Fri, May 07, 2010 at 03:31:02PM -0400, Chris Ross wrote:
> >> NetBSD/sparc64 OpenFirmware Boot, Revision 1.13
> bootp: no reply

This should not happen - your dhcp server was supposed to answer here.
Does it log anything interesting?

Martin
Permalink | Reply | 16 comments |
headers
Chris Ross | 7 May 2010 21:46

Re: Netbooting a sparc64


On May 7, 2010, at 3:35 PM, Martin Husemann wrote:
> On Fri, May 07, 2010 at 03:31:02PM -0400, Chris Ross wrote:
>>>> NetBSD/sparc64 OpenFirmware Boot, Revision 1.13
>> bootp: no reply
> 
> This should not happen - your dhcp server was supposed to answer here.
> Does it log anything interesting?

  No.  And for that matter, I don't see any packets coming into my DHCP server machine.  Not after the
Request/ACK pair that comes from the bootprom, immediately before the tftp of ofwboot.net.

  Might this be another case of "not waiting long enough for the ethernet to become sync'd up"?  Does ofwboot do
anything that would cause the ethernet hardware to reset or renegotiate it's link?

                  - Chris
Permalink | Reply | 4 comments |
headers
Martin Husemann | 7 May 2010 21:49
Picon

Re: Netbooting a sparc64

On Fri, May 07, 2010 at 03:46:45PM -0400, Chris Ross wrote:
>   Might this be another case of "not waiting long enough for the ethernet to become sync'd up"?  Does ofwboot
do anything that would cause the ethernet hardware to reset or renegotiate it's link?

yeah - and you might try a ofwboot from -current, it retries this part
a few times.

Martin
Permalink | Reply | 3 comments |
headers
Chris Ross | 7 May 2010 22:10

Re: Netbooting a sparc64


On May 7, 2010, at 3:49 PM, Martin Husemann wrote:
> On Fri, May 07, 2010 at 03:46:45PM -0400, Chris Ross wrote:
>>  Might this be another case of "not waiting long enough for the ethernet to become sync'd up"?  Does ofwboot
do anything that would cause the ethernet hardware to reset or renegotiate it's link?
> 
> yeah - and you might try a ofwboot from -current, it retries this part
> a few times.

  Ahh, thanks.  That did it.  Using an ofwboot 1.15 worked around this problem:

Executing last command: boot net:dhcp                                 
Boot device: /pci <at> 1f,0/ethernet <at> c:dhcp  File and args: 
Timeout waiting for BOOTP/DHCP reply. Retrying ... 
Timeout waiting for BOOTP/DHCP reply. Retrying ... 
Timeout waiting for BOOTP/DHCP reply. Retrying ... 
>> NetBSD/sparc64 OpenFirmware Boot, Revision 1.15
bootp: no reply
Using BOOTP protocol:
 ip addr=206.138.151.49
  netmask=255.255.255.0
  gateway=206.138.151.1
  root addr=206.138.151.36
  path=/export/sparc64/nfsroot
=0x859718
Loading netbsd: 7115192+366296+442296 [538536+348822]=0x99e7d0
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
(Continue reading)

Permalink | Reply | 0 comments |
headers
Chris Ross | 7 May 2010 22:31

port/sparc64 known working on Netra X1?


  I have a Netra X1 that I'm trying to get NetBSD onto.  I'm netbooting, which may be some of the problem here, but
I don't suspect that right off of the bat.

  The kernel gets loaded from the NFS root, and begins to run.  Then, while/after attaching psycho0, it seems
to just hang up pretty hard.  A break doesn't have any effect.  I'm using the serial console, so it's possible
also that the kernel is messing that connection up somehow, but I don't see that happen on other sparc64's, so.

  Does anyone have a Netra X1 (of the same class as the one below) running NetBSD?  Just to verify that it
*should* be working...

  Thanks.  kernel messages, that there are, are included.

                              - Chris

Loading netbsd: 7927744+359936+363984 [542856+355343]=0x98c768
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 5.99.26 (GENERIC.UP) #0: Sat Apr 10 15:28:44 EDT 2010
	cross <at> host.distal.com:/obj/NetBSD/src/sys/arch/sparc64/compile/GENERIC.UP
total memory = 640 MB
avail memory = 614 MB
mainbus0 (root): SUNW,UltraAX-i2 (Sun Netra X1): hostid 8305e47a
cpu0 at mainbus0: SUNW,UltraSPARC-IIe  <at>  500 MHz, UPA id 0
cpu0: 16K instruction (32 b/l), 16K data (32 b/l), 256K external (64 b/l)
psycho0 at mainbus0
(Continue reading)

Permalink | Reply | 44 comments |

Gmane