Unable to Scan

[cowherdboy]

I am now trying to use the 8192du module on a ppc embedded system. I was able to cross compile your code successfully. The insmod was successful. iwconfig shows:

wlan1 unassociated Nickname:"WIFI@REALTEK" Mode:Auto Frequency=5.18 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

wlan0 unassociated Nickname:"WIFI@REALTEK" Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

However, when I try to scan it shows the following:

iwlist wlan0 scan wlan0 No scan results

My laptop scan with the 8192du module in the same vicinity shows many APs present. I had no problem with the 8192cu either on the same embedded system.

I shall send you the kernel config for the embedded system separately. Please let me know if I have missed anything out.

[cowherdboy]

I also tried version 4.02 of the vendor's driver and got the following output when trying to connect to an AP:

iwconfig wlan0 essid rt.rzone =>rtw_wx_set_essid ssid=rt.rzone, len=8 Set SSID under fw_state=0x00000008 <=rtw_wx_set_essid, ret 0 survey done event (0) rtw_select_and_join_from scanned_queue: return _FAIL(candidate == NULL) try_to_join, but select scanning queue fail, to_roaming:0

I tried the same command with your driver. I failed to connect but did not get any error logs like the above.

The kernel version of my embedded system is 3.8.13-rt9-QorIQ-SDK-V1.4.

[cowherdboy]

Got it to work. I had to do the following:

ifconfig wlan0 down ifconfig wlan0 up iwconfig wlan0 mode Managed

ifconfig wlan1 down ifconfig wlan1 up iwconfig wlan1 mode Managed

I had to do for both 2.4 GHz and 5 GHz before I could scan or associate with APs. Initially I did not do the ifconfig down & up for the 5 GHz portion.

[lwfinger]

Unfortunately, Realtek's drivers seldom work for big-endian systems. The device is little-endian and the natural order is OK for x86. I have not yet had a chance to debug the driver on my PowerBook G4.

Things are improving. When I started, their drivers didn't work with x86_64.

[cowherdboy]

All is well now for ppc as far as WiFi client operation is concerned. Need to get hostapd cross-compiled for ppc now to test AP functionality.