darkdrgn2k Posted February 14, 2018 Share Posted February 14, 2018 Don't know if this is a Arabian issue or a driver issue But i got a ath9k mpcie board in en ExpressoBIN running Armbian nightly WIP lspci 00:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter dmesg shows: 20.892457] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x44 [ 21.154426] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x4 [ 21.505762] ath9k 0000:00:00.0: enabling device (0000 -> 0002) [ 21.505794] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x3c [ 21.657293] dsa dsa@0 wan: Link is Up - 1Gbps/Full - flow control rx/tx [ 21.771223] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0xc [ 21.954333] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x4 [ 22.208975] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x40 [ 22.458432] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0xc [ 22.758269] Unhandled fault: synchronous external abort (0x96000210) at 0xffffff8000a84020 [ 22.995638] Internal error: : 96000210 [#1] PREEMPT SMP [ 23.000798] Modules linked in: ath9k(+) ath9k_common ath9k_hw ath mac80211 cfg80211 rfkill bridge stp llc zram zsmalloc lz4_compress [ 23.013237] CPU: 1 PID: 462 Comm: systemd-udevd Not tainted 4.4.108-mvebu64 #6 [ 23.020813] Hardware name: Marvell Armada 3720 Community Board (DT) [ 23.020819] task: ffffffc038722e00 ti: ffffffc038628000 task.ti: ffffffc038628000 [ 23.020892] PC is at ath9k_ioread32+0x28/0x78 [ath9k] [ 23.020963] LR is at ath9k_hw_init+0xc0/0xad8 [ath9k_hw] [ 23.020967] pc : [<ffffffbffc1efd30>] lr : [<ffffffbffc161df0>] pstate: 80000145 [ 23.020968] sp : ffffffc03862b900 [ 23.020975] x29: ffffffc03862b900 x28: ffffffc038b7c068 [ 23.020979] x27: ffffffbffc202f60 x26: ffffffc038473420 [ 23.020983] x25: ffffffbffc203700 x24: 0000000000000000 [ 23.020987] x23: ffffffc038b7c068 x22: ffffffc038b7c068 [ 23.020991] x21: ffffffc0384706e0 x20: ffffffc038471420 [ 23.020995] x19: ffffff8000a80000 x18: 0000000000000a03 [ 23.020999] x17: 0000007f8bb33310 x16: 0000000000428018 [ 23.021002] x15: 0000007f8bcbe000 x14: 00000000000005c9 [ 23.021006] x13: 0000000000000003 x12: 0000000000000002 [ 23.021010] x11: 0000000000000000 x10: 00000000000007a0 [ 23.021014] x9 : ffffffc03862b850 x8 : ffffffc038723600 [ 23.021018] x7 : ffffffc03ffd8fc0 x6 : 0000000000000000 [ 23.021021] x5 : 0000000000000000 x4 : 000000000001035f [ 23.021025] x3 : 0000000000000032 x2 : 0000000000000000 [ 23.021029] x1 : ffffff8000a84020 x0 : ffffffc038b7c018 [ 23.021034] Process systemd-udevd (pid: 462, stack limit = 0xffffffc038628020) [ 23.021037] Stack: (0xffffffc03862b900 to 0xffffffc03862c000) [ 23.021043] b900: ffffffc03862b930 ffffffbffc161df0 ffffffc038b7c018 ffffffc038b7c018 [ 23.021047] b920: ffffffc0384706e0 ffffffc038b7c018 ffffffc03862b9a0 ffffffbffc1f07a0 [ 23.021052] b940: ffffffc038471420 ffffffc038b7c018 ffffffc0384706e0 ffffffc038b7c068 [ 23.021056] b960: ffffffc038b7c018 0000000000000000 ffffffbffc203700 ffffffc038473420 [ 23.021061] b980: ffffffbffc202f60 ffffffbffc1f0778 ffffffc038471420 00ffffc0378ff098 [ 23.021065] b9a0: ffffffc03862ba50 ffffffbffc1ff88c ffffffc0378ff000 ffffffc0378ff098 [ 23.021069] b9c0: ffffffc038471420 ffffffc0384706e0 0000000000000000 ffffffbffc201410 [ 23.021074] b9e0: 0000000000000001 ffffffc000120e50 ffffffc037cdccf8 0000000000000124 [ 23.021078] ba00: ffffffc03862ba50 ffffffbffc1ff86c ffffffc0378ff000 ffffffc0378ff098 [ 23.021083] ba20: 0000000838471420 ffffffc0384706e0 ffffffbffc202738 ffffffbffc201410 [ 23.021087] ba40: 0000000000000001 ffffffc000120e50 ffffffc03862bae0 ffffffc0005fe3b0 [ 23.021092] ba60: ffffffc0378ff098 ffffffbffc201410 ffffffc0378ff000 ffffffbffc203288 [ 23.021096] ba80: ffffffbffc203220 ffffffbffc203450 ffffffc000c8d568 000000002023d808 [ 23.021101] baa0: ffffffc03862bab0 ffffffc0006ca640 ffffffc03862bae0 ffffffc0005fe39c [ 23.021105] bac0: ffffffc0378ff098 ffffffbffc201410 ffffffc0378ff000 ffffffbffc203288 [ 23.021110] bae0: ffffffc03862bb20 ffffffc0006bfd3c ffffffc0378ff098 ffffffc000e6c000 [ 23.021115] bb00: 0000000000000000 ffffffbffc203288 0000000000000016 ffffffc000e6c000 [ 23.021119] bb20: ffffffc03862bb60 ffffffc0006bfec4 ffffffc0378ff098 ffffffbffc203288 [ 23.021124] bb40: ffffffc0378ff0f8 ffffffc000df15d8 ffffffc000e01000 ffffffc0006bfe50 [ 23.021128] bb60: ffffffc03862bb90 ffffffc0006bdebc 0000000000000000 ffffffbffc203288 [ 23.021132] bb80: ffffffc0006bfe28 ffffffc03862bbe0 ffffffc03862bbd0 ffffffc0006bf620 [ 23.021136] bba0: ffffffbffc203288 ffffffc038321f00 0000000000000000 ffffffc0009e1a58 [ 23.021141] bbc0: ffffffc039123ea8 ffffffc037947f68 ffffffc03862bbe0 ffffffc0006bf190 [ 23.021146] bbe0: ffffffc03862bc20 ffffffc0006c0678 ffffffbffc203288 ffffffc000dbb220 [ 23.021150] bc00: ffffffc038b84180 ffffffbffc20b000 0000000000000000 00000000ffffffd0 [ 23.021154] bc20: ffffffc03862bc40 ffffffc0005fd1b8 ffffffc000dbb220 ffffffc000dbb220 [ 23.021159] bc40: ffffffc03862bc50 ffffffbffc1ffbd0 ffffffc03862bc60 ffffffbffc20b00c [ 23.021163] bc60: ffffffc03862bc70 ffffffc000082950 ffffffc03862bcf0 ffffffc00015f46c [ 23.021168] bc80: ffffffbffc203400 ffffffc000dca000 0000000000000001 ffffffc038b84100 [ 23.021172] bca0: ffffffbffc203400 ffffffc000dca000 0000000000000001 ffffffc0389cb580 [ 23.021177] bcc0: ffffffbffc203400 ffffffbffc203450 0000000000000001 ffffffc000120e50 [ 23.021181] bce0: ffffffc037cdccf8 ffffffc0389cb5c8 ffffffc03862bd20 ffffffc00012407c [ 23.021186] bd00: ffffffc03862be58 ffffffc0389cb5c8 0000000000000001 ffffffc0389cb580 [ 23.021190] bd20: ffffffc03862be20 ffffffc000124810 0000000000000000 0000000000000014 [ 23.021194] bd40: 0000007f966d80f0 0000007f96617af4 0000000040000000 0000000000000015 [ 23.021198] bd60: 000000000000011d 0000000000000111 ffffffc0009f2000 ffffffc038628000 [ 23.021203] bd80: ffffffc000000064 ffffffc00000006e ffffffbf0000003f ffffff800000feff [ 23.021207] bda0: ffffffbffc20b048 ffffffc000a02280 ffffffbffc203730 ffffffc0024000c0 [ 23.021212] bdc0: ffff81a40b300001 0000000000000001 0000000000000000 000000000002f4c8 [ 23.021216] bde0: 000000005a4222a4 0000000000000000 0000000000000000 0000000000000000 [ 23.021220] be00: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 23.021224] be20: 0000007feb928c10 ffffffc000085e30 0000000000000000 0000000000000000 [ 23.021228] be40: ffffffffffffffff ffffffc0000895b0 0000000000000000 ffffff8000995000 [ 23.021232] be60: 000000000002f4c8 ffffff80009c3d08 ffffff80009c3bd8 ffffff80009b66c8 [ 23.021237] be80: 0000000000015730 00000000000194e0 0000000000000000 0000000000000000 [ 23.021241] bea0: 000000000000d6a8 0000001e0000001d 0000000000000017 0000000000000011 [ 23.021245] bec0: 0000000000000014 0000007f966d80f0 0000000000000000 0000000000000014 [ 23.021249] bee0: 0000000000000000 302f2f2f2f753968 0000000000000000 0000000000000000 [ 23.021254] bf00: 0000000000000111 0000007f966969a0 0000007feb927b50 0000000000000003 [ 23.021258] bf20: 0000000000000000 0000000000000000 0000000000000000 0000007f967a6000 [ 23.021262] bf40: 0000007f966ea1d0 0000007f96617ad0 0000007feb9282c8 00000055929a20d0 [ 23.021266] bf60: 0000000000000000 0000007f966d80f0 000000559298f9b0 0000000000020000 [ 23.021271] bf80: 0000000000000000 00000055929948d0 0000000000000000 0000000000020000 [ 23.021275] bfa0: 0000007feb928da0 0000007feb928c10 0000007f966d1980 0000007feb928c10 [ 23.021279] bfc0: 0000007f96617af4 0000000040000000 0000000000000014 0000000000000111 [ 23.021283] bfe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 23.021284] Call trace: [ 23.021349] [<ffffffbffc1efd30>] ath9k_ioread32+0x28/0x78 [ath9k] [ 23.021412] [<ffffffbffc161df0>] ath9k_hw_init+0xc0/0xad8 [ath9k_hw] [ 23.021462] [<ffffffbffc1f07a0>] ath9k_init_device+0x400/0xce0 [ath9k] [ 23.021511] [<ffffffbffc1ff88c>] ath_pci_probe+0x194/0x378 [ath9k] [ 23.021523] [<ffffffc0005fe3b0>] pci_device_probe+0xa0/0x118 [ 23.021530] [<ffffffc0006bfd3c>] driver_probe_device+0x1ec/0x2d8 [ 23.021534] [<ffffffc0006bfec4>] __driver_attach+0x9c/0xa0 [ 23.021540] [<ffffffc0006bdebc>] bus_for_each_dev+0x64/0xa0 [ 23.021544] [<ffffffc0006bf620>] driver_attach+0x20/0x28 [ 23.021547] [<ffffffc0006bf190>] bus_add_driver+0x108/0x228 [ 23.021552] [<ffffffc0006c0678>] driver_register+0x60/0xf8 [ 23.021556] [<ffffffc0005fd1b8>] __pci_register_driver+0x38/0x40 [ 23.021604] [<ffffffbffc1ffbd0>] ath_pci_init+0x18/0x38 [ath9k] [ 23.021652] [<ffffffbffc20b00c>] ath9k_init+0xc/0x48 [ath9k] [ 23.021659] [<ffffffc000082950>] do_one_initcall+0x90/0x1a0 [ 23.021666] [<ffffffc00015f46c>] do_init_module+0x60/0x1ac [ 23.021673] [<ffffffc00012407c>] load_module+0x188c/0x1df0 [ 23.021678] [<ffffffc000124810>] SyS_finit_module+0xb0/0xc0 [ 23.021683] [<ffffffc000085e30>] el0_svc_naked+0x24/0x28 Link to comment Share on other sites More sharing options...
darkdrgn2k Posted February 14, 2018 Author Share Posted February 14, 2018 I did find this http://espressobin.net/forums/reply/1389/ which leads to this https://www.spinics.net/lists/linux-pci/msg64811.html i dont know if those patches made it into the kernel (or which kernel) but it looks like they are superseded anyway!?!? Link to comment Share on other sites More sharing options...
Igor Posted February 14, 2018 Share Posted February 14, 2018 This fix is present at least in NEXT (4.14.y) kernel. Link to comment Share on other sites More sharing options...
darkdrgn2k Posted February 14, 2018 Author Share Posted February 14, 2018 Ah i see, well at least i know its not the PCB board Thanks Seems ExpressoBin is still on 4.4.x guess its a waiting game then! Link to comment Share on other sites More sharing options...
darkdrgn2k Posted March 19, 2018 Author Share Posted March 19, 2018 So im trying another mPCIE-E wireless board on the expressobin nightly. The board does not seem to be initialized properly 00:00.0 Ethernet controller: Qualcomm Atheros Device abcd (rev 01) 00:00.0 0200: 168c:abcd (rev 01) From what i understand 168c:abcd indicates the board was not successfully initialized. Quote The general consensus at work is - BIOSes are buggy and don't necessarily reset the PCI bus correctly. So either you can do your own PCI bus reset post-boot (and re-enumerate all the PCI devices, including initialising their BARs) or smack your vendor to fix their BIOSes. I can't really make any further suggestions besides that. Any idea what this could be? Link to comment Share on other sites More sharing options...
Igor Posted March 19, 2018 Share Posted March 19, 2018 Espressobin mPCI stack is not in a good shape and we have no resources to improve it. If this was not improved with the last u-boot update, then this won't change for a while. I also tested one of the most interesting cards (QCA9880/ath10) ... and it doesn't work. Use cards which we recommend/test. Quote The general consensus at work is - BIOSes are buggy and don't necessarily reset the PCI bus correctly. Development boards do not have BIOS. They have u-boot which take care of this job and that one was updated last week. Link to comment Share on other sites More sharing options...
darkdrgn2k Posted March 20, 2018 Author Share Posted March 20, 2018 I never thought of upgrading uboot. Sadly didnt work but (as expected) is there a way to "reset" the mPCIE Bus as many people suggest? Also out of curiosity is the expressobin not a open source board or is it still contain allot of proprietary components making it hard to port? Link to comment Share on other sites More sharing options...
darkdrgn2k Posted March 20, 2018 Author Share Posted March 20, 2018 Here is the interesting part. I dont know if it matters but it seems that uboot detects the mpcie correctly?!?! lspci shows 00:00.0 0200: 168c:abcd (rev 01) pci init in uboot shows it correct ``` Marvell>> pci init Scanning PCI devices on bus 0 BusDevFun VendorId DeviceId Device Class Sub-Class _____________________________________________________________ 00.00.00 0x168c 0x0030 Network controller 0x80 ``` and ``` Marvell>> pci header 00:00.00 vendor ID = 0x168c device ID = 0x0030 command register ID = 0x0006 status register = 0x0010 revision ID = 0x01 class code = 0x02 (Network controller) sub class code = 0x80 programming interface = 0x00 cache line = 0x08 latency time = 0x00 header type = 0x00 BIST = 0x00 base address 0 = 0xe8000004 base address 1 = 0x00000000 base address 2 = 0x00000000 base address 3 = 0x00000000 base address 4 = 0x00000000 base address 5 = 0x00000000 cardBus CIS pointer = 0x00000000 sub system vendor ID = 0x106b sub system ID = 0x009a expansion ROM base address = 0xe8020000 interrupt line = 0xff interrupt pin = 0x01 min Grant = 0x00 max Latency = 0x00 ``` Link to comment Share on other sites More sharing options...
darkdrgn2k Posted March 20, 2018 Author Share Posted March 20, 2018 More info Using espressobin's build root it seem to be fine Welcome to Buildroot buildroot login: root # lspci 00:00.0 Class 0280: 168c:0030 # Followed instructions here: http://wiki.espressobin.net/tiki-index.php?page=Downloading+image+and+boot+from+SD+card+-+Linux Using Root FS (ext4 parittion) ftp://downloads.globalscaletechnologies.com/Downloads/Espressobin/buildroot_fw/espressobin-rootfs-buildroot-20170718.tar.gz and Kernel (fat32 partition) http://espressobin.net/wp-content/uploads/2017/02/kernel.zip (moved files into root from kernel dir) source seems to be from http://espressobin.net/tech-spec/ Link to comment Share on other sites More sharing options...
Igor Posted March 20, 2018 Share Posted March 20, 2018 4 hours ago, darkdrgn2k said: Using espressobin's build root it seem to be fine We provide two kernels for Espressobin. One is stock (the same as on Buildroot and other stock builds. Only with bugfixes and some 3rd party wireless drivers), while the other is a modern one. Both should work and they do work for me. Which Wireless card do you use and is it actually working on a stock kernel? Can you extract kernel configuration of this image? Edit: If 168c:0030 is AR9380 than it must work with Armbian. I have one around and it works. Probably only with most recent u-boot. Link to comment Share on other sites More sharing options...
darkdrgn2k Posted March 20, 2018 Author Share Posted March 20, 2018 Config and DMESG attached config.gz dmesg EDIT: 450M Atheros AR5BXB112 AR9380 2.4/5GHz Mini PCI-E Wi-Fi Card Link to comment Share on other sites More sharing options...
darkdrgn2k Posted March 20, 2018 Author Share Posted March 20, 2018 Quote We provide two kernels for Espressobin. Do you mean legacy kernel (https://dl.armbian.com/espressobin/Debian_stretch_default.7z) tried that one this morning, no joy on the pci bus. I tried that one and the nightly one. Link to comment Share on other sites More sharing options...
Igor Posted March 20, 2018 Share Posted March 20, 2018 I made a few tests - all those cards are operational on Clearfog with the same (mainline) kernel drivers. 01:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter wlp1s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=14 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off wlp2s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on There are different Espressobins out there so its possible that some card works, some doesn't. Cards can also be little different. Working: Qualcomm Atheros AR928Xhttp://ix.io/101m Qualcomm Atheros QCA9565http://ix.io/101s Not working: Detected but crashing Qualcomm Atheros AR93xx (9382/ar5bhb116) legacy: http://ix.io/101u mainline: http://ix.io/101G Undetected properly Qualcomm Atheros AR9380 (9380/ar5bxb112) Undetected at all QCA9880 AC Link to comment Share on other sites More sharing options...
darkdrgn2k Posted March 20, 2018 Author Share Posted March 20, 2018 So the board i got apparently is original designed for Apple. https://wikidevi.com/wiki/Atheros_AR5BXB112 Its strange that it works on espressobin's buildroot but not espresso bin. (i use works loosly as i have note tested the drivers yet.. just enumarated correctly in lspci) Any idea why it would work on one but not the other? Link to comment Share on other sites More sharing options...
Igor Posted March 20, 2018 Share Posted March 20, 2018 3 hours ago, darkdrgn2k said: So the board i got apparently is original designed for Apple. Yes. The same as mine. (last picture) 3 hours ago, darkdrgn2k said: Its strange that it works on espressobin's buildroot but not espresso bin I am monitoring the development on various platforms and all had/have troubles in PCI implementation. The firstwith mPCI was Hummingboard 1 (imx6). Solidrun needed months to a year to bring it up on their legacy 3.14.y back then, then they changed the kernel for more recent "upstream" Freescale 3.14.y and mPCI was never fully operational again. We kept original 3.14.y where mPCI works fine. Also on Hummingboard 2. Then, on the latest mainline kernel 4.15.y, it also works fine. Even ath10 cards work. The situation with Clearfog was little better but only with second BSP package, when they moved to kernel 4.4.y ... the initial kernel was 3.10.y. And now with mainline where only a few things are missing. Then we have first Allwinner H6 mPCI which is ... broken. I have no experiences with Bananapi R2 (MT7623) mPCI implementation. 3 hours ago, darkdrgn2k said: Any idea why it would work on one but not the other? Random behavior can be a sign that implementation is broken. From my perspective and from what I know I can't say anything else than it is broken. If I would know why and where I would fix it. What can you do? Press on Globalscale/Marvell to put more efforts in fixing this. Link to comment Share on other sites More sharing options...
darkdrgn2k Posted March 20, 2018 Author Share Posted March 20, 2018 Awsome thanks as always !!!! i bought two cards and to expresso bins.. ill try to mix and mach and see what happens! Link to comment Share on other sites More sharing options...
hjc Posted March 22, 2018 Share Posted March 22, 2018 Are there any 802.11ac cards that can be confirmed working? I'm interested in building a wireless router with this board (Dual band, 3x3 or 4x4 is ideal), but based on what is mentioned above, it seems to be impossible now? Link to comment Share on other sites More sharing options...
Igor Posted March 22, 2018 Share Posted March 22, 2018 2 hours ago, firecb said: Are there any 802.11ac cards that can be confirmed working? Nope. The only good and operational are ath10 based cards and they are not recognized on this board, but they work on those: https://www.armbian.com/clearfog-base/ https://www.armbian.com/clearfog/ But you can use USB3 based AC cards. They work fine on mainline kernel: http://amzn.to/2jvV8q1 Link to comment Share on other sites More sharing options...
umiddelb Posted March 22, 2018 Share Posted March 22, 2018 4 hours ago, firecb said: Are there any 802.11ac cards that can be confirmed working? Intel Dual Band Wireless AC 7260 with mainline kernel. Link to comment Share on other sites More sharing options...
Igor Posted March 22, 2018 Share Posted March 22, 2018 24 minutes ago, umiddelb said: Intel Dual Band Wireless AC 7260 with mainline kernel. ... which AFAIK doesn't support AP at 5Ghz. Link to comment Share on other sites More sharing options...
umiddelb Posted March 23, 2018 Share Posted March 23, 2018 ubuntu@ebin:~$ iw list Wiphy phy0 max # scan SSIDs: 20 max scan IEs length: 425 bytes Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Device supports AP-side u-APSD. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP (00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP * AP/VLAN * monitor * P2P-client * P2P-GO * P2P-device Band 1: Capabilities: 0x11ee HT20/HT40 SM Power Save disabled RX HT20 SGI RX HT40 SGI TX STBC RX STBC 1-stream Max AMSDU length: 3839 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 4 usec (0x05) HT TX/RX MCS rate indexes supported: 0-15 Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps (short preamble supported) * 5.5 Mbps (short preamble supported) * 11.0 Mbps (short preamble supported) * 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] (22.0 dBm) * 2417 MHz [2] (22.0 dBm) * 2422 MHz [3] (22.0 dBm) * 2427 MHz [4] (22.0 dBm) * 2432 MHz [5] (22.0 dBm) * 2437 MHz [6] (22.0 dBm) * 2442 MHz [7] (22.0 dBm) * 2447 MHz [8] (22.0 dBm) * 2452 MHz [9] (22.0 dBm) * 2457 MHz [10] (22.0 dBm) * 2462 MHz [11] (22.0 dBm) * 2467 MHz [12] (22.0 dBm) (no IR) * 2472 MHz [13] (22.0 dBm) (no IR) Band 2: Capabilities: 0x11ee HT20/HT40 SM Power Save disabled RX HT20 SGI RX HT40 SGI TX STBC RX STBC 1-stream Max AMSDU length: 3839 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 4 usec (0x05) HT TX/RX MCS rate indexes supported: 0-15 VHT Capabilities (0x038071a0): Max MPDU length: 3895 Supported Channel Width: neither 160 nor 80+80 short GI (80 MHz) TX STBC SU Beamformee VHT RX MCS set: 1 streams: MCS 0-9 2 streams: MCS 0-9 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT RX highest supported: 0 Mbps VHT TX MCS set: 1 streams: MCS 0-9 2 streams: MCS 0-9 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT TX highest supported: 0 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: * 5180 MHz [36] (22.0 dBm) (no IR) * 5200 MHz [40] (22.0 dBm) (no IR) * 5220 MHz [44] (22.0 dBm) (no IR) * 5240 MHz [48] (22.0 dBm) (no IR) * 5260 MHz [52] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5280 MHz [56] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5300 MHz [60] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5320 MHz [64] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5500 MHz [100] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5520 MHz [104] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5540 MHz [108] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5560 MHz [112] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5580 MHz [116] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5600 MHz [120] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5620 MHz [124] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5640 MHz [128] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5660 MHz [132] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5680 MHz [136] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5700 MHz [140] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5720 MHz [144] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 324748 sec) DFS CAC time: 0 ms * 5745 MHz [149] (22.0 dBm) (no IR) * 5765 MHz [153] (22.0 dBm) (no IR) * 5785 MHz [157] (22.0 dBm) (no IR) * 5805 MHz [161] (22.0 dBm) (no IR) * 5825 MHz [165] (22.0 dBm) (no IR) Supported commands: * new_interface * set_interface * new_key * start_ap * new_station * new_mpath * set_mesh_config * set_bss * authenticate * associate * deauthenticate * disassociate * join_ibss * join_mesh * remain_on_channel * set_tx_bitrate_mask * frame * frame_wait_cancel * set_wiphy_netns * set_channel * set_wds_peer * start_sched_scan * probe_client * set_noack_map * register_beacons * start_p2p_device * set_mcast_rate * connect * disconnect * channel_switch * Unknown command (104) * Unknown command (105) * Unknown command (121) 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 * mesh point: 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 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0x40 0xb0 0xc0 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * mesh point: 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-device: 0x40 0xd0 WoWLAN support: * wake up on disconnect * wake up on magic packet * wake up on pattern match, up to 20 patterns of 16-128 bytes, maximum packet offset 0 bytes * can do GTK rekeying * wake up on GTK rekey failure * wake up on EAP identity request * wake up on 4-way handshake * wake up on rfkill release software interface modes (can always be added): * AP/VLAN * monitor valid interface combinations: * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1, total <= 3, #channels <= 2 HT Capability overrides: * MCS: ff ff ff ff ff ff ff ff ff ff * maximum A-MSDU length * supported channel width * short GI for 40 MHz * max A-MPDU length exponent * min MPDU start spacing Device supports TX status socket option. Device supports HT-IBSS. Device supports SAE with AUTHENTICATE command Device supports low priority scan. Device supports scan flush. Device supports per-vif TX power setting P2P GO supports CT window setting P2P GO supports opportunistic powersave setting Driver supports full state transitions for AP/GO clients Driver supports a userspace MPM Driver/device bandwidth changes during BSS lifetime (AP/GO mode) Device supports static SMPS Device supports dynamic SMPS There is indeed support for the 5 GHz band and the card is supposed to bc 802.11ac compliant. Link to comment Share on other sites More sharing options...
Igor Posted March 23, 2018 Share Posted March 23, 2018 50 minutes ago, umiddelb said: There is indeed support for the 5 GHz band and the card is supposed to bc 802.11ac compliant. I use this card in my notebook and it's a great performer when it comes to STA but I could not establish AP mode. Neither they did. It looks like firmware restriction. Link to comment Share on other sites More sharing options...
hjc Posted March 23, 2018 Share Posted March 23, 2018 14 hours ago, Igor said: The only good and operational are ath10 based cards and they are not recognized on this board I saw someone mentioned here that ath10k works after patching the kernel, is that worth a try? Link to comment Share on other sites More sharing options...
Igor Posted March 23, 2018 Share Posted March 23, 2018 3 minutes ago, firecb said: I saw someone mentioned here that ath10k works after patching the kernel, is that worth a try? I haven't notice that. Yes, it's worth trying. Link to comment Share on other sites More sharing options...
umiddelb Posted March 23, 2018 Share Posted March 23, 2018 5 hours ago, Igor said: I use this card in my notebook and it's a great performer when it comes to STA but I could not establish AP mode. Neither they did. It looks like firmware restriction. Have you tried it it with `driver=nl80211´ in `/etc/hostapd/hostapd.conf´ ? Link to comment Share on other sites More sharing options...
umiddelb Posted March 23, 2018 Share Posted March 23, 2018 I see, the access point broadcasts at 2.4 GHz only. Link to comment Share on other sites More sharing options...
hjc Posted March 27, 2018 Share Posted March 27, 2018 On 3/23/2018 at 4:40 PM, Igor said: I haven't notice that. Yes, it's worth trying. Well, I tried a QCA9994 card and it worked on Armbian without any kernel patch, if the correct firmware is loaded. (Debian firmware-atheros package is out-dated and does not support the card I use) Link to comment Share on other sites More sharing options...
Recommended Posts