Home Forums Hardware discussions Which PCIe wlan cards are supported?

This topic contains 66 replies, has 10 voices, and was last updated by  armbian 2 months, 3 weeks ago.

Viewing 15 posts - 16 through 30 (of 67 total)
  • Author
    Posts
  • #1051

    Boris
    Participant

    Do you see your card in the U-Boot shell ?

    NOTICE: Booting Trusted Firmware
    NOTICE: BL1: v1.3(release):armada-17.06.2:
    NOTICE: BL1: Built : 16:41:24, Jul 7 2
    NOTICE: BL2: v1.3(release):armada-17.06.2:
    NOTICE: BL2: Built : 16:41:26, Jul 7 2017
    NOTICE: BL31: v1.3(release):armada-17.06.2:
    NOTICE: BL31:

    U-Boot 2017.03-armada-17.06.3 (Aug 04 2017 – 14:23:22 +0200)

    Model: Marvell Armada 3720 Community Board ESPRESSOBin
    CPU @ 1000 [MHz]
    L2 @ 800 [MHz]
    TClock @ 200 [MHz]
    DDR @ 800 [MHz]
    DRAM: 1 GiB
    U-Boot DComphy-0: USB3 5 Gbps
    Comphy-1: PEX0 2.5 Gbps
    Comphy-2: SATA0 6 Gbps
    SATA link 0 timeout.
    AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
    flags: ncq led only pmp fbss pio slum part sxs
    PCIE-0: Link up
    MMC: sdhci@d0000: 0
    SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB
    Net: eth0: neta@30000
    Hit any key to stop autoboot: 0
    Marvell>> pci
    Scanning PCI devices on bus 0
    BusDevFun VendorId DeviceId Device Class Sub-Class
    _____________________________________________________________
    00.00.00 0x168c 0x003c Network controller 0x80
    Marvell>>

    #1052

    adamierymenko
    Participant

    Tried building the driver into the kernel instead of building as a module. Still doesn’t detect the card.

    #1053

    adamierymenko
    Participant
    #1054

    armbian
    Participant

    Tried building the driver into the kernel instead of building as a module. Still doesn’t detect the card.

    I have the same card and it also does not work. It looks like you need to recompile and update u-boot, but haven’t got time to try out.

    #1055

    adamierymenko
    Participant

    Marvell>> pci
    Scanning PCI devices on bus 0
    BusDevFun VendorId DeviceId Device Class Sub-Class
    _____________________________________________________________
    Non-posted PIO Response Status: CA, 0xe00 @ 0x0

    That doesn’t look good. Maybe there’s some issue with these cards?

    #1056

    adamierymenko
    Participant

    Looks related: http://espressobin.net/forums/topic/non-posted-pio-response-status-at-uboot/

    Is it possible to upgrade firmware on this thing perhaps?

    #1058

    adamierymenko
    Participant
    #1076

    adamierymenko
    Participant

    See the other thread. It seems the firmware the board ships with has very broken pci-e support and upgrading the firmware is a rather awful process. So far I’ve been unsuccessful.

    #1389

    crazy4chrissi
    Participant

    Hi guys,

    I am trying to get a Dell Wireless-DW1901 mini PCIe with an Atheros AR5B22 (ath9k driver) running.
    I tried Arch Linux with the latest kernel from the repository (4.14.7-1-ARCH #1 SMP Sun Dec 17 18:01:07 MST 2017 aarch64 GNU/Linux).
    It boots up, but the ath9k driver fails with request_irq failed:

    [ 8.271159] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x3c
    [ 8.278588] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x44
    [ 8.286378] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x4
    [ 8.293950] ath9k 0000:00:00.0: enabling device (0000 -> 0002)
    [ 8.300357] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x3c
    [ 8.307952] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0xc
    [ 8.315594] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x4
    [ 8.323227] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x40
    [ 8.331167] ath9k 0000:00:00.0: request_irq failed
    [ 8.335917] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @

    This is lspci:

    [root@alarm ~]# lspci
    [ 5719.645250] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x0
    [ 5719.652836] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x4
    [ 5719.660133] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x8
    [ 5719.668000] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0xc
    [ 5719.675680] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x10
    [ 5719.683368] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x14
    [ 5719.691214] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x18
    [ 5719.698850] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x1c
    [ 5719.706681] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x20
    [ 5719.714341] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x24
    [ 5719.722073] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x28
    [ 5719.729616] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x2c
    [ 5719.737566] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x30
    [ 5719.745222] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x34
    [ 5719.753122] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x38
    [ 5719.760619] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x3c
    00:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter

    This is the u boot pci output:

    Marvell>> pci
    Scanning PCI devices on bus 0
    BusDevFun VendorId DeviceId Device Class Sub-Class
    _____________________________________________________________
    00.00.00 0x168c 0x0034 Network controller 0x80

    Any ideas? I guess I am going to try Armbian next.

    I also found this:
    https://www.spinics.net/lists/linux-pci/msg64811.html
    Seems to be the same problem. But the patch mentioned there should already be in the kernel I am using….

    Problem is I need a card that can inject frames in monitor mode. So it does not help if some card works.
    Can everybody with a working card post the output of “iw list” so everybody knows what these cards support? This would be great!

    Greetings,
    Christopher

    #1390

    crazy4chrissi
    Participant

    Now tested Armbian “mainline kernel” (4.14.2-mvebu64 #6 SMP PREEMPT Fri Nov 24 19:22:00 CET 2017 aarch64 GNU/Linux) with the Dell Wireless-DW1901 mini PCIe with an Atheros AR5B22 (ath9k driver).

    Problem is more or less the same except that lspci does not print any errors. In dmesg, the same errors as on Arch Linux appear.

    I guess I am going to give the Armbian Legacy kernel a try, as the armbian espressobin page says they tested AR5BXB92 with the legacy kernel.

    Edit: Tried the Armbian legacy kernel (Linux espressobin 4.4.102-mvebu64 #3 SMP PREEMPT Fri Nov 24 18:31:22 CET 2017 aarch64 GNU/Linux).
    Does not work. From /var/log/kernel.log :

    Nov 25 00:34:28 localhost kernel: [ 13.257890] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x44
    PIO Response Status: CA, 0xe00 @ 0x4
    Nov 25 00:34:28 localhost kernel: [ 13.258014] ath9k 0000:00:00.0: enabling device (0000 -> 0002)
    Nov 25 00:34:28 localhost kernel: [ 13.258075] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x3c
    Nov 25 00:34:28 localhost kernel: [ 13.258126] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0xc
    Nov 25 00:34:28 localhost kernel: [ 13.258190] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x4
    Nov 25 00:34:28 localhost kernel: [ 13.258245] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0x40
    Nov 25 00:34:28 localhost kernel: [ 13.259241] advk-pcie d0070000.pcie: Posted PIO Response Status: CA, 0xe00 @ 0xc
    Nov 25 00:34:28 localhost kernel: [ 13.259297] Unhandled fault: synchronous external abort (0x96000010) at 0xffffff8000704020
    Nov 25 00:34:28 localhost kernel: [ 13.318660] Internal error: : 96000010 [#1] PREEMPT SMP
    Nov 25 00:34:28 localhost kernel: [ 13.324201] Modules linked in: ath9k(+) ath9k_common ath9k_hw ath mac80211 cfg80211 rfkill ip_tables x_tables
    Nov 25 00:34:28 localhost kernel: [ 13.334699] CPU: 0 PID: 268 Comm: systemd-udevd Not tainted 4.4.102-mvebu64 #3
    Nov 25 00:34:28 localhost kernel: [ 13.342218] Hardware name: Marvell Armada 3720 Community Board (DT)
    Nov 25 00:34:28 localhost kernel: [ 13.348888] task: ffffffc076db2280 ti: ffffffc076d7c000 task.ti: ffffffc076d7c000
    Nov 25 00:34:28 localhost kernel: [ 13.357050] PC is at ath9k_ioread32+0x28/0x78 [ath9k]
    Nov 25 00:34:28 localhost kernel: [ 13.362679] LR is at ath9k_hw_init+0xc0/0xad8 [ath9k_hw]
    Nov 25 00:34:28 localhost kernel: [ 13.368203] pc : [<ffffffbffc1b6d30>] lr : [<ffffffbffc128df0>] pstate: 80000145
    Nov 25 00:34:28 localhost kernel: [ 13.375962] sp : ffffffc076d7f900
    Nov 25 00:34:28 localhost kernel: [ 13.379528] x29: ffffffc076d7f900 x28: ffffffc0754fc068
    Nov 25 00:34:28 localhost kernel: [ 13.385134] x27: ffffffbffc1c9f60 x26: ffffffc076f57420
    Nov 25 00:34:28 localhost kernel: [ 13.390746] x25: ffffffbffc1ca700 x24: 0000000000000000
    Nov 25 00:34:28 localhost kernel: [ 13.396349] x23: ffffffc0754fc068 x22: ffffffc0754fc068
    Nov 25 00:34:28 localhost kernel: [ 13.401949] x21: ffffffc076f546e0 x20: ffffffc076f55420
    Nov 25 00:34:28 localhost kernel: [ 13.407557] x19: ffffff8000700000 x18: 0000000000000000
    Nov 25 00:34:28 localhost kernel: [ 13.413166] x17: 0000000000000001 x16: 0000000000000007
    […]
    Nov 25 00:39:55 localhost kernel: [ 16.044321] Call trace:
    Nov 25 00:39:55 localhost kernel: [ 16.047179] [<ffffffbffc1ebd30>] ath9k_ioread32+0x28/0x78 [ath9k]
    Nov 25 00:39:55 localhost kernel: [ 16.053875] [<ffffffbffc15ddf0>] ath9k_hw_init+0xc0/0xad8 [ath9k_hw]
    Nov 25 00:39:55 localhost kernel: [ 16.060751] [<ffffffbffc1ec7a0>] ath9k_init_device+0x400/0xce0 [ath9k]
    Nov 25 00:39:55 localhost kernel: [ 16.067813] [<ffffffbffc1fb88c>] ath_pci_probe+0x194/0x378 [ath9k]
    Nov 25 00:39:55 localhost kernel: [ 16.074303] [<ffffffc0005fe2a0>] pci_device_probe+0xa0/0x118
    Nov 25 00:39:55 localhost kernel: [ 16.080205] [<ffffffc0006bfb94>] driver_probe_device+0x1ec/0x2d8
    Nov 25 00:39:55 localhost kernel: [ 16.086506] [<ffffffc0006bfd1c>] __driver_attach+0x9c/0xa0
    Nov 25 00:39:55 localhost kernel: [ 16.092393] [<ffffffc0006bdd14>] bus_for_each_dev+0x64/0xa0
    Nov 25 00:39:55 localhost kernel: [ 16.098334] [<ffffffc0006bf478>] driver_attach+0x20/0x28
    Nov 25 00:39:55 localhost kernel: [ 16.103867] [<ffffffc0006befe8>] bus_add_driver+0x108/0x228
    Nov 25 00:39:55 localhost kernel: [ 16.109782] [<ffffffc0006c04d0>] driver_register+0x60/0xf8
    Nov 25 00:39:55 localhost kernel: [ 16.115612] [<ffffffc0005fd0a8>] __pci_register_driver+0x38/0x40
    Nov 25 00:39:55 localhost kernel: [ 16.122240] [<ffffffbffc1fbbd0>] ath_pci_init+0x18/0x38 [ath9k]
    Nov 25 00:39:55 localhost kernel: [ 16.128734] [<ffffffbffc20700c>] ath9k_init+0xc/0x48 [ath9k]
    Nov 25 00:39:55 localhost kernel: [ 16.134766] [<ffffffc000082950>] do_one_initcall+0x90/0x1a0
    Nov 25 00:39:55 localhost kernel: [ 16.140665] [<ffffffc00015f4ec>] do_init_module+0x60/0x1ac
    Nov 25 00:39:55 localhost kernel: [ 16.146500] [<ffffffc0001240fc>] load_module+0x188c/0x1df0
    Nov 25 00:39:55 localhost kernel: [ 16.152224] [<ffffffc000124890>] SyS_finit_module+0xb0/0xc0
    Nov 25 00:39:55 localhost kernel: [ 16.158145] [<ffffffc000085e8c>] __sys_trace_return+0x0/0x4
    Nov 25 00:39:55 localhost kernel: [ 16.164021] Code: 7100045f 54000160 f944fe93 8b214261 (b9400033)
    Nov 25 00:39:55 localhost kernel: [ 16.403579] —[ end trace f3e95249dbf0ddde ]—

    #1391

    ebin-dev
    Participant

    Did you flash your board to the latest u-boot ?

    #1393

    crazy4chrissi
    Participant

    Yes, as the armbian instructions say, I flashed it with this one.
    Booting it was a bit difficult, the armbian page does not give any instructions how to set up the u-boot environment and the defaults would not work. I came up with an environment that boots based on the one included in Arch for the Espressobin.

    #1763

    crazy4chrissi
    Participant

    Atheros QCWB335 works with current Arch Linux for Espressobin 🙂
    Also monitor mode works with this card.
    Atheros AR5B22 still does not work.

    #2151

    Xogium
    Participant

    Hi,
    I’ve decided to write in this topic in hope of getting some answers before I buy a new wireless card for my ebin.

    The marvell one I got when I bought my rev5 espressobin is having a driver bug since linux 4.13.x, thus forcing me to stay on kernel 4.12.12 to get it working, which is not acceptable to me because this kernel is long dead, slightly more than a year by now, and I wish to go on kernel 4.18+. So I’ve looked at this topic and found that an atheros 9565 aka qcwb335 was supported. However this was probably on an earlier revision of the board since this card seems to be half-size — https://www.newegg.ca/Product/Product.aspx?Item=9SIAFJX7S44637&cm_re=wifi_minipcie-_-9SIAFJX7S44637-_-Product

    So, two main questions:

    1. Is this card still known to perform well on this board, as an AP ?
    2. Would a half-size to full-size minipcie adapter make it fit in a rev5 of the ebin ?
    Thank you a lot, any help is appreciated.

    #2152

    crazy4chrissi
    Participant

    Hi,

    regarding 1: The atheros qcwb335 works for me. My board says “V5_0_1”. Is this what you mean with rev5? Mine also has a full-size mini pcie slot.

    regarding 2: Most cards nowadays are half-size. I have been using an half-size to full-size adapter in the espressobin and the qcwb335 without problems. I am using this adapter: https://www.ebay.de/itm/172618382710
    There are dozens of cheap ones on ebay.

    I have not using the board a lot lately. But when I checked last, it ran with the latest Arch Linux, so it probably had a rather new kernel.

    I still have some problems with the espressobin:
    – Sometimes, it does not detect the pcie-card when rebooting. So I need to reboot again.
    – Sometimes it gets stuck on reboot on the bootloader and I have to reboot it with the reset-switch. This is really bad as it means remote reboots are not possible (reliably).
    – The cpu is a little slow for me. “The Armada 88F3700 currently supports 1GHz CPU clock speed. Support for 1.2GHz will be ready soon.” The FAQ says this for a long time now. With only two cores and 1 GHz it is significantly slower than a Rasperry Pi3 for example, which runs 4 cores with up to 1.2 GHz.
    These are the main reasons why we are searching for a new hardware platform.

    Greetings,
    Christopher

Viewing 15 posts - 16 through 30 (of 67 total)

You must be logged in to reply to this topic.

Signup to our newsletter

Technical specification tables can not be displayed on mobile. Please view on desktop