From owner-freebsd-stable@FreeBSD.ORG Sat Jun 20 00:06:02 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 416EB1065675 for ; Sat, 20 Jun 2009 00:06:02 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id C61E28FC0A for ; Sat, 20 Jun 2009 00:06:01 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-255-48-78.bredband.comhem.se ([83.255.48.78]:55578 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.69) (envelope-from ) id 1MHnr7-0001EF-6J for freebsd-stable@freebsd.org; Sat, 20 Jun 2009 01:50:51 +0200 Received: (qmail 55632 invoked from network); 20 Jun 2009 01:50:47 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 20 Jun 2009 01:50:47 +0200 Received: (qmail 57622 invoked by uid 1001); 20 Jun 2009 01:50:47 +0200 Date: Sat, 20 Jun 2009 01:50:47 +0200 From: Erik Trulsson To: Michael Gass Message-ID: <20090619235047.GA57522@owl.midgard.homeip.net> References: <20090619172429.GA5197@unix.csbsju.edu> <20090619230802.GA5795@unix.csbsju.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090619230802.GA5795@unix.csbsju.edu> User-Agent: Mutt/1.5.19 (2009-01-05) X-Originating-IP: 83.255.48.78 X-Scan-Result: No virus found in message 1MHnr7-0001EF-6J. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MHnr7-0001EF-6J 4bb86c132314f0b0ca3d5c35c6254d22 Cc: freebsd-stable@freebsd.org Subject: Re: kernel wants the wrong driver for my NIC (new issue) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jun 2009 00:06:02 -0000 On Fri, Jun 19, 2009 at 06:08:02PM -0500, Michael Gass wrote: > On Fri, Jun 19, 2009 at 12:24:29PM -0500, Michael Gass wrote: > > I'm running 7.2-stable and I replaced an old ISA NIC with > > a D-Link DFE-530TX+ card. According to the manual, the > > correct driver for this card is rl driver. The kernel > > insists on using the vr driver which is for the DFE-530TX. > > >From what I can tell, the two cards have different chipsets > > and so the drivers are not compatable. > > > > I got the vr driver to work: it was an IRQ issue. Seems > sio1 wanted irq 3 which is what vr0 was taking. Somehow that > caused a problem. > > BUT > > I am still confused about the rl driver not working for this > card. The NOTES in /usr/src/sys/conf/NOTES explicitly state > that the rl driver is for the DFE-530TX+ and that the vr > driver is for the DFE-530TX. I have the former and so should > be using the rl drive it seems. Is this a mistake in the > documentation (including the man page for each driver)? Then perhaps the card you have actually is a DFE-530TX. Or maybe the manufacturer changed which chip they use without bothering to change the name of the card - such things happen all too often. I.e. there may well exist two different 'DFE-530TX+' variants - one which uses a Realtek controller, and one which uses a VIA controller. > > I made a new kernel without the vr driver and the result was > that no driver at all was recognized for the NIC. > Is there a way to force the kernel to put an entry in /dev > for rl0 so that I could try to configue it for the NIC? No. The kernel uses the PCI chip-ID to decide which driver attaches to the card. To change which driver is used you would have to go in and modify the kernel source and build a new kernel. Don't bother doing that however, because if the vr(4) driver works for this card (as you say it does) then there is absolutely no way that the rl(4) driver would work for the same card. (And vice versa.) > > BTW, visual inspection of the chip on my DFE-530TX+ says it > is a DL10030C. > > Here is some relevant output from running pciconf -lvc. > > vr0@pci0:0:11:0: class=0x020000 card=0x14061186 chip=0x31061106 rev=0x86 hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT6105M/LOM Rhine III PCI Fast Ethernet Controller' > class = network > subclass = ethernet > cap 01[40] = powerspec 2 supports D0 D1 D2 D3 current D0 That looks very much like a VIA chip which should indeed be handled by the vr(4) driver. -- Erik Trulsson ertr1013@student.uu.se