RTL8822CE connectivity issues after fresh installation

josepepito · 2025-03-14 21:53:35

Hi everyone, I'm having some problems with Wi-Fi connectivity on my laptop, and I'd want to solve it.

The thing is, the laptop seems to connect properly to the wifi network but it does get no internet (on any network), ethernet works flawlessly. Here are some outputs when trying to ping connected to a wireless connection:

 
[ganxo@ganxotatil ~]$ ping google.com
ping: google.com: Temporary failure in name resolution

[ganxo@ganxotatil ~]$ ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.11.44 icmp_seq=1 Destination Host Unreachable
From 192.168.11.44 icmp_seq=2 Destination Host Unreachable
From 192.168.11.44 icmp_seq=3 Destination Host Unreachable
From 192.168.11.44 icmp_seq=4 Destination Host Unreachable

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3066ms
pipe 3

Here are some logs of NetworkManager and wpa_supplicant (I've also tried to change the backend to iwd, or activatind dhcpcd but the problem persists):

Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5678] device (wlan0): supplicant interface state: associated -> completed
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5682] device (wlan0): ip:dhcp4: restarting
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5683] dhcp4 (wlan0): canceled DHCP transaction
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5683] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5684] dhcp4 (wlan0): state changed no lease
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5685] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5758] dhcp4 (wlan0): state changed new lease, address=****************, acd pending
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5773] dhcp4 (wlan0): state changed new lease, address=****************
Mar 14 22:28:09 ganxotatil NetworkManager[552]: <info>  [1741987689.3179] device (eno1): state change: activated -> unavailable (reason 'carrier-changed', managed-type: 'full')
Mar 14 22:28:09 ganxotatil NetworkManager[552]: <info>  [1741987689.3490] policy: set 'pelukass1' (wlan0) as default for IPv4 routing and DNS

(I've censored the addresses in case you were wondering)

However, when looking at the kernel logs there's something about the wifi card driver that doesn't feel right. The only way to avoid these messages is to plug and unplug the ethernet cable, then wifi connection starts working fine. First these are some kernel logs about the driver module, that also pop up after booting on a tty or ly (login manager):

Mar 14 22:27:07 ganxotatil kernel: rtw_8822ce 0000:03:00.0: failed to send h2c command
Mar 14 22:27:09 ganxotatil kernel: rtw_8822ce 0000:03:00.0: firmware failed to leave lps state
Mar 14 22:27:09 ganxotatil kernel: rtw_8822ce 0000:03:00.0: failed to send h2c command
Mar 14 22:27:11 ganxotatil kernel: rtw_8822ce 0000:03:00.0: firmware failed to leave lps state
Mar 14 22:27:11 ganxotatil kernel: rtw_8822ce 0000:03:00.0: failed to send h2c command
Mar 14 22:27:13 ganxotatil kernel: rtw_8822ce 0000:03:00.0: firmware failed to leave lps state
Mar 14 22:27:13 ganxotatil kernel: rtw_8822ce 0000:03:00.0: failed to send h2c command
Mar 14 22:27:15 ganxotatil kernel: rtw_8822ce 0000:03:00.0: firmware failed to leave lps state
Mar 14 22:27:17 ganxotatil kernel: rtw_8822ce 0000:03:00.0: firmware failed to leave lps state
Mar 14 22:27:17 ganxotatil kernel: rtw_8822ce 0000:03:00.0: failed to send h2c command
Mar 14 22:27:19 ganxotatil kernel: rtw_8822ce 0000:03:00.0: firmware failed to leave lps state
Mar 14 22:27:20 ganxotatil kernel: rtw_8822ce 0000:03:00.0: failed to get tx report from firmware
Mar 14 22:27:21 ganxotatil kernel: rtw_8822ce 0000:03:00.0: firmware failed to leave lps state
Mar 14 22:27:21 ganxotatil kernel: rtw_8822ce 0000:03:00.0: failed to send h2c command
Mar 14 22:27:21 ganxotatil kernel: rtw_8822ce 0000:03:00.0: failed to send h2c command

This is the thing about unplugging the cable that I mentioned:

Mar 14 22:27:21 ganxotatil NetworkManager[552]: <info>  [1741987641.0326] device (wlan0): supplicant interface state: completed -> disconnected
Mar 14 22:27:21 ganxotatil NetworkManager[552]: <info>  [1741987641.3315] device (wlan0): supplicant interface state: disconnected -> scanning
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.3692] device (wlan0): supplicant interface state: scanning -> authenticating
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.3831] device (wlan0): supplicant interface state: authenticating -> associating
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.4145] device (wlan0): supplicant interface state: associating -> associated
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5678] device (wlan0): supplicant interface state: associated -> completed
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5682] device (wlan0): ip:dhcp4: restarting
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5683] dhcp4 (wlan0): canceled DHCP transaction
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5683] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5684] dhcp4 (wlan0): state changed no lease
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5685] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5758] dhcp4 (wlan0): state changed new lease, address=192.168.11.44, acd pending
Mar 14 22:27:25 ganxotatil NetworkManager[552]: <info>  [1741987645.5773] dhcp4 (wlan0): state changed new lease, address=192.168.11.44
Mar 14 22:27:35 ganxotatil systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 14 22:28:09 ganxotatil NetworkManager[552]: <info>  [1741987689.3179] device (eno1): state change: activated -> unavailable (reason 'carrier-changed', managed-type: 'full')
Mar 14 22:28:09 ganxotatil NetworkManager[552]: <info>  [1741987689.3490] policy: set 'pelukass1' (wlan0) as default for IPv4 routing and DNS
Mar 14 22:28:19 ganxotatil systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

As you can see, the kernel messages stopped after doing the unplug thing, so it must be something about the driver or the module that is not working properly on the software.

I think is worth mentioning that on other distributions (fedora) I didn't have any issues, and with a live ISO or USB I the connection is successful.

Thanks you for your help, have a great day!

[EDIT] Some updates and additional information:

After some minutes, the wifi disconnects again. Here are some dmesg logs of that moment:

https://pastebin.com/sxmb7qMN

Appart from that, Irealised I haven't showedsome useful outputs. Here's the output of lscpi -v of the card:

03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter
	DeviceName: WLAN
	Subsystem: Hewlett-Packard Company Device 85f7
	Flags: bus master, fast devsel, latency 0, IRQ 149
	I/O ports at 3000 [size=256]
	Memory at 50800000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: rtw_8822ce
	Kernel modules: rtw88_8822ce

Last edited by josepepito (2025-03-14 23:33:24)

cantabile · 2025-03-15 22:05:39

I think is worth mentioning that on other distributions (fedora) I didn't have any issues, and with a live ISO or USB I the connection is successful.

That's very important. It suggests you did this to yourself. Did you install tlp?

josepepito · 2025-03-15 23:00:19

Hi, thanks for your help.

I guess I did, I installed it with the archinstall script. And no, I didn't install tlp nor any other power management tool

cantabile · 2025-03-16 21:25:59

Okay, maybe it's not something you did.

Try this in /etc/modprobe.d/rtw88_8822ce.conf:

options rtw_pci disable_aspm=y disable_msi=y
options rtw_core disable_lps_deep=y

options rtw88_pci disable_aspm=y disable_msi=y
options rtw88_core disable_lps_deep=y

And power off the computer. Rebooting is not enough for disable_aspm.

Last edited by cantabile (2025-03-16 21:26:25)

josepepito · 2025-03-16 21:54:09

Hello again, I've tried what you said and nothing seems to change, I'm still having the same issues.

cantabile · 2025-03-16 22:49:40

So the wifi was working fine with the Arch installer? If so, you can install the same kernel version. The 2025.03.01 installer has kernel 6.13.5. You can download it from here: https://archive.archlinux.org/packages/l/linux/

unixman · 2025-03-16 22:59:24

Your problem isn't HW but SW one i guess. ping your router/modem IP to see access ok.

Abondon NetworkManager and try other utils to connect. Maybe problem caused by NetworkManager.

Ensure only one service/app is managed to network device(s).
So disable excess systemd services accordingly. Temporarily disable NetworkManager systemd service and systemd.networkd, systemd.resolvd
Put DNS's to /etc/resolv.conf by hand.
Connect manually and get an IP from DHCP server manually. Even try static IP.

josepepito · 2025-03-17 09:27:54

cantabile wrote:

So the wifi was working fine with the Arch installer? If so, you can install the same kernel version. The 2025.03.01 installer has kernel 6.13.5. You can download it from here: https://archive.archlinux.org/packages/l/linux/

I'm sorry I'm still kind of new to some things. How is the proper way to do this if you don't mind attavhing a link or a wiki page?

josepepito · 2025-03-17 09:44:48

unixman wrote:

Your problem isn't HW but SW one i guess. ping your router/modem IP to see access ok.
Abondon NetworkManager and try other utils to connect. Maybe problem caused by NetworkManager.
Ensure only one service/app is managed to network device(s).
So disable excess systemd services accordingly. Temporarily disable NetworkManager systemd service and systemd.networkd, systemd.resolvd
Put DNS's to /etc/resolv.conf by hand.
Connect manually and get an IP from DHCP server manually. Even try static IP.

I'm going to try this thing first because as far as my knowledge goes the arch install ISO uses iwd and systemd-network, so I'll try first with that and of there is no success then I will change the kernel.

Also, Some thing that you commented:
- i pinged my router and it was the same as pinging a DNS server: Destination Host Unreachable.
- whether I have a DHCP or not, it keeps failing to connect to internet, but I'll try to adjust these thing manually in case is somewhat DHCP's fault.

Thank for your help, I'll update this topic when finishes.

cantabile · 2025-03-17 12:45:27

josepepito wrote:

cantabile wrote:
So the wifi was working fine with the Arch installer? If so, you can install the same kernel version. The 2025.03.01 installer has kernel 6.13.5. You can download it from here: https://archive.archlinux.org/packages/l/linux/
I'm sorry I'm still kind of new to some things. How is the proper way to do this if you don't mind attavhing a link or a wiki page?

You can do it like this:

pacman -U 'https://archive.archlinux.org/packages/l/linux/linux-6.13.5.arch1-1-x86_64.pkg.tar.zst'

josepepito · 2025-03-17 20:57:43

unixman wrote:

Your problem isn't HW but SW one i guess. ping your router/modem IP to see access ok.
Abondon NetworkManager and try other utils to connect. Maybe problem caused by NetworkManager.
Ensure only one service/app is managed to network device(s).
So disable excess systemd services accordingly. Temporarily disable NetworkManager systemd service and systemd.networkd, systemd.resolvd
Put DNS's to /etc/resolv.conf by hand.
Connect manually and get an IP from DHCP server manually. Even try static IP.

Hi again, I've tried everything that you said. I've changed to systemd-networkd and iwd to see if everything worked, and it didn't.

Also, I've disabled any DNS resolver I had runnning and tried to configure the /etc/resolv.conf file myself, but it didn't do anything, and the same goes to rtying to configura a manual IP for the wireless connections.

I also checked if the laptop was present in a list my router has of connected devices, but it didn't, even with the networkd/systemd and the laptop saying that it was properly connected, so it's kinda strange.

unixman · 2025-03-18 15:25:47

i have RTL nic too. iwd is not compatible RTL nic's. i cant connect via iwd.
So remove it from the system to avoid interfere/conflict.
play with them: "/sys/module/rtw88*/parameters/*" ips, swlps, fwlps maybe others.

Ensure rtl-firmware installed. Try other kernels available in repo.
Test wired connections works or not if you have wired NIC to.(ethernet)
Build own kernel

edit: look at dmesg after every connections attemps to see there is any meaningfull info exists.

Last edited by unixman (2025-03-18 15:29:06)

josepepito · 2025-03-18 17:13:54

unixman wrote:

i have RTL nic too. iwd is not compatible RTL nic's. i cant connect via iwd.

Weird. Then, why on the usb installation of arch linux, which uses iwd, is completely usable and connectable to internet?

unixman wrote:

Ensure rtl-firmware installed. Try other kernels available in repo.

I can't find that package. did you mean realtek-firmware? It is marked as outdated and was last modified around 5 years ago, so I don't know.
Also, maybe the LTS kernel would do the trick?

unixman wrote:

Test wired connections works or not if you have wired NIC to.(ethernet)
Build own kernel

edit: look at dmesg after every connections attemps to see there is any meaningfull info exists.

Except the thing about building my own kernel, all of that was specified on my first message, with ethernet everything works flawlessly and the dmesg messages should be on the pastebin.

unixman · 2025-03-18 17:26:15

Hi. I means linux-firmware or whatever arch names it. I use another distro that split firmware to much packages.

My NIC is different model than yours or iwd iprove itself since years i dont use it.
Feel free to try LTS or some others from somewere as long as compatible with arch userland.

Last edited by unixman (2025-03-18 17:27:45)

josepepito · 2025-03-18 17:42:40

unixman wrote:

Hi. I means linux-firmware or whatever arch names it. I use another distro that split firmware to much packages.
My NIC is different model than yours or iwd iprove itself since years i dont use it.
Feel free to try LTS or some others from somewere as long as compatible with arch userland.

Ok, thanks for the aclaration and help

josepepito · 2025-03-18 19:46:50

cantabile wrote:

josepepito wrote:
cantabile wrote:
So the wifi was working fine with the Arch installer? If so, you can install the same kernel version. The 2025.03.01 installer has kernel 6.13.5. You can download it from here: https://archive.archlinux.org/packages/l/linux/
I'm sorry I'm still kind of new to some things. How is the proper way to do this if you don't mind attavhing a link or a wiki page?
You can do it like this:
pacman -U 'https://archive.archlinux.org/packages/l/linux/linux-6.13.5.arch1-1-x86_64.pkg.tar.zst'

Hi again, I've downgraded the kernel to 6.13.5, and ftm using systemd-networkd, iwd and systemd-resolved returns some weird things after pinging:

[ganxo@ganxotatil network]$ ping google.com
ping: google.com: Temporary failure in name resolution
[ganxo@ganxotatil network]$ ping 8.8.8.8
ping: connect: Network is unreachable

It can be something about my DNS configuration that it must be wrong, so there is one pinch of hope left.

Also, when checking the kernel messages, it returns this:

[ganxo@ganxotatil network]$ journalctl -b | grep rtw
Mar 18 20:08:30 ganxotatil kernel: rtw_8822ce 0000:03:00.0: enabling device (0000 -> 0003)
Mar 18 20:08:30 ganxotatil kernel: rtw_8822ce 0000:03:00.0: Firmware version 9.9.15, H2C version 15
Mar 18 20:08:30 ganxotatil kernel: rtw_8822ce 0000:03:00.0: WOW Firmware version 9.9.4, H2C version 15
Mar 18 20:08:30 ganxotatil kernel: rtw_8822ce 0000:03:00.0 wlo1: renamed from wlan0

So I guess it's everythng good with the drivers.

Now, can someone help me with my dns configuration if it's no harm for you?

Thanks beforehand and a lot for resolving me this issue

[EDIT] I solved it, now everything works as expected. Thank a lot for the help and have a nice day!

Last edited by josepepito (2025-03-18 20:13:19)

cyddharth · 2025-09-29 22:06:22

josepepito wrote:

