From: Ben Greear <greearb@candelatech.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: Ken Brownfield <brownfld@irridia.com>,
Florin Andrei <florin@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.2.19: eepro100 and cmd_wait issues
Date: Tue, 12 Jun 2001 18:52:57 -0700 [thread overview]
Message-ID: <3B26C779.ECE9017C@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106121702500.25366-100000@dlang.diginsite.com>
David Lang wrote:
>
> I am useing the D-link 4 port card without running into problems
> (admittidly I have not been stressing it much yet)
I was able to get the D-Link to work in half-duplex (100bt), but
not in auto-negotiate or full-duplex mode. (Packets would pass,
but there would be huge number of carrier and other bad packets.)
I get a similar problem with the ZNYX 4-port, but I can't even
force it to half-duplex, or any other fixed speed (it just won't go).
It kinda autonegotiates something, claiming to be full-duplex, but it
still shows collisions and I can't get through-put above about 10Mbps
bi-directional, and its dropping many packets.
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-06-13 1:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 18:00 2.2.19: eepro100 and cmd_wait issues John Madden
2001-06-12 18:51 ` Florin Andrei
2001-06-12 19:20 ` Ken Brownfield
2001-06-13 0:51 ` Ben Greear
2001-06-13 0:03 ` David Lang
2001-06-13 1:52 ` Ben Greear [this message]
2001-06-13 11:16 ` Henning P. Schmiedehausen
2001-06-14 17:12 ` Florin Andrei
-- strict thread matches above, loose matches on Subject: below --
2001-06-13 21:30 Jason Murphy
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=3B26C779.ECE9017C@candelatech.com \
--to=greearb@candelatech.com \
--cc=brownfld@irridia.com \
--cc=david.lang@digitalinsight.com \
--cc=florin@sgi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.