From owner-freebsd-stable@FreeBSD.ORG Fri Aug 11 05:27:48 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 8A7ED16A4DD for ; Fri, 11 Aug 2006 05:27:48 +0000 (UTC) (envelope-from lnelson@naxostech.com) Received: from willow.nelsonsoftware.com (86.d8bed1.client.atlantech.net [209.190.216.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 229AA43D49 for ; Fri, 11 Aug 2006 05:27:45 +0000 (GMT) (envelope-from lnelson@naxostech.com) Received: from localhost (localhost [127.0.0.1]) by willow.nelsonsoftware.com (Postfix) with ESMTP id 47069785D for ; Fri, 11 Aug 2006 01:27:45 -0400 (EDT) Received: from willow.nelsonsoftware.com ([127.0.0.1]) by localhost (willow.nelsonsoftware.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19299-09 for ; Fri, 11 Aug 2006 01:27:42 -0400 (EDT) Received: from naxostech.com (localhost [127.0.0.1]) by willow.nelsonsoftware.com (Postfix) with ESMTP id BD18977F5 for ; Fri, 11 Aug 2006 01:27:42 -0400 (EDT) From: "lnelson" To: freebsd-stable@freebsd.org Date: Fri, 11 Aug 2006 01:27:42 -0400 Message-Id: <20060811051959.M95805@naxostech.com> X-Mailer: Open WebMail 2.01 20030425 X-OriginatingIP: 69.139.144.77 (lnelson@naxostech.com) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: amavisd-new at naxostech.com Subject: 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 05:27:48 -0000 Hi Everyone, I'm having an odd problem with the Intel em driver. It's built into the kernel by default, but it won't recognize the part. However, if I grab the driver source from the Intel website, compile it as a KLD, and put it in loader.conf, it works. The odd thing is that it complains that it is already loaded, and acts as if it is refusing to load the module. When it works, the message I get is: module_register: module pci/em already exists! Module pci/em failed to register: 17 ... ... em0: port 0x3000-0x301f mem 0xc8300000-0xc831ffff i rq 18 at device 0.0 on pci5 em0: Ethernet address: 00:30:48:78:5a:2a em0: Speed:N/A Duplex:N/A em1: port 0x3020-0x303f mem 0xc8320000-0xc833ffff i rq 19 at device 0.1 on pci5 em1: Ethernet address: 00:30:48:78:5a:2b em1: Speed:N/A Duplex:N/A When it doesn't work, I get no messages regarding em at all. It seems like the KLD is actually getting loaded, even though it says it isn't. I should mention that I am running the amd64 port of 6.1 RELEASE. Any thoughts? Can I run a production server like this? Thanks, Lee -- Naxos Technology