[SOLVED] Lenovo T14s does not receive a DHCP lease

dietzi96 · 2024-12-11 21:12:36

Hi,

I'm trying to get arch linux working on my Lenovo T14s Gen 6 (AMD), however wifi just does not work. Using dynamic ip addresses via dhcpcd results in a loop of

wlan0: soliciting an IPv6 router
wlan0: soliciting a DHCP lease
wlan0: carrier lost
wlan0: carrier acquired
wlan0: soliciting an IPv6 router
 ...
timed out

Using a static ip address yields

wlan0: probing address 192.168.178.119/24
wlan0: soliciting an IPv6 router
wlan0: carrier lost
wlan0: carrier acquired
...
wlan0: soliciting an IPv6 router
wlan0: using static address 192.168.178.119/24
wlan0: adding route to 192.168.178.0/24
wlan0: adding default route via 192.168.178.1

but using ping afterwards yields either in network is unreachable or in 100% packet loss...

Any ideas?

In journalctl there are many unprotected disconnect event, src=... dest=... bssid=... reason 2 or reason 6 messages.

Last edited by dietzi96 (2024-12-12 17:33:27)

Lone_Wolf · 2024-12-12 09:55:36

Please post the output of

$ find /etc/systemd -type l -exec test -f {} \; -print

Also as root run journalctl -b | curl -F 'file=@-' 0x0.st and post the link it outputs.

Last edited by Lone_Wolf (2024-12-12 09:56:04)

dietzi96 · 2024-12-12 17:25:43

Both commands yield

[root@chimchar ~]# find /etc/systemd -type l -exec test -f {} \; -print
/etc/systemd/system/multi-user.target.wants/iwd.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/sockets.target.wants/systemd-userdbd.socket
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/user/pipewire-session-manager.service
/etc/systemd/user/sockets.target.wants/pipewire-pulse.socket
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket
/etc/systemd/user/sockets.target.wants/pipewire.socket
/etc/systemd/user/pipewire.service.wants/wireplumber.service

and

curl: (6) Could not resolve host: 0x0.st

Running dmesg results in

[  256.095252] wlan0: send auth to e8:df:70:84:58:38 (try 1/3)
[  256.099792] wlan0: authenticated
[  256.100315] wlan0: associate with e8:df:70:84:58:38 (try 1/3)
[  256.104761] wlan0: RX AssocResp from e8:df:70:84:58:38 (capab=0x1511 status=0 aid=5)
[  256.119267] wlan0: associated
[  256.192400] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by e8:df:70:84:58:38
[  260.495603] wlan0: disassociated from e8:df:70:84:58:38 (Reason: 2=PREV_AUTH_NOT_VALID)
[  260.631631] ath12k_pci 0000:c2:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[  261.109483] wlan0: authenticate with e8:df:70:84:58:38 (local address=2c:9c:58:8e:3e:7d)
[  261.109494] wlan0: send auth to e8:df:70:84:58:38 (try 1/3)
[  261.114297] wlan0: authenticated
[  261.116986] wlan0: associate with e8:df:70:84:58:38 (try 1/3)
[  261.121428] wlan0: RX AssocResp from e8:df:70:84:58:38 (capab=0x1511 status=0 aid=5)
[  261.136069] wlan0: associated
[  261.210234] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by e8:df:70:84:58:38
[  265.420890] wlan0: disassociated from e8:df:70:84:58:38 (Reason: 2=PREV_AUTH_NOT_VALID)
[  266.051776] wlan0: authenticate with e8:df:70:84:58:38 (local address=2c:9c:58:8e:3e:7d)
[  266.051786] wlan0: send auth to e8:df:70:84:58:38 (try 1/3)
[  266.056467] wlan0: authenticated
[  266.056981] wlan0: associate with e8:df:70:84:58:38 (try 1/3)
[  266.061283] wlan0: RX AssocResp from e8:df:70:84:58:38 (capab=0x1511 status=0 aid=5)
[  266.062836] ath12k_pci 0000:c2:00.0: failed to enqueue rx buf: -28
[  266.075684] wlan0: associated
[  266.125194] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by e8:df:70:84:58:38
[  270.531001] wlan0: disassociated from e8:df:70:84:58:38 (Reason: 2=PREV_AUTH_NOT_VALID)
[  270.985132] wlan0: authenticate with e8:df:70:84:58:38 (local address=2c:9c:58:8e:3e:7d)
[  270.985141] wlan0: send auth to e8:df:70:84:58:38 (try 1/3)
[  270.989468] wlan0: authenticated
[  270.990295] wlan0: associate with e8:df:70:84:58:38 (try 1/3)
[  270.994326] wlan0: RX AssocResp from e8:df:70:84:58:38 (capab=0x1511 status=0 aid=5)
[  271.008913] wlan0: associated
[  271.039947] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by e8:df:70:84:58:38
[  275.343964] wlan0: disassociated from e8:df:70:84:58:38 (Reason: 2=PREV_AUTH_NOT_VALID)
[  275.537978] ath12k_pci 0000:c2:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 14 (-105)
[  275.537992] ath12k_pci 0000:c2:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 14 (-105)
[  275.538001] ath12k_pci 0000:c2:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[  275.538003] ath12k_pci 0000:c2:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[  275.538005] ath12k_pci 0000:c2:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[  275.538007] ath12k_pci 0000:c2:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[  275.538009] ath12k_pci 0000:c2:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[  275.952607] wlan0: authenticate with e8:df:70:84:58:38 (local address=2c:9c:58:8e:3e:7d)
[  275.952621] wlan0: send auth to e8:df:70:84:58:38 (try 1/3)
[  275.957041] wlan0: authenticated
[  275.960336] wlan0: associate with e8:df:70:84:58:38 (try 1/3)
[  275.964545] wlan0: RX AssocResp from e8:df:70:84:58:38 (capab=0x1511 status=0 aid=5)
[  275.967027] ath12k_pci 0000:c2:00.0: failed to enqueue rx buf: -28
[  275.978678] wlan0: associated
[  276.057749] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by e8:df:70:84:58:38

EDIT:
After looking up parts of the dmesg output on the internet I found a solution for my problem. It's a known bug on the kernel.org bugzilla and there is a workaround by setting a config option in /etc/iwd/main.conf

[General]
ControlPortOverNL80211=false

Last edited by dietzi96 (2024-12-12 17:32:20)

Arch Linux

#1 2024-12-11 21:12:36

[SOLVED] Lenovo T14s does not receive a DHCP lease

#2 2024-12-12 09:55:36

Re: [SOLVED] Lenovo T14s does not receive a DHCP lease

#3 2024-12-12 17:25:43

Re: [SOLVED] Lenovo T14s does not receive a DHCP lease

Board footer