Maintenance after Debian Trixie about rtl88x2bu

[Lid2be]

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

[cilynx]

Agreed. Readme has been updated with commentary on mainline and a link to this issue for anyone interested to comment.

[S-K-Tiger]

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

[3vi1]

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.

[MaxG87]

@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.

[3vi1]

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.