From: "Henning P. Schmiedehausen" <mailgate@hometree.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.2.19: eepro100 and cmd_wait issues
Date: Wed, 13 Jun 2001 11:16:57 +0000 (UTC) [thread overview]
Message-ID: <9g7i39$d33$1@forge.intermeta.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0106121702500.25366-100000@dlang.diginsite.com> <3B26C779.ECE9017C@candelatech.com>
Ben Greear <greearb@candelatech.com> writes:
>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.)
Yes. Exactly my experience (with 2.2.18 / 19 / 20pre). It is simply
not possible to make a tulip based card work reliably against our
Cisco Catalyst switches in these days. Sadly, because under 2.0.x,
these were rock-solid.
So I started to use 3COM exclusively (which work perfectly with our
switches) and eepro100 if necessary (or built onboard).
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2001-06-13 11:17 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
2001-06-13 11:16 ` Henning P. Schmiedehausen [this message]
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='9g7i39$d33$1@forge.intermeta.de' \
--to=mailgate@hometree.net \
--cc=hps@intermeta.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 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.