cantabile wrote:
josepepito wrote:
I'm sorry I'm still kind of new to some things. How is the proper way to do this if you don't mind attavhing a link or a wiki page?
You can do it like this:
pacman -U 'https://archive.archlinux.org/packages/l/linux/linux-6.13.5.arch1-1-x86_64.pkg.tar.zst'
Hi again, I've downgraded the kernel to 6.13.5, and ftm using systemd-networkd, iwd and systemd-resolved returns some weird things after pinging:
[ganxo@ganxotatil network]$ ping google.com
ping: google.com: Temporary failure in name resolution
[ganxo@ganxotatil network]$ ping 8.8.8.8
ping: connect: Network is unreachable
It can be something about my DNS configuration that it must be wrong, so there is one pinch of hope left.
Also, when checking the kernel messages, it returns this:
[ganxo@ganxotatil network]$ journalctl -b | grep rtw
Mar 18 20:08:30 ganxotatil kernel: rtw_8822ce 0000:03:00.0: enabling device (0000 -> 0003)
Mar 18 20:08:30 ganxotatil kernel: rtw_8822ce 0000:03:00.0: Firmware version 9.9.15, H2C version 15
Mar 18 20:08:30 ganxotatil kernel: rtw_8822ce 0000:03:00.0: WOW Firmware version 9.9.4, H2C version 15
Mar 18 20:08:30 ganxotatil kernel: rtw_8822ce 0000:03:00.0 wlo1: renamed from wlan0
So I guess it's everythng good with the drivers.
Now, can someone help me with my dns configuration if it's no harm for you?
Thanks beforehand and a lot for resolving me this issue
[EDIT] I solved it, now everything works as expected. Thank a lot for the help and have a nice day!

Hi, new to realtek stuff as well, i am encountering the same problems as you, infact exactly the same on my 8822ce, how did you fix this issue ?

seth · 2025-09-30 06:45:31

The OP downgraded to a 6.13 kernel, the original issue was "firmware failed to leave lps state" and there's essentially no way to get that if https://bbs.archlinux.org/viewtopic.php … 5#p2231935 is correctly applied.

rtw88_pci.disable_aspm=y rtw88_pci.disable_msi=y rtw88_core.disable_lps_deep=y

https://wiki.archlinux.org/title/Kernel_parameters
and cantabile indicated that a full power cycle (maybe taking out the battery) might be require to reset the device (so try that in doubt, but the "failed to leave lps state" needs to go immediately)

systool -vm rtw88_pci
systool -vm rtw88_core

to prove that the parameters were applied.

Arch Linux

#1 2025-03-14 21:53:35

RTL8822CE connectivity issues after fresh installation

#2 2025-03-15 22:05:39

Re: RTL8822CE connectivity issues after fresh installation

#3 2025-03-15 23:00:19

Re: RTL8822CE connectivity issues after fresh installation

#4 2025-03-16 21:25:59

Re: RTL8822CE connectivity issues after fresh installation

#5 2025-03-16 21:54:09

Re: RTL8822CE connectivity issues after fresh installation

#6 2025-03-16 22:49:40

Re: RTL8822CE connectivity issues after fresh installation

#7 2025-03-16 22:59:24

Re: RTL8822CE connectivity issues after fresh installation

#8 2025-03-17 09:27:54

Re: RTL8822CE connectivity issues after fresh installation

#9 2025-03-17 09:44:48

Re: RTL8822CE connectivity issues after fresh installation

#10 2025-03-17 12:45:27

Re: RTL8822CE connectivity issues after fresh installation

#11 2025-03-17 20:57:43

Re: RTL8822CE connectivity issues after fresh installation

#12 2025-03-18 15:25:47

Re: RTL8822CE connectivity issues after fresh installation

#13 2025-03-18 17:13:54

Re: RTL8822CE connectivity issues after fresh installation

#14 2025-03-18 17:26:15

Re: RTL8822CE connectivity issues after fresh installation

#15 2025-03-18 17:42:40

Re: RTL8822CE connectivity issues after fresh installation

#16 2025-03-18 19:46:50

Re: RTL8822CE connectivity issues after fresh installation

#17 2025-09-29 22:06:22

Re: RTL8822CE connectivity issues after fresh installation

#18 2025-09-30 06:45:31

Re: RTL8822CE connectivity issues after fresh installation

Board footer