Re: [cobalt-users] Raq4 - Kernel 2.4 Upgrade Woes

[Duncan Laurie <duncan@xxxxxxxxxxxx>]

Oops, re-sending my response back to the list so its
preserved for future generations...


Josh Trutwin wrote:
>
> I tried the tcpdump above, and it didn't produce anything, so I tried 
> .14 (the second ethernet port, same story).  So I tried the dhcp
> server's MAC address, and the output of that is attached.  Seems odd
> to me that the tcpdump on the Raq4's MAC wouldn't produce anything.
> I swapped the cable into a different PC just to make sure it wasn't
> that.  If there is no cable attached, it loops on the "Sending BOOTP
> requests" portion so it must be sending something over the wire.
>

Ok, that checks out as well.  The 192.168.0.4 server is sending out
a correct bootp packet with all the right info..

>
> 192.168.0.1 is my gateway, which is a Netgear broadband router, could
> it be interfering?
>

I think it might be.  The messages from the serial console show
that its getting a response from the router as well:

Sending BOOTP requests . OK
IP-Config: Got BOOTP answer from 192.168.0.1
IP-Config: Complete:
      device=eth0, addr=192.168.0.6, mask=255.255.255.0, gw=192.168.0.1,
     host=dhcppc5, domain=, nis-domain=(none),
     bootserver=192.168.0.1, rootserver=192.168.0.1, rootpath=

So its probably getting a response from both the router and the
nfs/dhcp server; either the router's offer gets there first or
its getting higher priority because of its IP address...

>
> I've also attached the output from the serial console.
>
> Are the "Invalid EEPROM checksum" warnings on the ethernet ports
> anything to be concerned about?
>

They are harmless.  (although you may see problems if you use Intel's
e100 driver instead of the becker eepro100)

-duncan