From owner-freebsd-stable@FreeBSD.ORG Wed Apr 9 22:01:07 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A66D15BB for ; Wed, 9 Apr 2014 22:01:07 +0000 (UTC) Received: from zoom.lafn.org (zoom.lafn.org [108.92.93.123]) by mx1.freebsd.org (Postfix) with ESMTP id 5F2DF18AF for ; Wed, 9 Apr 2014 22:01:07 +0000 (UTC) Received: from [10.0.1.3] (static-71-177-216-148.lsanca.fios.verizon.net [71.177.216.148]) (authenticated bits=0) by zoom.lafn.org (8.14.7/8.14.2) with ESMTP id s39M0xGZ085149 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 9 Apr 2014 15:00:59 -0700 (PDT) (envelope-from bc979@lafn.org) Subject: Re: 9.2 Boot Problem Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset=us-ascii From: Doug Hardie X-Priority: 3 (Normal) In-Reply-To: Date: Wed, 9 Apr 2014 15:00:58 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <0D72DAFC-B019-48B0-AC66-743291ACD4F6@lafn.org> References: <175D3755-BB9B-4EAD-BDAD-06E9670E06AB@lafn.org> <186472F9-A97B-4863-81BC-67BE788D5E9A@lafn.org> <791C8200-023A-4ACB-9B6F-F5A8B0E170F4@lafn.org> <14548387de8.27b7.0b331fcf0b21179f1640bd439e3f4a1e@tundraware.com> <09E89BAA-7A4A-4111-9C11-056902DB3770@lafn.org> To: "Chris H" X-Mailer: Apple Mail (2.1510) X-Virus-Scanned: clamav-milter 0.98 at zoom.lafn.org X-Virus-Status: Clean Cc: Tim Daneliuk , "freebsd-stable@freebsd.org List" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 22:01:07 -0000 On 9 April 2014, at 14:37, "Chris H" wrote: >>=20 >> On 9 April 2014, at 13:40, Tim Daneliuk = wrote: >>=20 >>> Make sure there is a /dev directory on the disk for the kernel to = populate. Without it, >>> the kernel will hang. >>=20 >>=20 >> The disk does have a /dev directory. The system boots fine after you = enter a return. It >> hangs waiting for a return on the keyboard. >>=20 >> This last time I used in /boot/loader.conf: >>=20 >> zool# more loader.conf >> verbose_loading=3D"YES" >> boot_verbose=3D"YES" >> loader_color=3D"NO" >> loader_logo=3D"beastiebw" >> autoboot_delay=3D"10" >>=20 >>=20 >> System behaved the same on boot other than the menu was complete. = However, I did see >> something flash on the left bottom of the screen where the Autoboot = message normally is. It >> was cleared immediately after it was written so there was no way to = read it. Note, this is >> on the serial console. I have not seen that before, but it might = have been there. It was >> just a flash. I am wondering if something is doing the equivalent of = pressing the space bar >> after the autoboot message is displayed. >>=20 >> I checked and the /boot/defaults/loader.conf file is identical = between the system that works >> and those that do not. >=20 >=20 >> I am going to see if the terminal emulator can disable the screen >> control functions so I can see what the message that flashes by is. > dmesg(8) is your friend (/var/run/dmesg.boot). See also = /var/log/messages >=20 > --Chris >=20 > P.S. You only need loader_logo=3D"beastiebw" to get a B/W console. dmesg starts after the boot begins. This problem occurs before that. = Similar issue for console.log and messages. =20