Deauthentication for reason 6 using Intel 5300 in 2.6.34

Deauthentication for reason 6 using Intel 5300 in 2.6.34

[Larry Finger]

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?

Thanks,

Larry

Re: Deauthentication for reason 6 using Intel 5300 in 2.6.34

[Rafał Miłecki]

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

-- 
Rafał

Re: Deauthentication for reason 6 using Intel 5300 in 2.6.34

[Guy, Wey-Yi]

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
 

Re: Deauthentication for reason 6 using Intel 5300 in 2.6.34

[Rafał Miłecki]

W dniu 31 października 2010 16:31 użytkownik Guy, Wey-Yi
<wey-yi.w.guy@intel.com> napisał:
> On Sun, 2010-10-31 at 02:38 -0700, Rafał Miłecki wrote:
>> 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.

What about now? After another month of waiting? I'd love to replace
that Intel but it's integrated.

If it takes so long to pass regulatory, maybe Intel should change sth?
Right now?

There is just another user complaining for that:
http://permalink.gmane.org/gmane.linux.kernel.wireless.general/61320

-- 
Rafał

Re: Deauthentication for reason 6 using Intel 5300 in 2.6.34

[Guy, Wey-Yi]

Hi Larry,

On Sat, 2010-10-30 at 20:31 -0700, Larry Finger wrote:
> 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?
I could be the same "tid not match" problem we seen on 2.6.35, but
different behavior. We are really working hard and try to release the
experimental versoin of the uCode; but we have to pass the regulatory
first which cause delay. I understand the need for it and I am working
my best to push it happen ASAP.

Thanks
Wey