From: "Paul Rolland" <rol@as2917.net>
To: "'Michael Knigge'" <Michael.Knigge@set-software.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: Strange e1000
Date: Fri, 4 Apr 2003 15:41:09 +0200 [thread overview]
Message-ID: <043501c2faaf$da061e10$3f00a8c0@witbe> (raw)
In-Reply-To: <20030404.7255311@knigge.local.net>
Hello,
> when I load the e1000 module, my NIC is recognized. Then, "pump -i
> eth0" is called (DHCP-Client), the message "e1000: eth0 NIC
> Link is Up
> 1000 Mbps Full Duplex" appears and after some time I get the message
> "operation failed".
>
> When I sleep some time (currently 20 seconds) before doing
> the "pump",
> everything works as expected.
>
> What the hell is happening here? Ok, I got it working with the
> 20-sec-sleep but this is not the way it sould work...
>
> My Board is a Gigabyte GA-7ZXR (1.0) and the Intel NIC is a PRO/1000
> MT (should be the 82540OEM Chip). The NIC is attached to a NetGear
> FSM726S Switch (24x100 + 2x1000). It is currenty the only box
> attached
Could it be possible that the 1000MBps FD on the e1000 side is
a local configuration, and that it needs some time to discuss with
the Netgear switch to negotiate correctly speed and duplex before
working correctly ? (i.e. 20 sec = negotiation time)
Regards,
Paul
next prev parent reply other threads:[~2003-04-04 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 7:25 Strange e1000 Michael Knigge
2003-04-04 13:41 ` Paul Rolland [this message]
2003-04-04 14:00 ` Michael Knigge
2003-04-04 14:19 ` Abhishek Agrawal
2003-04-04 18:14 ` Jeff Garzik
2003-04-05 8:41 ` Henning P. Schmiedehausen
2003-04-04 14:45 ` Justin Cormack
2003-04-04 15:48 ` Jeff Garzik
2003-04-04 17:02 ` Patrick R. McManus
2003-04-04 17:09 ` Patrick R. McManus
2003-04-07 7:45 ` Strange e1000 - SOLVED Michael Knigge
-- strict thread matches above, loose matches on Subject: below --
2003-04-07 21:52 Strange e1000 Mroczek, Joseph T
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='043501c2faaf$da061e10$3f00a8c0@witbe' \
--to=rol@as2917.net \
--cc=Michael.Knigge@set-software.de \
--cc=linux-kernel@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