On Thu, Mar 19, 2015 at 09:59:39AM +0100, Mattieu Baptiste wrote:
> On Thu, Mar 19, 2015 at 9:09 AM, Jonathan Gray <j...@jsg.id.au> wrote:
> >> It doesn't change anything.
> >> As soon as I set an address on the interface (manually or with
> >> dhclient), "mode 11g" is resetted and the errors in the logs are the
> >> same.
> >
> > Can you include the output of pcidump -v?
> >
> > It's possible you have an adapter that doesn't support 11a.
>
> Here it is:
The way your device is handled in Intel's Linux code is:
{IWL_PCI_DEVICE(0x08B2, 0xC262, iwl7260_n_cfg)},
Which is "Intel(R) Wireless N 7260"
http://ark.intel.com/products/75174/Intel-Wireless-N-7260
the 7260 adapters that can do multiple bands are
"Intel(R) Dual Band Wireless N 7260" iwl7260_2n_cfg
http://ark.intel.com/products/75440/Intel-Dual-Band-Wireless-N-7260
"Intel(R) Dual Band Wireless AC 7260"
iwl7260_2ac_cfg,iwl7260_2ac_cfg_high_temp
http://ark.intel.com/products/75439/Intel-Dual-Band-Wireless-AC-7260
The driver wrongly assumes all devices support 11a, this needs to be fixed.
Though the Linux code seems to make the band decision based on the EEPROM
not the sub device id.
> 3:0:0: Intel Dual Band Wireless AC 7260
> 0x0000: Vendor ID: 8086 Product ID: 08b2
> 0x0004: Command: 0006 Status: 0010
> 0x0008: Class: 02 Subclass: 80 Interface: 00 Revision: 6b
> 0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 10
> 0x0010: BAR mem 64bit addr: 0x00000000f0400000/0x00002000
> 0x0018: BAR empty (00000000)
> 0x001c: BAR empty (00000000)
> 0x0020: BAR empty (00000000)
> 0x0024: BAR empty (00000000)
> 0x0028: Cardbus CIS: 00000000
> 0x002c: Subsystem Vendor ID: 8086 Product ID: c262
> 0x0030: Expansion ROM Base Address: 00000000
> 0x0038: 00000000
> 0x003c: Interrupt Pin: 01 Line: 09 Min Gnt: 00 Max Lat: 00
> 0x00c8: Capability 0x01: Power Management
> 0x00d0: Capability 0x05: Message Signaled Interrupts (MSI)
> 0x0040: Capability 0x10: PCI Express
> Link Speed: 2.5 / 2.5 GT/s Link Width: x1 / x1
