Re: UEFI + SOL / COM ports = boot hang

The default state of this server is that FreeBSD hangs when booting off UEFI and the COM ports are enabled. That seems to be because console includes or adds "efi" by default. Under every circumstance I've tested, when console contains "efi", the server hangs at the same point shown in the first

Re: UEFI boot hangs after loading kernel with efi_max_resolution="4k"

With Toomas's help (thanks!), I was able to partially resolve the hang and blank screen at boot issue, for the record, for now this can be solved by adding: screen.font="16x32" in /boot/loader.conf; no more efi_max_resolution setting is needed. Setting allscreen_flags to load font still panics t

Re: uefi(8) fails to boot from ZFS with compression=zstd

Does it boot when you copy loader.efi to bootx64.efi? Toomas > On 23. Oct 2020, at 05:02, Jan Beich wrote: > > After r366657 (currently, on r366953) I've tried to boot from a > compression=zstd dataset but it failed to reach loader(8), see below. > However, switching to CSM path (boot1.efi ->

Re: uefi(8) fails to boot from ZFS with compression=zstd

Toomas Soome writes: > >> On 23. Oct 2020, at 05:02, Jan Beich wrote: >> >> After r366657 (currently, on r366953) I've tried to boot from a >> compression=zstd dataset but it failed to reach loader(8), see below. >> However, switching to CSM path (boot1.efi -> gptzfsboot) makes it work. >> >>

Re: UEFI and loader.efi in base/head past r355103

On Mon, 16 Dec 2019 10:27+0200, Toomas Soome wrote: > Also make sure you do have updated firmware. 1.22 is the latest one. > r355347 by itself does not really look like it should cause infinite loop on > normal input, but there we would need to check what we do get from keypress > and then we

Re: UEFI and loader.efi in base/head past r355103

> On 16. Dec 2019, at 08:30, Trond Endrestøl > wrote: > > On Sun, 15 Dec 2019 20:41+0100, Trond Endrestøl wrote: > >> I updated the loader.efi stored in the ESP of my laptop, Lenovo >> ThinkPad E590T (20NB), running boot firmware 1.22, as I wanted to try >> out base/head r355441. >> >> As

Re: UEFI and loader.efi in base/head past r355103

On Sun, 15 Dec 2019 20:41+0100, Trond Endrestøl wrote: > I updated the loader.efi stored in the ESP of my laptop, Lenovo > ThinkPad E590T (20NB), running boot firmware 1.22, as I wanted to try > out base/head r355441. > > As soon as I press a button, say 2 or 3, the loader freezes. > Ctrl+Alt+

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

from Niclas Zeising and my previous post: > > On 6/22/2019 20:16, Thomas Mueller wrote: > > > I am trying to set up UEFI to boot my FreeBSD and NetBSD installations, > > > and later, Linux. > > Easy.  Refind should do that and allow selection from a menu. > I wrote this as an instruction on ho

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On 6/23/2019 02:36, Thomas Mueller wrote: > from Karl Denninger and my previous post: > >>> This is scary (Bitlocker), sent me to Wikipedia to look up Bitlocker. >>> >>> Can you turn Bitlocker off after turning it on and get your system back? >> You SHOULD (better have!) kept the recovery key.  If

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On 2019-06-23 04:56, Karl Denninger wrote: On 6/22/2019 20:16, Thomas Mueller wrote: I am trying to set up UEFI to boot my FreeBSD and NetBSD installations, and later, Linux. Easy.  Refind should do that and allow selection from a menu. I wrote this as an instruction on how to get FreeBSD

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On Sun, 23 Jun 2019, 09:41 Thomas Mueller, wrote: > Can rEFInd find and boot FreeBSD, NetBSD, Haiku, etc? > > I don't see any refind, however partially capitalized, in FreeBSD base > system or ports, or NetBSD base system or pkgsrc. I find efibootmgr now in > FreeBSD, but not NetBSD, base system

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

from Karl Denninger and my previous post: > > This is scary (Bitlocker), sent me to Wikipedia to look up Bitlocker. > > Can you turn Bitlocker off after turning it on and get your system back? > You SHOULD (better have!) kept the recovery key.  If you have it, you > can boot with it.  Then turn

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On 6/22/2019 20:16, Thomas Mueller wrote: > from Karl Denninger: > >> On 6/22/2019 14:05, Rebecca Cran wrote: >>> On 2019-06-22 12:59, Karl Denninger wrote: I use Refind for this sort of thing and it has (thus far!) survived upgrades.  The only "gotcha" is that I had a Windows 10 "Featur

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

