#
…

2023-11-28

00:24kidplayer666 has quit [Quit: Connection closed for inactivity]
00:57pounce has quit [Ping timeout: 480 seconds]
01:03pounce has joined #asahi-alt
02:19possiblemeatball has joined #asahi-alt
03:26hightower3 has joined #asahi-alt
03:33hightower2 has quit [Ping timeout: 480 seconds]
04:14jeisom has quit [Read error: Connection reset by peer]
04:14jeisom has joined #asahi-alt
04:32jeisom has quit [Ping timeout: 480 seconds]
04:40possiblemeatball has quit [Quit: Quit]
06:54kidplayer666 has joined #asahi-alt
06:59veebop has joined #asahi-alt
08:33pjakobsson_ has quit [Ping timeout: 480 seconds]
09:04kidplayer666 has quit [Quit: Connection closed for inactivity]
10:02kidplayer666 has joined #asahi-alt
10:29yukamy wpa_supplicant keeps disconnecting from my wifi with kernel asahi-6.6-2, does anyone else have that?
10:38yuka"wlp1s0f0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1"
11:27yukathis is a regression from asahi-5.5-29
11:36mpsyuka: don't know about wpa_s but iwd works fine with 6.6-2
11:38yukait only happens with my unifi wifi
11:38yukanot with pixel android hotspot
11:42j`eyyuka: DannyB did most (all?) of the changes to the brcm driver recently, I invited him here, so maybe he can help at some point if you dont fix it beofre then
11:43yukaI'm rebuilding my kernel with BRCMDBG y BRCM_TRACING y now :)
12:09kloenk has joined #asahi-alt
13:14jeisom has joined #asahi-alt
13:25jeisom has quit [Quit: Leaving]
14:12DannyB has joined #asahi-alt
14:29john-cabaj has joined #asahi-alt
14:58yukamy home wifi (unifi) is being disconnected once per minute: https://termbin.com/mpi3
14:59DannyBWhat kind of auth do you use?
15:00yukaWPA2 PSK
15:00yukaI think
15:00DannyBThis is fedora 39?
15:01DannyBI ask becasue it's using wpa_supplicant which is weird
15:01yukait's not fedora
15:01yukawhich is why we are in #asahi-alt :)
15:02yukaat least my wpa_supplicant.conf only has an "ssid=" and "key=" for this wifi, so no sae_password or anything
15:02DannyBOkay, so what's happening is that there is some bad interaction with the external supplicant. Can you recompile a kernel? If so i can make this very easy to debug. If not, i can figure it out but it will take longer
15:02yukaI can recompile the kernel
15:04DannyBCan you set the options BRCM_TRACING and BRCMDBG in your kernel config, and then shove options brcmfmac debug=1097734 in /etc/modprobe.d/brcmfmac.conf
15:04DannyBThat will tell me what commands it's sending back and forth tot he chip and what the response is
15:04yukagood that I already rebuilt with those options :)
15:05DannyBthen yeah you can just rmmod it and re-modprobe it
15:05DannyBwith those options
15:06possiblemeatball has joined #asahi-alt
15:07DannyBi think what is happening is that the management frame handling is screwed up somehow
15:08j`eyDannyB: thanks for joining!
15:16DannyBOh, the patch to handle management frames properly never made it into the branch
15:17DannyBoh no it didn, looking at wrong branch
15:19DannyBoh, i know what it is
15:19DannyBgive me a sec i'll send you a patch
15:23yukaperfect, I'll try that
15:24DannyBactually one sec that's not complete, i forgot a function or two
15:24DannyBi forgot to add the external auth function on the branch
15:30yukado you have a base commit for that?
15:33DannyBThis is against the current asahi-wip branch
15:33DannyBFWIW, it may not be enough, but if that's the case, i know what is missing :)
15:38yukadoes not apply cleanly to asahi-wip. last item in brcmf_cfg80211_ops is .del_pmk and not .set_cqm_rssi_config
15:38yukabut I am building it now
15:39yuka^ this does actually apply
15:42pounce has quit [Ping timeout: 480 seconds]
15:43DannyBi know why
15:43DannyByes that's my fault
15:44DannyBi have patches i haven't sent yet for that iece
15:44DannyBthat are under this
15:45DannyBlet me rebase it myself against asahi-wip and paste a new one
15:45yukayes, thanks!
15:53pounce has joined #asahi-alt
16:27DannyBthat should apply to asahi-wip
16:33possiblemeatball has quit [Remote host closed the connection]
16:36possiblemeatball has joined #asahi-alt
16:40yukait does apply
16:42possiblemeatball has quit [Remote host closed the connection]
16:48DannyBAs an aside
16:48DannyByou should get out of the land of wpa_supplicant if you can.
16:48DannyBOne thing you are losing by doing this is that is not setting up PSK offload
16:48DannyBi think i added code that may turn it on in this case, but you are going to discover whether it works or not :)
16:49yukamigrating the config is work
16:50yukasadly it doesn't work
16:50yukaI'm still being disconnected
16:54DannyBSend me the logs
16:58DannyBso it acutally connected this time
16:58DannyBso progress
16:59DannyBit looks like it's not getting the key at this point
17:01yukait's the same behavior as without the patch: it connects, stays connected, and after about one minute disconnects with "reason=3 locally_generated=1"
17:04pounce has quit [Ping timeout: 480 seconds]
17:06pounce has joined #asahi-alt
17:07DannyBYes, but that's not what was really happening
17:07DannyByou are looking at what wpa supplicant is saying
17:07DannyBi'm looking at what the chip is saying :)
17:08DannyBthe chip before was saying it couldn't handle external station auth
17:08DannyBthat is what the Nov 28 16:20:29 m1 wpa_supplicant[1433]: nl80211: kernel reports: Registration to specific type not supported
17:08DannyBand so it was not even trying to hande the management frames to wpa_supplicant
17:11DannyBCan you set the debug options to 1098758 and regenerate the log
17:17pounce has quit [Ping timeout: 480 seconds]
17:39pounce has joined #asahi-alt
17:51pounce has quit [Ping timeout: 480 seconds]
18:03DannyBokay, this is odd
18:03DannyBbut i think i can fix it
18:03pounce has joined #asahi-alt
18:15DannyBso what is happening is acutally that wpa_supplicant is asking us to disocnnect
18:16yukabut why is it doing that with one kernel version and not another?
18:25DannyBSo i think maybe this thing by marcan broke it by accident
18:25DannyBbecause it's the only real change i see
18:25DannyBthe patch i gave you would work if supplicant was doing it one way but it's not
18:25DannyBand the way it's doing it this is the only code path difference
18:25DannyBlet's give it a shit
18:28pounce has quit [Ping timeout: 480 seconds]
18:47yukaDannyB: with this patch it does not manage to establish the connection in the first place. https://termbin.com/ce53
18:48yukaAt this point it might be easier for me to move to iwd, however other users of non-Fedora asahi might run into it as well
18:49yukaI'm also patient and thankful if someone wants to continue debugging
18:59DannyBYeah what the supplicant is doing doesn' make any sense
18:59DannyBwhat is happening is that we connect
18:59DannyBand report we connected
18:59DannyBand everything is fine
18:59DannyBand it sends a deauth message for no obvious reason
18:59DannyBso we disconnect
18:59DannyBi don't get it
19:00DannyBMost of this code was broken in past kernels
19:00DannyBand wpa supplicant was getting lucky somehow
19:00DannyBit's now not lucky
19:01DannyBThe last thig i would try is the following, which reverts support for more auth suites
19:16jannegfedora asahi uses wpa-supplicant but is patched. I'm only aware of patches for sae offload though
20:03mpshow/where I can see packaging scripts/source for mesa-asahi on gentoo
20:04mpsj`ey: thanks
20:05mpsoh, they also use old one
20:06mpsah, and one of newest 20231120
20:08j`eythere's 20231126 now too
20:09j`eyhm, failed to build for fedora though
20:10mpsI've built 20231126 for alpine and it works with some issues
20:11mpsah, ok, understand
20:11mpsyes, I'm using 20231126 two days now
20:11pounce has joined #asahi-alt
20:12mpsbut don't want to merge to alpine because I see some issues
20:12DannyBjanneg: There is nothing obvious in why the wpa_supplicant is choosing to disconnect in his case. With the patches (except the last one), it connects successfully, we report a successful connection, then the *suppllicant* decides to disconnect us anyway and we disconnect. it is not the driver deciding to disconnect on its own. The reason it gives us "DEAUTH_LEAVING" - IE it is choosing to leave this BSS for some other
20:12DannyBso it's extra weird
20:13DannyBbecause i doubt there are local patches tof edora that affect this
20:15DannyBthe exact sequence of events post-patches is:
20:15DannyBdriver auth and report success
20:15DannyBsupplicant tells driver to auth
20:15DannyBSupplicant reports connect success
20:15DannyBSupplicant asks us to change station
20:15DannyBSupplicant asks us to deauth and disconnect
20:16DannyBI can't see anything wrong in the driver logs - we are setting the key right, we are authing and reporting success, etc
20:34pounce has quit [Ping timeout: 480 seconds]
21:04chadmedmps: we try not to pull in updates that are unreleased unless absolutely necessary since its just bm to package and distribute unreleased software
21:05chadmednew tags for the kernel, mesa and friends that are earmarked for release get staged locally and i test them before pushing to the remote
21:12mpschadmed: I do similarly for alpine, so I understand you
21:13mpsI test all tags locally first and if I don't see anything problematic I then push
21:46asimpson has quit [Read error: Connection reset by peer]
21:46d4ve has quit [Read error: Connection reset by peer]
21:46signaryk has quit [Read error: Connection reset by peer]
21:46alethkit has quit [Write error: connection closed]
21:46handlerug has quit [Write error: connection closed]
21:46probie has quit [Write error: connection closed]
21:46okt has quit [Write error: connection closed]
21:46tsujp has quit [Write error: connection closed]
21:46pldtf has quit [Write error: connection closed]
21:46asimpson has joined #asahi-alt
21:46probie has joined #asahi-alt
21:46tsujp has joined #asahi-alt
21:46okt has joined #asahi-alt
21:46signaryk has joined #asahi-alt
21:46handlerug has joined #asahi-alt
21:46alethkit has joined #asahi-alt
21:46pldtf has joined #asahi-alt
21:46d4ve has joined #asahi-alt
22:39jeisom has joined #asahi-alt
…