How do I get the 3com 3c905b-tx to use 100Mbs?

Many apologies if this question has been posted previously, but I couldn't
find the answer. I (finally) got my home network set up so that my linux
box (Fedora Core 1, 2.4.22-1.2135.nptl) communicates with our other
computer via eth1 which is 3com's 3c905b-tx. The only problem is that it
only seems to operate in 10baseT mode. I've stepped down the laptop's
card to communicate at 10baseT, but if both are capable of using 100Mbps,
then why not. On the linux box, I tried using

mii-tools -F 100baseTx-FD eth1

but this does not work. mii-tools -v eth1 reveals that

eth1: autonegotiation restarted, link ok
product info: vendor 05:e1:c5, model 56 rev 7
basic mode: isolate, collision test, autonegotiation enabled
basic status: autonegotiation restarted, link ok
capabilities: 10baseT-FD
advertising: 100baseT4 100baseTx-FD 100baseTx-HD flow-control
link partner: 100baseT4 100baseTx-FD 100baseTx-HD flow-control

and mii-diag -v eth1 reveals

mii-diag.c:v2.00 4/19/2000 Donald Becker ((E-Mail Removed))
http://www.scyld.com/diag/index.html
MII PHY #0 transceiver registers:
1787 1787 1787 1787 1787 1787 1787 1787
1787 1787 1787 1787 1787 1787 1787 1787
1787 1787 1787 1787 1787 1787 1787 1787
1787 1787 1787 1787 1787 1787 1787 1787.
Basic mode control register 0x1787: Auto-negotiation enabled.
Internal Collision-Test enabled!
Restarted auto-negotiation in progress!
Transceiver isolated from the MII!
Basic mode status register 0x1787 ... 1787.
Link status: established.
This transceiver is capable of 10baseT-FD.
Unable to perform Auto-negotiation, negotiation not complete.
*** Link Jabber! ***
Your link partner is generating 100baseTx link beat (no autonegotiation).
MII PHY #0 transceiver registers:
1787 1787 1787 1787 1787 1787 1787 1787
1787 1787 1787 1787 1787 1787 1787 1787
1787 1787 1787 1787 1787 1787 1787 1787
1787 1787 1787 1787 1787 1787 1787 1787.
Basic mode control register 0x1787: Auto-negotiation enabled.
Transceiver isolated from the MII!
Restarted auto-negotiation in progress!
Internal Collision-Test enabled!
Basic mode status register 0x1787 ... 1787.
Link status: established.
Capable of 10baseT-FD.
Unable to perform Auto-negotiation, negotiation not complete.
*** Link Jabber! ***
This transceiver has no vendor identification.
I'm advertising 1787: Flow-control 100baseT4 100baseTx-FD 100baseTx
Advertising no additional info pages.
Using an unknown (non 802.3) encapsulation.
Link partner capability is 1787: Flow-control 100baseT4 100baseTx-FD 100baseTx.
Negotiation did not complete.


Since I am truly new to this part of computers (i.e., networking) I'm not
sure what the problem is. Is it:

1) The driver (3c59x - which came with the kernel distribution) sets it
link speed to 10Mbps and somehow sets the card up so that it cannot be
changed, or
2) The driver reads the link speed from the card at startup and so the
card has to be configured, somehow before the driver is even loaded.

Any advice is more than welcome.

Cheers,
Andrew

Have you tried the 3com site for the Linux tools?

--
Yours

Widow Twankey

Now 10% Twankier than ever
"Andrew P. Billyard" <(E-Mail Removed) >
wrote in message
news(E-Mail Removed) hisBit.uwaterloo.ca...
> Many apologies if this question has been posted previously, but I couldn't
> find the answer. I (finally) got my home network set up so that my linux
> box (Fedora Core 1, 2.4.22-1.2135.nptl) communicates with our other
> computer via eth1 which is 3com's 3c905b-tx. The only problem is that it
> only seems to operate in 10baseT mode. I've stepped down the laptop's
> card to communicate at 10baseT, but if both are capable of using 100Mbps,
> then why not. On the linux box, I tried using
>
> mii-tools -F 100baseTx-FD eth1
>
> but this does not work. mii-tools -v eth1 reveals that
>
> eth1: autonegotiation restarted, link ok
> product info: vendor 05:e1:c5, model 56 rev 7
> basic mode: isolate, collision test, autonegotiation enabled
> basic status: autonegotiation restarted, link ok
> capabilities: 10baseT-FD
> advertising: 100baseT4 100baseTx-FD 100baseTx-HD flow-control
> link partner: 100baseT4 100baseTx-FD 100baseTx-HD flow-control
>
> and mii-diag -v eth1 reveals
>
> mii-diag.c:v2.00 4/19/2000 Donald Becker ((E-Mail Removed))
> http://www.scyld.com/diag/index.html
> MII PHY #0 transceiver registers:
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787.
> Basic mode control register 0x1787: Auto-negotiation enabled.
> Internal Collision-Test enabled!
> Restarted auto-negotiation in progress!
> Transceiver isolated from the MII!
> Basic mode status register 0x1787 ... 1787.
> Link status: established.
> This transceiver is capable of 10baseT-FD.
> Unable to perform Auto-negotiation, negotiation not complete.
> *** Link Jabber! ***
> Your link partner is generating 100baseTx link beat (no
autonegotiation).
> MII PHY #0 transceiver registers:
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787.
> Basic mode control register 0x1787: Auto-negotiation enabled.
> Transceiver isolated from the MII!
> Restarted auto-negotiation in progress!
> Internal Collision-Test enabled!
> Basic mode status register 0x1787 ... 1787.
> Link status: established.
> Capable of 10baseT-FD.
> Unable to perform Auto-negotiation, negotiation not complete.
> *** Link Jabber! ***
> This transceiver has no vendor identification.
> I'm advertising 1787: Flow-control 100baseT4 100baseTx-FD 100baseTx
> Advertising no additional info pages.
> Using an unknown (non 802.3) encapsulation.
> Link partner capability is 1787: Flow-control 100baseT4 100baseTx-FD
100baseTx.
> Negotiation did not complete.
>
>
> Since I am truly new to this part of computers (i.e., networking) I'm not
> sure what the problem is. Is it:
>
> 1) The driver (3c59x - which came with the kernel distribution) sets it
> link speed to 10Mbps and somehow sets the card up so that it cannot be
> changed, or
> 2) The driver reads the link speed from the card at startup and so the
> card has to be configured, somehow before the driver is even loaded.
>
> Any advice is more than welcome.
>
> Cheers,
> Andrew

