From owner-freebsd-current@FreeBSD.ORG Mon Jun 6 15:54:14 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org 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 EFB1B16A41C for ; Mon, 6 Jun 2005 15:54:14 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3DAA43D1F for ; Mon, 6 Jun 2005 15:54:14 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-2.free.fr (Postfix) with ESMTP id DDEAE31DA5D; Mon, 6 Jun 2005 17:54:13 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id DD5DA407E; Mon, 6 Jun 2005 17:54:00 +0200 (CEST) Date: Mon, 6 Jun 2005 17:54:00 +0200 From: Jeremie Le Hen To: freebsd-current@FreeBSD.org Message-ID: <20050606155400.GP41050@obiwan.tataz.chchile.org> References: <20050606131957.GL41050@obiwan.tataz.chchile.org> <20050606133434.GG734@empiric.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050606133434.GG734@empiric.icir.org> User-Agent: Mutt/1.5.9i Cc: bana@sitadelle.com Subject: Re: Can't get MAC addr of an ed(4) adapter X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 15:54:15 -0000 Hi Bruce, thanks for your quick reply. > These cards are real mongrels. I had one about 7 years ago. Horrible. > Highly recommend getting rid of it. PCI Realtek 10Mbps, yes? Know them, > hate them. That's what I heard too, but sometimes we do with what we have :-). > I would try removing any device hints from the /boot/device.hints file > which begin with 'hint.ed.0' as they are probably misleading, if the > actual card is probed as ed1 (although I don't see this in the dmesg > output here). With this trick, ed1 is probed as ed0, even if the driver is a module. > Try recompiling with 'makeoptions ED_DEBUG' in the kernel config file > and see what it turns up. As I stated in my first mail, I already tried this and this gave no more diagnostic messages, unfortunately. It seems that the ed(4) driver from 2005.01.01 are working well. There have been numerous commits since then, but I'm trying to find the culprit ATM. I'll keep list abreast of the results. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >