[Bug 270935] efi(4) doesn't attach on the Windows 2023 Dev Kit
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270935
Bug ID: 270935
Summary: efi(4) doesn't attach on the Windows 2023 Dev Kit
Product: Base System
Version: 13.2-RELEASE
Hardware: arm64
OS: Any
Status: New
Keywords: uefi
Severity: Affects Only Me
Priority: ---
Component: arm
Assignee: [email protected]
Reporter: [email protected]
Created attachment 241590
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=241590&action=edit
/var/run/dmesg.boot
I am running FreeBSD 13.2 on my Windows 2023 Dev Kit. I had to apply D37765
and cherry pick D38031 to get this to work. hw.pac.enable=0 is needed in
/boot/loader.conf to make the kernel boot. I have installed FreeBSD on ZFS on
the internal NVMe SSD. (same setup as in bug #270895)
After booting, I notice that /dev/efi exists, but any ioctl on it fails with
ENOSYS (such as those issued by efivar(8) and efibootmgr(8)). dmesg doesn't
show anything interesting, either.
As the machine boots with EFI, I would expect EFI variables and the like to be
present and configurable. But apparently there's something wrong here.
--
You are receiving this mail because:
You are the assignee for the bug.