Date: Wed, 26 Jan 2022 12:35:26 +0100 From: Jesper Schmitz Mouridsen <jsm@FreeBSD.org> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-arm@freebsd.org, Warner Losh <imp@bsdimp.com> Subject: Re: pinebook pro video console not active Message-ID: <66042fd4-31fa-408a-3ec8-b911118750ef@FreeBSD.org> In-Reply-To: <20220126115453.255661b2e55f946d11eba1e9@bidouilliste.com> References: <4d738da2-28f0-6af2-4213-934244cc95f2@FreeBSD.org> <20220126115453.255661b2e55f946d11eba1e9@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi On 26.01.2022 11.54, Emmanuel Vadot wrote: > On Wed, 26 Jan 2022 00:44:33 +0100 > Jesper Schmitz Mouridsen <jsm@FreeBSD.org> wrote: > >> Hi >> >> On Pinebook Pro 14-current with console="efi,comconsole" in >> /boot/loader.conf >> vidcontrol -i active < /dev/console is not working because serial stays >> primary. Reverting 123b5b8763778e83b6816ad9db62a9b956055c32 fixes that >> for me. Can someone share some light on why that is? > You also need boot_multicons=YES in loader.conf for this to work (at > least on amd64). > Maybe imp@ knows more about this behavior. > Yes I have that set as well, my loader.conf is hw.regulator.disable_unused="0" boot_multicons="YES" console="efi,comconsole" beastie_disable="NO" loader_color="YES" ums_load=YES >> console kit relies on /dev/console beeing active so it is an annoying >> bug.. >> the original review is here https://reviews.freebsd.org/D32992 >> >> >> Thanks >> /jsm >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?66042fd4-31fa-408a-3ec8-b911118750ef>