Quoting Georg Schwarz <georg.schwarz@freenet.de>:

> I'M trying to netboot an O2. I've set up a dhcp server (dhcp3) and a
> tftp server (tftp-hpa-0.45) at 192.168.0.1.
> I've set the O2's netaddr to 192.168.0.15 (which is also returned by
> the dhcp server).
> When I enter bootp(): on the O2's prom, I almost immediately get a
> message that the address 192.168.0.15 has been received from the
> server, but that's it. After a while the O2 seems to give up saying
> "unable to execute bootp():: invalid argument".

I'm not sure if the O2 PROMs have the same bug, but have you looked at:
http://www.netbsd.org/Ports/sgimips/faq.html#prom-tftp-client-failing ?

[snip]

> I also noticed that I could not ping the O2. Is this normal, doesn't it
> react to ICMP echo requests?

No, it don't believe that the PROM is sufficiently featured to do this.

Steve