From owner-freebsd-stable@FreeBSD.ORG Fri Aug 11 09:23:07 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5027316A4E1 for ; Fri, 11 Aug 2006 09:23:07 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B4B643D46 for ; Fri, 11 Aug 2006 09:23:06 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k7B9N4ps089000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Aug 2006 13:23:04 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k7B9N3MX088999; Fri, 11 Aug 2006 13:23:03 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 11 Aug 2006 13:23:03 +0400 From: Gleb Smirnoff To: lnelson Message-ID: <20060811092303.GV96644@FreeBSD.org> References: <20060811051959.M95805@naxostech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20060811051959.M95805@naxostech.com> User-Agent: Mutt/1.5.6i Cc: freebsd-stable@FreeBSD.org Subject: Re: Odd problem with Intel em driver 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: Fri, 11 Aug 2006 09:23:07 -0000 On Fri, Aug 11, 2006 at 01:27:42AM -0400, lnelson wrote: l> I'm having an odd problem with the Intel em driver. It's l> built into the kernel by default, but it won't recognize l> the part. l> l> However, if I grab the driver source from the Intel website, l> compile it as a KLD, and put it in loader.conf, it works. l> The odd thing is that it complains that it is already loaded, l> and acts as if it is refusing to load the module. l> l> When it works, the message I get is: l> l> module_register: module pci/em already exists! l> Module pci/em failed to register: 17 l> ... ... l> em0: port 0x3000-0x301f mem l> 0xc8300000-0xc831ffff i l> rq 18 at device 0.0 on pci5 l> em0: Ethernet address: 00:30:48:78:5a:2a l> em0: Speed:N/A Duplex:N/A l> em1: port 0x3020-0x303f mem l> 0xc8320000-0xc833ffff i l> rq 19 at device 0.1 on pci5 l> em1: Ethernet address: 00:30:48:78:5a:2b l> em1: Speed:N/A Duplex:N/A l> l> When it doesn't work, I get no messages regarding l> em at all. l> l> It seems like the KLD is actually getting loaded, even l> though it says it isn't. l> l> I should mention that I am running the amd64 port of l> 6.1 RELEASE. l> l> Any thoughts? Can I run a production server like this? FreeBSD is always a bit behind in the version of the driver. First driver appears on Intel website, and later is merged to FreeBSD. Currently in 6-STABLE we've got version 6.0.5 driver. First you should try to update to 6-STABLE. If this doesn't help you should wait few weeks until driver 6.1.4 will be present in 6-STABLE. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE