On Fri, April 17, 2020 11:47 am, Peter Robinson wrote: [snip] >> I'll let you know in a couple hours how the testing goes -- unless >> you've >> seen this before and have an easy fix? Upgrading the Fedora-Minimal-31 system to 5.5.16-200.fc31.armv7hl and it's still working. > I've not seen it before but what I recommend is to go to a generic > initrd so it pulls in all the drivers, move over to the new device and > then allow it to go back to a host specific initrd. See https://bugzilla.redhat.com/show_bug.cgi?id=1698208 > I suspect there's slightly different HW requirements. Could be. I can try that. Right now I'm upgrading the "older" system to 5.5.16, so I'll test that first, but if that fails then I can go your route and "dnf reinstall" the kernel package after adding the dracut-config-generic package. > To do this install the dracut-config-generic package and reinstall or > upgrade the kernel, it'll be slower to boot, make sure it boots on the > current device, move to the new one. > > Once it's running on the new one remove the package and the next > kernel will go back to a host specific initrd with the specific initrd > for the new HW. > > Peter Thanks, -derek -- Derek Atkins 617-623-3745 derek@xxxxxxxxx www.ihtfp.com Computer and Internet Security Consultant _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx 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://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
