Date: Wed, 14 Nov 2018 06:49:03 -0600 From: Kyle Evans <kevans@freebsd.org> To: rebecca@bluestop.org Cc: freebsd-virtualization@freebsd.org, Mr Dandy <subbsd@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org>, "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net> Subject: Re: UEFI GOP: screen goes blank during boot after loader is finished Message-ID: <CACNAnaHxVtKWMPqimeK9_=YTsW8=BpcdToh1Xm5xsGgjjcHTUQ@mail.gmail.com> In-Reply-To: <16238656.sFgvYJuXru@photon.int.bluestop.org> References: <etPan.5beaf3b9.4c02f255.a98c@bluestop.org> <CAFt_eMpWZh4SZuNLkgCsgAN=RNbHHsENNwbV1NLs=7dsyYPFnQ@mail.gmail.com> <CACNAnaHLW2xrnuzD%2BLZxXG8EFxuuN-6r75w_6B%2Bo4OcgPs4y_A@mail.gmail.com> <16238656.sFgvYJuXru@photon.int.bluestop.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 13, 2018 at 9:53 PM Rebecca Cran <rebecca@bluestop.org> wrote: > > On Tuesday, 13 November 2018 18:57:25 MST Kyle Evans wrote: > > > However, because loader-land is funny in a not-ha-ha kind of way, can > > you try replacing loader.efi on your guest VM with the Forth-flavored > > version to rule that out or narrow it down, please? > > That didn't help. > As probably expected, the last output before the screen goes blank is > framebuffer information: > > /boot/kernel/kernel text=0x16776f0 data=0x1cd288+0x768b40 > syms=[0x8+0x174ca8+0x8+0x192218] > Booting... > Start @ 0xffffffff80341000 ... > EFI framebuffer information: > addr, size 0xc1000000, 0x1000000 > dimensions 800 x 600 > stride 800 > masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 > Good, good, so the loader <-> kernel transition would appear to be intact and information appears good at first blush. If you don't have time to dig into this, I'll try poking at it this weekend, but it looks to be either kernel problem or VNC server. Thanks, Kyle Evans
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaHxVtKWMPqimeK9_=YTsW8=BpcdToh1Xm5xsGgjjcHTUQ>