daily CVS update output
Updating src tree: P src/distrib/sets/lists/debug/module.mi P src/distrib/sets/lists/modules/mi P src/sys/arch/evbppc/explora/explora_start.S P src/sys/dev/files.audio P src/sys/dev/files.dev P src/sys/dev/midi.c U src/sys/dev/midi_mod.c U src/sys/dev/midi_seq_mod.c P src/sys/dev/sequencer.c U src/sys/dev/sequencer_mod.c P src/sys/modules/Makefile P src/sys/modules/midi/Makefile cvs update: `src/sys/modules/midi/midi.ioconf' is no longer in the repository U src/sys/modules/midi_seq/Makefile U src/sys/modules/midi_seq/midi_seq.ioconf P src/sys/modules/sequencer/Makefile cvs update: `src/sys/modules/sequencer/sequencer.ioconf' is no longer in the repository P src/sys/uvm/uvm_map.c P src/sys/uvm/uvm_mmap.c P src/tests/lib/libc/kevent_nullmnt/t_nullmnt.sh P src/tests/lib/libc/sys/t_mmap.c Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 43241553 Jun 5 03:03 ls-lRA.gz
Re: boot.cfg syntax question
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.47679 + +++ boot.cfg2022-06-05 00:49:18.797459000 + @@ -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 File a PR, I think. -RVP
Re: Branching for NetBSD 10
> > On Sat, Jun 04, 2022 at 05:16:34AM +, Thomas Mueller wrote: > > My big concern with the branch is the entropy bug, where building > > many packages from pkgsrc is stopped. > Yes, you are kinda right: > https://wiki.netbsd.org/releng/netbsd-10/ > "Waiting for Randot" as open point, although you may notice that all other > entropy related subpoints have been dealt with. > But again: this is not a bug, but a broken system setup - and nowadays > it is pretty hard to get into that state on new installations. The installer > will push you very hard to fix the setup before completing installation. > Various improvements in this area have happened lately, and once your > system setup is fixed (one time, and savely shutdown or rebooted w/o > crash after that fix) everything will just work. > But most importantly in this context: this is nothing that can delay > the branch itself (only the release). The one sub item that altered > libc ABI (addition of getentropy(3)) has happened. > Martin I suppose now the branch is just a few days away, and running "cvs up -dP -A" will just go the new HEAD? A lot must have happened with NetBSD-current since the time of 9.99.82, a little more than one year ago. I will want to try on amd64 and i386. Tom
boot.cfg syntax question
Hi! I read boot.cfg and thought that the following /boot.cfg would do what I wanted: menu=Boot without nouveau:rndseed /var/db/entropy-file;userconf disable nouveau*;boot 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 single user:rndseed /var/db/entropy-file;boot -s menu=Drop to boot prompt:prompt default=1 timeout=5 clear=1 i.e. 1 and 2 give me /netbsd (or /netbsd.old) booted with 'userconf disable nouveau*' while 3 boots /netbsd normally. 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? Thomas
nouveau: back in text console after switch to graphical one
Hi! On one system I have with an nvidia geforce 1050 ti, with a GENERIC kernel from 9.99.95 and also from yesterday, during boot there is the "blank" moment where it tries to enable the graphical console. But after that blank, it goes back to text console and the kernel log messages stop. I guess they continue on the graphical console (that is however not visible to me) since the boot finishes and I can login with ssh. /var/run/dmesg is not very interesting though, it consists of: # uniq -c dmesg 1 fo: SCHED_ERROR 20 [] 369 nouveau0: autoconfiguration error: error: fifo: SCHED_ERROR 20 [] 1 nouveau0: autoconfiguration error: error: fifo: fault 01 [WRITE] at 0027e000 engine 04 [BAR1] client 08 [HUB/HOST_CPU_NB] reason 02 [PTE] on channel -1 [103fe6e000 unknown] 437 nouveau0: autoconfiguration error: error: fifo: SCHED_ERROR 20 [] On the "text" console the last lines I see are nouveau: nouveau0: info NVIDIA GM204 (124020a1) nouveau0: info bios version 84.04.31.00.06 nouveau0: interrupting at msi9 vec 0 (nouveau0) nouveau0: info: fb: 4096 MiB GDDR5 Anyone else seeing this? Thomas
Re: Branching for NetBSD 10
On Fri 03 Jun 2022 at 21:08:15 +0200, Reinoud Zandijk wrote: > Well I'd like to add another point! Fixed i915 DRM support! That seems to work on my laptop (although glxgears doesn't work, so it must be missing some things) but the touchpad doesn't have any effect in my case. -Olaf. -- ___ "Buying carbon credits is a bit like a serial killer paying someone else to \X/ have kids to make his activity cost neutral." -The BOFHfalu.nl@rhialto signature.asc Description: PGP signature
Re: Branching for NetBSD 10
On Sat, Jun 04, 2022 at 05:16:34AM +, Thomas Mueller wrote: > My big concern with the branch is the entropy bug, where building > many packages from pkgsrc is stopped. Yes, you are kinda right: https://wiki.netbsd.org/releng/netbsd-10/ "Waiting for Randot" as open point, although you may notice that all other entropy related subpoints have been dealt with. But again: this is not a bug, but a broken system setup - and nowadays it is pretty hard to get into that state on new installations. The installer will push you very hard to fix the setup before completing installation. Various improvements in this area have happened lately, and once your system setup is fixed (one time, and savely shutdown or rebooted w/o crash after that fix) everything will just work. But most importantly in this context: this is nothing that can delay the branch itself (only the release). The one sub item that altered libc ABI (addition of getentropy(3)) has happened. Martin
Re: Branching for NetBSD 10
On Sat, Jun 04, 2022 at 05:16:34AM +, Thomas Mueller wrote: > My big concern with the branch is the entropy bug, where building many > packages from pkgsrc is stopped. Isn't "entropy bug" a misnomer for the interesting libpthread bug https://gnats.netbsd.org/56414 which has recently been fixed? Cheers, Patrick
Re: Branching for NetBSD 10
> On Mon, May 02, 2022 at 04:22:56PM +0200, Martin Husemann wrote: > > After a bit more than two years after the first NetBSD 9 release > > (9.0 happened February 14, 2020) and nearly a year after the last > > (so far) netbsd-9 release (9.2 happened May 12, 2021) we are in > > the final steps to prepare for the next really great release: > > > We are planning to branch netbsd-10 in about a week from now. > As you may have noticed, this did not happen. > Those who followed the NetBSD Foundation's annual general meeting saw > that we discussed a new plan that wanted to branch early two weeks ago - > and that also did not happen. > The major issue that came up late and that we are now trying to resolve > properly before the branch (so we can document what people testing the > branch need to know about it) is the handling of extended attributes > on FFS file systems. > See the thread about "File system corruption due to UFS2 extended attributes" > on current-users and tech-kern, starting here: > https://mail-index.netbsd.org/tech-kern/2022/05/24/msg028105.html > We hope to have these changes landed within the next few days and will > start with the branch process right after that. > Sorry for yet another delay, but let's do it right. > Martin > P.S.: of course the *real* cause for the delay is that we are still trying > very hard to find reasons to bump the -current version to 9.99.99 - only > two bumps to go! My big concern with the branch is the entropy bug, where building many packages from pkgsrc is stopped. I don't know if the situation now with NetBSD-current is any better than it was with NetBSD 9.99.82 (amd64 and i386). Is there any way to build NetBSD from source to disable the entropy bug, so it does not get in the way? Tom
