Hmm this is a bit bizarre, that driver wasn’t touched at all in 5.2.9. My thought was maybe it’s a bad mix of linux-firmware and the kernel, but those firmware files haven’t been touched in quite a while.
On a boot where the WiFi fails, what do dmesg and journalctl -b -u NetworkManager say?
Not that it matters now; but the link you gave is for 5.2.9 which as fine when I was using it. The problem I had was with 5.2.11 (only after that update did 5.2.9 stop working, so I fell back to 5.2.8). Now, for what ever reason, 5.2.11 seems to have un-pooped itself.
This just happened to me. The update from 5.13.16-300 to 5.4.7-200 killed my Network Manager. So I’ve just been booting into 5.13.16 figuring the next update would fix it. But now it’s updated 5.4.8 and still not. Fedoro only saves two back, so if the next update doesn’t fix things, I’ll have to reinstall unless someone has a fix. Here’s my basic info:
Did that same thing to my wired connection, in that it would not connect, and it cycled through cable unplugged and back to connecting, every 10 seconds. I deleted the network connection, added a fresh one back, and set the auto negotiation to manual. It immediately started working. Try removing the wireless connecton settings, create them again, and see if that works.
did a fresh reinstall of Fedora 31. Everything works now.
Update: Spoke too soon. Everything worked until I updated. I reinstalled multiple times and tried to isolate which package was the problem. Turns out there were two. Kernel updates killed the WiFi, another package (somewhere in the c’s (I updated chunks alphabetically to go faster)) would just kill the program completely. Bootup would just always hang with a black screen and cursor. So, since I’ve got work to do, and spent 12+ hours trying to workaround, I’m giving up. Switching to Mint. Peace all, and thanks for your help.