unisoc_wifi disconnections on OrangePi Zero 3

[Alessandro Lannocca]

Dear All,

I get frequent and random disconnection from orangepizero3 onboard wifi with armibian community (self-built) both trunk and 24.02

current kernel, 6.6.26 and 6.6.28

 

message is always

[21738.338021] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it
[21848.116072] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it
[21915.426734] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection sm_state (5), status: (2)!
[21915.426817] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection Vodafone-CSC failed status code:1!
[21919.477424] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it
[[21738.338021] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it
[21848.116072] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it
[21915.426734] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection sm_state (5), status: (2)!
[21915.426817] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection Vodafone-CSC failed status code:1!
[21919.477424] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it

 

Full logs available at armbianmonitor -u

 

Any help/hint/solution deeply appreciated

Edited April 19 by Alessandro Lannocca
incompletion

[Alessandro Lannocca]

After blaming:

- networkmanager

- ifupdown

- systemd

- my router

- my provider

- myself

 

I tested with a separate wifi AP (not managed by my provider) and sprdwl_ng crashes to the point of being incapable of "seeing" any network again (until rmmod and insmod) when the same ESSID is broadcast both under 2.4Ghz and 5.5Ghz

 

My wild assumption is that this driver doens't like (buggy perhaps?) to be "band-steered"

 

Whens ticking to a single band, no issue.

Hope it helps someone in my same situation

Edited April 25 by Alessandro Lannocca
incompletion

[Thomas Waterfall]

I have a similar problem with the official orange pi zero 3 image. It could also be band steering on my Asus XT8 mesh network. Wifi will stay connected for days and then drop out. I have noticed it occurs more frequently after I restart my router(s).

 

I wrote a simple CRON job to reconnect when wifi is disconnected however it doesn't seem to work.

 

*/5 * * * *  nmcli -t dev status | grep -q connected:Asus && echo "Connection 'Asus' is already connected" || (nmcli con up id Asus && echo "Connection 'Asus' is now connected" || echo "Failed to connect to 'Asus'")

 

  I hoped moving to Armbian would solve my problems however maybe I just make the above script reboot the machine on a less frequent basis when the connection drops. Following the topic incase someone figures out a software fix! Would much prefer being on armbian and glad to see there is now community support which wasn't the case when I last checked!

Edited April 30 by Thomas Waterfall

[Alessandro Lannocca]

Hi Thomas, thanks for your report - I was thinking about a cronjob too o something that monitors dmesg

nevertheless, as a mitigation to avoid a reboot when wifi stops I can suggest:

 

sudo rmmod sprdwl_ng && sudo modprobe sprdwl_ng

 

Definitely not elegant, but gets wifi back from the dead until the next band hop

Hope it helps

 

Ale

[link89]

I have the same issue when I connect my OrangePi Zero 3 to University WiFi

[  173.980677] unisoc_wifi unisoc_wifi wlan0: sprdwl_report_connection XMUNET+ failed status code:1!
[  249.201042] sprdwl:sprdwl_fc_add_share_credit, 533, mode:1 closed, index:0, share it

 

But it is stable when I connect to home WiFi. When I run `iwconfig`  it shows that the wlan0 may switch between 2.4GHz and 5GHz from time to time. So I force it to use 2.4G by adding  `band: 2.4GHz` to `netplan` configuration. And it seems to work pretty well.