Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

Linux_i7 · 2024-05-07 13:36:06

Hello,

my new HP 15-fc0017nl laptop (Ryzen 3 7320U) cannot connect to my 5Ghz wifi network but just to my 2,4Ghz, which is much much slower.

I managed to connect to 5Ghz only during arch installation with the archiso usb flash drive and iwctl. After installing Hyprland and NetworkManager, nm-applet doesn't even show my 5Ghz SIDD among the nets. It just shows my 2,4Ghz. My 5Ghz SIDD is shown instead in "hidden network" but I can't connect to it as well.

I can easily connect to my 5Ghz network in Windows 11, which I have in dual boot!

My lspci:

Network controller: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller [1T1R]

Please help

Last edited by Linux_i7 (2024-05-07 13:37:11)

seth · 2024-05-07 15:34:07

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

If that's not it (also try to reboot the AP/router) test iwd on the installed syste,

NM uses wpa_supplicant by default, do you have more luck w/ using iwd again, in doubt as NM backend?
https://wiki.archlinux.org/title/Networ … Fi_backend

But ideally first stop NM and try to manually scan/connect w/ iwd/iwctl

Linux_i7 · 2024-05-07 19:14:32

seth wrote:

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
If that's not it (also try to reboot the AP/router) test iwd on the installed syste,
NM uses wpa_supplicant by default, do you have more luck w/ using iwd again, in doubt as NM backend?
https://wiki.archlinux.org/title/Networ … Fi_backend
But ideally first stop NM and try to manually scan/connect w/ iwd/iwctl

I'm sorry, but I'm not sure to understand what you are telling me. My bad!

1. You say "3rd link below Mandatory". Ok but there is only one link not 3

2. you say "Disable it". Disable what? NetworkManager? If yes, I did it and I restarted win11 and arch twice for vodoo reasons :-), but no success.

3. You say "use iwd again" I did it, but in there my 5Ghz wifi network doesn't show up.

4. You say use iwd backend, So I tried to follow the wiki at the page you linked "Using iwd as the Wi-Fi backend", so I typed $ iwctl and so on, but it doesn't show my 5Ghz wifi as well, even stopping NM service. No success!

If I misunderstood your instruction, please be patient and tell me what to do in order, step by step.
Thank you for helping me btw

Last edited by Linux_i7 (2024-05-07 19:16:00)

seth · 2024-05-07 20:28:01

There're 4 links in my signature.
The 3rd one points to http://wiki.archlinux.org/title/Dual_bo … ibernation and tells you to disable that.
Windows by default doesn't shut down, even if it says so. It just hibernates the system what means you're running two OS at the same time, leaving the hardware in an undefined state and also probabyl still hold a stale lease at the AP.
WiFi/radio is the prime victim of this condition.

Linux_i7 · 2024-05-08 12:35:23

I followed all your instructions (fast boot and hybern. disabled - rebooting and re-starting win11 and arch - try to connect via iwd and iwctl after disabling NM) but unfortunately my 5 Ghz wifi doesn't show up.
I guess it must be a wifi driver issue.
Any other idea?

seth · 2024-05-08 14:04:23

Does it still work from the install iso?
Did you test the behavior w/ the LTS kernel?
2.4 GHz connections do work?

Please post a complete system journal after scanning w/ iwctl as well as the scan results.
Did you reboot the AP ("router") as well?

Linux_i7 · 2024-05-10 05:15:12

From the install iso, iwctl doesn't find my 5 Ghz wifi connection, but my 2.4 ghz does work.

I'm testing the linux-lts kernel, but I haven't find out any improvements by far.

My 2.4 Ghz does work w/ iwctl and w/ NM. Now I have to restart NM service to be able to connect to my 2.4 Ghz otherwise it doesn't connect at boot as it is supposed to do normally.

I rebooted my router too.

Here is my journal after scanning w/ iwctl (I wasn't able to connect even with my 2.4 Ghz wifi connection)
https://www.dropbox.com/scl/fi/ybjrjoua … gj0ll&dl=0

here is the iwctl scan result
https://pastebin.com/zBr1yNKa

Thank you

seth · 2024-05-10 06:22:39

mag 08 15:06:27 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -64, load: 9/255
mag 08 15:06:46 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -69, load: 9/255
mag 08 15:06:52 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -66, load: 10/255
mag 08 15:07:03 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -60, load: 13/255
mag 08 15:07:18 arch iwd[492]: event: connect-info, ssid: Vodafone-WiFi, bss: 92:36:6d:b2:37:85, signal: -90, load: 26/255
mag 08 15:07:28 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -68, load: 19/255
mag 08 15:07:46 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -63, load: 11/255
mag 08 15:08:28 arch iwd[492]: event: connect-info, ssid: Vodafone-WiFi, bss: 92:36:6d:b2:37:85, signal: -87, load: 29/255
mag 08 15:09:05 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -62, load: 27/255
mag 08 15:11:19 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -65, load: 21/255
mag 08 15:26:40 arch iwd[490]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -69, load: 15/255
mag 08 15:28:30 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -69, load: 16/255
mag 08 15:28:48 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -70, load: 9/255
mag 08 15:28:48 arch iwd[492]: event: connect-info, ssid: Vodafone-WiFi, bss: 92:36:6d:b2:37:85, signal: -90, load: 30/255
mag 08 15:30:15 arch iwd[495]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -65, load: 18/255
mag 08 15:30:35 arch iwd[495]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -74, load: 16/255
mag 08 15:36:43 arch iwd[498]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -69, load: 16/255

You've a borderline dead signal to Vodafone-WiFi and a poor-ish signal to D-Link-3B338A
If the 5GHz AP is in the same location as either of those you're rather not getting a signal to it which is then likely also why the install medium iwd (now!) can't find it.

=> Move closer to the AP and try the install iso again

mag 08 15:06:46 arch NetworkManager[460]: <info>  [1715173606.1136] device (wlan0): Activation: starting connection 'D-Link-3B338A 1' (61500cbc-02de-496a-b875-05168584ae5c)
mag 08 15:06:46 arch NetworkManager[460]: <info>  [1715173606.1138] audit: op="connection-activate" uuid="61500cbc-02de-496a-b875-05168584ae5c" name="D-Link-3B338A 1" pid=712 uid=1000 result="success"
mag 08 15:06:46 arch NetworkManager[460]: <info>  [1715173606.1139] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
mag 08 15:06:46 arch NetworkManager[460]: <info>  [1715173606.1140] manager: NetworkManager state is now CONNECTING
mag 08 15:06:46 arch NetworkManager[460]: <info>  [1715173606.1142] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
mag 08 15:06:46 arch iwd[492]: event: connect-info, ssid: D-Link-3B338A, bss: 0c:b6:d2:3b:33:8b, signal: -69, load: 9/255
mag 08 15:06:46 arch iwd[492]: event: state, old: disconnected, new: connecting
mag 08 15:06:46 arch NetworkManager[460]: <info>  [1715173606.1148] device (wlan0): new IWD device state is connecting
mag 08 15:06:46 arch iwd[492]: error parsing HT capabilities
mag 08 15:06:46 arch iwd[492]: error parsing HT capabilities
mag 08 15:06:46 arch iwd[492]: error parsing HT capabilities
mag 08 15:06:46 arch iwd[492]: error parsing HE capabilities
mag 08 15:06:46 arch iwd[492]: error parsing HT capabilities
mag 08 15:06:46 arch iwd[492]: event: connect-failed, status: 1
mag 08 15:06:46 arch iwd[492]: event: state, old: connecting, new: disconnected
mag 08 15:06:46 arch iwd[492]: event: state, old: disconnected, new: autoconnect_quick
mag 08 15:06:46 arch NetworkManager[460]: <error> [1715173606.8729] device (wlan0): Activation: (wifi) Network.Connect failed: GDBus.Error:net.connman.iwd.Failed: Operation failed
mag 08 15:06:46 arch NetworkManager[460]: <info>  [1715173606.8732] device (wlan0): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed')
mag 08 15:06:46 arch NetworkManager[460]: <info>  [1715173606.8736] manager: NetworkManager state is now DISCONNECTED

NM fails because you don't provide the wiki key, this is a session (hyprland) problem and unrelated to overall network issues.

Linux_i7 · 2024-05-10 12:41:26

I got closer to my router, in the same room at 1,5 m. from it and iwctl couldn't connect to my 5Ghz wifi as well (5Ghz didn't show up). I checked it out from my live install iso, here is the journal
https://pastebin.com/P5wzanbb

So I'm not sure that this issue is related to the distance from the AP and my laptop. Because, if it were true, Win11 couldn't connect either. Besides I have another laptop (Acer Aspire 15) that connects pretty easily with my 5 Ghz even with a weak signal.

Last edited by Linux_i7 (2024-05-10 12:49:23)

seth · 2024-05-10 14:56:30

iwd/systemd-networkd unfortunately don't log signal quality - the weak signal is suspicious though. How far had you been from the AP before (and was there some re-enforced concrete inbetween)?

Does it help to add

rtw89_core.disable_ps_mode=y

to the https://wiki.archlinux.org/title/Kernel_parameters ?

Linux_i7 · 2024-05-10 19:18:08

That kernel parameter didn't help.

I had been at about 10-15 meters from the AP and there are no reinforced concrete in between

seth · 2024-05-10 21:19:44

Add "rtw89_pci.disable_aspm_l1=y rtw89_pci.disable_aspm_l1ss=y rtw89_pci.disable_clkreq=y" to that.
How is the 2.4GHz signal when you're close to the AP?

Linux_i7 · 2024-05-11 08:45:16

That parameter doesn't help: the 5Ghz doesn't show up either. (I added that code to the linux.xxxxx line by pressing the E key at the Grub right before booting the OS, Is it right?)
The 2.4Ghz signal is good when I'm close to the AP

Last edited by Linux_i7 (2024-05-11 08:47:51)

seth · 2024-05-11 21:31:07

I added that code to the linux.xxxxx line by pressing the E key at the Grub right before booting the OS, Is it right?

Shoudl be -

cat /proc/cmdline

will confirm what you actually applied - you did combine that w/ the previous "rtw89_core.disable_ps_mode=y"?

So it's not powersavin and not fixed by the kernel parameter and the previously working (are you absolutely sure about that?) install iso doesn't work anymore either.
There's also

mag 08 15:06:26 arch kernel: rtw89_8852be 0000:02:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin

There're a lot of

mag 08 15:30:46 arch iwd[495]: error parsing VHT capabilities
mag 08 15:30:46 arch iwd[495]: error parsing HT capabilities
mag 08 15:30:46 arch iwd[495]: error parsing non-HT rates

Did you ever try wpa_supplicant?

Linux_i7 · 2024-05-13 06:41:11

In the mean time I reinstalled Arch ( now I have KDE ) and I've been testing the kernel parameters you suggested earlier: it seems working! Actually now I can connect to my 5Ghz, even though, after booting up my laptop, there is a little delay before NM succeed to connect to my 5Ghz wifi, it's about 1 minute, after that it manages to connect.

I'm using this kernel parameter:

cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=092d3f8d-4626-4bd5-9d86-28904973b0e3 rw rtw89_pci.disable_aspm_l1=y rtw89_pci.disable_aspm_l1ss=y rtw89_pci.disable_clkreq=y rtw89_core.disable_ps_mode=y
[giulio@arch ~]$

I put them in /etc/default/grub after this:

GRUB_CMDLINE_LINUX_DEFAULT=

and then I updated the Grub configuration.

I'm not sure if this is correct and I'd like to know what that parameters actually mean.

Thank you so much

EDIT:

It's not connecting anymore -:(

Last edited by Linux_i7 (2024-05-13 15:23:21)

seth · 2024-05-13 15:55:51

Is correct, they disable a bunch of power saving features in the chip.
Are they actually necessary (have you tested the re-installed system w/o them)?
Wrt the delay, do you have a system journal covering that?

Edit: F5, so it was/is a fluke? Did you boot windows inbetween?
Post the journals from a boot where it worked and one where it didn't nevertheless.

Last edited by seth (2024-05-13 15:57:28)

Linux_i7 · 2024-05-13 19:20:06

here's the log
https://www.dropbox.com/scl/fi/9nz551wx … eovxd&dl=0
here you should find the working 5Ghz and the not working part (sorry I'm not familiar w/ journal logs, so I hope you can find there something interesting, otherwise please tell me how to properly do it)

Honestly I don't remember if I booted Windows in between and yes I tested the new install but it doesn't connect to 5Ghz

seth · 2024-05-14 12:31:20

mag 13 13:57:58 arch wpa_supplicant[503]: wlan0: Trying to associate with 0c:b6:d2:3b:33:8d (SSID='D-Link-3B338A_5Ghz' freq=5220 MHz)
mag 13 13:57:58 arch wpa_supplicant[503]: wlan0: Associated with 0c:b6:d2:3b:33:8d
mag 13 13:57:58 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
mag 13 13:57:58 arch wpa_supplicant[503]: wlan0: WPA: Key negotiation completed with 0c:b6:d2:3b:33:8d [PTK=CCMP GTK=CCMP]
mag 13 13:57:58 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-CONNECTED - Connection to 0c:b6:d2:3b:33:8d completed [id=0 id_str=]
…
mag 13 14:55:05 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-77 noise=9999 txrate=19500
mag 13 14:55:11 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-78 noise=9999 txrate=19500
mag 13 14:56:55 arch wpa_supplicant[503]: wlan0: WPA: Group rekeying completed with 0c:b6:d2:3b:33:8d [GTK=CCMP]
mag 13 14:57:36 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-52 noise=9999 txrate=90000
mag 13 14:57:37 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-74 noise=9999 txrate=90000
mag 13 14:57:44 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-87 noise=9999 txrate=90000
…
mag 13 15:55:56 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-83 noise=9999 txrate=130000
mag 13 15:56:38 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-92 noise=9999 txrate=130000
mag 13 15:56:56 arch wpa_supplicant[503]: wlan0: WPA: Group rekeying completed with 0c:b6:d2:3b:33:8d [GTK=CCMP]
mag 13 15:56:58 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=117000
mag 13 15:57:10 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-77 noise=9999 txrate=117000
…
mag 13 16:23:13 arch systemd[1]: Stopped User Runtime Directory /run/user/1000.
mag 13 16:23:13 arch systemd[1]: Removed slice User Slice of UID 1000.
mag 13 16:23:13 arch systemd[1]: user-1000.slice: Consumed 30min 52.054s CPU time.
mag 13 16:23:13 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-DISCONNECTED bssid=0c:b6:d2:3b:33:8d reason=3 locally_generated=1
mag 13 16:23:13 arch NetworkManager[462]: <info>  [1715610193.1294] device (wlan0): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed')
mag 13 16:23:13 arch NetworkManager[462]: <info>  [1715610193.1297] manager: NetworkManager state is now DISCONNECTING
mag 13 16:23:13 arch dbus-broker-launch[458]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
mag 13 16:23:13 arch NetworkManager[462]: <warn>  [1715610193.1322] dispatcher: (10) failed (after 0.003 sec): Could not activate remote peer 'org.freedesktop.nm_dispatcher': activation request failed: unit is invalid
mag 13 16:23:13 arch NetworkManager[462]: <info>  [1715610193.1323] device (wlan0): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed')
mag 13 16:23:13 arch NetworkManager[462]: <info>  [1715610193.1324] dhcp4 (wlan0): canceled DHCP transaction
mag 13 16:23:13 arch NetworkManager[462]: <info>  [1715610193.1324] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
mag 13 16:23:13 arch NetworkManager[462]: <info>  [1715610193.1324] dhcp4 (wlan0): state changed no lease
mag 13 16:23:13 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
mag 13 16:23:13 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
mag 13 16:23:13 arch wpa_supplicant[503]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
mag 13 16:23:13 arch wpa_supplicant[503]: wlan0: CTRL-EVENT-TERMINATING
mag 13 16:23:13 arch systemd[1]: wpa_supplicant.service: Deactivated successfully.
mag 13 16:23:13 arch systemd[1]: Stopped WPA supplicant.
mag 13 16:23:13 arch systemd[1]: wpa_supplicant.service: Consumed 1.881s CPU time.
…
mag 13 16:23:13 arch systemd-journald[310]: Journal stopped
-- Boot 3138ede9aa544016a16e595575a7f115 --
mag 13 17:10:10 arch kernel: Linux version 6.8.9-arch1-2 (linux@archlinux) (gcc (GCC) 14.1.1 20240507, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Tue, 07 May 2024 21:35:54 +0000
…
mag 13 17:10:19 arch systemd[558]: Started KDE Plasma Workspace.
…
mag 13 17:10:11 arch wpa_supplicant[499]: Successfully initialized wpa_supplicant
mag 13 17:10:12 arch wpa_supplicant[499]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
mag 13 17:10:21 arch wpa_supplicant[499]: wlan0: Reject scan trigger since one is already pending
mag 13 17:13:54 arch wpa_supplicant[499]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
mag 13 17:13:54 arch wpa_supplicant[499]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
mag 13 17:13:54 arch wpa_supplicant[499]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
mag 13 17:13:54 arch wpa_supplicant[499]: wlan0: CTRL-EVENT-TERMINATING
mag 13 17:13:54 arch systemd[1]: wpa_supplicant.service: Deactivated successfully.
mag 13 17:13:54 arch systemd[1]: wpa_supplicant.service: Consumed 1.122s CPU time.
mag 13 17:14:07 arch wpa_supplicant[507]: Successfully initialized wpa_supplicant
mag 13 17:14:15 arch wpa_supplicant[507]: wlan0: Reject scan trigger since one is already pending
mag 13 17:14:34 arch wpa_supplicant[507]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
mag 13 17:15:38 arch wpa_supplicant[507]: wlan0: Reject scan trigger since one is already pending
mag 13 17:16:19 arch wpa_supplicant[507]: wlan0: Reject scan trigger since one is already pending

So yesterday ~14:00 you connected to the 5GHz AP, stayed there despite the signal veering between "meh" and " aaaaarghh", then disconnected w/ a logout at 16:23 and then, after a reboot ~17:10, the wifi NIC refuses to even scan for networks because the firmware thinks it's scanning.

It has all the indicators of the NIC being in an undefined state, most likely because windows is hibernating on it. It's not scanning on the linux boot.
wrt your previous comment on that, it's "fast start", not "fast boot" - the latter is a completely unrelated bios/uefi feature to skip some self checks during the boot.

Linux_i7 · 2024-05-14 14:44:32

If Windows is still hibernating I don't know why. Coz I disabled windows 'fast start' by typing

> powercfg /H off

in Windows command prompt with admin privileges. I did the same from Windows Control Panel -> Power Options -> click on Choose what the power buttons do -> Click on Change settings that are currently unavailable -> Uncheck the Turn on fast startup and saved. Then I rebooted windows twice and after that I booted Arch. But the issue is still there. So I don't know what to do else now, unless: -1) buying a wifi repeater to get a stronger wifi signal or 2) - last chance - buying an usb wifi adapter.
Which way do you recommend?

seth · 2024-05-14 15:30:45

unless: -1) buying a wifi repeater to get a stronger wifi signal or 2) - last chance - buying an usb wifi adapter.

