From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Matt Mathis <mathis@psc.edu>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: e1000 driver problems
Date: Tue, 4 Dec 2007 18:08:27 +0100 [thread overview]
Message-ID: <20071204170827.GH8704@ics.muni.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0712041043520.15251@tesla.psc.edu>
On Tue, Dec 04, 2007 at 11:02:23AM -0500, Matt Mathis wrote:
> This is probably not an e1000 problem, but a general Ethernet "feature".
> If you defeat auto-negotiation to force the data rate, you implicitly
> defeat duplex negotiation as well. You need to explicitly set the duplex
> mode.
ethtool reports, that I have full duplex line:
ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: umbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2007-12-04 17:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061017205316.25914.qmail@web83109.mail.mud.yahoo.com>
[not found] ` <45354850.6050900@intel.com>
[not found] ` <20071120143803.GA5638@ics.muni.cz>
[not found] ` <474B5610.4030800@intel.com>
[not found] ` <20071127150700.GB4365@ics.muni.cz>
[not found] ` <474C4A74.90705@intel.com>
[not found] ` <20071127173146.GG4365@ics.muni.cz>
2007-11-27 17:40 ` e1000 driver problems Kok, Auke
2007-11-27 17:44 ` Lukas Hejtmanek
2007-11-27 18:23 ` Kok, Auke
2007-12-03 9:50 ` Lukas Hejtmanek
2007-12-03 15:20 ` Kok, Auke
2007-12-04 15:03 ` Lukas Hejtmanek
2007-12-04 15:34 ` Lukas Hejtmanek
2007-12-04 16:02 ` Matt Mathis
2007-12-04 17:08 ` Lukas Hejtmanek [this message]
2007-12-04 17:19 ` Kok, Auke
2007-12-04 18:05 ` Rick Jones
2007-12-04 19:59 ` Lukas Hejtmanek
2007-12-04 20:38 ` Kok, Auke
2007-12-18 11:08 ` Lukas Hejtmanek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071204170827.GH8704@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=mathis@psc.edu \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).