From owner-freebsd-hardware Sat May 26 12:43:26 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from kt-exchange.edmonton.kanotech.net (edtn016788.hs.telusplanet.net [161.184.241.24]) by hub.freebsd.org (Postfix) with ESMTP id BCEBB37B423; Sat, 26 May 2001 12:43:17 -0700 (PDT) (envelope-from moligny@kanotech.com) content-class: urn:content-classes:message Subject: duplex mismatch or something bad like that? Date: Sat, 26 May 2001 13:43:16 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <76928F3E231DE4478876350F083583360272DE@kt-exchange.edmonton.kanotech.net> X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: duplex mismatch or something bad like that? Thread-Index: AcDmHBuC2nzp5x/US4GnDE6xfPyZHQ== From: "Mike Oligny" To: , Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ...excuse the cross-post. I really am sorry. *g* I just replaced an old 10BaseT/UTP NIC with a new (cheapo-RTL8139-sort) 100BaseT NIC. The reason I replaced this card had nothing to do with difference in speed -- I just didn't want an ISA card in this server anymore... if it ain't broke, break it? Anyway, it is plugged into a 10BaseT hub and for some reason it figured it should use full duplex. =20 6k/second is not a lot of fun. Especially after doing stupid things like making new cables thinking that the old ones might have split pairs or something. (Everyone I work with seems to think that it doesn't matter which wires you put where when making cables, as long as they go straight through... is this a common misconception? Grrr...) # ifconfig rtl0 media 10baset/utp=20 Yay! Network all better. I don't know the syntax for just saying 'half duplex' and didn't bother to look. This works great. Is this a bug? Should the NIC drivers be a little more intelligent? Has this subject been beaten to death elsewhere? Happens with 4.3-20010525-STABLE, and 4.1.1 for sure. FreeBSD xxx.xxx.xxx 4.3-20010525-STABLE FreeBSD 4.3-20010525-STABLE #0: Fri May 25 12:00:06 GMT 2001 root@usw3.freebsd.org:/usr/src/sys/compile/GENERIC i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message