Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 9 Apr 2014 15:00:58 -0700
From:      Doug Hardie <bc979@lafn.org>
To:        "Chris H" <bsd-lists@bsdforge.com>
Cc:        Tim Daneliuk <tundra@tundraware.com>, "freebsd-stable@freebsd.org List" <freebsd-stable@freebsd.org>
Subject:   Re: 9.2 Boot Problem
Message-ID:  <0D72DAFC-B019-48B0-AC66-743291ACD4F6@lafn.org>
In-Reply-To: <acf29fd624b9f7e76370e9335374f370.authenticated@ultimatedns.net>
References:  <175D3755-BB9B-4EAD-BDAD-06E9670E06AB@lafn.org> <186472F9-A97B-4863-81BC-67BE788D5E9A@lafn.org> <a865b8f2ccb9ad4918544bad3d49554d.authenticated@ultimatedns.net> <791C8200-023A-4ACB-9B6F-F5A8B0E170F4@lafn.org> <14548387de8.27b7.0b331fcf0b21179f1640bd439e3f4a1e@tundraware.com> <09E89BAA-7A4A-4111-9C11-056902DB3770@lafn.org> <acf29fd624b9f7e76370e9335374f370.authenticated@ultimatedns.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On 9 April 2014, at 14:37, "Chris H" <bsd-lists@bsdforge.com> wrote:

>>=20
>> On 9 April 2014, at 13:40, Tim Daneliuk <tundra@tundraware.com> =
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






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0D72DAFC-B019-48B0-AC66-743291ACD4F6>