The repeater won't help if the NIC doesn't scan because it thinks it is already scanning.

Wild guess, it doesn't look like you've wireless-regdb installed or are https://wiki.archlinux.org/title/Networ … ory_domain ?

Linux_i7 · 2024-05-16 11:43:38

Sadly I'm about to give linux up! At least to my current laptop. So sorry :-(

Thank you for helping me

Last edited by Linux_i7 (2024-05-16 14:33:05)

gecaro · 2024-05-17 10:17:16

Hello all,
I'm having a similar issue with a different wireless card (RTL8852CE) ̣-- I don't know whether I should open a new thread or continue this one:

I can see my 5Ghz wifi in NetworkManager
I could connect to my 5Ghz wifi in the arch installer
I can connect to my 2.4Ghz band
I cannot connect to my 5Ghz band

journalctl --unit wpa_supplicant

constrained to the time I try to connect to this network:

de maig 17 12:03:40 pinguxx wpa_supplicant[607]: wlan0: SME: Trying to authenticate with 50:c7:bf:17:54:c7 (SSID='TP-LINK_54C8_5G' freq=5240 MHz)
de maig 17 12:03:40 pinguxx wpa_supplicant[607]: wlan0: Trying to associate with 50:c7:bf:17:54:c7 (SSID='TP-LINK_54C8_5G' freq=5240 MHz)
de maig 17 12:03:40 pinguxx wpa_supplicant[607]: wlan0: Associated with 50:c7:bf:17:54:c7
de maig 17 12:03:40 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
de maig 17 12:03:40 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
de maig 17 12:03:45 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-DISCONNECTED bssid=50:c7:bf:17:54:c7 reason=2
de maig 17 12:03:45 pinguxx wpa_supplicant[607]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
de maig 17 12:03:45 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_54C8_5G" auth_failures=1 duration=10 reason=WRONG_KEY
de maig 17 12:03:45 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
de maig 17 12:03:51 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
de maig 17 12:03:51 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
de maig 17 12:03:51 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
de maig 17 12:03:54 pinguxx wpa_supplicant[607]: wlan0: SME: Trying to authenticate with 50:c7:bf:17:54:c7 (SSID='TP-LINK_54C8_5G' freq=5240 MHz)
de maig 17 12:03:54 pinguxx wpa_supplicant[607]: wlan0: Trying to associate with 50:c7:bf:17:54:c7 (SSID='TP-LINK_54C8_5G' freq=5240 MHz)
de maig 17 12:03:54 pinguxx wpa_supplicant[607]: wlan0: Associated with 50:c7:bf:17:54:c7
de maig 17 12:03:54 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
de maig 17 12:03:59 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-DISCONNECTED bssid=50:c7:bf:17:54:c7 reason=2
de maig 17 12:03:59 pinguxx wpa_supplicant[607]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
de maig 17 12:03:59 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_54C8_5G" auth_failures=1 duration=10 reason=WRONG_KEY
de maig 17 12:03:59 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

