Just a heads-up, since aarch64 is more and more easily available in
laptop and workstation form, I'm planning to request for generating LXQt
images for aarch64. In order to unify the workflow, I've filed a
self-contained change and also the corresponding ticket to
rel-eng. If there are any other tickets I should create, feel free to
let me know.
GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E
When you upgrade a SBC from one release to the next using the dnf upgrade method, it updates all the files in the filesystem in the same way as with a standard installation - I guess. So it would be fine to use that method on a SBC installed by arm-image-installer.
But what about the files idbloader.img and u-boot.itb which arm-image-installer copies to the boot media in a separate dd step? Does the dnf method upgrades those, too, or do I have to do it manually afterwards? Or is there something else to do?
I have a Pi 4B 2G with a Uputronics u-blox GPS HAT, which puts the GPS
module serial data on the first serial port lines. The problem is that
U-Boot stops boot on serial input, and the GPS module is always sending
data when it has a fix.
I put Fedora 36 Server on an SD card, and set the U-Boot stdin, stdout,
and stderr environment variables to exclude serial (which wrote
uboot.env), and that worked. Then I unplugged the keyboard... and it
appeared to automatically re-add the serial and stop boot.
I have an extra Logitech unifying receiver I could leave plugged in
(which seems to work), but that needlessly uses up a USB port. Is there
a way to tell U-Boot "no really, ignore input from the serial port"?
Chris Adams <linux(a)cmadams.net>