Date: Wed, 19 Apr 2023 15:23:01 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 270935] efi(4) doesn't attach on the Windows 2023 Dev Kit Message-ID: <bug-270935-7@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270935 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: freebsd-arm@FreeBSD.org Reporter: fuz@FreeBSD.org Created attachment 241590 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D241590&action= =3Dedit /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=3D0 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270935-7>