From: Johannes Berg <johannes@sipsolutions.net>
To: Oliver Zemann <oliver.zemann@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Intel 7260 not working on 4.4.24 / armv7
Date: Tue, 18 Oct 2016 21:06:18 +0200 [thread overview]
Message-ID: <1476817578.6425.40.camel@sipsolutions.net> (raw)
In-Reply-To: <fa098763-cdf6-03f8-6d75-0fa9dfb270e4@gmail.com> (sfid-20161018_182323_634850_59C65E60)
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
next prev parent reply other threads:[~2016-10-18 19:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1476817578.6425.40.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=oliver.zemann@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).