Created attachment 165220 [details] result of journalctl -u NetworkManager.service SUMMARY Using KDE Neon 5.27 on my Lenovo IdeaPad Pro 5 14APH8, I'm getting intermittent drops in WIFI connection which didn't previously occur on my previous distro (pop!OS). Usually, websites will fail to load due to DNS failure, and NetworkManager will update its state to "CONNECTED_SITE" within a few minutes (which triggers the plasmoid to show the little ! symbol) and eventually recovers. I can action a recovery faster by manually restarting the system daemon or toggling airplane mode with Fn + F8. I've scoured the available logs in journalctl and nothing seems to happen to "cause" the dropped network connectivity, just that eventually the daemon realizes it's disconnected and eventually sorts itself out. I've tried disabling ipv6, clearing the network keychain password in kwallet, setting the wifi security to "unencrypted" in wifi settings, and disabling power management in NetworkManager. Nothing seems to help unfortunately. As said before, this wasn't an issue with Pop!OS which is also Ubuntu-based, but I know it's significantly modified compared to that of Neon, so I'm hoping asking here might get me somewhere. STEPS TO REPRODUCE 1. Connect to Wifi 2. Wait/browse internet as usual OBSERVED RESULT "Limited Connectivity" notification eventually appears until I toggle airplane mode or restart NetworkManager daemon EXPECTED RESULT Network remains connected SOFTWARE/OS VERSIONS uname -a result: Linux tom-83am 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ADDITIONAL INFORMATION from lspci: Network controller: MEDIATEK Corp. Device 0616 I believe that's an MT7925 wifi card, if duckduckgo serves me well.
I've tried a Pop!OS live USB and the network is pretty much perfect. I'm gonna go on a whim and say that there's something going on with the network manager config or some kind of driver mismatch. As such, here's a link from diffchecker that shows the difference between: 1. lsmod for pop!OS (left) and kde neon (right) https://www.diffchecker.com/4conkDJK/ 2. nmcli device show for pop!OS (left) and kde neon (right) https://www.diffchecker.com/lPA4U1KR/ Both links will expire 1 month from now, so you may need me to re-run and re-post if you're visiting later.
Investigating further, it looks like an update to the drivers is causing issues. KDE Neon's live USB worked fine, and a fresh install of the distro (wiped everything) seemed to fix the issue... until the first system updates were applied. Searching "kernel 6.5.0 mt 7921e" it appears there's a bunch of issues with this driver. That being said, I saw some suggestions saying to boot down the laptop, unplug it, and hold the power button for ~60s to properly powerdown the components and properly configure the updated drivers. I *think* it's working better now, but might leave this bug up to see if there's a software issue that someone else can identify from my logs. Will update if it poops out again. (also, disabled ipv6 but it had no effect)
Nope, it's crapping out again. Have followed some discussions on the framework forums as they use the same SoC and WiFi adapter on the Framework, and one suggestions was to copy changes from the linux-firmware git repo: https://community.frame.work/t/responded-slow-wi-fi-on-amd-7040-with-ubuntu-22-04/43375 Will be testing. Once again working "okay" but I can't be sure until it happens again but right now I've gone for about an hour without more than 2 consecutive dropped packets.
Yup. The new drivers in linux-firmware's git fixed it for me. However, Ubuntu insists on pushing updates which seem to revert my changes to the older firmware and reproducing the issue. For now, I'm just replacing the updates as and when they occur. Either way, I'm not too experienced in how these bugs are handled (Where do I send reports? There's dozens of projects with individual bug trackers that have some influence on this) so advice on how to properly get this fixed for more than just myself would be good.
Latest firmware updates appear to fix. If not, recommend copying changes from linux-firmware repo as prev. mentioned.