From: Auke Kok <auke-jan.h.kok@intel.com>
To: Jeff Kirsher <tarbal@gmail.com>
Cc: a1 <a1k@mail.ru>, netdev@vger.kernel.org
Subject: Re: e1000 speed/duplex error
Date: Tue, 01 Aug 2006 07:35:25 -0700 [thread overview]
Message-ID: <44CF66AD.1030901@intel.com> (raw)
In-Reply-To: <9929d2390608010534x54324569ja70b1fcbdc23c097@mail.gmail.com>
Jeff Kirsher wrote:
> On 8/1/06, a1 <a1k@mail.ru> wrote:
>> Hi, Jeff.
>>
>>
>> JK> OPTION 2: Turn auto-negotiate on the e1000 card and tell it to only
>> JK> advertise 100 Full Duplex. This will allow negotiation between the
>> JK> two lnk partners and the e1000 will advertise that it is only able to
>> JK> do 100 Full duplex.
>>
>> Is there any way i could do this with ethtool? It only allows force
>> spd/dplx , but not set it for advertising...
>
> Not currently. That would be a nice feature though... :)
>
>>
>> If i do as follows other side reports 1000/FD:
>>
>> ethtool -s eth0 speed 100 duplex full autoneg on
>>
>
> Which is what I would expect. I have to step away for a bit, but if
> no one responds with how to load the driver with auto-negotiate
> advertising only 100 Full Duplex, I will do so when I return.
Here's that part of the driver documentation:
$ modprobe e1000 AutoNeg=0x08
e1000: 0000:00:00.0: e1000_validate_option: AutoNeg advertising 100/FD
99 /* Auto-negotiation Advertisement Override
100 *
101 * Valid Range: 0x01-0x0F, 0x20-0x2F (copper); 0x20 (fiber)
102 *
103 * The AutoNeg value is a bit mask describing which speed and duplex
104 * combinations should be advertised during auto-negotiation.
105 * The supported speed and duplex modes are listed below
106 *
107 * Bit 7 6 5 4 3 2 1 0
108 * Speed (Mbps) N/A N/A 1000 N/A 100 100 10 10
109 * Duplex Full Full Half Full Half
110 *
111 * Default Value: 0x2F (copper); 0x20 (fiber)
112 */
hth,
Auke
next prev parent reply other threads:[~2006-08-01 14:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 10:18 e1000 speed/duplex error a1
2006-08-01 11:20 ` Jeff Kirsher
2006-08-01 12:03 ` Re[2]: " a1
2006-08-01 12:21 ` Andy Gospodarek
2006-08-01 12:22 ` Re[2]: " Jamal Hadi Salim
2006-08-01 17:03 ` Rick Jones
[not found] ` <793732866.20060801153230@mail.ru>
[not found] ` <9929d2390608010445w4fd81b64g310ae90a423e1a7d@mail.gmail.com>
2006-08-01 12:20 ` Re[4]: " a1
2006-08-01 12:34 ` Jeff Kirsher
2006-08-01 14:35 ` Auke Kok [this message]
2006-08-01 17:15 ` Jeff Kirsher
2006-08-02 7:34 ` a1
2006-08-02 7:43 ` Jeff Kirsher
2006-08-02 8:39 ` a1
2006-08-02 15:02 ` Auke Kok
2006-08-03 7:51 ` a1
2006-08-02 16:19 ` Auke Kok
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=44CF66AD.1030901@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=a1k@mail.ru \
--cc=netdev@vger.kernel.org \
--cc=tarbal@gmail.com \
/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).