Fedora Linux Support Community & Resources Center
  #1  
Old 30th September 2004, 01:23 AM
azahra Offline
Registered User
 
Join Date: Sep 2004
Posts: 2
eth0: transmit error

I'm getting this:
Sep 27 03:00:26 zwoll020 kernel: eth0: Transmit error, Tx status register 82.
Sep 27 03:00:26 zwoll020 kernel: Probably a duplex mismatch. See Documentation/
networking/vortex.txt

How do I check and set the duplex?

Is there any good reference material on Fedora networking?
Reply With Quote
  #2  
Old 30th September 2004, 10:36 PM
Jman Offline
Registered User
 
Join Date: Mar 2004
Location: Minnesota, USA
Age: 27
Posts: 7,909
This error is so common it got it's own section in the kernel documentation (in the kernel-sourcecode package):
Code:
Transmit error, Tx status register 82
-------------------------------------
                                                                                                                             
This is a common error which is almost always caused by another host on
the same network being in full-duplex mode, while this host is in
half-duplex mode.  You need to find that other host and make it run in
half-duplex mode or fix this host to run in full-duplex mode.
                                                                                                                             
As a last resort, you can force the 3c59x driver into full-duplex mode
with
                                                                                                                             
        options 3c59x full_duplex=1
                                                                                                                             
but this has to be viewed as a workaround for broken network gear and
should only really be used for equipment which cannot autonegotiate.
I believe this option goes into /etc/modprobe.conf but I'm not sure.

What's the other hardware on your network?
Reply With Quote
  #3  
Old 1st October 2004, 01:21 AM
azahra Offline
Registered User
 
Join Date: Sep 2004
Posts: 2
I used mii-tool from the net-tools package to solve this.

I used mii-tool -v to query the state of the interface. It turned out that the ethernet switch it was connected to had autonegotiate turned off.

Last edited by azahra; 1st October 2004 at 01:58 AM.
Reply With Quote
Reply

Tags
error, eth0, transmit

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
lirc transmit KKJensen Using Fedora 0 5th May 2009 02:44 AM
NETDEV WATCHDOG: eth0 (atl1): transmit timed out jcliburn Servers & Networking 7 14th December 2008 05:25 AM
PCMCIA Wireless Modem Transmit Issues klopfest Servers & Networking 1 14th April 2004 03:31 AM


Current GMT-time: 00:23 (Thursday, 20-06-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat