diff mbox

iwlwifi crash with 3.13

Message ID 52E16978.3040602@gmail.com (mailing list archive)
State Not Applicable, archived
Headers show

Commit Message

Emmanuel Grumbach Jan. 23, 2014, 7:11 p.m. UTC 
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.

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.

Can you please try the patch attached?
I will prevent the driver from trying to work on A band while the HW
doesn't allow.

emmanuel

Comments

Petko Manolov Jan. 23, 2014, 8:19 p.m. UTC | #1 
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
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

From dd40219d34426e4f9c7d1b10653ece3dc67588c5 Mon Sep 17 00:00:00 2001
From: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date: Thu, 5 Dec 2013 22:42:55 +0200
Subject: [PATCH] iwlwifi: mvm: don't allow A band if SKU forbids it

Change-Id: I920b7c53dc05a41de43ab9762eb7853dc4bed1ed
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
---
 drivers/net/wireless/iwlwifi/iwl-nvm-parse.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/net/wireless/iwlwifi/iwl-nvm-parse.c b/drivers/net/wireless/iwlwifi/iwl-nvm-parse.c
index 1fce0ec..9600afc 100644
--- a/drivers/net/wireless/iwlwifi/iwl-nvm-parse.c
+++ b/drivers/net/wireless/iwlwifi/iwl-nvm-parse.c
@@ -192,6 +192,10 @@  static int iwl_init_channel_map(struct device *dev, const struct iwl_cfg *cfg,
 			continue;
 		}
 
+		if (ch_idx >= NUM_2GHZ_CHANNELS &&
+		    !data->sku_cap_band_52GHz_enable)
+			continue;
+
 		channel = &data->channels[n_channels];
 		n_channels++;
 
-- 
1.8.1.msysgit.1