Slow WiFi download speeds for network adapter RTL8852BE

FIX (clean + correct approach)

Step 1 — remove ALL Git Realtek drivers

Run:

sudo dkms remove rtw89_8852be_git --allsudo dkms remove rtw89_8852b_git --all

If any say “not found”, that’s fine.


Step 2 — remove Broadcom STA (important cleanup)

sudo dkms remove broadcom-sta --all

Then blacklist it:

echo "blacklist wl" | sudo sudo tee /etc/modprobe.d/blacklist-broadcom.conf

Step 3 — force use of kernel driver

Create a clean config:

echo "blacklist rtw89_8852be_git" | sudo tee /etc/modprobe.d/blacklist-rtw89-git.conf

Step 4 — rebuild initramfs (important)

sudo update-initramfs -u

Step 5 — reboot

sudo reboot

After reboot, verify

Run:

lsmod | grep rtw89

You SHOULD see:

  • rtw89_8852be
  • rtw89_core
  • rtw89_pci

:cross_mark: You should NOT see anything with _git


Expected result after fix

Your Wi-Fi link should jump from:

  • :cross_mark: 54 Mbps (broken legacy mode)
    to:
  • :white_check_mark: 300–1200+ Mbps (Wi-Fi 6 normal behavior)

And your speedtest should go from:

  • :cross_mark: ~17 Mbps
    to:
  • :white_check_mark: 150–600+ Mbps (depending on ISP/router)

Why this happened (short version)

Your system has been “upgraded” with experimental DKMS drivers (rtw89_*_git) that:

  • override kernel Wi-Fi stack
  • break modern modulation modes
  • force fallback to legacy 802.11a/g rates (54 Mbps cap)

Did it work ?

1 Like

At any point above, has it been suggested that @Etidorhpa switch their Router OFF/ON to see if any effect?

1 Like

in fact the problem came with kernel 6.15 it affect linux with Technicolor router, I made him install liquorix but the bug is still there, so will go back to 6.14, I didn't read that till today and I'm waiting the user confirm me that what you see above work but I have many doubts

1 Like

Good news. I isolated the issue by trying a hotspot connection from my phone. Low and behold the connection speed was there. So the issue is with the router. You mentioned this awhile ago but we never did this simple check but now we know.

Yes it is the router but I haven't discovered what it is exactly.

