From owner-freebsd-arm@freebsd.org Tue Aug 28 00:56:26 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C16DE109B0D6 for ; Tue, 28 Aug 2018 00:56:26 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7532F8B2E2 for ; Tue, 28 Aug 2018 00:56:26 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 120D7267EE for ; Tue, 28 Aug 2018 00:56:26 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f49.google.com with SMTP id e23-v6so634143lfc.13 for ; Mon, 27 Aug 2018 17:56:25 -0700 (PDT) X-Gm-Message-State: APzg51CQ4aTzzmioYgr/WI/hXCteRJAxFOLHUteNrUxVHP2UoKHp8MVw exzqZwnUKIONTQjTloRBxkVClBY7+brTwUk5GvI= X-Google-Smtp-Source: ANB0Vda3ucoRT3lMtoapB/jVJoQSyCkZcVHWPMQe7xuGWBAnsK5mQrQceyrncWaBhfGDZYvYInAQYV3Mrmoj0YzKtPw= X-Received: by 2002:a19:d105:: with SMTP id i5-v6mr10285733lfg.31.1535417784571; Mon, 27 Aug 2018 17:56:24 -0700 (PDT) MIME-Version: 1.0 References: <3C3F2C68-81C2-40F0-8DA0-95D1C55C9938@obsigna.com> In-Reply-To: From: Kyle Evans Date: Mon, 27 Aug 2018 19:56:12 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Serial console of 12.0-ALPHA3 fiddles with the terminal colors To: "Dr. Rolf Jansen" Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2018 00:56:27 -0000 On Mon, Aug 27, 2018 at 7:34 PM Dr. Rolf Jansen wrote: > > > Am 27.08.2018 um 20:22 schrieb Kyle Evans : > > > > On Mon, Aug 27, 2018 at 6:09 PM Dr. Rolf Jansen wrote: > >> > >> Hello, > >> > >> I updated my BeagleBone Black to 12.0-ALPHA3, and now, when booting, t= he serial console behaves differently (I use cu from a Mac Terminal via a F= DTI/USB adapter). > >> > >> When it comes to "Loading kernel...", the terminal color is inverted, = instead of maintaining the usual black on white, all over the sudden everyt= hing is displayed in white on black. And more seriously, the logging before= loading the kernel, is deleted, which means I cannot see the diagnostics o= f the u-boot loader. > >> > >> Is there any setting, to prevent the serial console manipulates color = and content of a terminal session? > >> > > > > Hi, > > > > You want loader_color in your loader.conf(5), which should (hopefully) > > disable all color while still being usable. We force the color scheme > > to white on black if colors are displayed because we can't necessarily > > sample or Q/A our color choice on all possible configurations. > > > > I'll double check on the screen clearing... I don't recall adding any > > extra clears except for password prompts and (re-)drawing the menu. > > > > Thanks, > > > > Kyle Evans > > Thank you for the quick reply. > > I added loader_color=3D"NO" and this didn't change anything. The u-boot l= oader diagnostics is shown in black on white, then the FreeBSD boot loader = takes over, and the first thing, which it does is deleting the u-boot loade= r diagnostics and then it switches the background to black and the followin= g is all white on black. Hmm... I'll take a look at this shortly. If colors are disabled, I think we should be leaving colors alone (full stop), to include the background reset. This must be a bug that I introduced. =3D( > What again is the purpose of setting the color scheme in the serial conso= le? I understand that something shall be set on the real screen, now in a t= erminal window? Think about the poor people who like it green on pink, and = you change it to white on black, come on :-) I blame imp@. =3D) In reality, though, I don't think we had a good reason for not allowing it by default and moving to a world where we just respect loader_color simplified quite a bit that was originally written to check if we're writing to a serial console. > Bets regards > > Rolf