From owner-freebsd-questions Fri Nov 3 15: 7:28 2000 Delivered-To: freebsd-questions@freebsd.org Received: from exchange.den.t-netix.com (unknown [63.86.248.102]) by hub.freebsd.org (Postfix) with ESMTP id 5D99B37B4CF for ; Fri, 3 Nov 2000 15:07:25 -0800 (PST) Received: by DENXCH with Internet Mail Service (5.5.2650.21) id ; Fri, 3 Nov 2000 16:07:24 -0700 Message-ID: <418E68E524A8D311ACCE00508B78866A0107CF3B@DENXCH> From: Mike Johnson To: "'freebsd-questions@FreeBSD.ORG'" Subject: Compaq 1850 Thunderlan Problems Date: Fri, 3 Nov 2000 16:07:24 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C045EA.D3D24CD4" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C045EA.D3D24CD4 Content-Type: text/plain; charset="iso-8859-1" The Netflex (Thunderlan) embedded ethernet controller in the Compaq 1850R does not seem to like the Thunderlan driver. When connected to a 10BaseT/UTP hub the controller will continuously cycle through the auto-detection bringing the connection (and the physical link) up and down repeatedly (driver with no arguments - default of autodetect). The same configuration will work fine and detect 100BaseT full duplex when connected to a 10/100 switch and the network connection functions. I have tried adding the 'media 10BaseT/UTP' argument which causes the controller to lock into that mode without autodetecting, leaving the link established. However, no data will pass (cannot ping in our out). I can ping the loopback address and I can ping the local IP. I have reproduced this problems with multiple versions of FreeBSD (2.x,3.x,4.x). My assumption is that Compaq has implemented the TI Thunderlan chipset in a "nonstandard" way and thereby broken the driver. Has anyone else seen/solved this problem? Any help/suggestions would be appreciated. Michael S. Johnson ------_=_NextPart_001_01C045EA.D3D24CD4 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Compaq 1850 Thunderlan Problems

The Netflex (Thunderlan) embedded = ethernet controller in the Compaq 1850R does not seem to like the = Thunderlan driver.  When connected to a 10BaseT/UTP hub the = controller will continuously cycle through the auto-detection bringing = the connection (and the physical link) up and down repeatedly (driver = with no arguments - default of autodetect).

The same configuration will work fine = and detect 100BaseT full duplex when connected to a 10/100 switch and = the network connection functions.  I have tried adding the 'media = 10BaseT/UTP' argument which causes the controller to lock into that = mode without autodetecting, leaving the link established.  = However, no data will pass (cannot ping in our out).  I can ping = the loopback address and I can ping the local IP.

I have reproduced this problems with = multiple versions of FreeBSD (2.x,3.x,4.x).  My assumption is that = Compaq has implemented the TI Thunderlan chipset in a = "nonstandard" way and thereby broken the driver.

Has anyone else seen/solved this = problem?  Any help/suggestions would be appreciated.

Michael S. Johnson

------_=_NextPart_001_01C045EA.D3D24CD4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message