You are not logged in.
Pages: 1
5.8.7 is the latest working kernel.
If I try to upgrade - it first seems normal, the device exists, it receives a new name wlan0 which I've done with udev, but it does not connect.
Dmesg | grep ath does not differ between 5.8.7 and newer kernels.
systemctl_restart wpa_supplicant@wlan0
just tells
wpa_supplicant@wlan0.service: Failed with result 'exit-code'.
In other words it tells nothing which is quite usual with systemd.
I have no idea how to get any more useful info at all.
And i didn't google anything useful about linux 5.8.8 and AR 9485 combination.
Neither bugzilla.kernel.org gave any results.
Maybe I encounter this issue
https://bugzilla.kernel.org/show_bug.cgi?id=204649
it looks quite recent. I'm using exactly 13th and didn't try any other channels.
Anyway if anybody encounters troubles with AR9485 - just try 5.8.7 kernel.
Offline
Systemd tells which cmdline was used while trying to start the service.
He's what do I see on 5.8.7 while trying to execute that cmdline manually (as root, of course):
Successfully initialized wpa_supplicant
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: SME: Trying to authenticate with 50:d2:f5:0c:8c:c2 (SSID='Victoria' freq=2472 MHz)
wlan0: Trying to associate with 50:d2:f5:0c:8c:c2 (SSID='Victoria' freq=2472 MHz)
wlan0: Associated with 50:d2:f5:0c:8c:c2
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: WPA: Key negotiation completed with 50:d2:f5:0c:8c:c2 [PTK=CCMP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to 50:d2:f5:0c:8c:c2 completed [id=0 id_str=]
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-DISCONNECTED bssid=50:d2:f5:0c:8c:c2 reason=3 locally_generated=1
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
wlan0: CTRL-EVENT-TERMINATING
CTRL_EVENT_DISCONNECTED and a consquent 'deinit' is being displayed after I press ctrl+c.
And on 5.8.8 or 5.8.10:
Successfully initialized wpa_supplicant
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
In the latter case wpa_supplicant exits while on older kernel it does not exit while connected.
Last edited by programmador (2020-09-23 14:45:21)
Offline
I've solved the issue actually.
I've accidently found a manual of how to manually connect with wpa_supplicant and it worked.
After experimenting a bit I've found that the defference is adding a -D wext option.
Actually it's described here https://wiki.archlinux.org/index.php/Wp … e_hardware
But it doesn't work as in wiki. 80211nl,wext is not working, I had to leave just wext.
So I've edited wpa_supplicant cmdline in systemd unit file as described in wiki, for me it's the next file:
/etc/systemd/system/multi-user.target.wants/wpa_supplicant@wlan0.service
And changed the line:
ExecStart=/usr/bin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant-%I.conf -i%I
to
ExecStart=/usr/bin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant-%I.conf -i%I -Dwext
Now it's okay.
Actually I don't know what to do with this information - whom should it be adressed to? Kernel? Wpa_supplicant?
Actually upgrading kernel caused it but maybe latest supplicant does not respect some new kernel feature.
Btw I don't know which driver was used on older kernels - maybe it was the same wext and not wl80211 and just autoselecting the driver has been broken, not the driver itself.
Offline
Pages: 1