From: Jonathan McDowell <noodles@earth.li>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Intel Linux Wireless <ilw@linux.intel.com>
Subject: Re: Intel 7260 not working in 802.11n mode
Date: Mon, 7 Apr 2014 07:45:56 +0100 [thread overview]
Message-ID: <20140407064556.GN24850@earth.li> (raw)
In-Reply-To: <CANUX_P3H=F1C1H6NvdvpTHQh1JqvPjvyUjAygSQgeNyZ-q6=ZQ@mail.gmail.com>
On Mon, Apr 07, 2014 at 08:00:19AM +0300, Emmanuel Grumbach wrote:
> On Mon, Apr 7, 2014 at 3:36 AM, Jonathan McDowell <noodles@earth.li> wrote:
> >
> > I have an Intel 7260 that fails to associate correctly in 802.11n mode.
> > Unfortunately I don't have any access to the AP in question, but I
> > believe it is an ASUS based device. This is on the 5GHz band; there is
> > some odd configuration with the router that results in the driver
> > refusing to associate on the 2.4GHz setup with the following error:
> >
> > [ 507.495986] iwlwifi 0000:02:00.0: AP 30:00:da:b1:da:d0 beacon interval is 7, refusing due to firmware bug!
>
> Ok - this is an interesting settings.
> I'll check with our firmware team what can be done here, but beacon
> interval=7 is really insane. I can't find what the spec defines as
> legal values right now.
I wouldn't rule out the person who configured the AP having made a
mistake; the MAC address is a custom one so they may have tweaked other
settings too. However my phone (running Android) can connect to the
2.4GHz AP just fine and I think the other users of the AP are running
Macs without problems.
> > On the 5GHz band the driver attempts to associate, but never seems to
> > actually fully associate to the point of getting an IP. If I pass the
> > 11n_disable=1 parameter to the driver then things work fine.
> >
> This is surprising - can you share your logs?
The log below is without the 11n_disable flag set - if it helps I can
provide the log of when it works too.
> > I've put a debug log of the failure to associate (kernel 3.14 but this
> > has happened with all the version I've tried) up at:
> >
> > http://the.earth.li/~noodles/iwlwifi-fail.log
> >
>
> I can't access: Access forbidden.
Sorry, fixed.
> > If there is more information I should be providing please let me know.
> > I'm sure it's related to the AP in question as I've had successful 11n
> > associations with other setups, but it's annoying to have to explicitly
> > disable 11n when in this location and then not in others.
J.
--
/-\ | Where's your fishing rod, lawn
|@/ Debian GNU/Linux Developer | ornament?
\- |
next prev parent reply other threads:[~2014-04-07 6:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 0:36 Intel 7260 not working in 802.11n mode Jonathan McDowell
2014-04-07 5:00 ` Emmanuel Grumbach
2014-04-07 6:45 ` Jonathan McDowell [this message]
2014-04-07 7:00 ` [Ilw] " Grumbach, Emmanuel
2014-04-07 15:23 ` Jonathan McDowell
2014-04-13 11:07 ` Grumbach, Emmanuel
2014-04-16 6:10 ` Jonathan McDowell
2014-04-16 19:58 ` Grumbach, Emmanuel
2014-04-17 17:31 ` Jonathan McDowell
2014-04-17 19:36 ` Grumbach, Emmanuel
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=20140407064556.GN24850@earth.li \
--to=noodles@earth.li \
--cc=egrumbach@gmail.com \
--cc=ilw@linux.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).