Brad Spencer <brad%anduin.eldar.org@localhost> writes:
> I can say with 100% certainty that the
> ${FAVORITE_RELEASE_BASE}/evbarm/binary/gzimg/rpi.img.gz works from a 9.x
> build works just fine on RPI3, RPI2 and RPI0. I run several RPI systems
> on 9.x.
>
> What I have usually done when updating an existing system is update the
> kernel7.img or kernel.img file with the new kernel I want to try and try
> booting up the system. If it doesn't boot correctly or probably at all
> THEN I replace all of /boot on the system with the /boot from that
> mentioned rpi.img.gz file.
Thanks for the confirmation. I went through this more slowly and found
that the problem was PEBKAC. I had a script to install a kernel from a
releasedir rsync or sshfs mount, and it was putting the .bin kernel into
/boot/kernel7.img. That doesn't boot or rather probably doesn't do
anything useful because the dtbs are not loaded. For that, you need the
.img flavor of the kernel.
With the right kernel, everything is fine.
Just for cleanliness, I did diff and update /boot from a recent
armv7.img, which meant boot.scr and efiboot on two systems, and the
netbsd-GENERIC.ub kernel. I think these are all unused but it seems
just as well to take all deviations from tip of netbsd-9 off the table.
The amusing thing is that I explained in the HOWTO about bin and img.
I have not looked into -current.
So:
Why is the .bin format kernel built on netbsd-9? It seems like it
can't work, so its presence is confounding with no benefit. But
obviously I oo not really understand everything...
Attachment:
signature.asc
Description: PGP signature