At 11:09 AM -0700 on 5/12/00, ferret@phonewave.net wrote:
>Tried it but it doesn't seem to let me set anything. I'm still reading the
>documentation, though.
>
>Although, link partner reports 0000? Maybe my hub doesn't like this NIC?
I am seeing the same problem with a 3C905c hooked up to a Cisco
100Mbps switch. Using Don's program to force full duplex masked the
problem, but auto-negotiation definitely did not work. As you
mentioned above, the link partner reports no auto-negotiation as far
as this NIC is concerned. This is clearly not the case as all other
devices on that switch negotiate just fine.
Here's another tidbit which may be helpful:
[Kernel 2.2.15 compiled with gcc-2.95.2]
May 11 11:16:47 Ayradyss kernel: 3c59x.c:v0.99H 11/17/98 Donald
Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
May 11 11:16:47 Ayradyss kernel: eth0: 3Com 3c905C Tornado at 0x1000,
***INVALID CHECKSUM 0022*** 00:50:da:59:f9:f3, IRQ 11
May 11 11:16:47 Ayradyss kernel: 8K byte-wide RAM 5:3 Rx:Tx split,
autoselect/Autonegotiate interface.
May 11 11:16:47 Ayradyss kernel: MII transceiver found at address
24, status 782d.
May 11 11:16:47 Ayradyss kernel: Enabling bus-master transmits and
whole-frame receives.
What's up with the checksum? The same driver seems to work fine on my
other Linux machines using 3C905b NICs.
Igor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:21 EST