From owner-freebsd-current@FreeBSD.ORG Mon Nov 12 06:55:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 303AD16A41B for ; Mon, 12 Nov 2007 06:55:16 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.org [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id E98D513C4A7 for ; Mon, 12 Nov 2007 06:55:15 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:59783 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IrTCA-000Kql-7o for freebsd-current@freebsd.org; Mon, 12 Nov 2007 06:54:54 +0000 Message-ID: <4737F8BD.40304@conducive.net> Date: Mon, 12 Nov 2007 06:54:53 +0000 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <47375D78.4040309@chuckr.org> <20071112005620.GA87383@cdnetworks.co.kr> <4737BCC3.5030509@chuckr.org> <20071112044340.GC87383@cdnetworks.co.kr> In-Reply-To: <20071112044340.GC87383@cdnetworks.co.kr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: nfe internet problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2007 06:55:16 -0000 Pyun YongHyeon wrote: > On Sun, Nov 11, 2007 at 09:38:59PM -0500, Chuck Robey wrote: > > Pyun YongHyeon wrote: *trimmed* > > > > OK, I just finished getting a verbose boot. Wouldn't you know it? The > > nfe ports aren't even recognized now. I have them static in the kernel > > (so they don't need kldloading) but I can offer you no probing info. I > > can find the nfe by using kldstat -v, so it's in the kernel (and i > > checked, an attempt to load it anyhow fails). I haven't any idea why it > > would not be probed, it's on the motherboard (an Asus Striker Extreme) > > If nfe(4) was loaded successfully and identified ethernet controller > it should have printed some information for the device.(You can check > it before invoking ifconfig(8)). If it's not detected by nfe(4) I > guess nfe(4) is not guilty for the issue. > It would be even better if you can post the output of "pciconf -lcv". > > > and needs only to have the bios agree to allow it, which it was. Hmm, I > > think I will reboot and check the bios again anyhow. Won't hurt > > anything, I guess. > > > > Your BIOS may have a ASF option for ethernet. Try toggling the option. > Side issue, but perhaps related (BIOS?) - the Asus P5K with Alantec NIC doesn't load any driver in probes *either*, but at least reports somthing is there; Extracts: (an older 7-CURRENT from September ISO); pcib4: irq 16 at device 28.5 on pci0 pci2: on pcib4 pci2: at device 0.0 (no driver attached) .. (8-CURRENT form 17 OCtober) pcib4: irq 16 at device 28.5 on pci0 pci2: on pcib4 pci2: at device 0.0 (no driver attached) That the OP's scan has gone totally 'blind' to the nfe suggests it might be a good idea to physically reset the MB BIOS by jumper, then start over. Gigabyte (often!), and Asus, (sometimes) get their BIOS knickers in a knot after many soft changes and go into unplanned states. Bill