moore-bryan
Hey Bryan, I've been tracking your issue for the last few months because I had it too. I have a Realtek wifi drive. Sometime in December of January the Wifi in my Solus Budgie stopped working. I was going to reinstall but I tried Manjaro Budgie for about two weeks just because I was wiping the HD. During the second week, the Wifi stopped working. I installed Solus KDE sometime around February and I gotsoemtimes download updates, sometimes not. It hung alot. Eventually I couldn't use it at all for anything web related, ethernet or wifi.
Last night I was determined to fix it so I hunted down your posts. to figure it out.
I did:
sudo clr-boot-manager list-kernels
I had current-5.5.7-150. It was a fresh install so nothing to revert too. It's on another device and I didn't screenshot.
After that I did
sudo eopkg install linux-lts linux-lts-headers
After that I shutdown (not restart) following some advice I had seen just in case. After the bootloader popped up I saw the LTS (I believe 4.9.something) and then to ensure I automatically started with this kernel I typed:
sudo clr-boot-manager update
Once I did that I was able to use the LTS Kernel and my Wifi worked without any problems. The speed wasn't great.. I have a 2.4Gh Wifi card and I only got between 30-55Mbs downloads on the bare wireless connection. My ISP usually can get me upwards of several hundred Mbs so this was disappointing.
But the computer was usable and it only took me 15 minutes once I researched for about an hour to make sure I did everything correctly. Apparently many people have this same wifi issue with a variety of cards.
NOTE: I found two commands while researching that I think you might find useful.
lsmod gives you a rundown of the drivers you have installed
AND
last gives you a list of the last kernel changes you've booted up in and how long your device was up and running for.
reboot system boot 5.4.12-144.curre Wed Jan 29 12:04 - 11:00 (22:56)
reboot system boot 5.4.12-143.curre Sun Jan 19 08:02 - 18:07 (9+10:04)
reboot system boot 5.3.18-140.curre Mon Jan 13 15:20 - 18:07 (15+02:46)
reboot system boot 5.3.15-138.curre Fri Dec 27 11:44 - 15:01 (17+03:17)
reboot system boot 5.4.1-137.curren Mon Dec 9 04:43 - 23:38 (17+18:55)
reboot system boot 5.4.1-137.curren Sun Dec 8 02:35 - 04:40 (1+02:04)
reboot system boot 5.3.13-135.curre Fri Dec 6 20:33 - 02:31 (1+05:57)
My entire output was longer and this isn't from the device I changed kernels on. But this should give you an idea of what the last comman does and a timeframe for when the kernel changes were implemented. The devs here seem to have rolled back a kernel update at some point because I have never messed around with the kernel before now.
Hope this helps!