Bill Davidsen wrote:
> In spite of modules.conf the system boots with the NIC in half duplex. I
> verified this with the mii-tool, I can set it full with mii-tool and it
> works right (copied a CD image 650MB), and the blade in the switch has
> been set either full or auto without gain. Yes, I tried the e100 driver as
> well.
>
> Info I think shows this attached to prevent munging, let me know if more
> is needed.
Lots of feedback/questions/response:
When you're on a network, more is always needed :)
Please give _plenty_ of details about what is on the other side of the
cable: hub? switch? vendor of hub/switch? crossover to another NIC?
what is the port configuration and what are the capabilities of the
other end? is it set to autonegotiate (on the other end)?
Why do you force full duplex? It is often the wrong thing to do.
For eepro100, you should use module option 'options' to specify
10baseT-FD... full_duplex appears to be somewhat redundant in the
context of your problem.
For e100, you should use 'e100_speed_duplex' module option to specify media.
Finally, I would be very interested to know the results of using ethtool
to set, and get, your media settings. It's in every distro these days,
plus you can d/l it from http://sf.net/projects/gkernel/
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 07 2002 - 22:00:17 EST