linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Peter Xu <peterx@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-wireless@vger.kernel.org
Subject: Re: Intel Wireless 7260 failed to work
Date: Tue, 27 Dec 2016 10:41:22 -0600	[thread overview]
Message-ID: <a1fbf107-24df-d9e8-1c69-78025c70a79c@lwfinger.net> (raw)
In-Reply-To: <20161227091706.GA20895@pxdev.xzpeter.org>

On 12/27/2016 03:17 AM, Peter Xu wrote:
> Hello,
>
> Looks like latest Linux master (4.10-rc1, 7ce7d89f) cannot work well
> with my wireless card, which is:
>
>   Intel Corporation Wireless 7260 (rev bb)
>
> Boot message shows that no suitable firmware found:
>
>     # journalctl -kp3
>     Dec 27 16:38:00 kernel: Error parsing PCC subspaces from PCCT
>     Dec 27 16:38:00 kernel: mmc0: Unknown controller version (3). You may experience problems.
>     Dec 27 16:38:02 kernel: DMAR: DRHD: handling fault status reg 2
>     Dec 27 16:38:02 kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 7200000000 [fault reason 05] PTE Write a
>     Dec 27 16:38:03 kernel: tpm tpm0: A TPM error (6) occurred attempting to read a pcr value
>     Dec 27 16:38:04 kernel: iwlwifi 0000:03:00.0: no suitable firmware found!
>
> Linux stable/master (Linux 4.8-rc8, 08895a8b6b) works for me. And no
> further tests have been done yet.
>
> Is this a known issue? Please let me know if anyone wants more info or
> logs, since this error triggers easily (everytime I boot).
>

The problem appears to be specific for your system. On my Toshiba Tecra A50A, 
kernel 4.10-rc1 the driver works the same as in earlier kernels. The dmesg log 
shows the following:

[    4.760600] Intel(R) Wireless WiFi driver for Linux
[    4.760601] Copyright(c) 2003- 2015 Intel Corporation
[    4.799519] iwlwifi 0000:04:00.0: loaded firmware version 17.352738.0 op_mode 
iwlmvm
[    4.880820] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
[    4.883340] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[    4.883584] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled

I'm not sure if the driver would look for firmware version 16 if 17 would not be 
available, but I think it would.

Check for firmware file /lib/firmware/iwlwifi-7260-17.ucode. If that is not 
present for your distro, it is in the repo at 
git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git.

If that firmware is present, or if adding it does not help, my next suggestion 
is to bisect between 4.8 and the current version to see where the problem was 
introduced. I would not limit the bisection to the Intel wireless drivers as the 
problem could be in the underlying PCIe support for your hardware. By the way, 
that bisection will require about 14 steps.

Larry

  reply	other threads:[~2016-12-27 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27  9:17 Intel Wireless 7260 failed to work Peter Xu
2016-12-27 16:41 ` Larry Finger [this message]
2016-12-28  3:50   ` Peter Xu
2016-12-27 19:46 ` Kalle Valo
2016-12-28  3:59   ` Peter Xu
2016-12-28  7:27     ` Luca Coelho
2016-12-28  8:10       ` Peter Xu
2016-12-28  8:17         ` Emmanuel Grumbach
2016-12-28  8:37           ` Luca Coelho
2016-12-28 12:13       ` Kalle Valo

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=a1fbf107-24df-d9e8-1c69-78025c70a79c@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peterx@redhat.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).