From owner-freebsd-stable@FreeBSD.ORG Tue Nov 29 00:15:30 2005 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 CC8E716A41F for ; Tue, 29 Nov 2005 00:15:30 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from forrie.com (c-24-62-224-187.hsd1.nh.comcast.net [24.62.224.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 443A743D58 for ; Tue, 29 Nov 2005 00:15:30 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [192.168.1.98] ([192.168.1.98]) (authenticated bits=0) by forrie.com (8.13.4/8.13.4) with ESMTP id jAT0FTT2004984 for ; Mon, 28 Nov 2005 19:15:29 -0500 (EST) (envelope-from forrie@forrie.com) Message-ID: <438B9E14.7040007@forrie.com> Date: Mon, 28 Nov 2005 19:17:24 -0500 From: Forrest Aldrich User-Agent: Thunderbird 1.5 (Windows/20051123) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87/1197/Mon Nov 28 13:09:01 2005 on forrie.com X-Virus-Status: Clean Subject: device em0 not showing up at boot 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: Tue, 29 Nov 2005 00:15:30 -0000 I have an older PC (Compaq AP200) that I'm running FreeBSD-6.0 on. I have an Intel Gigabit interface installed in one of the PCI slots, along with another dual 10/100 Intel in another. The "em0" device does not show up at boot time, and therefore the firewall rules fail. However, if I go in and manually type "ifconfig em0" it then becomes available and I'm able to run dhclient on it, etc. etc. I just did a buildworld/installworld today, so the OS is fairly current. In /etc/rc.conf I have a simple ifconfig_em0="DHCP". I wonder if this is a known problem...