On Thursday, July 31st, 2025 at 12:08 AM, Robert Elz <k...@munnari.oz.au> wrote:
> 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. I used to have a custom /boot.cfg but, these days I stick to the default. menu=Boot normally:rndseed /var/db/entropy-file;boot menu=Boot single user:rndseed /var/db/entropy-file;boot -s menu=Drop to boot prompt:prompt default=1 timeout=5 clear=1 > 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 This works, thank you! The noise is gone :) While here, updated to the latest, https://imgur.com/a/kgQI37l > 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). > > kre
