From: Krzysztof Halasa <khc@pm.waw.pl>
To: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
Cc: "Arne R. van der Heyde" <vanderHeydeAR@summitinstruments.com>,
<linux-kernel@vger.kernel.org>,
<c-d.hailfinger.kernel.2004@gmx.net>
Subject: Re: no carrier when using forcedeth on MSI K8N Neo4-F
Date: Fri, 13 Jan 2006 22:16:01 +0100 [thread overview]
Message-ID: <m3k6d3n81a.fsf@defiant.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0601131345260.8379@chaos.analogic.com> (linux-os@analogic.com's message of "Fri, 13 Jan 2006 13:56:27 -0500")
"linux-os \(Dick Johnson\)" <linux-os@analogic.com> writes:
> You need to use the correct kind of cross-over cable for the Gigabit
> ports.
Correct, with all pairs crossed.
I don't force-death but I think most gigabit cards (and some 100BaseTX)
work with plain cable as well (using auto MDI-X, and auto-polarity
if needed).
> Then, you need to set both ports manually because there
> is no hardware (the switch) to handle the auto-configuration. The
> default is usually `autoneg on`. This tells the switch to
> auto-configure. Connected to another port, not a switch, this
> means nothing and the device remains dormant.
Again, I don't know nforce, but normal cards with autonegotiation
(i.e., (almost?) all 100BaseTX and newer) can negotiate speed and
duplex without need for a switch. BTW from net POI switches and
cards are DTEs, there is no special distinction WRT autonegotiation.
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-01-13 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 18:37 no carrier when using forcedeth on MSI K8N Neo4-F Arne R. van der Heyde
2006-01-13 18:56 ` linux-os (Dick Johnson)
2006-01-13 21:16 ` Krzysztof Halasa [this message]
2006-01-13 22:26 ` Lennart Sorensen
2006-01-13 22:38 ` Christopher Friesen
2006-01-16 19:38 ` Lennart Sorensen
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=m3k6d3n81a.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=vanderHeydeAR@summitinstruments.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