Did a couple RC1 upgrades, amd64 and aarch64 so far.
https://wiki.netbsd.org/releng/netbsd-11/
Stuck on the #RaspberryPi 0W which has lost its pkg remote repository somehow.
Did a couple RC1 upgrades, amd64 and aarch64 so far.
https://wiki.netbsd.org/releng/netbsd-11/
Stuck on the #RaspberryPi 0W which has lost its pkg remote repository somehow.
Reconnected and getting sysupgrade lined up for the 1-core Pi 0W.
sysupgrade: I: Downloading https://cdn.netbsd.org/pub/NetBSD/NetBSD-11.0_RC1/evbarm-earmv6hf/binary/sets/base.tgz into /var/cache/sysupgrade
Trying [2a04:4e42:77::262]:443 ...
sysupgrade: I: Extracting man into /
100% |**************************************************************************************************| 33190 KiB 252.49 KiB/s 00:00 ETA
etc etc etc
Stymied by the kernel being in a different place than other ports.
#RTFM
"with different boot loader schemes ...
netbsd-GENERIC: A normal kernel in ELF format.
netbsd-GENERIC.img: In NetBSD >= 9, formatted for the RPI bootloader.
netbsd-GENERIC.bin:
In NetBSD >= 9, ??????
In NetBSD 9, this kernel WILL NOT boot.
netbsd-GENERIC.ub: A kernel in uboot format.
...
copy this either to /boot/kernel.img (First generation Pi, Pi Zero hardware) or to /boot/kernel7.img (Pi 2, Pi 3 hardware)
..."
Resolved by doing a fresh install to another microSD card, tarring the boot kernel files and replacing them in the #RasperryPi0W. Looks like the kernel is behaving better than the last beta I ran, or I have not hit it hard enough. One core rules!
A #NetBSD11RC1 burn test, running xscreensaver on a 1 core Pi0W. At first it crashed, but now it's been crawling with ants for 24 hours.
-rw------- 1 me us 656784 Feb 12 19:45 xscreensaver-get.core
1/
load averages: 1.18, 1.20, 1.17; up 1+01:36:12 19:26:36
46 processes: 1 runnable, 44 sleeping, 1 on CPU
CPU states: 16.5% user, 41.7% nice, 35.9% system, 3.9% interrupt, 1.9% idle
Memory: 239M Act, 122M Inact, 11M Wired, 34M Exec, 177M File, 12M Free
Swap: / Pools: 44M Used / Network: 267M In, 8520K Out
2/