from Karl Denninger: > On 6/22/2019 14:05, Rebecca Cran wrote: > > On 2019-06-22 12:59, Karl Denninger wrote: > >> I use Refind for this sort of thing and it has (thus far!) survived > >> upgrades.  The only "gotcha" is that I had a Windows 10 "Feature" > >> upgrade that reset the default boot in

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

rg Subject: Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to? On 2019-06-22 13:34, Karl Denninger wrote: > > All I had to do was put the EFI loader in a directory under the UEFI > partition and Refind found it.  I didn't have to specifically tell it >

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On 2019-06-22 13:34, Karl Denninger wrote: > > All I had to do was put the EFI loader in a directory under the UEFI > partition and Refind found it.  I didn't have to specifically tell it > that it was there. Sorry, I'm not talking about rEFInd. I know how great it is. I'm talking about systems

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On 6/22/2019 14:05, Rebecca Cran wrote: > On 2019-06-22 12:59, Karl Denninger wrote: >> I use Refind for this sort of thing and it has (thus far!) survived >> upgrades.  The only "gotcha" is that I had a Windows 10 "Feature" >> upgrade that reset the default boot in the firmware to Windows; it >> d

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On 2019-06-22 12:59, Karl Denninger wrote: > > I use Refind for this sort of thing and it has (thus far!) survived > upgrades.  The only "gotcha" is that I had a Windows 10 "Feature" > upgrade that reset the default boot in the firmware to Windows; it > didn't damage anything but did require that I

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On 6/22/2019 13:34, Rebecca Cran wrote: > I just upgraded my UEFI system firmware, and not unexpectedly lost the > "FreeBSD" boot manager entry after the settings got reset to default. I > was left with "Windows", "opensuse" and two "UEFI OS" entries. > > The "opensuse-secureboot" entry wasn't auto

Re: UEFI boot broken in 13?

On Tue, 4 Jun 2019 08:58:43 -0600 Warner Losh wrote: > On Tue, Jun 4, 2019 at 8:16 AM Warner Losh wrote: > > > > > > > On Tue, Jun 4, 2019 at 7:11 AM Tomoaki AOKI > > wrote: > > > >> Hi. > >> > >> Try attached patch for stand/efi/boot1/boot1.c. > >> This partially reverts r347193 and works at

Re: UEFI boot broken in 13?

On Tue, Jun 4, 2019 at 8:16 AM Warner Losh wrote: > > > On Tue, Jun 4, 2019 at 7:11 AM Tomoaki AOKI > wrote: > >> Hi. >> >> Try attached patch for stand/efi/boot1/boot1.c. >> This partially reverts r347193 and works at least for me. >> >> Without this, boot1.efi (bootx64.efi) forcibly boot from

Re: UEFI boot broken in 13?

On Tue, Jun 4, 2019 at 7:11 AM Tomoaki AOKI wrote: > Hi. > > Try attached patch for stand/efi/boot1/boot1.c. > This partially reverts r347193 and works at least for me. > > Without this, boot1.efi (bootx64.efi) forcibly boot from > first physical HDD/SSD, even if forcibly booted from other > phys

Re: UEFI boot broken in 13?

Hi. Try attached patch for stand/efi/boot1/boot1.c. This partially reverts r347193 and works at least for me. Without this, boot1.efi (bootx64.efi) forcibly boot from first physical HDD/SSD, even if forcibly booted from other physical drive via BIOS (UEFI firmware) menu. Remaining parts of r3471

Re: UEFI boot broken in 13?

> On 4 Jun 2019, at 04:38, Johannes Lundberg wrote: > > Hi > > I'm using poudriere-image to create usb memstick images. The images are > identical except OS version. They are tested on a laptop with 13-CURRENT > installed as only OS, having UEFI boot and root on zfs. > > 12-STABLE memstick b

Re: UEFI boot broken in 13?

On 6/3/19 7:25 PM, Rodney W. Grimes wrote: >> Hi >> >> I'm using poudriere-image to create usb memstick images. The images are >> identical except OS version. They are tested on a laptop with 13-CURRENT >> installed as only OS, having UEFI boot and root on zfs. >> >> 12-STABLE memstick boots fine

Re: UEFI boot broken in 13?

> Hi > > I'm using poudriere-image to create usb memstick images. The images are > identical except OS version. They are tested on a laptop with 13-CURRENT > installed as only OS, having UEFI boot and root on zfs. > > 12-STABLE memstick boots fine with in UEFI mode. Does it actually boot via a UE

Re: UEFI, loader.efi and /boot.config

On Thursday, 17 January 2019 20:02:46 MST David Wolfskill wrote: > Does the above only apply to UEFI booting, or also to booting from > BIOS/MBR? It's only for UEFI booting. -- Rebecca Cran signature.asc Description: This is a digitally signed message part.

Re: UEFI, loader.efi and /boot.config

On Friday, 18 January 2019 00:48:02 MST Kurt Jaeger wrote: > > With a recent change I made for UEFI, we now install loader.efi onto the > > ESP and don???t run boot1. That means that /boot.config is no longer > > read, and so console settings need to be put in /boot/loader.conf > Which change is t

Re: UEFI, loader.efi and /boot.config

On 18.01.2019 20:13, Warner Losh wrote: > If your BIOS allows it, you can set the standard ConOut variables the UEFI > standard defines with the efivar program. In addition, you can add args to > the 'binary blob' part of the BOOT OPTIONS variables (Boot), though > efibootmgr doesn't currently

Re: UEFI, loader.efi and /boot.config

On Fri, Jan 18, 2019 at 8:55 AM Lev Serebryakov wrote: > On 18.01.2019 17:10, Kyle Evans wrote: > > > There's some UEFI var that's supposed to serve the same kind of > > purpose as /boot.config -- early boot parameters. I think we had > > discussed implementing this at some point, but this hasn't

Re: UEFI, loader.efi and /boot.config

On Fri, Jan 18, 2019 at 8:27 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger > > > > Hi! > > > > > > > With a recent change I made for UEFI, we now install loader.efi onto > the > > > ESP and don???t run boot1. That means that /boot.

Re: UEFI, loader.efi and /boot.config

On 18.01.2019 17:10, Kyle Evans wrote: > There's some UEFI var that's supposed to serve the same kind of > purpose as /boot.config -- early boot parameters. I think we had > discussed implementing this at some point, but this hasn't been done > yet as far as I've seen. Would this be usable on your

Re: UEFI, loader.efi and /boot.config

> On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger > > Hi! > > > > > With a recent change I made for UEFI, we now install loader.efi onto the > > ESP and don???t run boot1. That means that /boot.config is no longer read, > > and so console settings need to be put in /boot/loader.conf > > > > Which chan

Re: UEFI, loader.efi and /boot.config

On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger Hi! > > > With a recent change I made for UEFI, we now install loader.efi onto the > ESP and don???t run boot1. That means that /boot.config is no longer read, > and so console settings need to be put in /boot/loader.conf > > Which change is that ? > Mov

Re: UEFI, loader.efi and /boot.config

On 18.01.2019 17:03, Olivier Cochard-Labbé wrote: > > I was wondering if people will expect /boot.config to still be > read and so code should be added to loader to continue to parse it, > or if loader.conf can be considered the correct place and > boot.config forgotten about? >

Re: UEFI, loader.efi and /boot.config

The loader.efi (EFI application) can receive command line arguments, set up in UEFI boot manager. rgds, toomas > On 18 Jan 2019, at 16:14, Kurt Jaeger wrote: > > Hello, > >> I was wondering if people will expect /boot.config to still be read and so >> code should be added to loader to cont

Re: UEFI, loader.efi and /boot.config

Hello, > I was wondering if people will expect /boot.config to still be read and so > code should be added to loader to continue to parse it, or if loader.conf can > be considered the correct place and boot.config forgotten about? If the early boot messages are not displayed as Olivier mentione

Re: UEFI, loader.efi and /boot.config

On Fri, Jan 18, 2019 at 8:04 AM Olivier Cochard-Labbé wrote: > > On Fri, Jan 18, 2019 at 2:10 PM Lev Serebryakov wrote: > > > On 18.01.2019 5:31, Rebecca Cran wrote: > > > > > > > I was wondering if people will expect /boot.config to still be read and > > so code should be added to loader to cont

Re: UEFI, loader.efi and /boot.config

On Fri, Jan 18, 2019 at 2:10 PM Lev Serebryakov wrote: > On 18.01.2019 5:31, Rebecca Cran wrote: > > > > I was wondering if people will expect /boot.config to still be read and > so code should be added to loader to continue to parse it, or if > loader.conf can be considered the correct place and

Re: UEFI, loader.efi and /boot.config

On 18.01.2019 5:31, Rebecca Cran wrote: > I was wondering if people will expect /boot.config to still be read and so > code should be added to loader to continue to parse it, or if loader.conf can > be considered the correct place and boot.config forgotten about? Please, not, please support /b

Re: UEFI, loader.efi and /boot.config

Hi! > With a recent change I made for UEFI, we now install loader.efi onto the ESP > and don???t run boot1. That means that /boot.config is no longer read, and so > console settings need to be put in /boot/loader.conf Which change is that ? > I was wondering if people will expect /boot.config

Re: UEFI, loader.efi and /boot.config

On Thu, Jan 17, 2019, 7:33 PM Rebecca Cran > With a recent change I made for UEFI, we now install loader.efi onto the > ESP and don’t run boot1. That means that /boot.config is no longer read, > and so console settings need to be put in /boot/loader.conf. > I was wondering if people will expect /b

Re: UEFI, loader.efi and /boot.config

On Thu, Jan 17, 2019 at 07:31:38PM -0700, Rebecca Cran wrote: > > With a recent change I made for UEFI, we now install loader.efi onto the ESP > and don’t run boot1. That means that /boot.config is no longer read, and so > console settings need to be put in /boot/loader.conf.  > I was wondering

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

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

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

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

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

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

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

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 -

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

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

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

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.

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

-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

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

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

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:

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

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

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 a

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 apolo

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

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'l

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 kerne

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

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

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

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

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,

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

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

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

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

On Sunday, 4 November 2018 16:07:17 MST Warner Losh wrote: > Finally, I have a /dev/efi/esp pseudo label support coded up for geom > (along with /dev/efi/boot for the putative root device). There's some > issues with it, so I set it aside some time ago to work on other higher > priority things. We

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

On Sun, Nov 4, 2018 at 4:10 PM Rebecca Cran wrote: > On Sunday, 4 November 2018 15:56:25 MST Warner Losh wrote: > > > I think that's a really really bad idea. We should *NEVER* create them by > > default. We are only sliding by on the coat-tails of compatibility by > using > > efi/boot/boot*.efi.

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

On Sunday, 4 November 2018 15:56:25 MST Warner Losh wrote: > I think that's a really really bad idea. We should *NEVER* create them by > default. We are only sliding by on the coat-tails of compatibility by using > efi/boot/boot*.efi. We shouldn't use those at all, unless there's a > compelling re

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

On Sun, Nov 4, 2018 at 2:27 PM Allan Jude wrote: > On 2018-11-04 16:20, Rebecca Cran wrote: > > I'm currently working on creating and updating the ESP (EFI System > Partition) > > for UEFI booting during installation and installworld. > > > > During installation, with my changes it gets mounted o

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

On Sun, Nov 4, 2018 at 2:43 PM Rebecca Cran wrote: > On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote: > > > it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi > is > > hard one of course. But then again, it is problem only when we can not > > setup EFI bootmanager

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

On 11/4/18, Rebecca Cran wrote: > On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote: > >> it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi >> is >> hard one of course. But then again, it is problem only when we can not >> setup EFI bootmanager variables ? the bootx

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote: > it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi is > hard one of course. But then again, it is problem only when we can not > setup EFI bootmanager variables ? the bootx64.efi is default when bootmgr > is not se

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

> On 4 Nov 2018, at 23:25, Allan Jude wrote: > > On 2018-11-04 16:20, Rebecca Cran wrote: >> I'm currently working on creating and updating the ESP (EFI System >> Partition) >> for UEFI booting during installation and installworld. >> >> During installation, with my changes it gets mounted

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

On Sunday, 4 November 2018 14:25:26 MST Allan Jude wrote: > I wouldn't depend on the /etc/fstab entry existing. I am not sure I want > installworld randomly fobbing around in my EFI partition. Especially if, > for example, my EFI/BOOT is not FreeBSD, but rEFInd or something. I tend to agree. I ha

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

On 2018-11-04 16:20, Rebecca Cran wrote: > I'm currently working on creating and updating the ESP (EFI System Partition) > for UEFI booting during installation and installworld. > > During installation, with my changes it gets mounted on /boot/efi and > loader.efi > copied into /boot/efi/EFI/F

Re: UEFI boot hangs after loader

Warner Losh wrote: > On Sun, Oct 28, 2018, 10:39 AM Yuri Pankov wrote: > >> Jung-uk Kim wrote: >>> On 18. 10. 24., Warner Losh wrote: On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > gryphon# efivar -N --hex $(efivar | grep Boot0002) > : 01 00 00 00 98 00 55 00 45 00

Re: UEFI boot hangs after loader

The patch you emailed fixed it for me ... was there something else I've missed ? On 28 October 2018 at 16:40, Warner Losh wrote: > > > On Sun, Oct 28, 2018, 10:39 AM Yuri Pankov wrote: > >> Jung-uk Kim wrote: >> > On 18. 10. 24., Warner Losh wrote: >> >> On Wed, Oct 24, 2018 at 10:33 AM Harry

Re: UEFI boot hangs after loader

On Sun, Oct 28, 2018, 10:39 AM Yuri Pankov wrote: > Jung-uk Kim wrote: > > On 18. 10. 24., Warner Losh wrote: > >> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > >> > >>> gryphon# efivar -N --hex $(efivar | grep Boot0002) > >>> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 > >>>

Re: UEFI boot hangs after loader

Jung-uk Kim wrote: > On 18. 10. 24., Warner Losh wrote: >> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: >> >>> gryphon# efivar -N --hex $(efivar | grep Boot0002) >>> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 >>> 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 >>> 0020: 6e

Re: UEFI boot hangs after loader

I've recreated something like this in efivar as well... I need to study the code for how to improve it to have sanity limits... I hope to have a patch soon... Thanks for this data point. I think I'm on the right track. Warner On Fri, Oct 26, 2018 at 3:47 PM Harry Newton wrote: > So patching o

Re: UEFI boot hangs after loader

So patching out find_currdev() in efi/loader/main.c allows the machine to boot. The hang occurs in the call to efi_devpath_name() in match_boot_info() because the (last) call to ConvertDevicePathToText() call does not return. /H On 24 October 2018 at 07:32, Toomas Soome wrote: > > > > On 24 Oc

Re: UEFI boot hangs after loader

On Wed, Oct 24, 2018 at 11:47 AM Jung-uk Kim wrote: > On 18. 10. 24., Warner Losh wrote: > > On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > > > >> gryphon# efivar -N --hex $(efivar | grep Boot0002) > >> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 > >> 0010: 20 00 4b 00 69 00 6e

Re: UEFI boot hangs after loader

On 18. 10. 24., Warner Losh wrote: > On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > >> gryphon# efivar -N --hex $(efivar | grep Boot0002) >> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 >> 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 >> 0020: 6e 00 44 00 61 00 74 00 61 0

Re: UEFI boot hangs after loader

Thanks — please let me if there's anything I can do to help. On 24 October 2018 at 18:25, Warner Losh wrote: > > > On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > >> gryphon# efivar -N --hex $(efivar | grep Boot0002) >> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 >> 0010: 20 00

Re: UEFI boot hangs after loader

On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > gryphon# efivar -N --hex $(efivar | grep Boot0002) > : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 > 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 > 0020: 6e 00 44 00 61 00 74 00 61 00 54 00 72 00 61 00 > 0030: 76 00 65 00 6c

Re: UEFI boot hangs after loader

> On 24 Oct 2018, at 10:13, Harry Newton wrote: > > Booted with the installer image makes efibootmgr to work as you said: > > gryphon# efibootmgr -v > BootCurrent: 0002 > Timeout : 2 seconds > BootOrder : 0001, 0002 > Boot0001* UEFI OS > HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x

Re: UEFI boot hangs after loader

gryphon# efivar -N --hex $(efivar | grep Boot0002) : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 0020: 6e 00 44 00 61 00 74 00 61 00 54 00 72 00 61 00 0030: 76 00 65 00 6c 00 65 00 72 00 20 00 32 00 2e 00 0040: 30 00 31 00 2e 00 30 00 30

Re: UEFI boot hangs after loader

On Wed, Oct 24, 2018 at 9:36 AM Toomas Soome wrote: > > > > On 24 Oct 2018, at 00:51, Kyle Evans wrote: > > > > Hi, > > > > I suspect 4th vs. lua has no impact here, given the output shown -- > > can you throw one of the installer images [0] on some removable media > > and give that a shot for b

Re: UEFI boot hangs after loader

> On 24 Oct 2018, at 00:51, Kyle Evans wrote: > > Hi, > > I suspect 4th vs. lua has no impact here, given the output shown -- > can you throw one of the installer images [0] on some removable media > and give that a shot for booting? If that works, we can explore UEFI > variables from there. >

Re: UEFI boot hangs after loader

On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote: > Booted with the installer image makes efibootmgr to work as you said: > > gryphon# efibootmgr -v > BootCurrent: 0002 > Timeout : 2 seconds > BootOrder : 0001, 0002 > Boot0001* UEFI OS > > HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x64

Re: UEFI boot hangs after loader

Re the efibootmgr hang: it appears to be in / under the call to efidp_format_device_path() in efibootmgr.c which is called with -v. Without -v: gryphon# efibootmgr BootCurrent: 0002 Timeout : 2 seconds BootOrder : 0001, 0002 Boot0001* UEFI OS + Boot0002* UEFI: USB Flash Memory1.00 gryphon# On

Re: UEFI boot hangs after loader

Booted with the installer image makes efibootmgr to work as you said: gryphon# efibootmgr -v BootCurrent: 0002 Timeout : 2 seconds BootOrder : 0001, 0002 Boot0001* UEFI OS HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/File(\EFI\BOOT\BOOTX64.EFI) ada0p1:/EFI/BOOT/BOOTX64.EFI (null) How

Re: UEFI boot hangs after loader

Hi, I suspect 4th vs. lua has no impact here, given the output shown -- can you throw one of the installer images [0] on some removable media and give that a shot for booting? If that works, we can explore UEFI variables from there. efibootmgr will only work on a successful UEFI boot, unfortunate

Re: UEFI boot hangs after loader

I set LOADER_DEFAULT_INTERP=4th and went in /usr/src/stand and re-made the binaries in /boot but this doesn't solve the problem. It did copy /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(8) which is what is called from /boot/boot1.efi and which contains the strings I see on

Re: UEFI boot hangs after loader

Right ... I've the binaries in /boot, freshly made. This might be a silly question ... do I not need to copy them (or dd the boot1.efifat image) to the EFI partition ? /H On 23 October 2018 at 21:30, Toomas Soome wrote: > you should have the binaries in boot - just ln (or copy) one to loader.e

Re: UEFI boot hangs after loader

you should have the binaries in boot - just ln (or copy) one to loader.efi rgds, toomas > On 23 Oct 2018, at 23:22, Harry Newton wrote: > > Yes ... so as everything is built, can I just alter LOADER_DEFAULT_INTERP in > /etc/make.conf and then reinstall just the loader and boot parts onto the

Re: UEFI boot hangs after loader

Yes ... so as everything is built, can I just alter LOADER_DEFAULT_INTERP in /etc/make.conf and then reinstall just the loader and boot parts onto the UEFI partition ? If so, how ? On 23 October 2018 at 21:17, Toomas Soome wrote: > ok, in that case I’d suggest to test out if forth based one is

Re: UEFI boot hangs after loader

ok, in that case I’d suggest to test out if forth based one is still working - at least you can get the bootable system. And then there is a chance to debug the lua version too (note it should be possible to chain /boot/loader_lua.efi). rgds, toomas > On 23 Oct 2018, at 23:08, Harry Newton wro

Re: UEFI boot hangs after loader

So it's got FORTH in it, but my loader is lua based, and also doesn't appear to read loader.rc. /H On 23 October 2018 at 21:03, Toomas Soome wrote: > hm. in that case, whats the content of /boot/loader.rc ? > > rgds, > toomas > > > On 23 Oct 2018, at 23:01, Harry Newton wrote: > > If boot menu

  1   2   3   >