I explain, The linux kernel since 6.15 introduce a bug for your RTL8852BE, it lead to a problem when your computer negotiate the connection with your router, so your router is not the problem but the kernel, that's why with Windows 11 you had a clean connection.
I will write you in few minutes a next fix to try to give you back decent connection. (I ever started to write it but I want to be sure it's easy to follow)

1 Like

Copy it on your computer and save it in a file to have it offline

Fix slow Wi-Fi (stuck at ~54 Mbps) on Comcast/Xfinity gateways — Linux kernel 6.14 workaround

What this fixes

If your Linux machine connects to an Xfinity/Comcast (or Rogers / Videotron) Wi-Fi gateway and your speed is stuck around 15–50 Mbps, while the same network is fast on phones and Windows, you are very likely hitting this bug.

A recent Comcast gateway firmware update makes the router advertise an invalid "basic MCS set". Linux kernels 6.15 and newer check this value, conclude the link can't meet it, and disable Wi-Fi 4/5/6 — dropping you all the way back to old 802.11a (54 Mbps max, 20 MHz). It hits Realtek, Intel and Qualcomm cards alike, because the bug is in the kernel's shared Wi-Fi layer (mac80211), not in your card.

This guide makes your machine boot kernel 6.14, which is older than that check, so full-speed Wi-Fi works again.

:warning: This is a workaround, not a permanent fix. See the note at the bottom for the clean long-term solution.


Step 0 — Confirm you actually have THIS problem

Open a terminal and run:

sudo dmesg | grep -i "disabling HT"

If you see a line like required MCSes not supported, disabling HT, this guide is for you.
If it prints nothing, your slow Wi-Fi has a different cause — stop here, this won't help.


Step 1 — Install the 6.14 kernel

sudo apt update
sudo apt install linux-image-6.14.0-37-generic linux-modules-6.14.0-37-generic linux-headers-6.14.0-37-generic

If apt says "Unable to locate package", list what's available and use the highest 6.14 number you see:

apt list 'linux-image-6.14.0-*-generic' 2>/dev/null

Then run the install command again, replacing -37 with that number in all three package names.

(Installing the -headers package matters: it lets any add-on Wi-Fi driver rebuild itself automatically for the new kernel.)


Step 2 — Make the boot menu visible and tidy

Open the GRUB settings:

sudo nano /etc/default/grub

Make these four lines look exactly like this — edit them if they already exist, add them if they're missing:

GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=y
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10

Save and exit: press Ctrl+X, then Y, then Enter.

Apply the change:

sudo update-grub

Step 3 — Set kernel 6.14 as the permanent default

Copy-paste this whole block. It finds the 6.14 entry automatically and pins it:

ENTRY=$(grep "menuentry '" /boot/grub/grub.cfg | grep 6.14 | head -n1 | cut -d"'" -f2)
sudo grub-set-default "$ENTRY"
echo "Default boot set to: $ENTRY"

The last line should print something containing 6.14.
If it prints an empty name, the 6.14 kernel didn't install — go back to Step 1.


Step 4 — Reboot

sudo reboot

Step 5 — Verify it worked

After you log back in:

uname -r

→ should show 6.14.0-...

sudo dmesg | grep -i "disabling HT"

→ should now be empty

iw dev wlp1s0 link

(Replace wlp1s0 with your Wi-Fi interface name if different — find it with iw dev.)
→ should show something like rx bitrate: ... HE-MCS ... 80MHz instead of 54.0 MBit/s.

Run a speed test to confirm you're back to normal speeds.


If something goes wrong

  • No Wi-Fi at all on 6.14 (no networks listed): an add-on driver failed to rebuild. Run sudo dkms autoinstall, then reboot.
  • You want to go back to the previous kernel: reboot and pick the other (newer) kernel from the boot menu. To make it the default again:
    sudo grub-set-default 0 && sudo update-grub
    

Important

  • Do NOT uninstall your old kernel — keep it as a safety fallback.
  • If your Wi-Fi becomes slow again after a future system update, your machine probably booted a newer kernel. Just redo Step 3 and reboot (or pick the 6.14 entry from the boot menu).
  • Clean long-term fix: stop using the gateway's Wi-Fi. Put the Comcast box in Bridge mode and use your own router / access point. That sidesteps the bug entirely and usually restores full speed for every device on the network.

Ok. I'll try when I get home. Thanks

1 Like

Ok I got 6.14 in the grub menu but when it's loaded there is no network. I tried the dkms autoinstall but it said no command found.

show me

uname -r

boot in 6.14 and copy this commands in a file as you will not have wifi
the add-on Wi-Fi driver was only built for your old kernel, and it blocks the kernel's built-in driver. On 6.14 the built-in driver works fine, so we just re-enable it:

sudo mv /etc/modprobe.d/rtw89.conf /etc/modprobe.d/rtw89.conf.disabled
sudo update-initramfs -u
sudo reboot

After it reboots, check Wi-Fi is back:

lsmod | grep rtw89
nmcli device status

sudo mv /etc/modprobe.d/rtw89.conf /etc/modprobe.d/rtw89.conf.disabled
mv: cannot stat '/etc/modprobe.d/rtw89.conf': No such file or directory

On 6.14
The file wasn't where we expected — let's find it and wake up Wi-Fi right now:

grep -rl rtw89 /etc/modprobe.d/
sudo modprobe rtw89_8852be
nmcli device status

Tell me what the first command prints, and whether Wi-Fi shows up after.

abanero@habanero-IdeaPad-5-15ABA7:~$ grep -rl rtw89 /etc/modprobe.d/
habanero@habanero-IdeaPad-5-15ABA7:~$ sudo modprobe rtw89_8852be
[sudo] password for habanero:
modprobe: FATAL: Module rtw89_8852be not found in directory /lib/modules/6.14.0-37-generic

are we looking for the firmware we installed earlier in this whole debugging or is this the firmware from 6.14?

The missing piece is the driver, not firmware, and Zorin keeps Wi-Fi drivers in a separate package I forgot sorry. Boot to liquorix (pick it from the boot menu) so you have internet, then install it:

sudo apt update
sudo apt install linux-modules-extra-6.14.0-37-generic
sudo reboot

It'll boot back into 6.14 by itself and Wi-Fi should come up. If your old kernel has no internet either, plug your phone in by USB and turn on USB tethering to get online for the install.

$ uname -r
6.14.0-37-generic
habanero@habanero-IdeaPad-5-15ABA7:~$ sudo dmesg | grep -i "disabling HT"
[sudo] password for habanero:
[ 13.301475] wlp1s0: required MCSes not supported, disabling HT
habanero@habanero-IdeaPad-5-15ABA7:~$ iw dev wlp1s0 link
Connected to fa:d0:0e:3d:d2:72 (on wlp1s0)
SSID: Konawifi
freq: 5785.0
RX: 618836 bytes (2243 packets)
TX: 155298 bytes (507 packets)
signal: -36 dBm
rx bitrate: 54.0 MBit/s
tx bitrate: 54.0 MBit/s
bss flags: short-slot-time
dtim period: 1
beacon int: 100

:smiling_face_with_tear: after all that.

I'm sorry but It's really a linux kernel problem I was think 6.14 didn't have this problem, I making you a tutorial to go back to liquorix where you will have more chance to obtain a fix with a kernel update, wait few minutes please

Keep this machine on the Liquorix kernel (waiting for the Wi-Fi fix)

Short version

Your slow Wi-Fi is caused by a bug between your Comcast/Xfinity gateway's firmware and recent Linux kernels. There is no clean local fix right now. The best plan is to stay on the Liquorix kernel, because it updates quickly and will receive the eventual official fix sooner than other kernels.

This guide sets Liquorix as your default boot kernel. It does NOT make Wi-Fi faster yet — it just puts you in the best position to get the fix the moment it ships.


Why we can't simply "fix" it

After a firmware update, your Comcast gateway started advertising an invalid "required data-rate" value over the air. Recent Linux kernels follow the Wi-Fi standard strictly: they read that value, conclude the connection can't meet it, and switch off Wi-Fi 4/5/6 — dropping you to old 802.11a (54 Mbps maximum).

A few key points:

  • It's not your laptop or your Wi-Fi card. The exact same thing happens on Intel, Realtek and Qualcomm cards — the decision is made by the kernel's shared Wi-Fi layer, above the driver. Swapping the card or the driver changes nothing.
  • There is no setting to turn it off. No checkbox, no command makes the kernel ignore the bad value.

That's the whole reason for this guide: keep you on the fast-moving Liquorix kernel, keep the system updated, and the fix lands here first.

Step 1 — Set Liquorix as the default boot kernel

Open a terminal and paste this whole block:

ENTRY=$(grep "menuentry '" /boot/grub/grub.cfg | grep -i liquorix | head -n1 | cut -d"'" -f2)
sudo grub-set-default "$ENTRY"
echo "Default boot set to: $ENTRY"

The last line should print an entry name containing liquorix.
If it prints an empty name, stop and report it.

Step 2 — Reboot

sudo reboot

Step 3 — Confirm you're on Liquorix

uname -r

→ should end in -liquorix-amd64.

Then make sure Wi-Fi connects. It will still be the slow ~54 Mbps for now — that's expected until the fix arrives.

If Wi-Fi does not connect at all, run this, then reboot:

sudo modprobe rtw89_8852be || sudo modprobe rtw89_8852be_git

How you'll get the fix when it lands

  • Keep the system updated — use the normal "Software Updater", or in a terminal:
    sudo apt update && sudo apt full-upgrade
    
    Liquorix kernel updates arrive through your normal updates.
  • After a future kernel update, you can check whether the fix is in:
    sudo dmesg | grep -i "disabling HT"
    
    When this command returns nothing and your speed jumps back up, the fix has landed.

Want full speed NOW (optional)

Waiting for the kernel fix could take weeks or months. If you want full speed immediately and permanently, the clean option is to stop using the gateway's Wi-Fi:

  • Put the Comcast box in Bridge mode and use your own router / access point, or
  • Put a Wi-Fi router or extender (one that does not use a recent Realtek chip) between the gateway and your devices.

Either way fixes the problem completely and for every device on your network — not just this laptop.


Notes

  • Keep both kernels installed (Liquorix and the 6.14 one). Don't remove either — they're your fallbacks.
  • This problem is the ISP gateway's fault, not your computer's. Nothing you did caused it.
1 Like