From owner-freebsd-questions@freebsd.org Wed Jan 25 04:06:30 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D989CC078B for ; Wed, 25 Jan 2017 04:06:30 +0000 (UTC) (envelope-from john@thehowies.com) Received: from remote.thehowies.com (remote.thehowies.com [50.197.91.218]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "remote.thehowies.com", Issuer "RapidSSL SHA256 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09512EAF for ; Wed, 25 Jan 2017 04:06:29 +0000 (UTC) (envelope-from john@thehowies.com) Received: from PRIMARY.thehowies.local ([fe80::6437:d031:7477:6451]) by PRIMARY.thehowies.local ([fe80::6437:d031:7477:6451%10]) with mapi id 14.03.0339.000; Tue, 24 Jan 2017 20:05:18 -0800 From: John Howie To: David Christensen CC: "freebsd-questions@freebsd.org" Subject: Re: How to capture console messages during boot? Thread-Topic: How to capture console messages during boot? Thread-Index: AQHSdr9sm4Dt/2imqkCzpl8Uw6vUWKFJGQcA Date: Wed, 25 Jan 2017 04:05:16 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [212.76.253.174] Content-Type: text/plain; charset="us-ascii" Content-ID: <683658F16A6B9C46AAD63CABADD34F15@thehowies.local> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 04:06:30 -0000 Hi David, Depending on your hardware, you can use a serial port as the console. If yo= u are running on a server-class machine (from DELL or HP, for example), you= should check the BIOS for this setting. Of course, you then need a serial = cable and another machine to connect from. Also, depending on your equipmen= t, using a serial port as console might disable the graphics/keyboard/mouse= , meaning you get false errors/lack of errors. Another extremely low-tech solution is simply to use your phone to record t= he boot sequence, and replay and pause the video. Simply point at screen an= d start filming! I must admit to having done that a few times... Regards, John > On Jan 25, 2017, at 4:59 AM, David Christensen wrote: >=20 > freebsd-questions: >=20 > I am attempting to build a graphical workstation using: >=20 > toor@freebsd:/root # freebsd-version > 11.0-RELEASE-p7 >=20 > toor@freebsd:/root # uname -a > FreeBSD freebsd 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu S= ep 29 03:40:55 UTC 2016 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/G= ENERIC i386 >=20 > toor@freebsd:/root # pkg info xorg | head -n 1 > xorg-7.7_2 >=20 > toor@freebsd:/root # pkg info xfce | head -n 1 > xfce-4.12_1 >=20 >=20 > As I add software and adjust configuration settings, invariably I create = or encounter issues. Some of these generate warnings/ errors on the consol= e when the system boots. I'd like to capture console messages during boot,= so that I can review them and fix things. >=20 >=20 > How? >=20 >=20 > TIA, >=20 > David >=20 >=20 > p.s. STFW has yielded outdated and/or unsatisfactory solutions, including= : >=20 > dmesg > /var/log/messages > Scroll Lock key and scrollback buffer >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg"