this is probably the same problem reported a few times already; the place
we load the kernel overlaps the EFI page tables.
no fix as of yet although there was a diff circulated a few months ago
that seemed to fix it for some people.
I did see the diff from 2021 for EliteBooks but that did not work for me.
I couldn't find any other diffs so hopefully that is the one you are
referring too.
I'm thinking its possibly a different offset is required?
Am i right in thinking my best course to diagnose would be to use the
boot hex dump
in order to find what memory is actually free and modify the diff
accordingly?
Also i read somewhere the machine mem command doesn't work for blocking
memory ranges on efi
which from my testing seems to be the case but want to double check is
this correct?
I completely understand if no fix is being worked on but just curious if
anyone is or not?
On 6/15/26 18:57, Mike Larkin wrote:
On Mon, Jun 15, 2026 at 02:31:53PM +0100, adooc wrote:
Hey,
Can you please verify this is not related to the expiration of the
Microsoft UEFI Secure Boot certificates that
will start happening this June 2026?
I have had secure boot disabled whilst trying this so that shouldn't be
affecting it?
this is probably the same problem reported a few times already; the place
we load the kernel overlaps the EFI page tables.
no fix as of yet although there was a diff circulated a few months ago
that seemed to fix it for some people.
On 6/15/26 13:48, Tito Mari Francis Escaño wrote:
Hello misc,
Can you please verify this is not related to the expiration of the
Microsoft UEFI Secure Boot certificates that will start happening this
June 2026?
Hope this helps.
Thanks.
On Mon, Jun 15, 2026 at 6:24 PM adooc <[email protected]> wrote:
Hi there,
I am trying to install openbsd and i am boot using BOOTX64.EFI
I've tried booting using pxe and a usb stick and get to the same
results.
On two slightly older amd64 devices everything works fine.
However, on a HP 430 G8 and a HP 630 G9 i get the exact same issue.
I have tried with 7.7,7.8,7.9 and get the same result, see below.
> probing: pc0 mem[636K 1047M 30904M]
> disk: hd0*
> >> OpenBSD/amd64 BOOTX64 3.69
> boot> boot
> booting tftp:bsd.rd: 4227986+1770496+3891816+0+716800 [109+484896
> +336185]=0xae8b50
> entry point at 0x1001000
>
It then hangs at this point.
I have tried boot -c but it hangs at the same point.
As such any help on how to diagnose this would be appreciated.
