Long ago, I had trouble updating along netbsd-9. The new kernel failed
to boot, and I am now returning to this.
I looked through my saved messages, and can't find it, but I dimly
remember that there was some change in some config file in /boot that
was needed to adapt to new firmware, or maybe new firmware for new
kernel.
Diffing from my boot partition (old netbsd-9, works) to a fresh img from
netbsd-9, I see:
Binary files /mnt/boot/EFI/BOOT/bootarm.efi and /mnt2/EFI/BOOT/bootarm.efi differ
Binary files /mnt/boot/boot.scr and /mnt2/boot.scr differ
diff -ur /mnt/boot/cmdline.txt /mnt2/cmdline.txt
--- /mnt/boot/cmdline.txt 2020-06-20 20:24:50.000000000 -0400
+++ /mnt2/cmdline.txt 2022-06-01 23:14:30.000000000 -0400
@@ -1,3 +1,3 @@
-root=ld0a
+root=ld0a console=fb
#fb=1280x1024 # to select a mode, otherwise try EDID
#fb=disable # to disable fb completely
Only in /mnt/boot/: kernel7-ok.img
Binary files /mnt/boot/kernel7.img and /mnt2/kernel7.img differ
Binary files /mnt/boot/netbsd-GENERIC.ub and /mnt2/netbsd-GENERIC.ub differ
So I am guessing
bootarm.efi I should update, but this isn't booting via EFI so doesn't
matter
boot.scr I have no idea about but am guessing that could matter
I want serial console, that's ok
kernel7.img is different I know
netbsd-GENERIC.ub is presumably for non-RPI
The actual boot.scr diff
--- /mnt/boot/boot.scr 2020-10-09 03:09:00.000000000 -0400
+++ /mnt2/boot.scr 2022-06-01 23:14:32.000000000 -0400
@@ -1,4 +1,4 @@
-'V_LNetBSD/armv7 bootif test "${soc}" = "tegra210" ; then
+'VjbNetBSD/armv7 bootif test "${soc}" = "tegra210" ; then
# enable PCIe
pci enum
fi
Any clues appreciated; next step is to hook up console and boot with the
new kernel.
Attachment:
signature.asc
Description: PGP signature