* compex wle900vx (ath10k) problem on 4.4.24 / armv7 [not found] <b61ccf3c-1861-c8f8-ff7d-91c2b6ff4df5@gmail.com> @ 2016-10-15 14:00 ` Oliver Zemann 2016-10-15 14:44 ` Sebastian Gottschall 0 siblings, 1 reply; 18+ messages in thread From: Oliver Zemann @ 2016-10-15 14:00 UTC (permalink / raw) To: linux-wireless I have a clearfog pro (arm7) from marvel and bought a pcie wifi card. Unfortunately, it does not work. I am not sure if this is a bug in the module or even in some pci-e driver. Maybe someone could tell me that. dmesg: [ 5.348307] mvebu-pcie soc:pcie-controller: /soc/pcie-controller/pcie@2,0: reset gpio is active low [ 5.358026] mvebu-pcie soc:pcie-controller: /soc/pcie-controller/pcie@3,0: reset gpio is active low [ 5.421496] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 0000:00 [ 5.428390] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 5.434680] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff] [ 5.441575] pci_bus 0000:00: root bus resource [bus 00-ff] [ 5.447083] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400 [ 5.447198] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400 [ 5.447295] PCI: bus0: Fast back to back transfers disabled [ 5.452887] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 5.460911] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 5.468986] PCI: bus1: Fast back to back transfers enabled [ 5.474491] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 5.474561] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000 [ 5.474593] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit] [ 5.474617] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref] [ 5.474667] pci 0000:02:00.0: supports D1 D2 [ 5.511395] PCI: bus2: Fast back to back transfers enabled [ 5.516894] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02 [ 5.516905] pci 0000:02:00.0: of_irq_parse_pci() failed with rc=134 [ 5.523207] pci 0000:00:03.0: BAR 14: assigned [mem 0xf8000000-0xf82fffff] [ 5.530098] pci 0000:00:02.0: PCI bridge to [bus 01] [ 5.535082] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8000000-0xf81fffff 64bit] [ 5.542413] pci 0000:02:00.0: BAR 0: error updating (0xf8000004 != 0xffffffff) [ 5.549652] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff) [ 5.557155] pci 0000:02:00.0: BAR 6: assigned [mem 0xf8200000-0xf820ffff pref] [ 5.564396] pci 0000:00:03.0: PCI bridge to [bus 02] [ 5.569372] pci 0000:00:03.0: bridge window [mem 0xf8000000-0xf82fffff] [ 5.576256] pcieport 0000:00:03.0: enabling device (0140 -> 0142) lspci: [root@alarm alarm]# lspci 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter (rev ff) Thanks! ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-15 14:00 ` compex wle900vx (ath10k) problem on 4.4.24 / armv7 Oliver Zemann @ 2016-10-15 14:44 ` Sebastian Gottschall 2016-10-15 17:04 ` Oliver Zemann 0 siblings, 1 reply; 18+ messages in thread From: Sebastian Gottschall @ 2016-10-15 14:44 UTC (permalink / raw) To: Oliver Zemann, linux-wireless could you please attach a full log? i see no driver loading here. this is just a small part of the kernel boot log, but no driver intialisation Am 15.10.2016 um 16:00 schrieb Oliver Zemann: > I have a clearfog pro (arm7) from marvel and bought a pcie wifi card. > Unfortunately, it does not work. > I am not sure if this is a bug in the module or even in some pci-e > driver. Maybe someone could tell me that. > > dmesg: > > [ 5.348307] mvebu-pcie soc:pcie-controller: > /soc/pcie-controller/pcie@2,0: reset gpio is active low > [ 5.358026] mvebu-pcie soc:pcie-controller: > /soc/pcie-controller/pcie@3,0: reset gpio is active low > [ 5.421496] mvebu-pcie soc:pcie-controller: PCI host bridge to bus > 0000:00 > [ 5.428390] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] > [ 5.434680] pci_bus 0000:00: root bus resource [mem > 0xf8000000-0xffdfffff] > [ 5.441575] pci_bus 0000:00: root bus resource [bus 00-ff] > [ 5.447083] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400 > [ 5.447198] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400 > [ 5.447295] PCI: bus0: Fast back to back transfers disabled > [ 5.452887] pci 0000:00:02.0: bridge configuration invalid ([bus > 00-00]), reconfiguring > [ 5.460911] pci 0000:00:03.0: bridge configuration invalid ([bus > 00-00]), reconfiguring > [ 5.468986] PCI: bus1: Fast back to back transfers enabled > [ 5.474491] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 > [ 5.474561] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000 > [ 5.474593] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit] > [ 5.474617] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref] > [ 5.474667] pci 0000:02:00.0: supports D1 D2 > [ 5.511395] PCI: bus2: Fast back to back transfers enabled > [ 5.516894] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02 > [ 5.516905] pci 0000:02:00.0: of_irq_parse_pci() failed with rc=134 > [ 5.523207] pci 0000:00:03.0: BAR 14: assigned [mem > 0xf8000000-0xf82fffff] > [ 5.530098] pci 0000:00:02.0: PCI bridge to [bus 01] > [ 5.535082] pci 0000:02:00.0: BAR 0: assigned [mem > 0xf8000000-0xf81fffff 64bit] > [ 5.542413] pci 0000:02:00.0: BAR 0: error updating (0xf8000004 != > 0xffffffff) > [ 5.549652] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 != > 0xffffffff) > [ 5.557155] pci 0000:02:00.0: BAR 6: assigned [mem > 0xf8200000-0xf820ffff pref] > [ 5.564396] pci 0000:00:03.0: PCI bridge to [bus 02] > [ 5.569372] pci 0000:00:03.0: bridge window [mem 0xf8000000-0xf82fffff] > [ 5.576256] pcieport 0000:00:03.0: enabling device (0140 -> 0142) > > lspci: > > > [root@alarm alarm]# lspci > 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) > 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) > 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac > Wireless Network Adapter (rev ff) > > Thanks! > > -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Berliner Ring 101, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.dd-wrt.com email: s.gottschall@dd-wrt.com Tel.: +496251-582650 / Fax: +496251-5826565 ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-15 14:44 ` Sebastian Gottschall @ 2016-10-15 17:04 ` Oliver Zemann 2016-10-18 16:22 ` Intel 7260 not working " Oliver Zemann 2016-10-21 16:25 ` compex wle900vx (ath10k) problem " Oliver Zemann 0 siblings, 2 replies; 18+ messages in thread From: Oliver Zemann @ 2016-10-15 17:04 UTC (permalink / raw) To: linux-wireless I hope thats what you mean. I am not that familiar with linux drivers [root@alarm ~]# lsmod Module Size Used by ath10k_pci 30053 0 ath10k_core 193491 1 ath10k_pci ath 18176 1 ath10k_core mac80211 405739 1 ath10k_core cfg80211 215848 3 ath,mac80211,ath10k_core rfkill 14391 2 cfg80211 marvell_cesa 25839 0 des_generic 16747 1 marvell_cesa sch_fq_codel 7757 9 ip_tables 11170 0 x_tables 11520 1 ip_tables autofs4 22783 2 [root@alarm ~]# rmmod ath10k_pci ath10k_core [root@alarm ~]# modprobe ath10k_core [root@alarm ~]# modprobe ath10k_pci [28501.637198] ath10k_pci 0000:02:00.0: Refused to change power state, currently in D3 [28501.675138] ath10k_pci 0000:02:00.0: failed to wake up device : -110 [28501.681625] ath10k_pci: probe of 0000:02:00.0 failed with error -110 Am 15.10.2016 um 16:44 schrieb Sebastian Gottschall: > could you please attach a full log? i see no driver loading here. this > is just a small part of the kernel boot log, but no driver intialisation > > Am 15.10.2016 um 16:00 schrieb Oliver Zemann: >> I have a clearfog pro (arm7) from marvel and bought a pcie wifi card. >> Unfortunately, it does not work. >> I am not sure if this is a bug in the module or even in some pci-e >> driver. Maybe someone could tell me that. >> >> dmesg: >> >> [ 5.348307] mvebu-pcie soc:pcie-controller: >> /soc/pcie-controller/pcie@2,0: reset gpio is active low >> [ 5.358026] mvebu-pcie soc:pcie-controller: >> /soc/pcie-controller/pcie@3,0: reset gpio is active low >> [ 5.421496] mvebu-pcie soc:pcie-controller: PCI host bridge to bus >> 0000:00 >> [ 5.428390] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] >> [ 5.434680] pci_bus 0000:00: root bus resource [mem >> 0xf8000000-0xffdfffff] >> [ 5.441575] pci_bus 0000:00: root bus resource [bus 00-ff] >> [ 5.447083] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400 >> [ 5.447198] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400 >> [ 5.447295] PCI: bus0: Fast back to back transfers disabled >> [ 5.452887] pci 0000:00:02.0: bridge configuration invalid ([bus >> 00-00]), reconfiguring >> [ 5.460911] pci 0000:00:03.0: bridge configuration invalid ([bus >> 00-00]), reconfiguring >> [ 5.468986] PCI: bus1: Fast back to back transfers enabled >> [ 5.474491] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 >> [ 5.474561] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000 >> [ 5.474593] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff >> 64bit] >> [ 5.474617] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref] >> [ 5.474667] pci 0000:02:00.0: supports D1 D2 >> [ 5.511395] PCI: bus2: Fast back to back transfers enabled >> [ 5.516894] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02 >> [ 5.516905] pci 0000:02:00.0: of_irq_parse_pci() failed with rc=134 >> [ 5.523207] pci 0000:00:03.0: BAR 14: assigned [mem >> 0xf8000000-0xf82fffff] >> [ 5.530098] pci 0000:00:02.0: PCI bridge to [bus 01] >> [ 5.535082] pci 0000:02:00.0: BAR 0: assigned [mem >> 0xf8000000-0xf81fffff 64bit] >> [ 5.542413] pci 0000:02:00.0: BAR 0: error updating (0xf8000004 != >> 0xffffffff) >> [ 5.549652] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 != >> 0xffffffff) >> [ 5.557155] pci 0000:02:00.0: BAR 6: assigned [mem >> 0xf8200000-0xf820ffff pref] >> [ 5.564396] pci 0000:00:03.0: PCI bridge to [bus 02] >> [ 5.569372] pci 0000:00:03.0: bridge window [mem 0xf8000000-0xf82fffff] >> [ 5.576256] pcieport 0000:00:03.0: enabling device (0140 -> 0142) >> >> lspci: >> >> >> [root@alarm alarm]# lspci >> 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) >> 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) >> 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac >> Wireless Network Adapter (rev ff) > >> >> Thanks! >> >> > > ^ permalink raw reply [flat|nested] 18+ messages in thread
* Intel 7260 not working on 4.4.24 / armv7 2016-10-15 17:04 ` Oliver Zemann @ 2016-10-18 16:22 ` Oliver Zemann 2016-10-18 19:06 ` Johannes Berg 2016-10-18 19:30 ` Emmanuel Grumbach 2016-10-21 16:25 ` compex wle900vx (ath10k) problem " Oliver Zemann 1 sibling, 2 replies; 18+ messages in thread From: Oliver Zemann @ 2016-10-18 16:22 UTC (permalink / raw) To: linux-wireless Because of the problems with the ath10 card, i bought an intel 7260 (mpcie) wifi card. Unfortunately it is also not working. I get tons of those messages: [ 175.777030] usb 1-1: new full-speed USB device number 2 using orion-ehci [ 175.933953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 175.940681] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 175.966954] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 175.973313] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 176.183954] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 176.749831] usb 1-1: USB disconnect, device number 2 [ 177.076993] usb 1-1: new full-speed USB device number 3 using orion-ehci [ 177.233953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 177.240682] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 177.266957] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 177.273316] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 177.482955] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 178.046910] usb 1-1: USB disconnect, device number 3 [ 178.376958] usb 1-1: new full-speed USB device number 4 using orion-ehci [ 178.533954] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 178.540682] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 178.566973] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 178.573315] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 178.782953] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 179.356044] usb 1-1: USB disconnect, device number 4 [ 179.686915] usb 1-1: new full-speed USB device number 5 using orion-ehci [ 179.842952] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 179.849680] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 179.878956] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 179.885298] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 180.094953] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 180.650673] usb 1-1: USB disconnect, device number 5 [ 180.976877] usb 1-1: new full-speed USB device number 6 using orion-ehci [ 181.132954] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 181.139682] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 181.165957] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 181.172311] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 181.381955] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 181.950509] usb 1-1: USB disconnect, device number 6 [ 182.276841] usb 1-1: new full-speed USB device number 7 using orion-ehci [ 182.432953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 182.439681] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 182.465956] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 182.472309] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 182.681956] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 183.247916] usb 1-1: USB disconnect, device number 7 [ 183.576809] usb 1-1: new full-speed USB device number 8 using orion-ehci [ 183.732954] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 183.739682] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 183.765954] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 183.772307] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 183.982955] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 184.552876] usb 1-1: USB disconnect, device number 8 [ 184.886772] usb 1-1: new full-speed USB device number 9 using orion-ehci [ 185.042953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 185.049681] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 185.073955] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 185.080318] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 185.291956] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 185.854882] usb 1-1: USB disconnect, device number 9 [ 186.186739] usb 1-1: new full-speed USB device number 10 using orion-ehci [ 186.342953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 186.349680] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 186.373956] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 186.380311] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 186.589954] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 187.160396] usb 1-1: USB disconnect, device number 10 [ 187.486706] usb 1-1: new full-speed USB device number 11 using orion-ehci [ 187.642954] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 187.649682] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 187.675955] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 187.682314] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 187.892955] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 188.464325] usb 1-1: USB disconnect, device number 11 [ 188.796675] usb 1-1: new full-speed USB device number 12 using orion-ehci [ 188.952953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 188.959681] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 188.985954] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 188.992344] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 189.202955] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 189.770861] usb 1-1: USB disconnect, device number 12 [ 190.106645] usb 1-1: new full-speed USB device number 13 using orion-ehci [ 190.262953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc [ 190.269682] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 190.296958] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 190.303299] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 190.512954] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 191.076700] usb 1-1: USB disconnect, device number 13 some information about the card: Bus 001 Device 011: ID 8087:07dc Intel Corp. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize0 64 idVendor 0x8087 Intel Corp. idProduct 0x07dc bcdDevice 0.01 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 177 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0000 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0000 1x 0 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0011 1x 17 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0011 1x 17 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0019 1x 25 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0019 1x 25 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 4 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0021 1x 33 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0021 1x 33 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 5 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0031 1x 49 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0031 1x 49 bytes bInterval 1 [root@alarm log]# uname -a Linux alarm 4.4.24-2-ARCH #1 SMP Fri Oct 14 01:04:22 MDT 2016 armv7l GNU/Linux What's confusing me is that this device is connected through pcie, not usb. When i use lspci i get: [root@alarm log]# lspci 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter (rev ff) So the other card is seen as pci device, but the intel is not. I am really lost now. ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Intel 7260 not working on 4.4.24 / armv7 2016-10-18 16:22 ` Intel 7260 not working " Oliver Zemann @ 2016-10-18 19:06 ` Johannes Berg 2016-10-18 19:09 ` Johannes Berg 2016-10-18 19:44 ` Oliver Zemann 2016-10-18 19:30 ` Emmanuel Grumbach 1 sibling, 2 replies; 18+ messages in thread From: Johannes Berg @ 2016-10-18 19:06 UTC (permalink / raw) To: Oliver Zemann, linux-wireless On Tue, 2016-10-18 at 18:22 +0200, Oliver Zemann wrote: > Because of the problems with the ath10 card, i bought an intel 7260 > (mpcie) wifi card. Unfortunately it is also not working. > I get tons of those messages: > > [ 175.777030] usb 1-1: new full-speed USB device number 2 using > orion-ehci > [ 175.933953] usb 1-1: New USB device found, idVendor=8087, > idProduct=07dc > [ 175.940681] usb 1-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 175.966954] Bluetooth: hci0: read Intel version: > 3707100180012d0d00 > [ 175.973313] Bluetooth: hci0: Intel Bluetooth firmware file: > intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq > [ 176.183954] Bluetooth: hci0: Intel Bluetooth firmware patch > completed > and activated > [ 176.749831] usb 1-1: USB disconnect, device number 2 This is odd. However, it's entirely related to the NICs *Bluetooth* function, which lives on USB. > What's confusing me is that this device is connected through pcie, > not usb. When i use lspci i get: > [root@alarm log]# lspci > 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev > 04) > 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev > 04) > 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac > Wireless Network Adapter (rev ff) > > So the other card is seen as pci device, but the intel is not. I am > really lost now. The NICs *WiFi* function should be a PCIe device, but the USB connect/disconnect cycles suggest that there's something wrong with the electrical connection, which presumably causes the PCIe part of the device to never appear on the bus. johannes ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Intel 7260 not working on 4.4.24 / armv7 2016-10-18 19:06 ` Johannes Berg @ 2016-10-18 19:09 ` Johannes Berg 2016-10-18 19:44 ` Oliver Zemann 1 sibling, 0 replies; 18+ messages in thread From: Johannes Berg @ 2016-10-18 19:09 UTC (permalink / raw) To: Oliver Zemann, linux-wireless On Tue, 2016-10-18 at 21:06 +0200, Johannes Berg wrote: > > The NICs *WiFi* function should be a PCIe device, but the USB > connect/disconnect cycles suggest that there's something wrong with > the > electrical connection, which presumably causes the PCIe part of the > device to never appear on the bus. > Also, FWIW, I had our later NIC (8260) running on an ARMv7 (a Hummingboard Pro i2ex or so), in both little (default) and big endian modes. I haven't tried the 7260 but conceivably could. johannes ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Intel 7260 not working on 4.4.24 / armv7 2016-10-18 19:06 ` Johannes Berg 2016-10-18 19:09 ` Johannes Berg @ 2016-10-18 19:44 ` Oliver Zemann 2016-10-18 19:56 ` Johannes Berg 1 sibling, 1 reply; 18+ messages in thread From: Oliver Zemann @ 2016-10-18 19:44 UTC (permalink / raw) To: linux-wireless Is there some way to disable the bluetooth functionality? Am 18.10.2016 um 21:06 schrieb Johannes Berg: > On Tue, 2016-10-18 at 18:22 +0200, Oliver Zemann wrote: >> Because of the problems with the ath10 card, i bought an intel 7260 >> (mpcie) wifi card. Unfortunately it is also not working. >> I get tons of those messages: >> >> [ 175.777030] usb 1-1: new full-speed USB device number 2 using >> orion-ehci >> [ 175.933953] usb 1-1: New USB device found, idVendor=8087, >> idProduct=07dc >> [ 175.940681] usb 1-1: New USB device strings: Mfr=0, Product=0, >> SerialNumber=0 >> [ 175.966954] Bluetooth: hci0: read Intel version: >> 3707100180012d0d00 >> [ 175.973313] Bluetooth: hci0: Intel Bluetooth firmware file: >> intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq >> [ 176.183954] Bluetooth: hci0: Intel Bluetooth firmware patch >> completed >> and activated >> [ 176.749831] usb 1-1: USB disconnect, device number 2 > This is odd. However, it's entirely related to the NICs *Bluetooth* > function, which lives on USB. > >> What's confusing me is that this device is connected through pcie, >> not usb. When i use lspci i get: >> [root@alarm log]# lspci >> 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev >> 04) >> 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev >> 04) >> 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac >> Wireless Network Adapter (rev ff) >> >> So the other card is seen as pci device, but the intel is not. I am >> really lost now. > The NICs *WiFi* function should be a PCIe device, but the USB > connect/disconnect cycles suggest that there's something wrong with the > electrical connection, which presumably causes the PCIe part of the > device to never appear on the bus. > > johannes ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Intel 7260 not working on 4.4.24 / armv7 2016-10-18 19:44 ` Oliver Zemann @ 2016-10-18 19:56 ` Johannes Berg 0 siblings, 0 replies; 18+ messages in thread From: Johannes Berg @ 2016-10-18 19:56 UTC (permalink / raw) To: Oliver Zemann, linux-wireless On Tue, 2016-10-18 at 21:44 +0200, Oliver Zemann wrote: > Is there some way to disable the bluetooth functionality? > Not that I know of. It's kinda pointless though since you then wouldn't have any functionality anyway? I don't have the board you mentioned to Emmanuel, but I can try the 7260 on the Hummingboard. I do know that, for example, on my old G5 powermac the newer Intel NICs cause the system to be unable boot, so there sometimes are PCIe bus incompatibilities. johannes (please quote properly) ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Intel 7260 not working on 4.4.24 / armv7 2016-10-18 16:22 ` Intel 7260 not working " Oliver Zemann 2016-10-18 19:06 ` Johannes Berg @ 2016-10-18 19:30 ` Emmanuel Grumbach 2016-10-18 19:31 ` Oliver Zemann 1 sibling, 1 reply; 18+ messages in thread From: Emmanuel Grumbach @ 2016-10-18 19:30 UTC (permalink / raw) To: Oliver Zemann; +Cc: linux-wireless On Tue, Oct 18, 2016 at 7:22 PM, Oliver Zemann <oliver.zemann@gmail.com> wrote: > Because of the problems with the ath10 card, i bought an intel 7260 (mpcie) > wifi card. Unfortunately it is also not working. > I get tons of those messages: > > [ 175.777030] usb 1-1: new full-speed USB device number 2 using orion-ehci > [ 175.933953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc > [ 175.940681] usb 1-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 175.966954] Bluetooth: hci0: read Intel version: 3707100180012d0d00 > [ 175.973313] Bluetooth: hci0: Intel Bluetooth firmware file: > intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq > [ 176.183954] Bluetooth: hci0: Intel Bluetooth firmware patch completed and > activated > [ 176.749831] usb 1-1: USB disconnect, device number 2 > [ 177.076993] usb 1-1: new full-speed USB device number 3 using orion-ehci > [ 177.233953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc > [ 177.240682] usb 1-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 177.266957] Bluetooth: hci0: read Intel version: 3707100180012d0d00 > [ 177.273316] Bluetooth: hci0: Intel Bluetooth firmware file: > intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq > [ 177.482955] Bluetooth: hci0: Intel Bluetooth firmware patch completed and > activated > [ 178.046910] usb 1-1: USB disconnect, device number 3 > [ 178.376958] usb 1-1: new full-speed USB device number 4 using orion-ehci > [ 178.533954] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc > [ 178.540682] usb 1-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 Hmm... bad connectors? USB seems to think that the device keeps disconnecting. But that's the BT part. > some information about the card: > Bus 001 Device 011: ID 8087:07dc Intel Corp. > Couldn't open device, some information will be missing > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 224 Wireless > bDeviceSubClass 1 Radio Frequency > bDeviceProtocol 1 Bluetooth > bMaxPacketSize0 64 > idVendor 0x8087 Intel Corp. > idProduct 0x07dc > bcdDevice 0.01 > iManufacturer 0 > iProduct 0 > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 177 > bNumInterfaces 2 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 224 Wireless > bInterfaceSubClass 1 Radio Frequency > bInterfaceProtocol 1 Bluetooth > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 Wireless > bInterfaceSubClass 1 Radio Frequency > bInterfaceProtocol 1 Bluetooth > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 EP 3 OUT > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0000 1x 0 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0000 1x 0 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 1 > bNumEndpoints 2 > bInterfaceClass 224 Wireless > bInterfaceSubClass 1 Radio Frequency > bInterfaceProtocol 1 Bluetooth > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 EP 3 OUT > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0009 1x 9 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0009 1x 9 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 2 > bNumEndpoints 2 > bInterfaceClass 224 Wireless > bInterfaceSubClass 1 Radio Frequency > bInterfaceProtocol 1 Bluetooth > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 EP 3 OUT > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0011 1x 17 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0011 1x 17 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 3 > bNumEndpoints 2 > bInterfaceClass 224 Wireless > bInterfaceSubClass 1 Radio Frequency > bInterfaceProtocol 1 Bluetooth > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 EP 3 OUT > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0019 1x 25 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0019 1x 25 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 4 > bNumEndpoints 2 > bInterfaceClass 224 Wireless > bInterfaceSubClass 1 Radio Frequency > bInterfaceProtocol 1 Bluetooth > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 EP 3 OUT > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0021 1x 33 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0021 1x 33 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 5 > bNumEndpoints 2 > bInterfaceClass 224 Wireless > bInterfaceSubClass 1 Radio Frequency > bInterfaceProtocol 1 Bluetooth > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 EP 3 OUT > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0031 1x 49 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0031 1x 49 bytes > bInterval 1 > > > [root@alarm log]# uname -a > Linux alarm 4.4.24-2-ARCH #1 SMP Fri Oct 14 01:04:22 MDT 2016 armv7l > GNU/Linux > > What's confusing me is that this device is connected through pcie, not usb. > When i use lspci i get: > [root@alarm log]# lspci > 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) > 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) > 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless > Network Adapter (rev ff) > > So the other card is seen as pci device, but the intel is not. I am really > lost now. So is the NIC :) It is lost. If it doesn't appear in the enumeration, it seems you have a bad platform issue. the arm thing in your uname -a hints me that you can't really talk your OEM, right? ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Intel 7260 not working on 4.4.24 / armv7 2016-10-18 19:30 ` Emmanuel Grumbach @ 2016-10-18 19:31 ` Oliver Zemann 0 siblings, 0 replies; 18+ messages in thread From: Oliver Zemann @ 2016-10-18 19:31 UTC (permalink / raw) Cc: linux-wireless I tried 2 of those wifi cards. Both behaved the same. Also on another clearfog pro. So i guess this is not a hardware fault. Also, the compex WLE600 works (unfortunately the WLE900 does not). Am 18.10.2016 um 21:30 schrieb Emmanuel Grumbach: > On Tue, Oct 18, 2016 at 7:22 PM, Oliver Zemann <oliver.zemann@gmail.com> wrote: >> Because of the problems with the ath10 card, i bought an intel 7260 (mpcie) >> wifi card. Unfortunately it is also not working. >> I get tons of those messages: >> >> [ 175.777030] usb 1-1: new full-speed USB device number 2 using orion-ehci >> [ 175.933953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc >> [ 175.940681] usb 1-1: New USB device strings: Mfr=0, Product=0, >> SerialNumber=0 >> [ 175.966954] Bluetooth: hci0: read Intel version: 3707100180012d0d00 >> [ 175.973313] Bluetooth: hci0: Intel Bluetooth firmware file: >> intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq >> [ 176.183954] Bluetooth: hci0: Intel Bluetooth firmware patch completed and >> activated >> [ 176.749831] usb 1-1: USB disconnect, device number 2 >> [ 177.076993] usb 1-1: new full-speed USB device number 3 using orion-ehci >> [ 177.233953] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc >> [ 177.240682] usb 1-1: New USB device strings: Mfr=0, Product=0, >> SerialNumber=0 >> [ 177.266957] Bluetooth: hci0: read Intel version: 3707100180012d0d00 >> [ 177.273316] Bluetooth: hci0: Intel Bluetooth firmware file: >> intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq >> [ 177.482955] Bluetooth: hci0: Intel Bluetooth firmware patch completed and >> activated >> [ 178.046910] usb 1-1: USB disconnect, device number 3 >> [ 178.376958] usb 1-1: new full-speed USB device number 4 using orion-ehci >> [ 178.533954] usb 1-1: New USB device found, idVendor=8087, idProduct=07dc >> [ 178.540682] usb 1-1: New USB device strings: Mfr=0, Product=0, >> SerialNumber=0 > Hmm... bad connectors? USB seems to think that the device keeps disconnecting. > But that's the BT part. > >> some information about the card: >> Bus 001 Device 011: ID 8087:07dc Intel Corp. >> Couldn't open device, some information will be missing >> Device Descriptor: >> bLength 18 >> bDescriptorType 1 >> bcdUSB 2.00 >> bDeviceClass 224 Wireless >> bDeviceSubClass 1 Radio Frequency >> bDeviceProtocol 1 Bluetooth >> bMaxPacketSize0 64 >> idVendor 0x8087 Intel Corp. >> idProduct 0x07dc >> bcdDevice 0.01 >> iManufacturer 0 >> iProduct 0 >> iSerial 0 >> bNumConfigurations 1 >> Configuration Descriptor: >> bLength 9 >> bDescriptorType 2 >> wTotalLength 177 >> bNumInterfaces 2 >> bConfigurationValue 1 >> iConfiguration 0 >> bmAttributes 0xe0 >> Self Powered >> Remote Wakeup >> MaxPower 100mA >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 0 >> bAlternateSetting 0 >> bNumEndpoints 3 >> bInterfaceClass 224 Wireless >> bInterfaceSubClass 1 Radio Frequency >> bInterfaceProtocol 1 Bluetooth >> iInterface 0 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x81 EP 1 IN >> bmAttributes 3 >> Transfer Type Interrupt >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0040 1x 64 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x02 EP 2 OUT >> bmAttributes 2 >> Transfer Type Bulk >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0040 1x 64 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x82 EP 2 IN >> bmAttributes 2 >> Transfer Type Bulk >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0040 1x 64 bytes >> bInterval 1 >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 1 >> bAlternateSetting 0 >> bNumEndpoints 2 >> bInterfaceClass 224 Wireless >> bInterfaceSubClass 1 Radio Frequency >> bInterfaceProtocol 1 Bluetooth >> iInterface 0 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x03 EP 3 OUT >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0000 1x 0 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x83 EP 3 IN >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0000 1x 0 bytes >> bInterval 1 >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 1 >> bAlternateSetting 1 >> bNumEndpoints 2 >> bInterfaceClass 224 Wireless >> bInterfaceSubClass 1 Radio Frequency >> bInterfaceProtocol 1 Bluetooth >> iInterface 0 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x03 EP 3 OUT >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0009 1x 9 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x83 EP 3 IN >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0009 1x 9 bytes >> bInterval 1 >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 1 >> bAlternateSetting 2 >> bNumEndpoints 2 >> bInterfaceClass 224 Wireless >> bInterfaceSubClass 1 Radio Frequency >> bInterfaceProtocol 1 Bluetooth >> iInterface 0 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x03 EP 3 OUT >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0011 1x 17 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x83 EP 3 IN >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0011 1x 17 bytes >> bInterval 1 >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 1 >> bAlternateSetting 3 >> bNumEndpoints 2 >> bInterfaceClass 224 Wireless >> bInterfaceSubClass 1 Radio Frequency >> bInterfaceProtocol 1 Bluetooth >> iInterface 0 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x03 EP 3 OUT >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0019 1x 25 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x83 EP 3 IN >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0019 1x 25 bytes >> bInterval 1 >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 1 >> bAlternateSetting 4 >> bNumEndpoints 2 >> bInterfaceClass 224 Wireless >> bInterfaceSubClass 1 Radio Frequency >> bInterfaceProtocol 1 Bluetooth >> iInterface 0 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x03 EP 3 OUT >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0021 1x 33 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x83 EP 3 IN >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0021 1x 33 bytes >> bInterval 1 >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 1 >> bAlternateSetting 5 >> bNumEndpoints 2 >> bInterfaceClass 224 Wireless >> bInterfaceSubClass 1 Radio Frequency >> bInterfaceProtocol 1 Bluetooth >> iInterface 0 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x03 EP 3 OUT >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0031 1x 49 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x83 EP 3 IN >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0031 1x 49 bytes >> bInterval 1 >> >> >> [root@alarm log]# uname -a >> Linux alarm 4.4.24-2-ARCH #1 SMP Fri Oct 14 01:04:22 MDT 2016 armv7l >> GNU/Linux >> >> What's confusing me is that this device is connected through pcie, not usb. >> When i use lspci i get: >> [root@alarm log]# lspci >> 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) >> 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) >> 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless >> Network Adapter (rev ff) >> >> So the other card is seen as pci device, but the intel is not. I am really >> lost now. > So is the NIC :) It is lost. If it doesn't appear in the enumeration, > it seems you have a bad platform issue. the arm thing in your uname -a > hints me that you can't really talk your OEM, right? ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-15 17:04 ` Oliver Zemann 2016-10-18 16:22 ` Intel 7260 not working " Oliver Zemann @ 2016-10-21 16:25 ` Oliver Zemann 2016-10-21 16:54 ` Michal Kazior 2016-10-22 11:55 ` Jonas Gorski 1 sibling, 2 replies; 18+ messages in thread From: Oliver Zemann @ 2016-10-21 16:25 UTC (permalink / raw) To: linux-wireless The problem is gone with kernel 4.7.3 on armbian - both compex cards work (wle600, wle900), unfortunately that kernel does not support sfp (seems like its kind of proprietary drivers from clearfog). So its a driver issue but i have no clue who to contact or where to file a bug report. The only available kernel which supports sfp (from solidrun, vendor of the clearfog board) is 4.4.23 I am wondering if i could simply checkout the 4.4.x sources, merge the atheros drivers in it and try to rebuild the kernel? Am 15.10.2016 um 19:04 schrieb Oliver Zemann: > I hope thats what you mean. I am not that familiar with linux drivers > > [root@alarm ~]# lsmod > Module Size Used by > ath10k_pci 30053 0 > ath10k_core 193491 1 ath10k_pci > ath 18176 1 ath10k_core > mac80211 405739 1 ath10k_core > cfg80211 215848 3 ath,mac80211,ath10k_core > rfkill 14391 2 cfg80211 > marvell_cesa 25839 0 > des_generic 16747 1 marvell_cesa > sch_fq_codel 7757 9 > ip_tables 11170 0 > x_tables 11520 1 ip_tables > autofs4 22783 2 > [root@alarm ~]# rmmod ath10k_pci ath10k_core > [root@alarm ~]# modprobe ath10k_core > [root@alarm ~]# modprobe ath10k_pci > [28501.637198] ath10k_pci 0000:02:00.0: Refused to change power state, > currently in D3 > [28501.675138] ath10k_pci 0000:02:00.0: failed to wake up device : -110 > [28501.681625] ath10k_pci: probe of 0000:02:00.0 failed with error -110 > > > Am 15.10.2016 um 16:44 schrieb Sebastian Gottschall: >> could you please attach a full log? i see no driver loading here. >> this is just a small part of the kernel boot log, but no driver >> intialisation >> >> Am 15.10.2016 um 16:00 schrieb Oliver Zemann: >>> I have a clearfog pro (arm7) from marvel and bought a pcie wifi >>> card. Unfortunately, it does not work. >>> I am not sure if this is a bug in the module or even in some pci-e >>> driver. Maybe someone could tell me that. >>> >>> dmesg: >>> >>> [ 5.348307] mvebu-pcie soc:pcie-controller: >>> /soc/pcie-controller/pcie@2,0: reset gpio is active low >>> [ 5.358026] mvebu-pcie soc:pcie-controller: >>> /soc/pcie-controller/pcie@3,0: reset gpio is active low >>> [ 5.421496] mvebu-pcie soc:pcie-controller: PCI host bridge to bus >>> 0000:00 >>> [ 5.428390] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] >>> [ 5.434680] pci_bus 0000:00: root bus resource [mem >>> 0xf8000000-0xffdfffff] >>> [ 5.441575] pci_bus 0000:00: root bus resource [bus 00-ff] >>> [ 5.447083] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400 >>> [ 5.447198] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400 >>> [ 5.447295] PCI: bus0: Fast back to back transfers disabled >>> [ 5.452887] pci 0000:00:02.0: bridge configuration invalid ([bus >>> 00-00]), reconfiguring >>> [ 5.460911] pci 0000:00:03.0: bridge configuration invalid ([bus >>> 00-00]), reconfiguring >>> [ 5.468986] PCI: bus1: Fast back to back transfers enabled >>> [ 5.474491] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 >>> [ 5.474561] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000 >>> [ 5.474593] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff >>> 64bit] >>> [ 5.474617] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff >>> pref] >>> [ 5.474667] pci 0000:02:00.0: supports D1 D2 >>> [ 5.511395] PCI: bus2: Fast back to back transfers enabled >>> [ 5.516894] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02 >>> [ 5.516905] pci 0000:02:00.0: of_irq_parse_pci() failed with rc=134 >>> [ 5.523207] pci 0000:00:03.0: BAR 14: assigned [mem >>> 0xf8000000-0xf82fffff] >>> [ 5.530098] pci 0000:00:02.0: PCI bridge to [bus 01] >>> [ 5.535082] pci 0000:02:00.0: BAR 0: assigned [mem >>> 0xf8000000-0xf81fffff 64bit] >>> [ 5.542413] pci 0000:02:00.0: BAR 0: error updating (0xf8000004 != >>> 0xffffffff) >>> [ 5.549652] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 >>> != 0xffffffff) >>> [ 5.557155] pci 0000:02:00.0: BAR 6: assigned [mem >>> 0xf8200000-0xf820ffff pref] >>> [ 5.564396] pci 0000:00:03.0: PCI bridge to [bus 02] >>> [ 5.569372] pci 0000:00:03.0: bridge window [mem 0xf8000000-0xf82fffff] >>> [ 5.576256] pcieport 0000:00:03.0: enabling device (0140 -> 0142) >>> >>> lspci: >>> >>> >>> [root@alarm alarm]# lspci >>> 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) >>> 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) >>> 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac >>> Wireless Network Adapter (rev ff) >> >>> >>> Thanks! >>> >>> >> >> > ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-21 16:25 ` compex wle900vx (ath10k) problem " Oliver Zemann @ 2016-10-21 16:54 ` Michal Kazior 2016-10-22 11:55 ` Jonas Gorski 1 sibling, 0 replies; 18+ messages in thread From: Michal Kazior @ 2016-10-21 16:54 UTC (permalink / raw) To: Oliver Zemann; +Cc: linux-wireless On 21 October 2016 at 18:25, Oliver Zemann <oliver.zemann@gmail.com> wrote: > The problem is gone with kernel 4.7.3 on armbian - both compex cards work > (wle600, wle900), unfortunately that kernel does not support sfp (seems l= ike > its kind of proprietary drivers from clearfog). So its a driver issue but= i > have no clue who to contact or where to file a bug report. The only > available kernel which supports sfp (from solidrun, vendor of the clearfo= g > board) is 4.4.23 > > I am wondering if i could simply checkout the 4.4.x sources, merge the > atheros drivers in it and try to rebuild the kernel? That's what backports[1] are for. The problem could be in the pci subsystem though so backporting the driver itself might not solve your problem. [1]: https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports Micha=C5=82 ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-21 16:25 ` compex wle900vx (ath10k) problem " Oliver Zemann 2016-10-21 16:54 ` Michal Kazior @ 2016-10-22 11:55 ` Jonas Gorski 2016-10-23 15:53 ` Oliver Zemann 1 sibling, 1 reply; 18+ messages in thread From: Jonas Gorski @ 2016-10-22 11:55 UTC (permalink / raw) To: Oliver Zemann; +Cc: linux-wireless@vger.kernel.org Hi, On 21 October 2016 at 18:25, Oliver Zemann <oliver.zemann@gmail.com> wrote: > The problem is gone with kernel 4.7.3 on armbian - both compex cards work > (wle600, wle900), Interesting to know this issue isn't present in 4.7 - I also encountered it in 4.4 with LEDE. > unfortunately that kernel does not support sfp (seems like > its kind of proprietary drivers from clearfog). They aren't really proprietary, they are proper patches that were submitted as RFC once, so it shouldn't be much effort to port them to e.g. 4.7. Anyways ... > So its a driver issue but i > have no clue who to contact or where to file a bug report. The only > available kernel which supports sfp (from solidrun, vendor of the clearfog > board) is 4.4.23 > > I am wondering if i could simply checkout the 4.4.x sources, merge the > atheros drivers in it and try to rebuild the kernel? the issue seems to be that MSI interrupts do not work on 4.4 (at least with ath10k, didn't have any other drivers that support it to test). Your options are either to disable support for them in the kernel config, or pass irq_mode=1 to ath10k_pci on probe to force legacy interrupts; it should work then properly. Regards Jonas ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-22 11:55 ` Jonas Gorski @ 2016-10-23 15:53 ` Oliver Zemann 2016-10-23 19:33 ` Jonas Gorski 0 siblings, 1 reply; 18+ messages in thread From: Oliver Zemann @ 2016-10-23 15:53 UTC (permalink / raw) To: Jonas Gorski; +Cc: linux-wireless@vger.kernel.org Thanks for that info Jonas. I passed optargs=irq_mode=1 in /boot/uEnv.txt on archlinux arm (kernel 4.4.23) and verified with [root@alarm ~]# cat /proc/cmdline console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait irq_mode=1 But it still does not work: [root@alarm ~]# rmmod ath10k_pci [root@alarm ~]# modprobe ath10k_pci [ 28.791404] ath10k_pci 0000:02:00.0: Refused to change power state, currently in D3 [ 28.829352] ath10k_pci 0000:02:00.0: failed to wake up device : -110 [ 28.835861] ath10k_pci: probe of 0000:02:00.0 failed with error -110 Did i do something wrong? If somehow possible, i would prefer to not rebuild the kernel and somehow configure the existing one without changes. Kind regards Oli Am 22.10.2016 um 13:55 schrieb Jonas Gorski: > Hi, > > On 21 October 2016 at 18:25, Oliver Zemann <oliver.zemann@gmail.com> wrote: >> The problem is gone with kernel 4.7.3 on armbian - both compex cards work >> (wle600, wle900), > Interesting to know this issue isn't present in 4.7 - I also > encountered it in 4.4 with LEDE. > >> unfortunately that kernel does not support sfp (seems like >> its kind of proprietary drivers from clearfog). > They aren't really proprietary, they are proper patches that were > submitted as RFC once, so it shouldn't be much effort to port them to > e.g. 4.7. Anyways ... > >> So its a driver issue but i >> have no clue who to contact or where to file a bug report. The only >> available kernel which supports sfp (from solidrun, vendor of the clearfog >> board) is 4.4.23 >> >> I am wondering if i could simply checkout the 4.4.x sources, merge the >> atheros drivers in it and try to rebuild the kernel? > the issue seems to be that MSI interrupts do not work on 4.4 (at least > with ath10k, didn't have any other drivers that support it to test). > Your options are either to disable support for them in the kernel > config, or pass irq_mode=1 to ath10k_pci on probe to force legacy > interrupts; it should work then properly. > > > Regards > Jonas ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-23 15:53 ` Oliver Zemann @ 2016-10-23 19:33 ` Jonas Gorski 2016-10-23 19:42 ` Oliver Zemann 0 siblings, 1 reply; 18+ messages in thread From: Jonas Gorski @ 2016-10-23 19:33 UTC (permalink / raw) To: Oliver Zemann; +Cc: linux-wireless@vger.kernel.org On 23 October 2016 at 17:53, Oliver Zemann <oliver.zemann@gmail.com> wrote: > Thanks for that info Jonas. I passed optargs=irq_mode=1 in /boot/uEnv.txt on > archlinux arm (kernel 4.4.23) and verified with > > [root@alarm ~]# cat /proc/cmdline > console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait irq_mode=1 > > But it still does not work: > > [root@alarm ~]# rmmod ath10k_pci > [root@alarm ~]# modprobe ath10k_pci > [ 28.791404] ath10k_pci 0000:02:00.0: Refused to change power state, > currently in D3 > [ 28.829352] ath10k_pci 0000:02:00.0: failed to wake up device : -110 > [ 28.835861] ath10k_pci: probe of 0000:02:00.0 failed with error -110 > > Did i do something wrong? If somehow possible, i would prefer to not rebuild > the kernel and somehow configure the existing one without changes. For the kernel command line you need to prefix with the module name, i.e. "ath10k_pci.irq_mode=1". Alternative is while modprobing with "modprobe ath10_pci irq_mode=1". See <https://www.kernel.org/doc/Documentation/kernel-parameters.txt> for details. Regards Jonas ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-23 19:33 ` Jonas Gorski @ 2016-10-23 19:42 ` Oliver Zemann 2016-10-24 11:14 ` Jonas Gorski 0 siblings, 1 reply; 18+ messages in thread From: Oliver Zemann @ 2016-10-23 19:42 UTC (permalink / raw) To: Jonas Gorski; +Cc: linux-wireless@vger.kernel.org Thanks, but its still not working. I dont get any error now when i do modprobe and installed is the wle900 [root@alarm alarm]# rmmod ath10k_pci [root@alarm alarm]# modprobe ath10k_pci irq_mode=1 but: [root@alarm alarm]# dmesg | grep ath10k [ 220.356314] ath10k_pci 0000:02:00.0: Refused to change power state, currently in D3 [ 220.394265] ath10k_pci 0000:02:00.0: failed to wake up device : -110 [ 220.400770] ath10k_pci: probe of 0000:02:00.0 failed with error -110 [root@alarm alarm]# cat /proc/cmdline console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait ath10k_pci.irq_mode=1 Thanks for your patience Regards Oli Am 23.10.2016 um 21:33 schrieb Jonas Gorski: > On 23 October 2016 at 17:53, Oliver Zemann <oliver.zemann@gmail.com> wrote: >> Thanks for that info Jonas. I passed optargs=irq_mode=1 in /boot/uEnv.txt on >> archlinux arm (kernel 4.4.23) and verified with >> >> [root@alarm ~]# cat /proc/cmdline >> console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait irq_mode=1 >> >> But it still does not work: >> >> [root@alarm ~]# rmmod ath10k_pci >> [root@alarm ~]# modprobe ath10k_pci >> [ 28.791404] ath10k_pci 0000:02:00.0: Refused to change power state, >> currently in D3 >> [ 28.829352] ath10k_pci 0000:02:00.0: failed to wake up device : -110 >> [ 28.835861] ath10k_pci: probe of 0000:02:00.0 failed with error -110 >> >> Did i do something wrong? If somehow possible, i would prefer to not rebuild >> the kernel and somehow configure the existing one without changes. > For the kernel command line you need to prefix with the module name, > i.e. "ath10k_pci.irq_mode=1". Alternative is while modprobing with > "modprobe ath10_pci irq_mode=1". See > <https://www.kernel.org/doc/Documentation/kernel-parameters.txt> for > details. > > Regards > Jonas ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-23 19:42 ` Oliver Zemann @ 2016-10-24 11:14 ` Jonas Gorski 2016-10-24 18:10 ` Oliver Zemann 0 siblings, 1 reply; 18+ messages in thread From: Jonas Gorski @ 2016-10-24 11:14 UTC (permalink / raw) To: Oliver Zemann; +Cc: linux-wireless@vger.kernel.org Hi, (please don't toppost) On 23 October 2016 at 21:42, Oliver Zemann <oliver.zemann@gmail.com> wrote: > Thanks, but its still not working. I dont get any error now when i do > modprobe and installed is the wle900 > > [root@alarm alarm]# rmmod ath10k_pci > [root@alarm alarm]# modprobe ath10k_pci irq_mode=1 Strange, this was working for me with a Sparklan WPEA-352ACN. > > but: > > [root@alarm alarm]# dmesg | grep ath10k > [ 220.356314] ath10k_pci 0000:02:00.0: Refused to change power state, > currently in D3 Maybe there is a separate issue related to this. I don't remember seeing this message in my kernel log. (At least to me) it would be interesting to know if it works using a LEDE image, or if it fails there as well. I don't have a Compex card here. You can find an sd-card image at https://downloads.lede-project.org/snapshots/targets/mvebu/generic/ - it won't contain any wifi drivers though, you will need to install them separately - easiest by providing internet access over the wan port (the single ethernet port for the pro, it defaults to dhcp client), then running "opkg install kmod-ath10k" on shell. Note that this kernel has MSI disabled, so you don't need to do anything there extra. > [ 220.394265] ath10k_pci 0000:02:00.0: failed to wake up device : -110 > [ 220.400770] ath10k_pci: probe of 0000:02:00.0 failed with error -110 > > [root@alarm alarm]# cat /proc/cmdline > console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait ath10k_pci.irq_mode=1 > > Thanks for your patience Regards Jonas ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7 2016-10-24 11:14 ` Jonas Gorski @ 2016-10-24 18:10 ` Oliver Zemann 0 siblings, 0 replies; 18+ messages in thread From: Oliver Zemann @ 2016-10-24 18:10 UTC (permalink / raw) To: Jonas Gorski; +Cc: linux-wireless@vger.kernel.org > > (please don't toppost) Did not know that this is forbidden, sorry > You can find an sd-card image at > https://downloads.lede-project.org/snapshots/targets/mvebu/generic/ - > it won't contain any wifi drivers though, you will need to install > them separately - easiest by providing internet access over the wan > port (the single ethernet port for the pro, it defaults to dhcp > client), then running "opkg install kmod-ath10k" on shell. I used dd to install the latest image from today to the SD. I am connected through usb with screen, thats a very nice feature of the board :) I logged in, updated the packages with opkg update and then installed kmod-ath10k but i received many errors: [ 380.987440] ath10k_core: Unknown symbol cfg80211_find_ie_match (err 0) [ 380.993996] ath10k_core: Unknown symbol ieee80211_wake_queue (err 0) [ 381.000383] ath10k_core: Unknown symbol ieee80211_find_sta (err 0) [ 381.006586] ath10k_core: Unknown symbol ieee80211_stop_rx_ba_session_offl (err 0) [ 381.014101] ath10k_core: Unknown symbol ieee80211_tx_status_irqsafe (err 0) [ 381.021096] ath10k_core: Unknown symbol ieee80211_iter_chan_contexts_atomic (err 0) [ 381.028778] ath10k_core: Unknown symbol __cfg80211_alloc_reply_skb (err 0) [ 381.035681] ath10k_core: Unknown symbol __cfg80211_alloc_event_skb (err 0) [ 381.042584] ath10k_core: Unknown symbol cfg80211_put_bss (err 0) [ 381.048623] ath10k_core: Unknown symbol ieee80211_bss_get_ie (err 0) [ 381.055005] ath10k_core: Unknown symbol wiphy_to_ieee80211_hw (err 0) [ 381.061472] ath10k_core: Unknown symbol __cfg80211_send_event_skb (err 0) [ 381.068284] ath10k_core: Unknown symbol ath_reg_notifier_apply (err 0) [ 381.074878] ath10k_core: Unknown symbol ieee80211_queue_delayed_work (err 0) [ 381.081959] ath10k_core: Unknown symbol ieee80211_proberesp_get (err 0) [ 381.088610] ath10k_core: Unknown symbol ieee80211_find_sta_by_ifaddr (err 0) [ 381.095689] ath10k_core: Unknown symbol ieee80211_remain_on_channel_expired (err 0) [ 381.103379] ath10k_core: Unknown symbol ath_is_world_regd (err 0) [ 381.109503] ath10k_core: Unknown symbol ieee80211_wake_queues (err 0) [ 381.115965] ath10k_core: Unknown symbol ieee80211_report_low_ack (err 0) [ 381.122691] ath10k_core: Unknown symbol ieee80211_beacon_get_template (err 0) [ 381.129855] ath10k_core: Unknown symbol ieee80211_free_txskb (err 0) [ 381.136232] ath10k_core: Unknown symbol ieee80211_alloc_hw_nm (err 0) [ 381.142699] ath10k_core: Unknown symbol cfg80211_get_bss (err 0) [ 381.148731] ath10k_core: Unknown symbol ieee80211_tx_dequeue (err 0) [ 381.155111] ath10k_core: Unknown symbol __ieee80211_get_channel (err 0) [ 381.161755] ath10k_core: Unknown symbol cfg80211_vendor_cmd_reply (err 0) [ 381.168574] ath10k_core: Unknown symbol ieee80211_tx_status (err 0) [ 381.174866] ath10k_core: Unknown symbol ieee80211_stop_queue (err 0) [ 381.181246] ath10k_core: Unknown symbol ieee80211_ready_on_channel (err 0) [ 381.188142] ath10k_core: Unknown symbol ieee80211_stop_queues (err 0) [ 381.194621] ath10k_core: Unknown symbol ieee80211_scan_completed (err 0) [ 381.201349] ath10k_core: Unknown symbol ieee80211_iterate_active_interfaces_atomic (err 0) [ 381.209651] ath10k_core: Unknown symbol ieee80211_channel_to_frequency (err 0) [ 381.216896] ath10k_core: Unknown symbol ieee80211_unregister_hw (err 0) [ 381.223537] ath10k_core: Unknown symbol dfs_pattern_detector_init (err 0) [ 381.230354] ath10k_core: Unknown symbol ath_regd_init (err 0) [ 381.236119] ath10k_core: Unknown symbol ieee80211_csa_update_counter (err 0) [ 381.243195] ath10k_core: Unknown symbol ieee80211_beacon_get_tim (err 0) [ 381.249924] ath10k_core: Unknown symbol ieee80211_hdrlen (err 0) [ 381.255951] ath10k_core: Unknown symbol ieee80211_start_rx_ba_session_offl (err 0) [ 381.263548] ath10k_core: Unknown symbol ieee80211_radar_detected (err 0) [ 381.270276] ath10k_core: Unknown symbol ieee80211_csa_is_complete (err 0) [ 381.277090] ath10k_core: Unknown symbol ieee80211_queue_work (err 0) [ 381.283475] ath10k_core: Unknown symbol cfg80211_find_vendor_ie (err 0) [ 381.290123] ath10k_core: Unknown symbol ieee80211_csa_finish (err 0) [ 381.296498] ath10k_core: Unknown symbol ieee80211_rx_napi (err 0) [ 381.330745] ath10k_pci: Unknown symbol ath10k_warn (err 0) [ 381.336261] ath10k_pci: Unknown symbol ath10k_err (err 0) [ 381.341699] ath10k_pci: Unknown symbol ath10k_print_driver_info (err 0) [ 381.348340] ath10k_pci: Unknown symbol ath10k_htt_hif_tx_complete (err 0) [ 381.355162] ath10k_pci: Unknown symbol ath10k_htc_tx_completion_handler (err 0) [ 381.362509] ath10k_pci: Unknown symbol ath10k_debug_get_new_fw_crash_data (err 0) [ 381.370020] ath10k_pci: Unknown symbol ath10k_core_create (err 0) [ 381.376143] ath10k_pci: Unknown symbol ath10k_htt_rx_pktlog_completion_handler (err 0) [ 381.384097] ath10k_pci: Unknown symbol ath10k_core_destroy (err 0) [ 381.390304] ath10k_pci: Unknown symbol ath10k_htc_rx_completion_handler (err 0) [ 381.397637] ath10k_pci: Unknown symbol ath10k_core_register (err 0) [ 381.403930] ath10k_pci: Unknown symbol ath10k_info (err 0) [ 381.409445] ath10k_pci: Unknown symbol backport_dependency_symbol (err 0) [ 381.416255] ath10k_pci: Unknown symbol ath10k_htt_t2h_msg_handler (err 0) [ 381.423072] ath10k_pci: Unknown symbol ath10k_core_unregister (err 0) [ 381.429537] ath10k_pci: Unknown symbol ath10k_htt_txrx_compl_task (err 0) Regards Oli ^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2016-10-24 18:10 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <b61ccf3c-1861-c8f8-ff7d-91c2b6ff4df5@gmail.com>
2016-10-15 14:00 ` compex wle900vx (ath10k) problem on 4.4.24 / armv7 Oliver Zemann
2016-10-15 14:44 ` Sebastian Gottschall
2016-10-15 17:04 ` Oliver Zemann
2016-10-18 16:22 ` Intel 7260 not working " Oliver Zemann
2016-10-18 19:06 ` Johannes Berg
2016-10-18 19:09 ` Johannes Berg
2016-10-18 19:44 ` Oliver Zemann
2016-10-18 19:56 ` Johannes Berg
2016-10-18 19:30 ` Emmanuel Grumbach
2016-10-18 19:31 ` Oliver Zemann
2016-10-21 16:25 ` compex wle900vx (ath10k) problem " Oliver Zemann
2016-10-21 16:54 ` Michal Kazior
2016-10-22 11:55 ` Jonas Gorski
2016-10-23 15:53 ` Oliver Zemann
2016-10-23 19:33 ` Jonas Gorski
2016-10-23 19:42 ` Oliver Zemann
2016-10-24 11:14 ` Jonas Gorski
2016-10-24 18:10 ` Oliver Zemann
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).