From: Petri Lehtinen <petri@digip.org>
To: linux-wireless@vger.kernel.org
Subject: Intel 8265 iwlwifi broken recent linux-firmware
Date: Wed, 7 Nov 2018 07:34:39 +0200 [thread overview]
Message-ID: <20181107053439.GA2730@ping.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
Loading iwlwifi produces the following messages to dmesg. Trying to
bring the wifi interface up also fails.
[Tue Oct 23 07:17:12 2018] iwlwifi 0000:3a:00.0: loaded firmware version 36.7596afd4.0 op_mode iwlmvm
[Tue Oct 23 07:17:12 2018] iwlwifi 0000:3a:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[Tue Oct 23 07:17:13 2018] iwlwifi 0000:3a:00.0: SecBoot CPU1 Status: 0x3040001, CPU2 Status: 0x0
[Tue Oct 23 07:17:13 2018] iwlwifi 0000:3a:00.0: Failed to start INIT ucode: -110
[Tue Oct 23 07:17:13 2018] iwlwifi 0000:3a:00.0: Failed to run INIT ucode: -110
I'm on Arch Linux, and linux-firmware is built from commit d877533.
With older firmware (commit f1b95fe), it works with this in dmesg
output:
[Tue Oct 23 07:28:51 2018] iwlwifi 0000:3a:00.0: enabling device (0000 -> 0002)
[Tue Oct 23 07:28:51 2018] iwlwifi 0000:3a:00.0: loaded firmware version 36.e91976c0.0 op_mode iwlmvm
[Tue Oct 23 07:28:51 2018] iwlwifi 0000:3a:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[Tue Oct 23 07:28:51 2018] iwlwifi 0000:3a:00.0: base HW address: 00:28:f8:87:a2:e9
Kernel version is 4.18.16, the machine is a Lenovo T470s. I'm happy to
provide more info!
Petri
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-11-07 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 5:34 Petri Lehtinen [this message]
2018-11-07 6:57 ` Intel 8265 iwlwifi broken recent linux-firmware Emmanuel Grumbach
2018-11-07 8:07 ` Intel 8265 iwlwifi broken on " Petri Lehtinen
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=20181107053439.GA2730@ping.localdomain \
--to=petri@digip.org \
--cc=linux-wireless@vger.kernel.org \
/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