On Sun, Mar 23, 2025 at 06:46:19PM +0700, Robert Elz wrote:
> | UEFI doesn't even know the "bootme" attribue, so that must be something
> | else.
>
> It is even worse than that, despite what our gpt(8) might allow one to
> believe, it is impossible to set "bootme" on an ESP. "bootme" is one
On Sat, 22 Mar 2025, Michael van Elst wrote:
p...@whooppee.com (Paul Goyette) writes:
My boot.cfg file looks like this:
dev=NAME=NVME-sys:
If I just let it boot and take the default option 7, the ``dev'' is not
set and the boot fails since the default dev is NAME=NVME-efi which
doesn't have
On Mon, 24 Mar 2025, RVP wrote:
On Sat, 22 Mar 2025, Paul Goyette wrote:
My machine doesn't work this way. It fails to boot if I mark the
NetBSD partition; instead it proceeds to the next bootable device.
The bootme flag seems to be acting as "this is where bootx64.efi is
found".
Can you s
At Sat, 22 Mar 2025 14:31:04 -0700, "Greg A. Woods" wrote:
Subject: Re: MKLLVMRT=yes failure on macOS
>
> At Sat, 22 Mar 2025 12:53:48 -0700, "Greg A. Woods" wrote:
> Subject: MKLLVM=yes failure on macOS
>
> Sorry, that should have been MKLLVMRT=yes of course.
Oy -- it doesn't matter. As I shou
Updating src tree:
P src/external/gpl3/gcc/lib/preinit.mk
P src/sys/arch/acorn32/doc/history
P src/sys/arch/epoc32/stand/e32boot/include/elf.h
P src/sys/dev/pci/if_iavf.c
P src/sys/dev/usb/ums.c
P src/sys/dev/usb/uts.c
P src/sys/dev/wscons/wskbd.c
P src/sys/dev/wscons/wsmouse.c
P src/sys/dev/wsco
On Sun, 23 Mar 2025, Paul Goyette wrote:
On Mon, 24 Mar 2025, RVP wrote:
On Sat, 22 Mar 2025, Paul Goyette wrote:
My machine doesn't work this way. It fails to boot if I mark the
NetBSD partition; instead it proceeds to the next bootable device.
The bootme flag seems to be acting as "this i
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
first successful build:
2025.03.23.23.58.56 christos src/external/gpl3/gcc/lib/preinit.mk 1.3
Logs can be found at:
http://releng.NetBSD.org/b5reports/i386/commits-2025
