-----Original Message----- From: owner-freebsd-virtualizat...@freebsd.org <owner-freebsd-virtualizat...@freebsd.org> On Behalf Of Warner Losh Sent: 15 November 2018 02:57 To: Kyle Evans <kev...@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>; Rodney W. Grimes <freebsd-...@pdx.rh.cn85.dnsmgr.net>; freebsd-virtualizat...@freebsd.org Subject: Re: UEFI GOP: screen goes blank during boot after loader is finished
On Wed, Nov 14, 2018 at 4:00 PM Kyle Evans <kev...@freebsd.org> wrote: > On Wed, Nov 14, 2018 at 4:55 PM Subbsd <sub...@gmail.com> wrote: > > > > On Thu, Nov 15, 2018 at 1:33 AM Kyle Evans <kev...@freebsd.org> wrote: > > > > > > On Wed, Nov 14, 2018 at 4:30 PM Kyle Evans <kev...@freebsd.org> wrote: > > > > > > > > On Wed, Nov 14, 2018 at 4:23 PM Subbsd <sub...@gmail.com> wrote: > > > > > > > > > > On Thu, Nov 15, 2018 at 1:05 AM Subbsd <sub...@gmail.com> wrote: > > > > > > > > > > > > On Thu, Nov 15, 2018 at 12:21 AM Rebecca Cran < > rebe...@bluestop.org> wrote: > > > > > > > > > > > > > > On November 14, 2018 at 2:18:04 PM, Subbsd > > > > > > > (sub...@gmail.com) > wrote: > > > > > > >> > > > > > > >> > > > > > > >> My current host: FreeBSD 13.0-CURRENT r340319 and the > > > > > > >> problem > is > > > > > > >> still present. > > > > > > > > > > > > > > Rod was asking about the guest OS version, not the host though. > > > > > > > > > > > > > > > > > > > > > > > > > > I apologize, it seemed to me that I wrote earlier) Guest version: > > > > > > > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0 > /FreeBSD-13.0-CURRENT-amd64-20181101-r339979-disc1.iso.xz > > > > > > > > > > Hm, it seems the problem is 'boot_serial' which is sets to YES > > > > > by > default in gop > > > > > > > > > > set boot_serial=NO > > > > > boot > > > > > > > > > > solve this issue > > > > > > > > Huh? This is perhaps going to be a stupid question, but where is > > > > boot_serial=YES getting set? Loader will not set it by itself > > > > and > UEFI > > > > doesn't respect /boot.config, so this must be explicitly set in > > > > /boot/loader.conf or /boot/defaults/loader.conf, but it's not > > > > clear > to > > > > me what's putting it there. > > > > > > > http://src.illumos.org/source/xref/freebsd-head/usr.sbin/bhyveload/bhy > veload.c#832 > > > is the only place I can see immediately that this might be > > > happening, but do UEFI boots go through bhyveload? I'm ignorant here. > > > > This is UEFI GOP methodvia bootrom/uefi-firmware, no bhyveload: > > > > bhyve -AHP -s 0:0,hostbridge -s 31:0,lpc -s > > 4:0,ahci-cd,/tmp/FreeBSD-13.0-CURRENT-amd64-20181101-r339979-disc1.i > > so -c 1 -m 1024M -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -l > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd freebsd1 > > > > https://snag.gy/0MH7zU.jpg > > https://snag.gy/kF5cxZ.jpg > > https://snag.gy/htHMG0.jpg > > https://snag.gy/vK1ALN.jpg > > https://snag.gy/qKNPGU.jpg > > What does your /boot/loader.conf look like? > >What is the ConOut evifar look like? We set serial when the UEFI env says to >do so. >Warner I can confirm that 11.2-REL boots fine but 12.0-BETA4 goes blank just after the loader, using the exact same bhyve configuration. (This is on an 11.2 host) A few lines are output just before going blank but I can't catch what they say. I'm using the official ISO files with no other configuration so it does seem that 12.0 will currently not boot under UEFI-GOP bhyve. I can check the efivars if someone lets me know how. Matt _______________________________________________ freebsd-virtualizat...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
