Re: UEFI GOP: screen goes blank during boot after loader is finished

[Subbsd]

Hi,



On Tue, Nov 13, 2018 at 7:22 PM Rodney W. Grimes
 wrote:
>
> Uh oh, ok, thats not what I was thinking of then.  I do not have any
> bhyve capable hardware running on 12BETA at this time to test with.
>
> I wonder if we have a bad interaction between the loader and
> bhyve again, we have had a few of those.
>

it's broken before 12-ALPHA1, my post from 14-Sep to current@

https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071206.html

probably the lua loader doesn't understand efifb/term very well
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Kyle Evans]

On Tue, Nov 13, 2018 at 5:15 PM Subbsd  wrote:
>
> Hi,
>
>
>
> On Tue, Nov 13, 2018 at 7:22 PM Rodney W. Grimes
>  wrote:
> >
> > Uh oh, ok, thats not what I was thinking of then.  I do not have any
> > bhyve capable hardware running on 12BETA at this time to test with.
> >
> > I wonder if we have a bad interaction between the loader and
> > bhyve again, we have had a few of those.
> >
>
> it's broken before 12-ALPHA1, my post from 14-Sep to current@
>
> https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071206.html
>
> probably the lua loader doesn't understand efifb/term very well

These things are basically completely unrelated- the interpreter
included in loader(8) doesn't have to know anything about graphics and
this stuff is handled before and after the interpreter is invoked.

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?

Thanks,

Kyle Evans
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Rebecca Cran]

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 @ 0x80341000 ...
EFI framebuffer information:
addr, size   0xc100, 0x100
dimensions   800 x 600
stride 800
masks  0x00ff, 0xff00, 0x00ff, 0xff00

-- 
Rebecca


___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Kyle Evans]

On Tue, Nov 13, 2018 at 9:53 PM Rebecca Cran  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 @ 0x80341000 ...
> EFI framebuffer information:
> addr, size   0xc100, 0x100
> dimensions   800 x 600
> stride 800
> masks  0x00ff, 0xff00, 0x00ff, 0xff00
>

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
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Subbsd]

On Wed, Nov 14, 2018 at 3:49 PM Kyle Evans  wrote:

> 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.

FreeBSD 11.{1,2} and various Linux distros boot fine with UEFI GOP in
the same time, the problem is only with FreeBSD 12-ALPHA+.
Therefore it does not look like VNC server issue.
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Rodney W. Grimes]

> On Tue, Nov 13, 2018 at 5:15 PM Subbsd  wrote:
> >
> > Hi,
> >
> >
> >
> > On Tue, Nov 13, 2018 at 7:22 PM Rodney W. Grimes
> >  wrote:
> > >
> > > Uh oh, ok, thats not what I was thinking of then.  I do not have any
> > > bhyve capable hardware running on 12BETA at this time to test with.
> > >
> > > I wonder if we have a bad interaction between the loader and
> > > bhyve again, we have had a few of those.
> > >
> >
> > it's broken before 12-ALPHA1, my post from 14-Sep to current@
> >
> > https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071206.html
> >
> > probably the lua loader doesn't understand efifb/term very well
> 
> These things are basically completely unrelated- the interpreter
> included in loader(8) doesn't have to know anything about graphics and
> this stuff is handled before and after the interpreter is invoked.
> 
> 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?
> 
> Thanks,

Am I miss remebering or didn't we solve a similiar problem
earlier in the release cycle?   Perhaps that was with non
GOP console only.

Either way, we need to make sure this is resolved.  Sad state is
I do not have any access until after the holiday most likely to
any hardware that I can use to work on this problem.

Please keep me in the loop though, I am reading emails each morning,
and as times allow during the day.

Thanks,
-- 
Rod Grimes rgri...@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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Rodney W. Grimes]

> On Wed, Nov 14, 2018 at 3:49 PM Kyle Evans  wrote:
> 
> > 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.
> 
> FreeBSD 11.{1,2} and various Linux distros boot fine with UEFI GOP in
> the same time, the problem is only with FreeBSD 12-ALPHA+.
> Therefore it does not look like VNC server issue.

Lets make sure this is not the invalid instruction trap (CLFLUSH)
that has already been fixed by BETA3.  Is everyone infact using
BETA3 or later as a guest?   We know of and have fixed this other
bug and I want to make sure we are not chassing a red hearing.

Thanks,
-- 
Rod Grimes rgri...@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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Subbsd]

On Wed, Nov 14, 2018 at 6:52 PM Rodney W. Grimes
 wrote:
