Date: Sun, 27 Jul 2025 15:17:38 +0900
From: Makoto Fujiwara <mak...@ki.nu>
Message-ID: <875xfe88e5.wl-mak...@ki.nu>
| open netbsd/kernel: Not a directory
| boot: hd0a:netbsd/kernel: Not a directory
| open netbsd/kernel.gz: Not a directory
| boot: hd0a:netbsd/kernel.gz: Not a directory
| open onetbsd/kernel: No such file or directory
| boot: hd0a:onetbsd/kernel: No such file or directory
| heap full (0x6f790+16384)
| --------------------------------------------
|
| Probably simple issue, but I've no idea at the moment,
| The lines before the last line is familiar to me, and not surprising ...
But they shouldn't be - current versions of boot (which the date in
the revision info beside the flag says that you have) attempt to boot
/netbsd first, before trying netbsd/kernel (etc). So unless you have
no /netbsd (nor netbsd.gz) installed in the root of the filesystem
you're booting, you should never see any of that, as they shouldn't
be being attempted (the wisdom of writing error messages about failing
to load speculative filenames is another question, rather less important).
I have no idea about the heap full message though, one possibility is
that it is just a stray error value being printed when boot cannot find
anything which will actually boot, and doesn't actually mean anything.
Another would be that each of the boot attempts is allocating memory
for something, and failing to free it when that attempt fails - and
your system is running out of however much is available.
But as a first step, make sure you have a kernel properly in place.
kre
