From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>,
"Zheng, Jiajia" <jiajia.zheng@intel.com>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: Deauthentication for reason 6 using Intel 5300 in 2.6.34
Date: Sun, 31 Oct 2010 08:31:40 -0700 [thread overview]
Message-ID: <1288539100.14805.16.camel@wwguy-ubuntu> (raw)
In-Reply-To: <AANLkTin_dPPk8XBKWjEbuHmQJg3zok5bUcrrn99qV6dn@mail.gmail.com>
Hi Rafal,
On Sun, 2010-10-31 at 02:38 -0700, Rafał Miłecki wrote:
> 2010/10/31 Larry Finger <Larry.Finger@lwfinger.net>:
> > A user on the openSUSE forum reports that the connection drops frequently when
> > using 802.11n on a 5300 with a 2.6.34 kernel. It is deauthenticated for reason
> > 6. He was able to stabilize the connection by disabling N mode. I think he used
> > "options iwlagn 11n_disable=1 11n_disable50=1".
> >
> > Is this a known problem? Would the situation be improved by using
> > compat-wireless? If so, is "bleeding-edge" needed?
>
> It's fu* known problem. Intel doesn't seem to care about users, they
> have fixed firmware but didn't decide to release it for 2 months.
>
> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2214#c19
>
We do care very much, really sorry the delay. we need to pass regulatory
before we can release it. I am doing everything I can to move the
process as fast as it can.
Wey
next prev parent reply other threads:[~2010-10-31 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 3:31 Deauthentication for reason 6 using Intel 5300 in 2.6.34 Larry Finger
2010-10-31 9:38 ` Rafał Miłecki
2010-10-31 15:31 ` Guy, Wey-Yi [this message]
2010-12-12 18:50 ` Rafał Miłecki
2010-10-31 15:26 ` Guy, Wey-Yi
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=1288539100.14805.16.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=Larry.Finger@lwfinger.net \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jiajia.zheng@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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).