>
> > On Wed, Nov 14, 2018 at 3:49 PM Kyle Evans  wrote:
> >
> > > 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.
> >
> > FreeBSD 11.{1,2} and various Linux distros boot fine with UEFI GOP in
> > the same time, the problem is only with FreeBSD 12-ALPHA+.
> > Therefore it does not look like VNC server issue.
>
> Lets make sure this is not the invalid instruction trap (CLFLUSH)
> that has already been fixed by BETA3.  Is everyone infact using
> BETA3 or later as a guest?   We know of and have fixed this other
> bug and I want to make sure we are not chassing a red hearing.


My current host: FreeBSD 13.0-CURRENT r340319  and the problem is
still present. As I recall, I first encountered this problem when
FreeBSD-CURRENT (12) moved to the ALPHA-1 state. At least a month
before the ALPHA-1, everything worked fine. At this time, the
bootloader was changed to work with lua (and the distinguishing
feature is that during this transition the boot menu lost color in the
UEFI GOP mode).
So, the first thing I thought was that it was related to the lua based
menu. Now we know that it is not. However, the root of the problem
lies at this time.
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Rebecca Cran]

On November 14, 2018 at 2:18:04 PM, Subbsd 
(sub...@gmail.com(mailto: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.






___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Subbsd]

On Thu, Nov 15, 2018 at 12:21 AM Rebecca Cran  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
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Subbsd]

On Thu, Nov 15, 2018 at 1:05 AM Subbsd  wrote:
>
> On Thu, Nov 15, 2018 at 12:21 AM Rebecca Cran  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
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Kyle Evans]

On Wed, Nov 14, 2018 at 4:23 PM Subbsd  wrote:
>
> On Thu, Nov 15, 2018 at 1:05 AM Subbsd  wrote:
> >
> > On Thu, Nov 15, 2018 at 12:21 AM Rebecca Cran  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.
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Kyle Evans]

On Wed, Nov 14, 2018 at 4:30 PM Kyle Evans  wrote:
>
> On Wed, Nov 14, 2018 at 4:23 PM Subbsd  wrote:
> >
> > On Thu, Nov 15, 2018 at 1:05 AM Subbsd  wrote:
> > >
> > > On Thu, Nov 15, 2018 at 12:21 AM Rebecca Cran  
> > > 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/bhyveload.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.
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Subbsd]

On Thu, Nov 15, 2018 at 1:33 AM Kyle Evans  wrote:
>
> On Wed, Nov 14, 2018 at 4:30 PM Kyle Evans  wrote:
> >
> > On Wed, Nov 14, 2018 at 4:23 PM Subbsd  wrote:
> > >
> > > On Thu, Nov 15, 2018 at 1:05 AM Subbsd  wrote:
> > > >
> > > > On Thu, Nov 15, 2018 at 12:21 AM Rebecca Cran  
> > > > 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/bhyveload.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.iso
-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
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Kyle Evans]

On Wed, Nov 14, 2018 at 4:55 PM Subbsd  wrote:
>
> On Thu, Nov 15, 2018 at 1:33 AM Kyle Evans  wrote:
> >
> > On Wed, Nov 14, 2018 at 4:30 PM Kyle Evans  wrote:
> > >
> > > On Wed, Nov 14, 2018 at 4:23 PM Subbsd  wrote:
> > > >
> > > > On Thu, Nov 15, 2018 at 1:05 AM Subbsd  wrote:
> > > > >
> > > > > On Thu, Nov 15, 2018 at 12:21 AM Rebecca Cran  
> > > > > 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/bhyveload.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.iso
> -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?
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Warner Losh]

On Wed, Nov 14, 2018 at 4:00 PM Kyle Evans  wrote:

> On Wed, Nov 14, 2018 at 4:55 PM Subbsd  wrote:
> >
> > On Thu, Nov 15, 2018 at 1:33 AM Kyle Evans  wrote:
> > >
> > > On Wed, Nov 14, 2018 at 4:30 PM Kyle Evans  wrote:
> > > >
> > > > On Wed, Nov 14, 2018 at 4:23 PM Subbsd  wrote:
> > > > >
> > > > > On Thu, Nov 15, 2018 at 1:05 AM Subbsd  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/bhyveload.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.iso
> > -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
___
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"

RE: UEFI GOP: screen goes blank during boot after loader is finished

[Matt Churchyard]

-Original Message-
From: owner-freebsd-virtualizat...@freebsd.org 
 On Behalf Of Warner Losh
Sent: 15 November 2018 02:57
To: Kyle Evans 
Cc: FreeBSD Current ; Rodney W. Grimes 
; 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  wrote:

> On Wed, Nov 14, 2018 at 4:55 PM Subbsd  wrote:
> >
> > On Thu, Nov 15, 2018 at 1:33 AM Kyle Evans  wrote:
> > >
> > > On Wed, Nov 14, 2018 at 4:30 PM Kyle Evans  wrote:
> > > >
> > > > On Wed, Nov 14, 2018 at 4:23 PM Subbsd  wrote:
> > > > >
> > > > > On Thu, Nov 15, 2018 at 1:05 AM Subbsd  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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Rebecca Cran]

