From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 12 22:08:27 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5E20F16A400 for ; Mon, 12 Mar 2007 22:08:27 +0000 (UTC) (envelope-from tim@spyderweb.com.au) Received: from ipmail03.adl2.internode.on.net (ipmail03.adl2.internode.on.net [203.16.214.135]) by mx1.freebsd.org (Postfix) with ESMTP id D411C13C44B for ; Mon, 12 Mar 2007 22:08:26 +0000 (UTC) (envelope-from tim@spyderweb.com.au) Received: from ppp100-124.static.internode.on.net (HELO mail.biocentral-labs.com) ([150.101.100.124]) by ipmail03.adl2.internode.on.net with ESMTP; 13 Mar 2007 08:23:00 +1030 X-IronPort-AV: i="4.14,275,1170595800"; d="scan'208"; a="61531444:sNHT23960349" Received: from [192.168.0.93] (port=61424) by server.biocentral-labs.com with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1HQsRp-000LRj-DM for freebsd-hardware@freebsd.org; Tue, 13 Mar 2007 08:22:58 +1030 Message-ID: <45F5CA49.3010008@spyderweb.com.au> Date: Tue, 13 Mar 2007 08:16:49 +1030 From: Tim Aslat User-Agent: Thunderbird 1.5.0.9 (X11/20070222) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.4 (-) X-Spam-Report: Spam detection software, running on the system "server.biocentral-labs.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Hi All, I have a server I'm building up for production within a small company, and I'm using this particular board. Initially I had trouble with the onboard PATA controller now being recognised, so I got around that with an external USB CD-ROM for installing. My problem is actually concerned with the onboard Intel EtherExpress Pro 1000. I can't make it connect at 1000baseTX at all, although the 100baseTX works fine, as long as I let it autodetect. If I manually configure the 100baseTX using ifconfig, I get a lot of errors on the interface and I'm not sure of the exact cause. [...] Content analysis details: (-1.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP Subject: Intel dq965gf & onboard thernet X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2007 22:08:27 -0000 Hi All, I have a server I'm building up for production within a small company, and I'm using this particular board. Initially I had trouble with the onboard PATA controller now being recognised, so I got around that with an external USB CD-ROM for installing. My problem is actually concerned with the onboard Intel EtherExpress Pro 1000. I can't make it connect at 1000baseTX at all, although the 100baseTX works fine, as long as I let it autodetect. If I manually configure the 100baseTX using ifconfig, I get a lot of errors on the interface and I'm not sure of the exact cause. Currenly installed is the following version of FreeBSD with a custom kernel # uname -a FreeBSD mail.biocentral-labs.com 6.1-RELEASE-p3 FreeBSD 6.1-RELEASE-p3 #2: Wed Oct 11 19:14:10 CST 2006 Kernel mods are include GENERIC ident BIOCENTRAL device smbus # added for smbus hardware monitoring device iicsmb device iicbus device iicbb device iic options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets options IPFILTER #ipfilter support options IPFILTER_LOG #ipfilter logging options IPSTEALTH #support for stealth forwarding options TCPDEBUG options DUMMYNET # reboot if kernel panics options KDB_UNATTENDED options PANIC_REBOOT_WAIT_TIME=16 Currently I'm getting around the problem by using a pci card (Intel Etherexpress BT I think, would have to open the case to check for sure. This is the dmesg output for the onboard ethernet em0: port 0x30c0-0x30df mem 0x50300000-0x5031ffff,0x50324000-0x50324fff irq 20 at device 25.0 on pci0 and this is the dmesg output from the card em1: port 0x1000-0x103f mem 0x50020000-0x5003ffff,0x50000000-0x5001ffff irq 22 at device 1.0 on pci6 Is anyone else using this model mainboard and have a workaround for the ethernet connection speed problem? Regards Tim -- Tim Aslat Spyderweb Consulting http://www.spyderweb.com.au Mobile: +61 0401088479