Date: Wed, 20 Jul 2016 10:42:44 -0400 From: Ed Maste <emaste@freebsd.org> To: Eric van Gyzen <vangyzen@freebsd.org> Cc: Karl Denninger <karl@denninger.net>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: 11-Beta1 problem with virtual KVM Message-ID: <CAPyFy2Aq7BwKuE2j8BEJwnbR8hs=7a0YGiOg4ek8a4JiCFdufQ@mail.gmail.com> In-Reply-To: <bd5decf7-7757-2591-783e-998399ad220a@FreeBSD.org> References: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> <CAPed3OG9sa-F_t%2B%2BwTFHydBgHNO20cc_w6eaC7qVOU72rbHRsw@mail.gmail.com> <4e137b8a-4dd4-10c9-7843-83452c217a70@denninger.net> <bd5decf7-7757-2591-783e-998399ad220a@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 July 2016 at 13:22, Eric van Gyzen <vangyzen@freebsd.org> wrote:
>
> You might try adding this to /boot/loader.conf and rebooting:
>
> kern.vty="sc"
>
> That will at least narrow down the problem to the new vt(4).
Or instead, add this:
hw.vga.textmode=1
which will continue using vt(4) but in text mode instead.
Could someone with this issue take a screen capture, and post it
somewhere or email me directly? Also, is this with BIOS/CSM boot, or
UEFI?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Aq7BwKuE2j8BEJwnbR8hs=7a0YGiOg4ek8a4JiCFdufQ>