On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote:

> What is the ConOut evifar look like? We set serial when the UEFI env says
> to do  so.

Booting with:

sudo bhyve -A -P -c 2 -H -m 4G -s 0:0,hostbridge -s 31:0,lpc -s 2,ahci-
cd,FreeBSD-12.0-BETA4-amd64-disc1.iso -s 
29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -l bootrom,/usr/local/share/uefi-
firmware/BHYVE_UEFI.fd -u vm5

dh in the shell shows:

7D: ConsoleOut SimpleTextOut GraphicsOutput(GraphicsOutput)
PCIIO DevicePath(PciRoot (0x0)/Pci(0x1D,0x0))

84: StdErr ConsoleOut ConsoleIn SimpleTextOut SimpleTextInEx SimpleTextIn 
DevicePath(t(115200,8,N,1)/VenVt100Plus())

89: SimpleTextOut SimpleTextInEx SimpleTextIn DevicePath(Uart(115200,8,N,1)/
VenPcAnsi())

-- 
Rebecca


___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Marcelo Araujo]

Hi,

I have the same issue on FreeBSD-HEAD as host and with FreeBSD-HEAD as
guest.

Em sex, 16 de nov de 2018 às 03:10, Rebecca Cran via freebsd-virtualization
 escreveu:

> On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote:
>
> > What is the ConOut evifar look like? We set serial when the UEFI env says
> > to do  so.
>
> Booting with:
>
> sudo bhyve -A -P -c 2 -H -m 4G -s 0:0,hostbridge -s 31:0,lpc -s 2,ahci-
> cd,FreeBSD-12.0-BETA4-amd64-disc1.iso -s
> 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -l
> bootrom,/usr/local/share/uefi-
> firmware/BHYVE_UEFI.fd -u vm5
>
> dh in the shell shows:
>
> 7D: ConsoleOut SimpleTextOut GraphicsOutput(GraphicsOutput)
> PCIIO DevicePath(PciRoot (0x0)/Pci(0x1D,0x0))
>
> 84: StdErr ConsoleOut ConsoleIn SimpleTextOut SimpleTextInEx SimpleTextIn
> DevicePath(t(115200,8,N,1)/VenVt100Plus())
>
> 89: SimpleTextOut SimpleTextInEx SimpleTextIn
> DevicePath(Uart(115200,8,N,1)/
> VenPcAnsi())
>
> --
> Rebecca
>
>
> ___
> 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"
>


-- 

-- 
Marcelo Araujo(__)ara...@freebsd.org
\\\'',)http://www.FreeBSD.org    \/  \ ^
Power To Server. .\. /_)
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Warner Losh]

On Thu, Nov 15, 2018 at 12:10 PM Rebecca Cran  wrote:

> On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote:
>
> > What is the ConOut evifar look like? We set serial when the UEFI env says
> > to do  so.
>
> Booting with:
>
> sudo bhyve -A -P -c 2 -H -m 4G -s 0:0,hostbridge -s 31:0,lpc -s 2,ahci-
> cd,FreeBSD-12.0-BETA4-amd64-disc1.iso -s
> 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -l
> bootrom,/usr/local/share/uefi-
> firmware/BHYVE_UEFI.fd -u vm5
>
> dh in the shell shows:
>
> 7D: ConsoleOut SimpleTextOut GraphicsOutput(GraphicsOutput)
> PCIIO DevicePath(PciRoot (0x0)/Pci(0x1D,0x0))
>
> 84: StdErr ConsoleOut ConsoleIn SimpleTextOut SimpleTextInEx SimpleTextIn
> DevicePath(t(115200,8,N,1)/VenVt100Plus())
>
> 89: SimpleTextOut SimpleTextInEx SimpleTextIn
> DevicePath(Uart(115200,8,N,1)/
> VenPcAnsi())
>

If I read that right, then the ConOut variable first has the video device
listed, then the serial port (this wasn't the form I expected to see it in,
so I'm not sure thats the case). In either event, we should get console
output on both the serial and the video at least until the /etc/rc script
starts...

Warner
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Subbsd]

