From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 14:23:41 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D03CFDEC for ; Wed, 6 Feb 2013 14:23:41 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 9904AE07 for ; Wed, 6 Feb 2013 14:23:41 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 09:23:41 -0500 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr16.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id CFP65958; Wed, 6 Feb 2013 09:23:40 -0500 X-Auth-ID: anat Received: from pool-71-187-31-131.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([71.187.31.131]) by smtp04.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 09:23:40 -0500 Message-ID: <5112676B.7070202@aldan.algebra.com> Date: Wed, 06 Feb 2013 09:23:39 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: pyunyh@gmail.com Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop References: <5111DE44.7040008@aldan.algebra.com> <5111F739.7070607@aldan.algebra.com> <5111FACB.5040104@aldan.algebra.com> <20130206071324.GB1442@michelle.cdnetworks.com> In-Reply-To: <20130206071324.GB1442@michelle.cdnetworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 14:23:41 -0000 On 06.02.2013 02:13, YongHyeon PYUN wrote: >> Disabling "Wake on LAN" in the BIOS solved this problem. Now xl0 is seen >> >and functional. Solved. > Because I added WOL support xl(4) in the past I'm interested in > knowing whether that change broke your controller when BIOS enables > WOL. I can not reproduce this -- after enabling WOL in BIOS, both kernels (mine and 9.1-R GENERIC) still see xl0 now. Maybe, it is a BIOS issue -- I'm using Lattitude's BIOS version A02, but the last update from Dell before they stopped supporting the laptop is A23. Yours, -mi