From owner-freebsd-current Tue Feb 25 20: 7:53 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35FE137B401 for ; Tue, 25 Feb 2003 20:07:52 -0800 (PST) Received: from pakastelohi.cypherpunks.to (pakastelohi.cypherpunks.to [213.130.163.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6729D43FB1 for ; Tue, 25 Feb 2003 20:07:51 -0800 (PST) (envelope-from shamrock@cypherpunks.to) Received: from VAIO650 (adsl-208-201-229-160.sonic.net [208.201.229.160]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pakastelohi.cypherpunks.to (Postfix) with ESMTP id A4C0B3647D; Wed, 26 Feb 2003 05:07:44 +0100 (CET) From: "Lucky Green" To: Cc: Subject: Re: Ethernet (xl) will not transmit or receive Date: Tue, 25 Feb 2003 20:07:45 -0800 Message-ID: <003201c2dd4c$a1342f80$6601a8c0@VAIO650> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kevin wrote: > I updated my 5.0 system built in late January to RELENG_5_0 on Sunday > and the Ethernet was not working. I tried again last night with no > change in behavior. > > The system is an AMD K6-2 on an ASUS P5A mobo. I have a 3Com 3c905B > Ethernet which had been working fine on a kernel built in late > January. > > The dmesg is not too meaningful, but the system shows no errors. It > simply never receives a packet. ARPs are all incomplete and no packets > are transmitted although netstat -in indicates that they are. The > packets never actually reach the wire, though. > > I can't believe that no one else has this card, but I didn't find > anything in the archives on it. I experienced the exact same behavior with my GF's GigaByte GA-5AN AMD K6-2 motherboard. Both a 3COM and a Realtek (yeah, I know...) card refused to pass packets, staying in hardware loopback. The link light on both cards would remain on until it appears the device was probed. At that point the link was lost permanently. The motherboard and both cards work fine with FreeBSD 4.7, which I even re-tested after the futile 5.0-RELEASE installation. I even flashed in the latest BIOS, but that had no effect. (The hardware has since been re-tasked and is no longer available for testing). --Lucky Green To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message