From owner-freebsd-current Thu Dec 19 16:28:47 2002 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 D4E7337B405 for ; Thu, 19 Dec 2002 16:28:46 -0800 (PST) Received: from ip68-100-111-63.nv.nv.cox.net (ip68-100-111-63.nv.nv.cox.net [68.100.111.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6431243EEF for ; Thu, 19 Dec 2002 16:28:46 -0800 (PST) (envelope-from fluxbox@cox.net) Received: by ip68-100-111-63.nv.nv.cox.net (Postfix, from userid 1001) id 4E38F403; Thu, 19 Dec 2002 19:28:49 -0500 (EST) Date: Thu, 19 Dec 2002 19:28:49 -0500 From: User Phrackbox To: current@freebsd.org Subject: if_dc: ethernet address now reported as 00:00:00:00:00:00 Message-ID: <20021220002849.GA27476@ip68-100-111-63.nv.nv.cox.net> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i 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 I have been recently experimenting with FreeBSD-current and have noticed a bug in dc network driver that it doesn't set the ethernet address correctly (I have seen this problem reported before on current, but I was hoping it could be fixed before 5.0-release). I am trying to find a fix myself but I am still getting comfortable with sources. Here is my dmesg output. dc0: port 0xe000-0xe0ff mem 0xef005000-0xef0050ff irq 10 at device 9.0 on pci0 dc0: Ethernet address: 00:00:00:00:00:00 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message