Re: 2.2.19: eepro100 and cmd_wait issues

Henning P. Schmiedehausen (mailgate@hometree.net)
Wed, 13 Jun 2001 11:16:57 +0000 (UTC)


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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/