After this happens, kde asks for the password again, and the logs keep repeating if I re-insert the password.

I also tried disabling the password in my router settings but it won't connect either. I guess the thing is the `WPA: 4-Way Handshake failed - pre-shared key may be incorrect` but I am lost in terms on what to do.

Also yes I disabled the safe boot as in your signature link and added the above kernel parameters and I still get the error.

lspci:

05:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8852CE PCIe 802.11ax Wireless Network Controller (rev 01)

seth · 2024-05-17 11:22:47

de maig 17 12:03:45 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_54C8_5G" auth_failures=1 duration=10 reason=WRONG_KEY

This is different from the OPs problem - you're entering the wrong password.

I also tried disabling the password in my router settings

What does the journal for that look like?

Also yes I disabled the safe boot as in your signature link and added the above kernel parameters and I still get the error.

Did you reboot the router afterwards?
reason #2 is "Previous authentication no longer valid"…

journalctl --unit wpa_supplicant

Please don't filter the journal in case there's some kwallet interference, driver issues etcetc.

gecaro · 2024-05-17 12:19:53

What does the journal for that look like?

https://gist.github.com/gecaro/60347a58 … e6b043facc

Did you reboot the router afterwards?

Yes.

Please don't filter the journal in case there's some kwallet interference, driver issues etcetc.

