On Sun, Jun 05, 2022 at 12:53:09AM +0000, RVP wrote: > On Sun, 5 Jun 2022, Thomas Klausner wrote: > > > However, when I press '3' in that config, I get a kernel where nouveau > > is disabled. > > > > Did I misunderstand the man page or is there a bug here? > > > > Looks like a bug when a bare `boot' is encountered. Work around it by > forcing a kernel filename: > > --- boot.cfg.orig 2022-06-05 00:48:51.476790000 +0000 > +++ boot.cfg 2022-06-05 00:49:18.797459000 +0000 > @@ -1,6 +1,6 @@ > -menu=Boot without nouveau:rndseed /var/db/entropy-file;userconf disable > nouveau*;boot > +menu=Boot without nouveau:rndseed /var/db/entropy-file;userconf disable > nouveau*;boot /netbsd > menu=Boot old without nouveau:rndseed /var/db/entropy-file;userconf disable > nouveau*;boot /netbsd.old > -menu=Boot normally:rndseed /var/db/entropy-file;boot > +menu=Boot normally:rndseed /var/db/entropy-file;boot /netbsd > menu=Boot single user:rndseed /var/db/entropy-file;boot -s > menu=Drop to boot prompt:prompt > default=1
Yes, this works around the issue for me. Thanks! Thomas
