The Linux Tulip driver

Tracker: Bugs

5 Half-Duplex Selected instead of Full-Duplex - ID: 1294822

Last Update: Comment added ( nobody )

Details:

Linux 2.6.13.2, AMD Athlon

0000:00:11.0 Ethernet controller: Digital Equipment
Corporation DECchip 21140 [FasterNet] (rev 20)

For some strange reason, my card seems to report pick
half-duplex when the connection is capable of
full-duplex on bootup. Disconnecting and reconnecting
the network connection, then running
/etc/init.d/networking restart (a Debian system) will
cause the connection to be properly detected.

tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media MII (#11) described by a
21140 MII PHY (1) block.
tulip0: MII transceiver #1 config 3100 status 782b
advertising 01e1.

[snip]

eth0: Setting half-duplex based on MII#1 link partner
capability of 0000.

[snip, connection reset, networking restarted]

eth0: Setting full-duplex based on MII#1 link partner
capability of 05e1.

Submitted:

Nobody/Anonymous ( nobody ) - 2005-09-18 21:48

Priority:

Status:

Open

Resolution:

None

Assigned:

Nobody/Anonymous

Category:

Media selection

Group:

Errors, but still works

Visibility:

Public

Comment ( 1 )

Date: 2005-10-06 10:21 Sender: nobody Logged In: NO I am seeing the exact same thing - except that I have two identical Tulip 21143 cards connected to each other with a cross-over cable. The issue is that I have to run mii-tool -r eth1 on both machines at the same time in order to make the cards renegotiate the link. If I reboot one machine after a successfull link state, then both machines fails to renegotiate the correct link state. Even if I run "mii-tool -r eth1" on one machine then link does not come up. I have to run the mii-tool on both machines. I am running the linux 2.6.13 kernel with the tulip driver

Date: 2005-10-06 10:21
Sender: nobody

Logged In: NO

I am seeing the exact same thing - except that I have two
identical Tulip 21143 cards connected to each other with a
cross-over cable. The issue is that I have to run mii-tool
-r eth1 on both machines at the same time in order to make
the cards renegotiate the link.
If I reboot one machine after a successfull link state, then
both machines fails to renegotiate the correct link state.
Even if I run "mii-tool -r eth1" on one machine then link
does not come up. I have to run the mii-tool on both machines.

I am running the linux 2.6.13 kernel with the tulip driver

The Linux Tulip driver

Tracker: Bugs

Comment ( 1 )

Log in to comment.

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.

About SourceForge

Find Software

Develop Software

Community

Help