Re: net install downloads bootloader program then complains about RARP request?

On 11/03/2012 09:07 PM, Christian Weisgerber wrote:
> Kaya Saman <[email protected]> wrote:
>
>> {1} ok boot net bsd.mp
>> Boot device: /pci@1f,700000/network@2  File and args: bsd.mp
>> 100 Mbps full duplex  Link up
>> Requesting Internet Address for 0:3:ba:9c:53:55
>> Requesting Internet Address for 0:3:ba:9c:53:55
>> Requesting Internet Address for 0:3:ba:9c:53:55
>> Requesting Internet Address for 0:3:ba:9c:53:55
>> Requesting Internet Address for 0:3:ba:9c:53:55
>> Requesting Internet Address for 0:3:ba:9c:53:55
>> Requesting Internet Address for 0:3:ba:9c:53:55
>>   >> OpenBSD BOOT 1.4
>> 100 Mbps full duplex  Link up
>> No response for RARP request
> Something odd is going on there.
>
> The firmware requests the IP address by RARP.  This eventually
> succeeds, but why does it take so many tries?  Later the bootstrap
> tries to request the IP address by RARP again, but it doesn't receive
> a reply.  Maybe it just doesn't retry as often as the firmware.
>
> It looks like RARP requests aren't answered reliably on your network.
>
It was a rarp inconsistency which I fixed as the /etc/hosts file had the 
servername and fqdn in it.

Now rarp works but I get some kind of strange error after:

Rebooting with command: boot net bsd.mp
Boot device: /pci@1f,700000/network@2  File and args: bsd.mp
100 Mbps full duplex  Link up
Requesting Internet Address for 0:3:ba:9c:53:55
Requesting Internet Address for 0:3:ba:9c:53:55
Requesting Internet Address for 0:3:ba:9c:53:55
Requesting Internet Address for 0:3:ba:9c:53:55
Requesting Internet Address for 0:3:ba:9c:53:55
Requesting Internet Address for 0:3:ba:9c:53:55
Requesting Internet Address for 0:3:ba:9c:53:55
ERROR: Last Trap: Fast Data Access MMU Miss

I ran bootparamd with the 'debug' option and it seems that information 
isn't even getting to it. The error states that the boot system is 
confused denoting a configuration error - according to a google search.

However I have no idea as both FreeBSD and Debian systems are giving me 
this when used as servers. Perhaps I should just build the jumpstart box 
using vbox and openbsd??

I mean the network itself is a Cisco 2950 switch using a /24 subnet with 
no extra ACL's or anything blocking in the way. I could try putting 
things onto a separate vlan and seeing what happens there?

Regards,


Kaya