On Thu, 31 Jul 2025, Robert Elz wrote:
Date: Wed, 30 Jul 2025 17:27:03 +0000 From: pin <void...@protonmail.com> Message-ID: <fxP64kAZdzrhwRofVMRBuf9QnEG7FJU5LU6FalTpNe5CAAd0NGPXk-mRzK6bHtO1wOnGsRj_gavsAelpE5PUYcuYhHfQkpcc08kVxw5aNI0=@protonmail.com>| diff -u /boot /usr/mdec/boot gives an empty output. I'd generally recommend "cmp" for comparing binary files, but that's OK, diff works too. I now know what the problem is ... if you don't have a boot.cfg file with the current code (both BIOS and EFI variants) you will see the behaviour you are reporting, or if you do have one, and it is just the default, which has no boot filename given to the boot command. A simple workaround for you, until the code gets fixed, would be to just install, or modify, a boot.cfg file in / Something like the following 6 lines (all starting in column 1, not indented as in this e-mail): menu=Boot normally:rndseed /var/db/entropy-file;boot netbsd menu=Boot single user:rndseed /var/db/entropy-file;boot netbsd -s menu=Drop to boot prompt:prompt default=1 timeout=5 clear=1 The issue is when no boot menu has been defined, or when no filename is given to the "boot" command, the boot code simply boots files from its internal "names[][]" array, and that is ordered (still) in the fashion of the original implementation of the KERNEL_DIRS modification to the boot code (directory version first, simple files second). I will leave it to Paul to fix the "names" array order (in both versions) which should make the workaround above (explicitly specifying the file name) unnecessary (to avoid the unwanted noise during normal boots).
Done! +---------------------+--------------------------+----------------------+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses: | | (Retired) | 1B11 1849 721C 56C8 F63A | p...@whooppee.com | | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoye...@netbsd.org | | & Network Engineer | | pgoyett...@gmail.com | +---------------------+--------------------------+----------------------+
