Re: UEFI GOP: screen goes blank during boot after loader is finished
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
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
> 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
> 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: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On 11/14/18 5:41 AM, Conrad Meyer wrote: > You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL? > I.e., sometimes the CPU chooses to report on a range from 0-225C and > sometimes -49C-206C. I think someone else's 2990WX did the same > thing. I guess that patch never landed? 102°C - 49°C is the very > reasonable 53°C. > > Yeah, sigh, it never landed: https://reviews.freebsd.org/D16855 > > Ok I'll go ahead and commit that too. Applied to 12.0-BETA, Ryzen 7 2700 values are now in the 30-55C range. Looks reasonable. Thanks! ___ 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
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
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
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
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
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
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
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
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
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"
