Peter,
On Fri, April 17, 2020 12:09 pm, Derek Atkins wrote: [snip]
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.
So I had to dnf reinstall kernel{,-core,-modules}-5.5.16-200.fc31.armv7hl to get it to rebuild the initramfs. Just reinstalling 'kernel-..' was not sufficient.
However it was also not sufficient to get past this issue. I still have the same failure, same oops, and the system doesn't come up. So there must be something with the old disk or something about upgrading from F25 -> F31 that leaves something behind that this device doesn't like. If nothing else, it does not come up on the network using the old disk in the new board.
So the generic initramfs is not sufficient. I guess if I want to swap hardware I need to start from a fresh SD card F31-Minimal and migrate all my configuration. :-(
Any other suggestions?
-derek