Open DanMan opened 8 years ago
diederikdehaas
commented
8 years ago It looks like Realtek uses much of the same code across chipsets and only uses the parts which are set by conditionals. It is very likely that you'd need a different driver then this repo provides.
DanMan
commented
8 years ago Ok, thanks.
weedy
commented
8 years ago https://aur.archlinux.org/packages/rtl8812au_rtl8821au-dkms-git/
According to this, copies of 4.3.20 should have very complete rtl8812 driver and 4.3.21 has been stripped down and tuned for rtl8814. Can we either combine these trees or is anyone interested in cleaning up the 4.3.21 driver to work with new kernels?
weedy
commented
8 years ago Follow up.
I have a WPA2 connection right now to my home router and it seems stable. And I can connect to my across the street neighbour.
wlan1 IEEE 802.11an ESSID:"mine" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:5.745 GHz
Bit Rate:300 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-****-**** Security mode:open
Power Management:off
Link Quality=86/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0wlan1 IEEE 802.11bgn ESSID:"neighbour" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:2.412 GHz
Bit Rate:130 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-****-**** Security mode:open
Power Management:off
Link Quality=99/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0ath9k card for comparison
wlan0 IEEE 802.11 ESSID:"mine"
Mode:Managed Frequency:5.745 GHz
Bit Rate=243 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=55/70 Signal level=-55 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:31 Missed beacon:0ath9k
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=1 ttl=64 time=1.28 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=2 ttl=64 time=1.26 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=3 ttl=64 time=1.31 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=4 ttl=64 time=1.25 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=5 ttl=64 time=1.29 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=6 ttl=64 time=1.28 ms8814au D-Link DeathStar DWA-192
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=1 ttl=64 time=3.75 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=2 ttl=64 time=2.17 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=3 ttl=64 time=2.23 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=4 ttl=64 time=2.21 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=5 ttl=64 time=2.23 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=6 ttl=64 time=2.17 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=7 ttl=64 time=2.11 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=8 ttl=64 time=2.15 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=9 ttl=64 time=3.21 ms@weedy for testing purposes only you could try https://github.com/diederikdehaas/rtl8812AU/tree/driver-4.3.20-add-vht-capabilities-wip which is the original 4.3.20 driver to which I added the patches to work up to kernel 4.8.
Can we either combine these trees or is anyone interested in cleaning up the 4.3.21 driver to work with new kernels?
My intention is to find/create a patch(-set) so that VHT capabilities will be added to the 4.3.20 driver, which are present in 4.3.21 and 4.3.22-beta, but not in 4.3.20. But this entails comparing 3 different driver archives so it's a bit of work. I was already aware of Grawp's work, but I hadn't visited his AUR page in a while which now contains some very useful info regarding that and especially the 4.3.21 driver. So thanks for that :+1:
weedy
commented
8 years ago Doing a quick diff you're completely missing the rtl8814 folder in 4.3.20. So I can't see any way of it working.
It's a bit strange, I'm scrolling through meld and 4.3.20 or 4.3.21 will trade places on refinements. I think you should use 4.3.21 as the base if you were going to try and merge drivers into a unified tree. It seems to have much fuller beamforming code for example.
EDIT: It also has 80mhz channels. And either 5ghz support or seemingly more fleshed out 5ghz support.
weedy
commented
8 years ago Should I open a new issue or can you reopen this one to keep track of things?
diederikdehaas
commented
8 years ago I can reopen this issue, but I don't see the need for it.
I just did a quick test by adding the rtl8814au folders into this driver's tree and enabled the setting in the Makefile, but running make quickly bailed out because of
error: nested redefinition of ‘enum _TX_PWR_PERCENTAGE’
and a bunch of similar errors.
While it may be possible to make those compilation errors go away and thereby giving the appearance of it supporting both rtl8812au and rtl8814au, I don't think it's worth it and on top of that I don't have a rtl8814au device so I won't be able to test it.
I (therefor) still think my initial response is correct and you should consider rtl8814au a different driver. The 4.3.21 driver is an excellent starting point for that and there's a real good chance that the patches applied to this repo to support newer kernels can be applied simply/cleanly to the rtl8814au driver and I would have no problem at all if you'd grab them straight from this repo.
As the code base is indeed rather similar, I do intend to use the 4.3.21 (and 4.3.22-beta) code as inspiration to add VHT (80mhz channels) capabilities to the 4.3.20 driver for the rtl8812au chipset.
weedy
commented
8 years ago @uminokoe has already made a tree with it and used it with his hardware. I had to revert changes that he made to swap it back to a rtl8814au driver. So there is already a combined driver tree with VHT and 4.3.22-beta stuff pulled in.
weedy
commented
8 years ago @uminokoe I do use your tree and I have reverted 9260f77 and 8d33100, my RTL8814AU works perfect. I guess I'm trying to push for @diederikdehaas to adopt your work so we can keep all the fixes here. This is the most active RTL8812AU repository on github and I don't want to split the "community" if I don't have to. Also I don't know C so I would have to blindly pull things from you and uminokoe and hope they keep working.
weedy
commented
8 years ago I just want to comment that I've had 0 problems with the combined driver and it's connection to my router. And apparently @uminokoe has a stable AP running on it too.
diederikdehaas
commented
8 years ago I guess 4.3.21 is similar to 4.3.22-beta
What is that guess based on? I've spend way more time that I'd have liked trying to do a 3-way compare on the original downloads, whereby I converted line-endings on the 4.3.20 driver to unix to not make it really impossible (4.3.21 and 4.3.22-beta were already unix) :-/
And now I'm thoroughly confused and annoyed by Realtek('s (lack of (proper)) development procedure). :-1: Some things are equal between 4.3.20 and 4.3.21, but different on 4.3.22-beta. Some things are equal between 4.3.21 and 4.3.22-beta, but different on 4.3.20. Some things are equal between 4.3.20 and 4.3.22-beta, but different on 4.3.21.
And it is not clear to me which of those is 'better' at any given point. I'm even inclined to think that the 4.3.22-beta driver is the most advanced as several to do items in 4.3.20 and 4.3.21 have been replaced with an actual implementation and several things seem to be refactored into separate functions. But its code is older then the 4.3.20 and 4.3.21 drivers based on timestamp and it's also marked as beta.
And as I'm not a C developer, let alone an (very) experienced one, I find it way to risky to try to integrate those driver versions of which 4.3.21 is also made for a different chipset. And 'conclusions' like it compiles and/or it seems to work aren't good enough for me. If there was an extensive unit test suite to run, that would be another matter, but there isn't one. And I don't have the skills or inclination to (learn to) write one. But it would be truly awesome if someone else would.
diederikdehaas
commented
8 years ago The above reply may have come across more hostile then I intended; sorry about that. But I do like to know what your reasons are/were for thinking that 4.3.21 and 4.3.22-beta are similar.
I'm planning to abandon my attempts to add vht capabilities to the 4.3.20 driver as I'm not comfortable with the (imo) substantial changes that I'd need to apply to that driver version in order to support that and I also prefer to stay close to 'upstream' and wait till Realtek releases a driver for rtl8812AU with vht and monitor mode and upload that then.
@uminokoe I'll also add your 4.3.21 driver to this repo, but with a 'disclaimer' that it is based on a driver for the rtl8814au chipset and therefor 'experimental'. Is that OK with you?
I'll also add the instructions in what to do to make it work on a(n actual) rtl8814au device. But I'm really uncomfortable with giving users of this repo the impression that I (can) actually support this device while I don't have one to verify that even the basic functionality works, let alone the more advanced things. Creating a separate repo for rtl8814au would give the same impression.
I don't want to split the "community"
I like that, I really do. I have thought about that many times before and was even on the verge of creating an organization in the hope of creating such a community where we'd all work together to support and improve these out-of-tree kernel drivers. But I'm afraid that would give an impression I wouldn't be able to live up to and/or be able to sustain such an effort, so I didn't.
After all, I consider myself just some random user on the internet who happen to find a more recent driver for my device and uploaded it to GitHub. Just like so many others :-/ The only difference may be that I didn't abandon it after the initial upload. But the popularity it has gotten since still surprises me.
diederikdehaas
commented
8 years ago I found that version 4.3.20's implementation of 802.11ac seemed to be inferior to 4.3.22-beta, and I assumed that this might be why the VHT capabilities could not be added.
I'm quite sure you're right about that. IIRC it actually says somewhere in the comments that the 4.3.20 driver (explicitly) doesn't support 80+80 for example. But to me 802.11ac is primarily the higher speed, and the reason I bought my ac device, and as I consistently get a connection speed of 867 Mbps (vs 54/144 Mbps for n) I've accomplished that goal. But contributions like yours does make me want to achieve more of ac then just that :smile:
The main reason that I'm a bit hesitant about 4.3.21 and where the it compiles and/or it seems to work aren't good enough for me comes from, is that on at least 2 occasions I saw in the comments sth like on rtl8814au we should do X and yet Realtek didn't enclose those sections in #ifdef structures or sth like that actually testing for that device type.
And that gives me the creeps.
And that could also mean that the 4.3.21 driver really shouldn't be applied/run on anything else then a rtl8814au device. While I actually don't expect that to be the case, this whole diff-ing process did not make me happy, to put it mildly :wink: It really annoyed me that 4.3.19 is for rtl8821au devices, 4.3.20 is for rtl8812au devices and 4.3.21 is for rtl8814au devices and too many diffs are (to me) just different instead of natural progressions/improvements as I would expect from sequential version numbers. It's like each release was branched of at a semi random point, various fixes were applied to make that work for a (very) specific chipset and then released, but they never bothered to merge those fixes back into mainline/master.
Addendum: I just compared the product pages for EW-7822UAC with rtl8812au chipset against the EW-7833UAC with rtl8814au chipset and made the following observations:
:thinking:
diederikdehaas
commented
8 years ago Ah, fsck it. I'll create a repo for the rtl8814au chipset even though I don't have the device (and it's not available in NL)
weedy
commented
8 years ago I'll do my best to check any changes you commit to the tree for 14au. If you do want to make an org I'll join it. Our readme can just be "This is a best effort project. None of us know what we are doing, and Realtek sucks at releasing drivers. This will probably kill your pet, we're mostly sorry about that. We did warn you".
Aliexpress has devices for 25usd if you're interested.
diederikdehaas
commented
8 years ago @weedy, @DanMan: I've created the https://github.com/diederikdehaas/rtl8814AU repository and added the initial code and on my system it now compiles on kernels up to and including 4.8
weedy
commented
8 years ago As an FYI since I have access to a higher end AC AP today.
wlan1 IEEE 802.11AC ESSID:"friends" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:5.745 GHz
Bit Rate:1.3 Gb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-****-**** Security mode:open
Power Management:off
Link Quality=96/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=2.47 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=2.58 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=2.21 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=4.36 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=2.64 msOct 17 17:02:42 localhost NetworkManager[8443]: <info> [1476738162.3996] device (wlan0): supplicant interface state: disconnected -> inactive
==> /var/log/kern.log <==
Oct 17 17:02:45 localhost kernel: [1344234.453207] RTL871X: rtw_set_802_11_connect(wlan1) fw_state=0x00000008
Oct 17 17:02:45 localhost kernel: [1344234.453221] RTL871X: [by_bssid:1][assoc_ssid:coco][to_roam:0] new candidate: friend(40:65:a3:b0:5c:ff, ch149) rssi:-41
Oct 17 17:02:45 localhost kernel: [1344234.453233] RTL871X: [HT] HAL Support LDPC = 0x03
Oct 17 17:02:45 localhost kernel: [1344234.453235] RTL871X: [HT] HAL Support STBC = 0x03
Oct 17 17:02:45 localhost kernel: [1344234.453236] RTL871X: [HT] HAL Support Beamformer
Oct 17 17:02:45 localhost kernel: [1344234.453238] RTL871X: [HT] Declare supporting RX LDPC
Oct 17 17:02:45 localhost kernel: [1344234.453239] RTL871X: [HT] Declare supporting TX STBC
Oct 17 17:02:45 localhost kernel: [1344234.453241] RTL871X: [HT] Declare supporting RX STBC = 1
Oct 17 17:02:45 localhost kernel: [1344234.453244] RTL871X: [VHT] Support LDPC = 0x03
Oct 17 17:02:45 localhost kernel: [1344234.453245] RTL871X: [VHT] Support STBC = 0x03
Oct 17 17:02:45 localhost kernel: [1344234.453246] RTL871X: [VHT] Support Beamformer
Oct 17 17:02:45 localhost kernel: [1344234.453247] RTL871X: [VHT] Support Beamformee
==> /var/log/daemon.log <==
Oct 17 17:02:45 localhost NetworkManager[8443]: <info> [1476738165.0629] device (wlan1): supplicant interface state: scanning -> associating
==> /var/log/kern.log <==
Oct 17 17:02:45 localhost kernel: [1344234.888586] RTL871X: start auth
Oct 17 17:02:45 localhost kernel: [1344234.896279] RTL871X: auth success, start assoc
Oct 17 17:02:45 localhost kernel: [1344234.901529] RTL871X: Current VHT LDPC Setting = 0A
Oct 17 17:02:45 localhost kernel: [1344234.901531] RTL871X: Current VHT STBC Setting = 0A
Oct 17 17:02:45 localhost kernel: [1344234.901556] RTL871X: RateBitmap=000000003fffffff , pVHTRate[0]=ea] pVHTRate[1]=ff]
Oct 17 17:02:45 localhost kernel: [1344234.901583] RTL871X: rtw_cfg80211_indicate_connect(wlan1) BSS not found !!
Oct 17 17:02:45 localhost kernel: [1344234.901589] RTL871X: assoc success
Oct 17 17:02:45 localhost kernel: [1344234.901614] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Oct 17 17:02:45 localhost kernel: [1344234.903145] RTL871X: recv eapol packet
Oct 17 17:02:45 localhost kernel: [1344234.904961] RTL871X: send eapol packet
Oct 17 17:02:45 localhost kernel: [1344234.907384] ath: EEPROM regdomain: 0x807c
Oct 17 17:02:45 localhost kernel: [1344234.907388] ath: EEPROM indicates we should expect a country code
Oct 17 17:02:45 localhost kernel: [1344234.907390] ath: doing EEPROM country->regdmn map search
Oct 17 17:02:45 localhost kernel: [1344234.907392] ath: country maps to regdmn code: 0x3a
Oct 17 17:02:45 localhost kernel: [1344234.907394] ath: Country alpha2 being used: CA
Oct 17 17:02:45 localhost kernel: [1344234.907397] ath: Regpair used: 0x3a
Oct 17 17:02:45 localhost kernel: [1344234.907399] ath: regdomain 0x807c dynamically updated by country IE
Oct 17 17:02:45 localhost kernel: [1344234.911022] RTL871X: recv eapol packet
Oct 17 17:02:45 localhost kernel: [1344234.911711] RTL871X: send eapol packet
==> /var/log/daemon.log <==
Oct 17 17:02:45 localhost NetworkManager[8443]: <info> [1476738165.4687] device (wlan1): supplicant interface state: associating -> 4-way handshake
Oct 17 17:02:45 localhost NetworkManager[8443]: <info> [1476738165.4774] device (wlan1): supplicant interface state: 4-way handshake -> completed That looks quite good :smile: Is that with uminokoe's driver or with mine? It likely will be the same, but still good to have verification whether my driver works properly (too).
weedy
commented
8 years ago uhh still his tree. if you just cloned his repo then it would be the same.
In case you have something diff I'll clone yours now.
diederikdehaas
commented
8 years ago if you just cloned his repo
No, I didn't. I took the original download of the rtl8814AU drivers and added some patches to support kernels up to 4.8 (which are the same as used for this repo). See https://github.com/diederikdehaas/rtl8814AU/commits/driver-4.3.21 for details/'changelog'.
weedy
commented
8 years ago Here we go.
rm -f /lib/modules/4.7.4-zen+/kernel/drivers/net/wireless//8814au.ko
/sbin/depmod -a 4.7.4-zen+
install -p -m 644 8814au.ko /lib/modules/4.7.4-zen+/kernel/drivers/net/wireless/
/sbin/depmod -a 4.7.4-zen+
HAF diederik # modprobe -r 8814au; modprobe 8814au
HAF diederik # iwconfig
wlan1 IEEE 802.11AC ESSID:"friends" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:5.745 GHz
Bit Rate:1.3 Gb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-****-**** Security mode:open
Power Management:off
Link Quality=92/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=2.22 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=2.32 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=2.50 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=2.33 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=2.50 msOct 17 18:59:21 localhost NetworkManager[8443]: <info> [1476745161.7857] sup-iface[0x1f11f70,wlan1] config: set interface ap_scan to 1
Oct 17 18:59:21 localhost NetworkManager[8443]: <info> [1476745161.7992] device (wlan1): supplicant interface state: disconnected -> inactive
==> /var/log/kern.log <==
Oct 17 18:59:21 localhost kernel: [1351231.244714] RTL871X: =>cfg80211_rtw_connect(wlan1) - Start to Connection
Oct 17 18:59:21 localhost kernel: [1351231.244718] RTL871X: privacy=1, key= (null), key_len=0, key_idx=0, auth_type=0
Oct 17 18:59:21 localhost kernel: [1351231.244723] RTL871X: _rtw_pwr_wakeup call ips_leave....
Oct 17 18:59:21 localhost kernel: [1351231.244725] RTL871X: ==>ips_leave cnts:5
Oct 17 18:59:21 localhost kernel: [1351231.244726] RTL871X: ===> rtw_ips_pwr_up..............
Oct 17 18:59:21 localhost kernel: [1351231.244731] RTL871X: ===> ips_netdrv_open.........
Oct 17 18:59:21 localhost kernel: [1351231.251866] RTL871X: power-on :REG_SYS_CLKR 0x09=0xb0. REG_CR 0x100=0xea.
Oct 17 18:59:21 localhost kernel: [1351231.251868] RTL871X: MAC has not been powered on yet.
Oct 17 18:59:21 localhost kernel: [1351231.273361] RTL871X: ===>_InitQueueReservedPage_8814AUsb()
Oct 17 18:59:21 localhost kernel: [1351231.277610] RTL871X: <===_InitQueueReservedPage_8814AUsb()
Oct 17 18:59:21 localhost kernel: [1351231.279108] RTL871X: FirmwareDownload8814A fw source from Header
Oct 17 18:59:21 localhost kernel: [1351231.279111] RTL871X: FirmwareDownload8814A fw:NIC, size: 66904
Oct 17 18:59:21 localhost kernel: [1351231.279114] RTL871X: FirmwareDownload8814A: fw_ver=25 fw_subver=0 sig=0x8814
Oct 17 18:59:21 localhost kernel: [1351231.282859] RTL871X: HalROMDownloadFWRSVDPage8814A(): There is an Adapter is sending beacon.
Oct 17 18:59:21 localhost kernel: [1351231.283984] RTL871X: dmem_pkt_size = 5120, iram_pkt_size = 61720,FWHeaderSize = 64, Len = 66904!!
Oct 17 18:59:21 localhost kernel: [1351231.283986] RTL871X: MaxRsvdPageBufSize 1488, Total len 66904
Oct 17 18:59:21 localhost kernel: [1351231.295355] RTL871X: Check sum OK
Oct 17 18:59:21 localhost kernel: [1351231.295730] RTL871X: dmem check sum tmp 33
Oct 17 18:59:21 localhost kernel: [1351231.414151] RTL871X: Check sum OK
Oct 17 18:59:21 localhost kernel: [1351231.414512] RTL871X: imem check sum tmp 105
Oct 17 18:59:22 localhost kernel: [1351231.469378] RTL871X: FWDL success. write_fw:0, 190ms
Oct 17 18:59:22 localhost kernel: [1351231.469382] RTL871X: rtl8814au_hal_init: Download Firmware Success!!
Oct 17 18:59:22 localhost kernel: [1351231.557621] RTL871X: EEEPROMRegulatory 1
Oct 17 18:59:23 localhost kernel: [1351233.097498] RTL871X: ==>PHY_SwitchWirelessBand8814() 2.4G
Oct 17 18:59:23 localhost kernel: [1351233.110900] RTL871X: <==PHY_SwitchWirelessBand8814():Switch Band OK.
Oct 17 18:59:23 localhost kernel: [1351233.258348] RTL871X: pDM_Odm TxPowerTrackControl = 1
Oct 17 18:59:23 localhost kernel: [1351233.258352] RTL871X: pDM_Odm TxPowerTrackControl = 1
Oct 17 18:59:23 localhost kernel: [1351233.267605] RTL871X: MAC Address from REG_MACID = c4:12:f5:5f:da:97
Oct 17 18:59:23 localhost kernel: [1351233.267610] RTL871X: rtl8814au_hal_init in 2023ms
Oct 17 18:59:23 localhost kernel: [1351233.267987] RTL871X: ==>PHY_SwitchWirelessBand8814() 5G
Oct 17 18:59:23 localhost kernel: [1351233.279602] RTL871X: <==PHY_SwitchWirelessBand8814():Switch Band OK.
Oct 17 18:59:23 localhost kernel: [1351233.393732] RTL871X: hw_var_set_opmode()-4935 mode = 2
Oct 17 18:59:23 localhost kernel: [1351233.395202] RTL871X: Registry kfree default force disable.
Oct 17 18:59:23 localhost kernel: [1351233.395216] RTL871X: <=== rtw_ips_pwr_up.............. in 2153ms
Oct 17 18:59:23 localhost kernel: [1351233.395218] RTL871X: nolinked power save leave
Oct 17 18:59:23 localhost kernel: [1351233.395573] RTL871X: ==> ips_leave.....LED(0xc0228282)...
Oct 17 18:59:23 localhost kernel: [1351233.395578] RTL871X: ssid=friends, len=4
Oct 17 18:59:23 localhost kernel: [1351233.395580] RTL871X: bssid=40:65:a3:b0:5c:ff
Oct 17 18:59:23 localhost kernel: [1351233.395581] RTL871X: rtw_cfg80211_set_wpa_version, wpa_version=2
Oct 17 18:59:23 localhost kernel: [1351233.395583] RTL871X: rtw_cfg80211_set_auth_type, nl80211_auth_type=0
Oct 17 18:59:23 localhost kernel: [1351233.395585] RTL871X: cfg80211_rtw_connect, ie_len=22
Oct 17 18:59:23 localhost kernel: [1351233.395589] RTL871X: set wpa_ie(length:22):
Oct 17 18:59:23 localhost kernel: [1351233.395595] RTL871X: 0x30 0x14 0x01 0x00 0x00 0x0f 0xac 0x04
Oct 17 18:59:23 localhost kernel: [1351233.395600] RTL871X: 0x01 0x00 0x00 0x0f 0xac 0x04 0x01 0x00
Oct 17 18:59:23 localhost kernel: [1351233.395603] RTL871X: 0x00 0x0f 0xac 0x02 0x00 0x00 0x00 0x00
Oct 17 18:59:23 localhost kernel: [1351233.395606] RTL871X: got wpa2_ie, wpa2_ielen:20
Oct 17 18:59:23 localhost kernel: [1351233.396709] RTL871X: SetHwReg8814A, 5817, RCR= f40060ca
Oct 17 18:59:23 localhost kernel: [1351233.396722] RTL871X: rtw_cfg80211_set_cipher, ucast=1, cipher=0xfac04
Oct 17 18:59:23 localhost kernel: [1351233.396723] RTL871X: rtw_cfg80211_set_cipher, ucast=0, cipher=0xfac04
Oct 17 18:59:23 localhost kernel: [1351233.396725] RTL871X: rtw_cfg80211_set_key_mgt, key_mgt=0xfac02
Oct 17 18:59:23 localhost kernel: [1351233.396736] RTL871X: rtw_set_802_11_connect(wlan1) fw_state=0x00000008
Oct 17 18:59:23 localhost kernel: [1351233.396741] RTL871X: [by_bssid:1][assoc_ssid:friends][to_roam:0] new candidate: friends(40:65:a3:b0:5c:ff, ch149) rssi:-40
Oct 17 18:59:23 localhost kernel: [1351233.396748] RTL871X: rtw_select_and_join_from_scanned_queue: candidate: friends(40:65:a3:b0:5c:ff, ch:149)
Oct 17 18:59:23 localhost kernel: [1351233.396751] RTL871X: link to Artheros AP
Oct 17 18:59:23 localhost kernel: [1351233.396760] RTL871X: [HT] HAL Support LDPC = 0x03
Oct 17 18:59:23 localhost kernel: [1351233.396762] RTL871X: [HT] HAL Support STBC = 0x03
Oct 17 18:59:23 localhost kernel: [1351233.396764] RTL871X: [HT] Declare supporting RX LDPC
Oct 17 18:59:23 localhost kernel: [1351233.396765] RTL871X: [HT] Declare supporting TX STBC
Oct 17 18:59:23 localhost kernel: [1351233.396766] RTL871X: [HT] Declare supporting RX STBC = 1
Oct 17 18:59:23 localhost kernel: [1351233.396770] RTL871X: [VHT] Support LDPC = 0x03
Oct 17 18:59:23 localhost kernel: [1351233.396771] RTL871X: [VHT] Support STBC = 0x03
Oct 17 18:59:23 localhost kernel: [1351233.396772] RTL871X: [VHT] Support Beamformee
Oct 17 18:59:23 localhost kernel: [1351233.396782] RTL871X: rtw_chk_start_clnt_join(wlan1) req: 149,2,1
Oct 17 18:59:23 localhost kernel: [1351233.396784] RTL871X: rtw_chk_start_clnt_join(wlan1) union: 149,2,1
Oct 17 18:59:23 localhost kernel: [1351233.396790] RTL871X: set ssid:dot11AuthAlgrthm=2, dot11PrivacyAlgrthm=4, dot118021XGrpPrivacy=4
Oct 17 18:59:23 localhost kernel: [1351233.396792] RTL871X: <=cfg80211_rtw_connect, ret 0
==> /var/log/daemon.log <==
Oct 17 18:59:23 localhost NetworkManager[8443]: <info> [1476745163.9587] device (wlan1): supplicant interface state: inactive -> associating
==> /var/log/kern.log <==
Oct 17 18:59:24 localhost kernel: [1351233.823174] RTL871X: OnBeacon: beacon keys ready
Oct 17 18:59:24 localhost kernel: [1351233.823179] RTL871X: link to Artheros AP
Oct 17 18:59:24 localhost kernel: [1351233.823181] RTL871X: start auth
Oct 17 18:59:24 localhost kernel: [1351233.823186] RTL871X: issue_auth
Oct 17 18:59:24 localhost kernel: [1351233.831783] RTL871X: OnAuthClient
Oct 17 18:59:24 localhost kernel: [1351233.831786] RTL871X: auth success, start assoc
Oct 17 18:59:24 localhost kernel: [1351233.831794] RTL871X: network.SupportedRates[0]=8C]
Oct 17 18:59:24 localhost kernel: [1351233.831796] RTL871X: network.SupportedRates[1]=12]
Oct 17 18:59:24 localhost kernel: [1351233.831798] RTL871X: network.SupportedRates[2]=98]
Oct 17 18:59:24 localhost kernel: [1351233.831800] RTL871X: network.SupportedRates[3]=24]
Oct 17 18:59:24 localhost kernel: [1351233.831802] RTL871X: network.SupportedRates[4]=B0]
Oct 17 18:59:24 localhost kernel: [1351233.831804] RTL871X: network.SupportedRates[5]=48]
Oct 17 18:59:24 localhost kernel: [1351233.831805] RTL871X: network.SupportedRates[6]=60]
Oct 17 18:59:24 localhost kernel: [1351233.831807] RTL871X: network.SupportedRates[7]=6C]
Oct 17 18:59:24 localhost kernel: [1351233.831809] RTL871X: bssrate_len = 8
Oct 17 18:59:24 localhost kernel: [1351233.836022] RTL871X: OnAssocRsp
Oct 17 18:59:24 localhost kernel: [1351233.836026] RTL871X: Enable HT Tx LDPC!
Oct 17 18:59:24 localhost kernel: [1351233.836028] RTL871X: Enable HT Tx STBC!
Oct 17 18:59:24 localhost kernel: [1351233.836030] RTL871X: Current VHT LDPC Setting = 0A
Oct 17 18:59:24 localhost kernel: [1351233.836032] RTL871X: Current VHT STBC Setting = 0A
Oct 17 18:59:24 localhost kernel: [1351233.836036] RTL871X: report_join_res(1)
Oct 17 18:59:24 localhost kernel: [1351233.836039] RTL871X: rtw_joinbss_update_network
Oct 17 18:59:24 localhost kernel: [1351233.836043] RTL871X: +rtw_update_ht_cap()
Oct 17 18:59:24 localhost kernel: [1351233.836052] RTL871X: rtw_alloc_macid(wlan1) if1, hwaddr:40:65:a3:b0:5c:ff macid:0
Oct 17 18:59:24 localhost kernel: [1351233.836053] RTL871X: rtw_joinbss_update_stainfo
Oct 17 18:59:24 localhost kernel: [1351233.836058] RTL871X: RateBitmap=000000003fffffff , pVHTRate[0]=ea] pVHTRate[1]=ff]
Oct 17 18:59:24 localhost kernel: [1351233.836060] RTL871X: supp_mcs_set = ff, ff, ff, rf_type=255, tx_ra_bitmap=000003fffffffff0
Oct 17 18:59:24 localhost kernel: [1351233.836063] RTL871X: rtw_get_tx_nss: 2 SS, rf_type=1
Oct 17 18:59:24 localhost kernel: [1351233.836065] RTL871X: ### Set STA_(0) info ###
Oct 17 18:59:24 localhost kernel: [1351233.836071] RTL871X: rtw_cfg80211_indicate_connect(wlan1)
Oct 17 18:59:24 localhost kernel: [1351233.836092] RTL871X: rtw_cfg80211_indicate_connect(wlan1) BSS not found !!
Oct 17 18:59:24 localhost kernel: [1351233.836103] RTL871X: assoc success
Oct 17 18:59:24 localhost kernel: [1351233.836171] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Oct 17 18:59:24 localhost kernel: [1351233.838525] RTL871X: recv eapol packet
Oct 17 18:59:24 localhost kernel: [1351233.839727] RTL871X: HW_VAR_BASIC_RATE: 0x150 -> 0x150 -> 0x150
Oct 17 18:59:24 localhost kernel: [1351233.841313] RTL871X: _rtw_reg_notifier
Oct 17 18:59:24 localhost kernel: [1351233.841318] RTL871X: _rtw_reg_notifier_apply: NL80211_REGDOM_SET_BY_COUNTRY_IE
Oct 17 18:59:24 localhost kernel: [1351233.841328] ath: EEPROM regdomain: 0x807c
Oct 17 18:59:24 localhost kernel: [1351233.841330] ath: EEPROM indicates we should expect a country code
Oct 17 18:59:24 localhost kernel: [1351233.841331] ath: doing EEPROM country->regdmn map search
Oct 17 18:59:24 localhost kernel: [1351233.841332] ath: country maps to regdmn code: 0x3a
Oct 17 18:59:24 localhost kernel: [1351233.841334] ath: Country alpha2 being used: CA
Oct 17 18:59:24 localhost kernel: [1351233.841335] ath: Regpair used: 0x3a
Oct 17 18:59:24 localhost kernel: [1351233.841337] ath: regdomain 0x807c dynamically updated by country IE
Oct 17 18:59:24 localhost kernel: [1351233.842739] RTL871X: WMM(0): 0, a42b
Oct 17 18:59:24 localhost kernel: [1351233.842753] RTL871X: send eapol packet
Oct 17 18:59:24 localhost kernel: [1351233.843178] RTL871X: WMM(1): 0, a44f
Oct 17 18:59:24 localhost kernel: [1351233.843508] RTL871X: WMM(2): 0, 5e4322
Oct 17 18:59:24 localhost kernel: [1351233.843878] RTL871X: WMM(3): 0, 2f3222
Oct 17 18:59:24 localhost kernel: [1351233.843880] RTL871X: wmm_para_seq(0): 0
Oct 17 18:59:24 localhost kernel: [1351233.843881] RTL871X: wmm_para_seq(1): 1
Oct 17 18:59:24 localhost kernel: [1351233.843882] RTL871X: wmm_para_seq(2): 2
Oct 17 18:59:24 localhost kernel: [1351233.843884] RTL871X: wmm_para_seq(3): 3
Oct 17 18:59:24 localhost kernel: [1351233.843885] RTL871X: HTOnAssocRsp
Oct 17 18:59:24 localhost kernel: [1351233.844257] RTL871X: VHTOnAssocRsp
Oct 17 18:59:24 localhost kernel: [1351233.844630] RTL871X: UpdateHalRAMask8814A => mac_id:0, networkType:0x44, mask:0x000003fffffffff0
Oct 17 18:59:24 localhost kernel: [1351233.844630] ==> rssi_level:0, rate_bitmap:0x000003fffffff010, shortGIrate=1
Oct 17 18:59:24 localhost kernel: [1351233.844634] RTL871X: rtl8814_set_raid_cmd, bitmap=0x000003fffffff010, mac_id=0x0, raid=0x9, shortGIrate=1, init_rate=31, power training=00
Oct 17 18:59:24 localhost kernel: [1351233.846654] RTL871X: recv eapol packet
Oct 17 18:59:24 localhost kernel: [1351233.846714] RTL871X: send eapol packet
Oct 17 18:59:24 localhost kernel: [1351233.846746] RTL871X: cfg80211_rtw_add_key(wlan1) adding key for 40:65:a3:b0:5c:ff
Oct 17 18:59:24 localhost kernel: [1351233.846748] RTL871X: cipher=0xfac04
Oct 17 18:59:24 localhost kernel: [1351233.846750] RTL871X: key_len=0x10
Oct 17 18:59:24 localhost kernel: [1351233.846751] RTL871X: seq_len=0x6
Oct 17 18:59:24 localhost kernel: [1351233.846752] RTL871X: key_index=0
Oct 17 18:59:24 localhost kernel: [1351233.846753] RTL871X: pairwise=1
Oct 17 18:59:24 localhost kernel: [1351233.846755] RTL871X: rtw_cfg80211_set_encryption
Oct 17 18:59:24 localhost kernel: [1351233.846757] RTL871X: rtw_cfg80211_set_encryption, : param->u.crypt.set_tx ==1
Oct 17 18:59:24 localhost kernel: [1351233.846758] RTL871X: ~~~~set sta key:unicastkey
Oct 17 18:59:24 localhost kernel: [1351233.846761] RTL871X: rtw_cfg80211_set_encryption, ret=0
Oct 17 18:59:24 localhost kernel: [1351233.846775] RTL871X: cfg80211_rtw_set_default_key(wlan1) key_index=0, unicast=1, multicast=0
Oct 17 18:59:24 localhost kernel: [1351233.846868] RTL871X: cfg80211_rtw_add_key(wlan1) adding key for (null)
Oct 17 18:59:24 localhost kernel: [1351233.846870] RTL871X: cipher=0xfac04
Oct 17 18:59:24 localhost kernel: [1351233.846882] RTL871X: key_len=0x10
Oct 17 18:59:24 localhost kernel: [1351233.846884] RTL871X: seq_len=0x6
Oct 17 18:59:24 localhost kernel: [1351233.846885] RTL871X: key_index=2
Oct 17 18:59:24 localhost kernel: [1351233.846886] RTL871X: pairwise=0
Oct 17 18:59:24 localhost kernel: [1351233.846888] RTL871X: rtw_cfg80211_set_encryption
Oct 17 18:59:24 localhost kernel: [1351233.846889] RTL871X: ~~~~set sta key:groupkey
Oct 17 18:59:24 localhost kernel: [1351233.846891] RTL871X: ==> rtw_set_key algorithm(4),keyid(2),key_mask(0)
Oct 17 18:59:24 localhost kernel: [1351233.846893] RTL871X: rtw_cfg80211_set_encryption, ret=0
Oct 17 18:59:24 localhost kernel: [1351233.847003] RTL871X: cfg80211_rtw_change_station(wlan1)
==> /var/log/daemon.log <==
Oct 17 18:59:24 localhost NetworkManager[8443]: <info> [1476745164.4042] device (wlan1): supplicant interface state: associating -> completed I need to make a PR for the couple edits I made to shut up most debug but not alllllllll debug. I forgot how noisy this thing is stock. My poor SSD.
diederikdehaas
commented
8 years ago I need to make a PR for the couple edits I made to shut up most debug but not alllllllll debug.
No need for that. I'll cherry-pick commit https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc6bae5695b1317925497c2ead167e09a48
EDIT: Pushed it, so you only need to do a git pull
weedy
commented
8 years ago It's not the same. I'll show you later.
diederikdehaas
commented
8 years ago Ok :+1:
Just found the following in the Makefile:
###################### MP HW TX MODE FOR VHT #######################
CONFIG_MP_VHT_HW_TX_MODE = nSo it looks like VHT stuff isn't enabled (by default)
weedy
commented
8 years ago I saw that, and then I grep'ed the code. I don't know NEAR enough C (read none) to figure out if that's specifically VHT or some kind of VHT-in-the-firmware-something-something. AND @uminokoe did this thing on his tree https://github.com/uminokoe/rtl8812AU/commit/5f75242fce32cc1d86cb80a10ffdb7da9dac5185.
diederikdehaas
commented
8 years ago Just applied the following diff and it still compiles ... :
diederik@bagend:~/dev/drivers/rtl8814AU$ git diff
diff --git a/Makefile b/Makefile
index addda91..d907b0e 100644
--- a/Makefile
+++ b/Makefile
@@ -74,7 +74,7 @@ CONFIG_AP_WOWLAN = n
######### Notify SDIO Host Keep Power During Syspend ##########
CONFIG_RTW_SDIO_PM_KEEP_POWER = y
###################### MP HW TX MODE FOR VHT #######################
-CONFIG_MP_VHT_HW_TX_MODE = n
+CONFIG_MP_VHT_HW_TX_MODE = y
###################### Platform Related #######################
CONFIG_PLATFORM_I386_PC = y
CONFIG_PLATFORM_ANDROID_X86 = n
@@ -528,8 +528,8 @@ endif
########### HAL_RTL8814A #################################
ifeq ($(CONFIG_RTL8814A), y)
## ADD NEW VHT MP HW TX MODE ##
-#EXTRA_CFLAGS += -DCONFIG_MP_VHT_HW_TX_MODE
-#CONFIG_MP_VHT_HW_TX_MODE = y
+EXTRA_CFLAGS += -DCONFIG_MP_VHT_HW_TX_MODE
+CONFIG_MP_VHT_HW_TX_MODE = y
##########################################
RTL871X = rtl8814a
ifeq ($(CONFIG_USB_HCI), y)But mostly interested in the changes you saw with uminokoe's patch applied.
diederikdehaas
commented
8 years ago Please forgive me for being stupid as I do not have knowledge in programming or WiFi adapter driver development.
Welcome to the club! LOL
I went through the code as well and I primarily noticed how very few useful comments are present in the code. Iow, I have no clue (either).
weedy
commented
8 years ago Please forgive me for being stupid as I do not have knowledge in programming or WiFi adapter driver development.
F***ing same, so very same
# grep CONFIG_MP_VHT_HW_TX_MODE Makefile
CONFIG_MP_VHT_HW_TX_MODE = y
EXTRA_CFLAGS += -DCONFIG_MP_VHT_HW_TX_MODE
CONFIG_MP_VHT_HW_TX_MODE = y
ifeq ($(CONFIG_MP_VHT_HW_TX_MODE), y)
EXTRA_CFLAGS += -DCONFIG_MP_VHT_HW_TX_MODEEdit: Actually I'm the only one here who has seen the full iw output. So here.
# iw phy
Wiphy phy31
max # scan SSIDs: 9
max scan IEs length: 2304 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* P2P-client
* P2P-GO
Band 1:
Capabilities: 0x19e3
RX LDPC
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT Max RX data rate: 450 Mbps
HT TX/RX MCS rate indexes supported: 0-23
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps
* 5.5 Mbps
* 11.0 Mbps
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (30.0 dBm)
* 2417 MHz [2] (30.0 dBm)
* 2422 MHz [3] (30.0 dBm)
* 2427 MHz [4] (30.0 dBm)
* 2432 MHz [5] (30.0 dBm)
* 2437 MHz [6] (30.0 dBm)
* 2442 MHz [7] (30.0 dBm)
* 2447 MHz [8] (30.0 dBm)
* 2452 MHz [9] (30.0 dBm)
* 2457 MHz [10] (30.0 dBm)
* 2462 MHz [11] (30.0 dBm)
* 2467 MHz [12] (disabled)
* 2472 MHz [13] (disabled)
* 2484 MHz [14] (disabled)
Band 2:
Capabilities: 0x19e3
RX LDPC
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT Max RX data rate: 450 Mbps
HT TX/RX MCS rate indexes supported: 0-23
VHT Capabilities (0x03c158b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
SU Beamformer
SU Beamformee
+HTC-VHT
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 1300 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 1300 Mbps
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5170 MHz [34] (disabled)
* 5180 MHz [36] (17.0 dBm)
* 5190 MHz [38] (disabled)
* 5200 MHz [40] (17.0 dBm)
* 5210 MHz [42] (disabled)
* 5220 MHz [44] (17.0 dBm)
* 5230 MHz [46] (disabled)
* 5240 MHz [48] (17.0 dBm)
* 5260 MHz [52] (24.0 dBm) (no IR)
* 5280 MHz [56] (24.0 dBm) (no IR)
* 5300 MHz [60] (24.0 dBm) (no IR)
* 5320 MHz [64] (24.0 dBm) (no IR)
* 5500 MHz [100] (24.0 dBm) (no IR)
* 5520 MHz [104] (24.0 dBm) (no IR)
* 5540 MHz [108] (24.0 dBm) (no IR)
* 5560 MHz [112] (24.0 dBm) (no IR)
* 5580 MHz [116] (24.0 dBm) (no IR)
* 5600 MHz [120] (30.0 dBm) (no IR)
* 5620 MHz [124] (30.0 dBm) (no IR)
* 5640 MHz [128] (30.0 dBm) (no IR)
* 5660 MHz [132] (24.0 dBm) (no IR)
* 5680 MHz [136] (24.0 dBm) (no IR)
* 5700 MHz [140] (24.0 dBm) (no IR)
* 5745 MHz [149] (30.0 dBm)
* 5765 MHz [153] (30.0 dBm)
* 5785 MHz [157] (30.0 dBm)
* 5805 MHz [161] (30.0 dBm)
* 5825 MHz [165] (30.0 dBm)
* 5920 MHz [184] (disabled)
* 5940 MHz [188] (disabled)
* 5960 MHz [192] (disabled)
* 5980 MHz [196] (disabled)
* 6000 MHz [200] (disabled)
* 6020 MHz [204] (disabled)
* 6040 MHz [208] (disabled)
* 6060 MHz [212] (disabled)
* 6080 MHz [216] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* set_bss
* join_ibss
* set_pmksa
* del_pmksa
* flush_pmksa
* remain_on_channel
* frame
* set_channel
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
WoWLAN support:
* wake up on anything (device continues operating normally)
software interface modes (can always be added):
interface combinations are not supported
Device supports scan flush.
I see mention of that chipset in the sources, but if I plug in a D-Link DWA-192, the driver currently doesn't seem to support it, unfortunatly.
What's missing?