To hang a little more meat on this bone,
I've used the update/full-upgrade process with moOde 6.5.2 on four different model RPIs: ZeroW, 3A+, 3B+, and 4B. Expect it to take a while, especially with the single-core ZeroW.
I won't claim to have tested exhaustively but so far no anomalies have popped up as a result of this upgrade. Before the upgrade, the 4B was running on the 64-bit kernel while the others were on the default 32-bit kernel, so I know the kernels are handled.
Two sample moodeutl outputs:
Code:
The ZeroW
20200529 225832 worker: -- System
20200529 225838 worker: Host (moode0w)
20200529 225838 worker: moOde (6.5.2 2020-05-03
20200529 225838 worker: Raspbian (10.4)
20200529 225838 worker: Kernel (4.19.118+ #1311)
20200529 225838 worker: Platform (Pi-Zero W 512MB v1.1)
20200529 225838 worker: ARM arch (armv6l, 32-bit kernel)
---------------
The 4B
20200529 164307 worker: -- System
20200529 164308 worker: Host (moodelr)
20200529 164308 worker: moOde (6.5.2 2020-05-03)
20200529 164308 worker: Raspbian (10.4)
20200529 164308 worker: Kernel (4.19.118-v8+ #1311)
20200529 164308 worker: Platform (Pi-4B 2GB v1.1)
20200529 164308 worker: ARM arch (aarch64, 64-bit kernel)
One bug already announced in the usual channels: this 10.4 upgrade breaks the beta USB boot code for the RPi4B. A workaround has been published.
My RPi3B+ under test was already configured to boot from a USB thumbdrive without a uSD card present and that still works after the upgrade.
Regards,
Kent