Whenever I use rpi-update on a 64-bit Raspberry Pi, it copies 32-bit kernels to the boot partition. Then on the following boot, it thinks I'm running a 32-bit kernel and fails to boot. The system was booting fine prior to running rpi-update, so I expect that it should not clobber a working system.
My suggestion: If rpi-update is run on a 64-bit system, please don't copy the 32-bit kernels. Or check if the 32-bit kernels are there, and only copy the 32-bit kernels if they are.
I know I can set a config.txt option, but that's redundant and forces me to maintain separate config.txt files for each OS variant.
Whenever I use
rpi-updateon a 64-bit Raspberry Pi, it copies 32-bit kernels to the boot partition. Then on the following boot, it thinks I'm running a 32-bit kernel and fails to boot. The system was booting fine prior to runningrpi-update, so I expect that it should not clobber a working system.My suggestion: If
rpi-updateis run on a 64-bit system, please don't copy the 32-bit kernels. Or check if the 32-bit kernels are there, and only copy the 32-bit kernels if they are.I know I can set a config.txt option, but that's redundant and forces me to maintain separate config.txt files for each OS variant.