Open MaxG87 opened 6 months ago
Agreed. Readme has been updated with commentary on mainline and a link to this issue for anyone interested to comment.
For me when using rtw88_8822bu I found that, when attempting to connect to a network using saved credentials, it would ask for credentials and ask again if provided repeatedly. Installing rtl88x2bu has fixed this issue for me.
System info
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-31-generic (64-bit)
[...]
System Version: 2.0
Device info
idVendor 0x2357 TP-Link
idProduct 0x0115 Archer T4U ver.3
bcdDevice 2.10
iManufacturer 1 Realtek
iProduct 2 802.11ac NIC
Preface: I have used your driver with Ubuntu and the latest mainline kernels with no problems for years. Thanks so much for maintaining this!
I hope you can continue to maintain this for at least a short while longer. Let me explain:
Since they added rtw88 support in the newer kernels, I've been trying to make that work instead. While that "works" (at first), I'm of the opinion that the drivers in kernel are still suffering from major bugs that make them unsuitable for anything more than testing.
The main problem I experience with the default kernel drivers is that the interface goes down/disappears, usually about 24 hours into use (sometimes less, sometimes more), and the only way to re-establish it is to remove/re-insert the modules. Dmesg points to "Failed to get tx report from firmware" or lps issues (though it happens when the wifi is being actively used). I can expect it to happen anytime my systems been up for a day and I'm doing backups while downloading anything; somehow active USB disk activity seems to be a catalyst for the failures.
Eventually, reloading the drivers won't fix the issue and the system needs an entire reboot to get the wifi working... at which point it's good for maybe another day before it starts showing the same problems again.
I found others online complaining of similar issues. After fighting with it for months and trying everything that other claimed had worked for them (tweaking kernel parameters, turning off wifi powersave, setting lps options on the drivers, etc.) I gave up and tried the lwfinger rtw88 drivers (just slightly newer versions of what's packaged with new kernels, from what I understand). Unfortunately, no change in symptoms when using those.
I even bought a different USB dongle (same chipset) so that I could verify it wasn't a hardware issue. It shows the exact same issue, ruling out hardware.
After retrying all combination of settings, I finally decided to install your drivers again - to verify it really was the kernel drivers and not something else in my ever-changing system configuration. I've now been up for over 3 days without any issue at all using your drivers with kernel 6.10rc4, I have never been able to go more than two full days using the drivers in the newer kernels.
So, again, I'm hoping you continue to keep these compiling with newer kernels until they shake out the issues in the mainlined drivers. I'll continue testing them and report these issues upstream as newer kernels become available, and hopefully they get more feedback as other distros roll with newer kernels.
Thanks for all your hard work. It has been appreciated.
@S-K-Tiger , @3vi1: Thank you very much for sharing this.
I want to reassure you that I am not planning to stop maintenance on this driver in the near future. As stated above, I will continue maintenance at least until Debian Trixie is released. After that, the driver will be functional for three additional releases, since Debian releases stick to the major kernel version the offered at release time.
I think it wouldn't be reasonable to use this driver much longer though. All I do is keeping it compatible with new Kernel releases. Only the in-tree driver will receive potential improvements or security fixes. If you experience issues with the in-tree driver, I want to encourage you report the bugs to your distribution or the maintainer directly.
That's great to hear. I'll definitely be reporting issues whenever the amd64 6.10 kernel is available (it doesn't look like they've had a successful build since rc4 at https://kernel.ubuntu.com/mainline/v6.10/) and I can test.
Until then, I'm very grateful to have your drivers. It's been 3 weeks now and yours have been steady as a rock whereas the in-kernel drivers all through 6.9 (maybe earlier... I forget) and 6.10rc4 fail after a day.
Hi all. I've just started using Linux Mint 22 (uname -a: 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC x86_64 x86_64 x86_64 GNU/Linux
) and my WI-Fi adapter had not worked. I've compiled this project and run sudo modprobe cfg80211
and sudo insmod 88x2bu.ko
and Wi-Fi works. What does it mean? Does the kernel I use have support included or not? TIA
In my copy of the Kernel sources version 6.8 includes the folder drivers/net/wireless/realtek/rtw88
. However, every distribution is free to provide and configure whatever it considers to be reasonable. So, maybe your Kernel does not yet support your WIFI adapter. Since Linux Mint 22 is rather new, maybe tutorials on how to activate trw_88_8822b
and rtw88_8822bu
have yet to be written.
@Lid2be On Ubuntu 22.04, it works for me after installing linux-image-generic-hwe-22.04
. It installs linux-image-6.8.0-45-generic
and (importantly) linux-modules-extra-6.8.0-45-generic
. The extra kernel modules contain rtw88_8822bu
which gets automatically loaded on boot if the adapter is plugged in.
Thank-you @cilynx and @MaxG87 for maintaining this driver.
I recently upgraded to Ubuntu 24.04.1 LTS and found that the drivers you have noted are installed for me by default, but they cease to work after about an hour. Additionally a generic speedtest between the rtw88 and 88x2bu drivers show that the 88x2bu sustains at least twice the bandwidth (on my system at least). I will periodically check the rtw88 driver for improvements, but will stick with your drivers for the moment.
Wifi Device:
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0xb812 RTL88x2bu [AC1200 Techkey]
bcdDevice 2.10
iManufacturer 1 Realtek
iProduct 2 USB3.0 802.11ac 1200M Adapter
Preface: I have used your driver with Ubuntu and the latest mainline kernels with no problems for years. Thanks so much for maintaining this!
I hope you can continue to maintain this for at least a short while longer. Let me explain:
Since they added rtw88 support in the newer kernels, I've been trying to make that work instead. While that "works" (at first), I'm of the opinion that the drivers in kernel are still suffering from major bugs that make them unsuitable for anything more than testing.
The main problem I experience with the default kernel drivers is that the interface goes down/disappears, usually about 24 hours into use (sometimes less, sometimes more), and the only way to re-establish it is to remove/re-insert the modules. Dmesg points to "Failed to get tx report from firmware" or lps issues (though it happens when the wifi is being actively used). I can expect it to happen anytime my systems been up for a day and I'm doing backups while downloading anything; somehow active USB disk activity seems to be a catalyst for the failures.
Eventually, reloading the drivers won't fix the issue and the system needs an entire reboot to get the wifi working... at which point it's good for maybe another day before it starts showing the same problems again.
I found others online complaining of similar issues. After fighting with it for months and trying everything that other claimed had worked for them (tweaking kernel parameters, turning off wifi powersave, setting lps options on the drivers, etc.) I gave up and tried the lwfinger rtw88 drivers (just slightly newer versions of what's packaged with new kernels, from what I understand). Unfortunately, no change in symptoms when using those.
I even bought a different USB dongle (same chipset) so that I could verify it wasn't a hardware issue. It shows the exact same issue, ruling out hardware.
After retrying all combination of settings, I finally decided to install your drivers again - to verify it really was the kernel drivers and not something else in my ever-changing system configuration. I've now been up for over 3 days without any issue at all using your drivers with kernel 6.10rc4, I have never been able to go more than two full days using the drivers in the newer kernels.
So, again, I'm hoping you continue to keep these compiling with newer kernels until they shake out the issues in the mainlined drivers. I'll continue testing them and report these issues upstream as newer kernels become available, and hopefully they get more feedback as other distros roll with newer kernels.
Thanks for all your hard work. It has been appreciated.
I had the same issue, too. In my case, unplugging my adapter and plugging it back in fixed it, but it was still annoying.
My speed seem to be the same though, but i will continue to use this driver until the mainline one is fixed.
Thank you everyone for your responses. It means a lot to me to see that people depend on this.
Your messages helped me to understand better the connection loss I encountered. I wasn't aware that my issue was caused by the in-tree driver. I was accepting it without other thoughts. I switched back to the driver of the repository and will pay attention whether this helps.
I want to stress again that maintenance will endure at least until Trixie is released. Given the reported issues it is likely I will continue after it.
We really appreciate that @MaxG87 . As of the 6.11 kernels, my testing shows the mainline drivers are still very flaky and lose connection after a couple of days (or even within hours sometimes). I've tested with multiple external 88x2bu USB adapters and get the same results.
The drivers from this repo, however, continue to be rock solid with both adapters (in use 8 days at the moment with no issues).
I recently migrated to Debian Trixie (which is still testing). Since then I have the drivers
rtw88_8822b
andrtw88_8822bu
available by the distribution. Therefore, I am no longer dog-footing the driver.I think, soon the repository will not be required any more. I think it is reasonable to continue maintenance until the release of Debian Trixie. After that, I consider to stop fixing compilation issues.
Are there any thoughts on this? Should a remark on this be added to the README, so others can prepare or ask for longer support?