[vortex-bug] Re: Linux network driver: vortex 3c519x will not use 100baseT on 3com 905C PCI card

Donald Becker becker@scyld.com
Wed, 20 Sep 2000 16:38:59 -0400 (EDT)

On Wed, 20 Sep 2000, Darryl Presley wrote:

> I have a PCI 3COM 905C (Managed version of this card) and am using the
> 3c59x.o module.  Its compiled as a loadable module, not as part of the
> kernel.
> The hardware detects that its a 100bastT and the hub LED shows that
> indeed 100baseT is enabled.  However, when linux boots and starts the
> network services, it reverts back to 10baseT. In fact, the hub port on
> which the linux box is connected changes from 100baseT to 10baseT.  This
> is verified by the info provided below.

This is usually caused by passing an invalid transceiver type as a module

> The module is loaded at boot time, so how is insmod going to help?  Is
> conf.modules the right place to add the options parameters?  Can someone
> provide an example of what I need to do?

The solution is to *not* provide a module option.  Or at least provide the
correct setting if you insist on passing an option.

>  Transceiver/media interfaces available:  100baseTx 10baseT.
> Transceiver type in use:  10baseT.
> 3c59x.c:v0.99H 11/17/98 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> eth0: 3Com 3c905C Tornado at 0xe480,  00:01:02:73:0e:2a, IRQ 9
>   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.

Note that the original v0.99H did not support the 3c905C.
You have a modified driver version.

The driver has been modified to prevent forcing the internal 10baseT-only
transceiver when passing an invalid transceiver option.

Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Beowulf-II Cluster Distribution
Annapolis MD 21403