On maandag 24 januari 2022 15:38:01 CET Daniel wrote: > *** Reporter, please consider answering these questions, where appropriate > *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead? > > *** End of the template - remove these template lines ***
Could you fill in the above template so we'll have more information to help you? "Doesn't work" isn't much to go on and the kernel log included in the bug report seems to indicate a successful wireless connection: > [ 24.900350] wlo1: authenticate with 02:09:c1:90:4a:10 > [ 24.903768] wlo1: send auth to 02:09:c1:90:4a:10 (try 1/3) > [ 24.948852] wlo1: authenticated > [ 24.949316] wlo1: associate with 02:09:c1:90:4a:10 (try 1/3) > [ 24.953015] wlo1: RX AssocResp from 02:09:c1:90:4a:10 (capab=0x1131 > status=0 aid=1) > [ 24.972100] wlo1: associated > [ 25.041391] wlo1: Limiting TX power to 14 (14 - 0) dBm as advertised by > 02:09:c1:90:4a:10 > [ 25.041487] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
signature.asc
Description: This is a digitally signed message part.
