On Fri, Jan 14, 2022 at 10:55 AM David W. Legg <email@example.com> wrote:
So, then I reverted to my working 5.14.10 kernel and did a:
dnf update --exclude=kernel*
which included an update up to:
uboot-images-armv8-2021.10-2.fc35 was our release version, uboot-images-armv8-2021.10-3 is in updates.
and re-booted. Everything is fine.
So, the only known problem I have is the 5.15.13-200.fc35.aarch64 upgrade.
There is a bit of a delay before it boots, but it should work. I have it running on a few RPi4s. I would be interested if you
see the same errors you saw previously with the kernel provided dtb.
The dtb symlink gets recreated on kernel upgrade, if you want to continue using the firmware provided dtb you'll need
to 'sudo echo "FirmwareDT=True" >> /etc/u-boot.conf'. That will stop the symlink from getting recreated on every kernel
arm mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://firstname.lastname@example.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Post a Comment