andrew what version of linix are you using and what hardware is in
your desk top?

wm


On Sat, 24 Jan 2004 19:24:21 GMT, "Andrew P. Billyard"
<(E-Mail Removed) > wrote:

>Many apologies if this question has been posted previously, but I couldn't
>find the answer. I (finally) got my home network set up so that my linux
>box (Fedora Core 1, 2.4.22-1.2135.nptl) communicates with our other
>computer via eth1 which is 3com's 3c905b-tx. The only problem is that it
>only seems to operate in 10baseT mode. I've stepped down the laptop's
>card to communicate at 10baseT, but if both are capable of using 100Mbps,
>then why not. On the linux box, I tried using
>
>mii-tools -F 100baseTx-FD eth1
>
>but this does not work. mii-tools -v eth1 reveals that
>
>eth1: autonegotiation restarted, link ok
> product info: vendor 05:e1:c5, model 56 rev 7
> basic mode: isolate, collision test, autonegotiation enabled
> basic status: autonegotiation restarted, link ok
> capabilities: 10baseT-FD
> advertising: 100baseT4 100baseTx-FD 100baseTx-HD flow-control
> link partner: 100baseT4 100baseTx-FD 100baseTx-HD flow-control
>
>and mii-diag -v eth1 reveals
>
>mii-diag.c:v2.00 4/19/2000 Donald Becker ((E-Mail Removed))
> http://www.scyld.com/diag/index.html
> MII PHY #0 transceiver registers:
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787.
> Basic mode control register 0x1787: Auto-negotiation enabled.
> Internal Collision-Test enabled!
> Restarted auto-negotiation in progress!
> Transceiver isolated from the MII!
> Basic mode status register 0x1787 ... 1787.
> Link status: established.
> This transceiver is capable of 10baseT-FD.
> Unable to perform Auto-negotiation, negotiation not complete.
> *** Link Jabber! ***
> Your link partner is generating 100baseTx link beat (no autonegotiation).
> MII PHY #0 transceiver registers:
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787
> 1787 1787 1787 1787 1787 1787 1787 1787.
> Basic mode control register 0x1787: Auto-negotiation enabled.
> Transceiver isolated from the MII!
> Restarted auto-negotiation in progress!
> Internal Collision-Test enabled!
> Basic mode status register 0x1787 ... 1787.
> Link status: established.
> Capable of 10baseT-FD.
> Unable to perform Auto-negotiation, negotiation not complete.
> *** Link Jabber! ***
> This transceiver has no vendor identification.
> I'm advertising 1787: Flow-control 100baseT4 100baseTx-FD 100baseTx
> Advertising no additional info pages.
> Using an unknown (non 802.3) encapsulation.
> Link partner capability is 1787: Flow-control 100baseT4 100baseTx-FD 100baseTx.
> Negotiation did not complete.
>
>
>Since I am truly new to this part of computers (i.e., networking) I'm not
>sure what the problem is. Is it:
>
>1) The driver (3c59x - which came with the kernel distribution) sets it
>link speed to 10Mbps and somehow sets the card up so that it cannot be
>changed, or
>2) The driver reads the link speed from the card at startup and so the
>card has to be configured, somehow before the driver is even loaded.
>
>Any advice is more than welcome.
>
>Cheers,
>Andrew

On Sat, 24 Jan 2004 19:24:21 +0000, Andrew P. Billyard wrote:

> Many apologies if this question has been posted previously, but I
> couldn't find the answer. I (finally) got my home network set up so
> that my linux box (Fedora Core 1, 2.4.22-1.2135.nptl) communicates with
> our other computer via eth1 which is 3com's 3c905b-tx. The only problem
> is that it only seems to operate in 10baseT mode. I've stepped down
> the laptop's card to communicate at 10baseT, but if both are capable of
> using 100Mbps, then why not. On the linux box, I tried using
>
> mii-tools -F 100baseTx-FD eth1

[snip]

> Since I am truly new to this part of computers (i.e., networking) I'm
> not sure what the problem is. Is it:
>
> 1) The driver (3c59x - which came with the kernel distribution) sets it
> link speed to 10Mbps and somehow sets the card up so that it cannot be
> changed, or
> 2) The driver reads the link speed from the card at startup and so the
> card has to be configured, somehow before the driver is even loaded.

The way I set my 3c905c to 100MB should be the same:

modprobe 3c59x options=0x04

Of course, this is for the module. Read the vortex.txt file under <kernel
source>Documentation/networking/ to see how to pass it as a kernel
argument at lilo or grub. I've done it before... I forget how.

I think it would be something like:

<your_kernel> ether=0,0,0x04

Do a 'man bootparam' for more info on 'ether' parameteres.

Hope this helps.