Skip to content

kernel 20261107-d2107de6 arm64

Pre-release
Pre-release

Choose a tag to compare

View all tags
@enavarre-cl enavarre-cl released this 07 Nov 22:56
· 37 commits to main since this release
20261107-d2107de6
d2107de

EmiBSD kernel for arm64, built by just dist-arm64 from commit d2107de6 (main: milestone N5 met, tag n5-vfs, plus N6.0). It replaces 20261106-ac41e133.

What changed from 20261106-ac41e133

  • No abi_openbsd.ko any more. The OpenBSD ABI (crate abi) is linked into the kernel image (decision 47). The boot loader no longer loads a module, and the install media need none. Drop the file from any manifest or image step that expected it. The system-call ABI is unchanged: 331 system calls, 170 of them served by the native kernel.
  • N5 is complete. The buffer cache, vnode, mount, name lookup, files and the VFS system calls are the native kernel's. So are ufs/ffs/mfs, ext2fs, msdosfs, cd9660, udf, tmpfs and fuse.
  • N6.0: the network lock and SMR live in hal. Nothing userland sees changes.
  • The zero DUID reported in 20261106-ac41e133 (newfs_msdos: /dev/r0000000000000000.i during an ISO install) is OpenBSD's own behaviour: a spoofed label shared with cd0 has no DUID. No kernel change was made for it.

One tarball for EmiBSD/OS to assemble the install media with Userland's sets. Fetch it by this tag, check the sum, then unpack:

a6612550f5015fb8fadf1a059562cebd773d5831071b3652474a3b02de8a61f2  kernel-20261107-d2107de6-arm64.tar.zst

Inside kernel-20261107-d2107de6-arm64/, covered by its SHA256 (OpenBSD's format):

File What
bsd.mp the MULTIPROCESSOR kernel with the ABI linked in, release profile (LTO, symbols kept), default features (no qemu)
bsd.RAMDISK the same kernel with an empty 32 MiB ramdisk (65536 sectors); cargo xtask rdsetroot fills it with a miniroot to make bsd.rd
BOOTAA64.EFI the EFI boot loader
BUILDINFO commit, dates, toolchain (rustc 1.99.1), LandingZone pin, profiles

Pre-release: a development build, tested only under QEMU (virt). Before packing, this kernel booted once and passed the user-mode checks of smoke-boot up to init's last one, then hit OpenBSD's "init died" panic as expected (12.0 s). The N5 close ran on n5-vfs: just ci, ci-full and diff-openbsd passed. d2107de6 adds N6.0 on top; it passed one arm64 boot after its merge but has not been through a close's ci. arm64 only until amd64 is homologated (N10).

Assets 4
Loading