Noted, thanks.

seth · 2024-05-17 12:52:59

de maig 17 14:05:59 pinguxx NetworkManager[548]: <info>  [1715947559.5855] Config: added 'ssid' value 'TP-LINK_54C8_5G'
de maig 17 14:05:59 pinguxx NetworkManager[548]: <info>  [1715947559.5855] Config: added 'scan_ssid' value '1'
de maig 17 14:05:59 pinguxx NetworkManager[548]: <info>  [1715947559.5855] Config: added 'bgscan' value 'simple:30:-70:86400'
de maig 17 14:05:59 pinguxx NetworkManager[548]: <info>  [1715947559.5855] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
de maig 17 14:05:59 pinguxx NetworkManager[548]: <info>  [1715947559.5855] Config: added 'psk' value '<hidden>'
de maig 17 14:05:59 pinguxx systemsettings[3328]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
de maig 17 14:05:59 pinguxx plasmashell[1041]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
de maig 17 14:05:59 pinguxx wpa_supplicant[607]: wlan0: WPS-CANCEL
de maig 17 14:05:59 pinguxx NetworkManager[548]: <info>  [1715947559.6703] device (wlan0): supplicant interface state: disconnected -> scanning
de maig 17 14:05:59 pinguxx NetworkManager[548]: <info>  [1715947559.6703] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
de maig 17 14:05:59 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
de maig 17 14:06:01 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
de maig 17 14:06:01 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
de maig 17 14:06:08 pinguxx systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
de maig 17 14:06:10 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
---------------------
de maig 17 14:06:24 pinguxx NetworkManager[548]: <warn>  [1715947584.9782] device (wlan0): Activation: (wifi) association took too long, failing activation
de maig 17 14:06:24 pinguxx NetworkManager[548]: <info>  [1715947584.9782] device (wlan0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
--------------------------
de maig 17 14:06:24 pinguxx wpa_supplicant[607]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
de maig 17 14:06:24 pinguxx NetworkManager[548]: <info>  [1715947584.9784] manager: NetworkManager state is now DISCONNECTED
de maig 17 14:06:25 pinguxx NetworkManager[548]: <info>  [1715947585.0114] device (wlan0): set-hw-addr: set MAC address to 02:F7:5D:92:8D:8C (scanning)
de maig 17 14:06:25 pinguxx NetworkManager[548]: <warn>  [1715947585.0910] device (wlan0): Activation: failed for connection 'TP-LINK_54C8_5G'

Reactivate the PW on the router, stop NM and try to connect w/ wifi-menu

Edit: make the wifi-password ascii- and qwerty-safe, eg. "12345"

Last edited by seth (2024-05-17 12:53:52)

Arch Linux

#1 2024-05-07 13:36:06

Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#2 2024-05-07 15:34:07

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#3 2024-05-07 19:14:32

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#4 2024-05-07 20:28:01

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#5 2024-05-08 12:35:23

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#6 2024-05-08 14:04:23

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#7 2024-05-10 05:15:12

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#8 2024-05-10 06:22:39

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#9 2024-05-10 12:41:26

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#10 2024-05-10 14:56:30

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#11 2024-05-10 19:18:08

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#12 2024-05-10 21:19:44

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#13 2024-05-11 08:45:16

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#14 2024-05-11 21:31:07

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#15 2024-05-13 06:41:11

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#16 2024-05-13 15:55:51

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#17 2024-05-13 19:20:06

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#18 2024-05-14 12:31:20

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#19 2024-05-14 14:44:32

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#20 2024-05-14 15:30:45

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#21 2024-05-16 11:43:38

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#22 2024-05-17 10:17:16

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#23 2024-05-17 11:22:47

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#24 2024-05-17 12:19:53

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

#25 2024-05-17 12:52:59

Re: Cannot connect to my 5Ghz wifi network - Realtek RTL8852BE driver

Board footer