Jump to content

Recommended Posts

Posted
27 minutes ago, taner97 said:

that im not be annoyed of low throughput and i just want to connect my dorms wifi..

 

The amount of retries needed to get a frame in/out of the wifi interface affects more than just throughput. It can break association, DHCP etc. Of course you know all of this because you know better than everyone else right?

 

28 minutes ago, taner97 said:

So as long as this open wifi connection bug is not introduced and developers doesnt know

 

It works for me from what I remember. I actually broke WPA/WPA2 support at some point trying to get the chip to pass encrypted frames directly to the kernel and connecting to open aps was the only thing that worked. 

As far as I can tell you haven't actually posted anything to show what happens when you try to connect to an open AP let alone anything that shows your issue is an issue with the xradio driver.

 

And... it could be an issue that is unsolvable without more details on the firmware running on the chip. The xr819 doesn't just take frames off of the air and pass them to the host. Maybe it thinks it should be decrypting frames it shouldn't? Who knows.

 

35 minutes ago, taner97 said:

im here to do bug reporting that maybe can easily solved which i'm believing to

 

Maybe it is easy to fix but where are the logs and packet dumps? I'm not sure what your idea of reporting a bug is but it's not "This doesn't work for me, fix it now!".  I don't think you have ever said where it fails to connect.. not associating outright is different to no passing any IP traffic etc. 

 

Posted
1 hour ago, dgp said:

Maybe it is easy to fix but where are the logs and packet dumps? I'm not sure what your idea of reporting a bug is but it's not "This doesn't work for me, fix it now!".  I don't think you have ever said where it fails to connect.. not associating outright is different to no passing any IP traffic etc. 

 

Its failing to associate and this problem not occurs on legacy kernel which is using same firmware. but i dont know how to get debug info. there is no modprobe param for it

Posted
1 hour ago, taner97 said:

Its failing to associate and this problem not occurs on legacy kernel which is using same firmware. but i dont know how to get debug info. there is no modprobe param for it

 

There is a line in the Makefile for the module to enable debugging. You should see messages in dmesg about association even without that.

Posted
Quote

[  206.929383] ieee80211 phy0: Freq 2432 (wsm ch: 5).
[  206.930313] wlan0: send auth to b4:e9:b0:a7:xx:xx (try 1/3)
[  206.930904] wlan0: send auth to b4:e9:b0:a7:xx:xx (try 2/3)
[  206.938186] wlan0: send auth to b4:e9:b0:a7:xx:xx (try 3/3)
[  206.939800] wlan0: authentication with b4:e9:b0:a7:xx:xx timed out
[  207.010463] ieee80211 phy0: ignore IEEE80211_CONF_CHANGE_MONITOR (0)IEEE80211_CONF_CHANGE_IDLE (1)

@dgpdmesg outputs just that without enabling debug. I got this error while compiling with debug flags. Tried -Wno-error but cant make it

Quote

root/xradio/rx.c: In function ‘xradio_rx_cb’:
/root/xradio/rx.c:122:3: error: implicit declaration of function ‘xradio_check_go_neg_conf_success’ [-Werror=implicit-function-declaration]
   xradio_check_go_neg_conf_success(hw_priv, action);
   ^
cc1: some warnings being treated as errors
scripts/Makefile.build:294: recipe for target '/root/xradio/rx.o' failed
make[1]: *** [/root/xradio/rx.o] Error 1
Makefile:1490: recipe for target '_module_/root/xradio' failed
 

 

Posted

So it's missing the auth responses or not sending the packets at all. Do you have a laptop or something you can run wireshark on and dump what is happening on the air?

Also what does /proc/interrupts look like?

Posted

device(client) mac: 12:42:06:22:8e:d2 and I tried 3 times command iwconfig wlan0 essid KYKWIFI

and its the interrupts.

Quote

           CPU0       CPU1       CPU2       CPU3       
 17:          0          0          0          0     GIC-0  29 Level     arch_timer
 18:       5717      22773      10637      12565     GIC-0  30 Level     arch_timer
 21:          0          0          0          0     GIC-0  50 Level     sun4i_timer0
 22:          0          0          0          0     GIC-0  82 Level     1c02000.dma-controller
 24:      66523          0          0          0     GIC-0  92 Level     sunxi-mmc
 25:      20395          0          0          0     GIC-0  93 Level     sunxi-mmc
 26:        954          0          0          0     GIC-0 103 Level     musb-hdrc.1.auto
 27:          0          0          0          0     GIC-0 104 Level     ehci_hcd:usb1
 28:          0          0          0          0     GIC-0 105 Level     ohci_hcd:usb3
 29:          0          0          0          0     GIC-0 106 Level     ehci_hcd:usb2
 30:          0          0          0          0     GIC-0 107 Level     ohci_hcd:usb4
 34:      11137          0          0          0     GIC-0  97 Level     sun6i-spi
 36:       1182          0          0          0     GIC-0  63 Level     1c25000.ths
 37:        579          0          0          0     GIC-0  32 Level     serial
 38:          0          0          0          0     GIC-0 114 Level     1c30000.ethernet
 39:          0          0          0          0     GIC-0  72 Level     1f00000.rtc
 84:        263          0          0          0  sunxi_pio_edge  42 Edge      xradio
 86:          1          0          0          0  sunxi_pio_edge  44 Edge      usb0-id-det
109:          1          0          0          0  sunxi_pio_edge   3 Edge      sw4
IPI0:          0          0          0          0  CPU wakeup interrupts
IPI1:          0          0          0          0  Timer broadcast interrupts
IPI2:       3041      24675       2739       2807  Rescheduling interrupts
IPI3:         10          7          3          7  Function call interrupts
IPI4:          0          0          0          0  CPU stop interrupts
IPI5:         16        118         18          4  IRQ work interrupts
IPI6:          0          0          0          0  completion interrupts
Err:          0
 

 

dsds.pcapng

Posted

Ok, so we can see probe requests going out from the xr819 (as long as this is not captured on the orange pi zero) and no probe response.

I think you said this works with the legacy kernel driver. Can you capture the packets there so we can compare? 

Posted

here it is. client mac dc:44:6d:d3:a6:7f

lega.pcapng

 

edit : also i prepared another captures with smartphone hotspot named Redmi. while KYKWIFI network has multiple ssid that maybe cause a confusion. 

legaredmi is connection with legacy kernel client mac addr is  dc:44:6d:d3:a6:7f

devredmi is mainline kernel client mac addr  12:42:06:22:8e:d2

devredmi.pcapng

legaredmi.pcapng

Posted

I'm not seeing anything after the probe request in either capture which suggests you aren't getting everything.

I don't have anything to setup a test access point with right at this moment but I will test this myself at some point.

Again, if it works for me I can't really do much without more raw data to go from.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines