From: "Hanno Böck" <hanno@hboeck.de>
To: linux-wireless@vger.kernel.org
Subject: firmware loading fails (iwl 7260)
Date: Fri, 28 Nov 2014 00:40:32 +0100 [thread overview]
Message-ID: <20141128004032.441c4670@pc> (raw)
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Hi,
I have an X1 Carbon laptop with an intel 7260 chip.
The automatic firmware loading doesn't work (kernel 3.17.2). I get this
in dmesg:
[ 1.615155] iwlwifi 0000:03:00.0: Direct firmware load for
iwlwifi-7260-10.ucode failed with error -2
The firmware then gets loaded by the userspace helper, however as far
as I understand it (and the description of the kernel option) this is
deprecated and shouldn't be used. Also, it takes quite a while
(minutes) till the wifi is available after boot which is quite annoying.
Any idea what I should do to debug/fix this? Is this a bug? (firmware
is the latest from intel's page, 23.10.10.0)
cu,
--
Hanno Böck
http://hboeck.de/
mail/jabber: hanno@hboeck.de
GPG: BBB51E42
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-11-27 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 23:40 Hanno Böck [this message]
2014-11-28 0:15 ` firmware loading fails (iwl 7260) Vladimir Zapolskiy
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=20141128004032.441c4670@pc \
--to=hanno@hboeck.de \
--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