3c905C: invalid checksum

[dana@leopard.cybersource.com.sg]

Hmm... This is the same error (warning?) message I get as well.

But, I don't think you bought a 905B, you bought a 905C.

Anyway, even though I get this message each time I boot up, the server
we install to still work (without any problem), and has been running 14
days non-stop (ya, I bought 2 weeks ago). So I guess we can savely ignore
this error (warning) for now.

Regards
Sei Heng


On Sun, 21 Nov 1999, Ian Schmidt wrote:

> Hi,
> 
> I recently added a new machine to my network, and bought a 3c905C for it (my
> other machines run with 3c905Bs and have been trouble-free under Linux, but
> apparently 905B's aren't made anymore).  The card itself installed and works
> fine, but I get the following Scary Error(tm) every time on bootup:
> 
> 3c59x.c:v0.99H 11/17/98 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> eth0: 3Com 3c905C Tornado at 0xec80,  ***INVALID CHECKSUM 002f***
> 00:50:da:1a:23:60, IRQ 17
>   8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
>   MII transceiver found at address 24, status 782d.
>   Enabling bus-master transmits and whole-frame receives.
> 
> The machine is a dual PPro 200 running Redhat 6.1 with the kernel updated to
> 2.2.14pre7 (SMP is enabled).
> 
> Should I worry about this error?  Is there some way to fix the checksum?
> 
> Thanks,
> -Ian Schmidt
> ischmidt@cfl.rr.com
> 
> 
>