Date: Sun, 14 Jun 2020 13:17:42 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: dwilde1@gmail.com, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Virtual consoles stopped working Message-ID: <1fd6e537-80f2-ed14-d61b-738c9dbf8bf5@grosbein.net> In-Reply-To: <CAEC73927Ej9ZA00F4JL3i3Meu1kd-N6dm=a7t4vyTE0KA253DA@mail.gmail.com> References: <CAEC73927Ej9ZA00F4JL3i3Meu1kd-N6dm=a7t4vyTE0KA253DA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
14.06.2020 12:21, Donald Wilde wrote: > Since I am using this mule as a dev system for a server-based > application, I have no WM or GUI activated. I really would like to > have the virtual consoles back, and I will gladly learn from what I > did to mess it up. :D Can you boot it with distribution image of the Release to make sure its virtual consoles work fine in same environment? And/or try to interrupt boot at loader stage, break into loader prompt and do: set kern.vty=sc boot To see if your kernel has same problem with syscons(1) console driver.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1fd6e537-80f2-ed14-d61b-738c9dbf8bf5>