On Fri, Nov 16, 2018 at 8:03 AM Warner Losh  wrote:
>
>
>
> On Thu, Nov 15, 2018 at 12:10 PM Rebecca Cran  wrote:
>>
>> On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote:
>>
>> > What is the ConOut evifar look like? We set serial when the UEFI env says
>> > to do  so.
>>
>> Booting with:
>>
>> sudo bhyve -A -P -c 2 -H -m 4G -s 0:0,hostbridge -s 31:0,lpc -s 2,ahci-
>> cd,FreeBSD-12.0-BETA4-amd64-disc1.iso -s
>> 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -l bootrom,/usr/local/share/uefi-
>> firmware/BHYVE_UEFI.fd -u vm5
>>
>> dh in the shell shows:
>>
>> 7D: ConsoleOut SimpleTextOut GraphicsOutput(GraphicsOutput)
>> PCIIO DevicePath(PciRoot (0x0)/Pci(0x1D,0x0))
>>
>> 84: StdErr ConsoleOut ConsoleIn SimpleTextOut SimpleTextInEx SimpleTextIn
>> DevicePath(t(115200,8,N,1)/VenVt100Plus())
>>
>> 89: SimpleTextOut SimpleTextInEx SimpleTextIn DevicePath(Uart(115200,8,N,1)/
>> VenPcAnsi())
>
>
> If I read that right, then the ConOut variable first has the video device 
> listed, then the serial port (this wasn't the form I expected to see it in, 
> so I'm not sure thats the case). In either event, we should get console 
> output on both the serial and the video at least until the /etc/rc script 
> starts...
>
> Warner

Perhaps this is not a special case of FreeBSD guest, since the latest
versions of FreeBSD are loaded normally in other UEFI systems (e.g
Virtualbox, KVM). For example someone from CBSD Telegram chat reported
a similar problem for OpenIndiana 2018 ( which uses FreeBSD loader
however) in bhyve.
Thus, perhaps the root of this problem should be sought in
uefi-edk2-bhyve the package. Latest CBSD release (12.0.1) fixed this
problem by disabling serial console. However, CBSD uses an alternative
boot method  for bhyve ( uefi-edk2-bhyve + reFIND )
___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Toomas Soome]

> On 17 Nov 2018, at 18:29, Subbsd  wrote:
> 
> On Fri, Nov 16, 2018 at 8:03 AM Warner Losh  > wrote:
>> 
>> 
>> 
>> On Thu, Nov 15, 2018 at 12:10 PM Rebecca Cran  wrote:
>>> 
>>> On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote:
>>> 
 What is the ConOut evifar look like? We set serial when the UEFI env says
 to do  so.
>>> 
>>> Booting with:
>>> 
>>> sudo bhyve -A -P -c 2 -H -m 4G -s 0:0,hostbridge -s 31:0,lpc -s 2,ahci-
>>> cd,FreeBSD-12.0-BETA4-amd64-disc1.iso -s
>>> 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -l bootrom,/usr/local/share/uefi-
>>> firmware/BHYVE_UEFI.fd -u vm5
>>> 
>>> dh in the shell shows:
>>> 
>>> 7D: ConsoleOut SimpleTextOut GraphicsOutput(GraphicsOutput)
>>> PCIIO DevicePath(PciRoot (0x0)/Pci(0x1D,0x0))
>>> 
>>> 84: StdErr ConsoleOut ConsoleIn SimpleTextOut SimpleTextInEx SimpleTextIn
>>> DevicePath(t(115200,8,N,1)/VenVt100Plus())
>>> 
>>> 89: SimpleTextOut SimpleTextInEx SimpleTextIn DevicePath(Uart(115200,8,N,1)/
>>> VenPcAnsi())
>> 
>> 
>> If I read that right, then the ConOut variable first has the video device 
>> listed, then the serial port (this wasn't the form I expected to see it in, 
>> so I'm not sure thats the case). In either event, we should get console 
>> output on both the serial and the video at least until the /etc/rc script 
>> starts...
>> 
>> Warner
> 
> Perhaps this is not a special case of FreeBSD guest, since the latest
> versions of FreeBSD are loaded normally in other UEFI systems (e.g
> Virtualbox, KVM). For example someone from CBSD Telegram chat reported
> a similar problem for OpenIndiana 2018 ( which uses FreeBSD loader
> however) in bhyve.
> Thus, perhaps the root of this problem should be sought in
> uefi-edk2-bhyve the package. Latest CBSD release (12.0.1) fixed this
> problem by disabling serial console. However, CBSD uses an alternative
> boot method  for bhyve ( uefi-edk2-bhyve + reFIND )
> ___

You can not yet bring in OpenIndiana into the game because it does not have FB 
console support - it *only* can use serial console with UEFI. 

rgds,
toomas

___
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"

Re: UEFI GOP: screen goes blank during boot after loader is finished

[Rebecca Cran]

On Saturday, 17 November 2018 09:29:34 MST Subbsd wrote:

> Thus, perhaps the root of this problem should be sought in
> uefi-edk2-bhyve the package. Latest CBSD release (12.0.1) fixed this
> problem by disabling serial console. However, CBSD uses an alternative
> boot method  for bhyve ( uefi-edk2-bhyve + reFIND )

Another data point is that OVMF (UEFI version 2.70) running under Qemu the 
problem doesn't occur.

-- 
Rebecca


___
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"