From: Petko Manolov <petkan@nucleusys.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>
Subject: Re: iwlwifi crash with 3.13
Date: Thu, 23 Jan 2014 22:19:22 +0200 [thread overview]
Message-ID: <20140123201922.GB4064@localhost> (raw)
In-Reply-To: <52E16978.3040602@gmail.com>
On 14-01-23 21:11:52, Emmanuel Grumbach wrote:
> Ok - I put the pieces together:
>
> > iwlwifi 0000:01:00.0: loaded firmware version 22.15.8.0 op_mode iwlmvm
> > iwlwifi 0000:01:00.0: Detected Intel(R) Wireless N 7260, REV=0x144
>
> This means that your NIC is 2.4GHz only. Dual band NICs print something
> else.
This isn't correct. My NIC happily connects to my crappy Linksys WRT610Nv1 at 5GHz. After a while the router's (5GHz) radio dies, but before
that i am able to easily do more than 100Mbps.
iwconfig output:
wlan0 IEEE 802.11abgn ESSID:"xxxxxxx"
Mode:Managed Frequency:5.745 GHz Access Point: xx:xx:xx:xx:xx:xx
Bit Rate=135 Mb/s Tx-Power=16 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=64/70 Signal level=-46 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:9 Invalid misc:3 Missed beacon:0
> Now here come the catch. You seem to have an "old" NIC in a way that the
> NVM (EEPROM like) is old. In that NVM, there was a bug that advertised
> the A band channels but disabled the A band in SKU cap.
iwlwifi-7260-7 ucode works fine for both bands. iwlwifi-7260-8.ucode seems unable to connect at 5GHz.
> Can you please try the patch attached?
Do you still think it is a good idea to apply and test the patch?
Petko
next prev parent reply other threads:[~2014-01-23 20:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 9:16 iwlwifi crash with 3.13 Petko Manolov
2014-01-23 9:22 ` Grumbach, Emmanuel
2014-01-23 12:31 ` Petko Manolov
2014-01-23 12:34 ` Grumbach, Emmanuel
2014-01-23 12:45 ` Grumbach, Emmanuel
2014-01-23 19:11 ` Emmanuel Grumbach
2014-01-23 20:19 ` Petko Manolov [this message]
2014-01-23 20:00 ` Petko Manolov
2014-01-23 20:07 ` Emmanuel Grumbach
2014-01-23 20:21 ` Petko Manolov
2014-02-07 21:40 ` Petko Manolov
2014-02-08 18:10 ` Emmanuel Grumbach
2014-02-09 13:26 ` Petko Manolov
2014-02-09 13:31 ` Grumbach, Emmanuel
2014-02-09 13:49 ` Petko Manolov
2014-02-07 11:08 ` Niklas Claesson
2014-02-08 18:11 ` Emmanuel Grumbach
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=20140123201922.GB4064@localhost \
--to=petkan@nucleusys.com \
--cc=egrumbach@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).