linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Freitas <steve@newportit.com>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "ilw@linux.intel.com" <ilw@linux.intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [Ilw] Re: Slow throughput on Ultimate-N 6300
Date: Tue, 09 Jul 2013 22:44:31 -0700	[thread overview]
Message-ID: <51DCF4BF.5010900@newportit.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB3019FFDDF@HASMSX103.ger.corp.intel.com>

Emmanuel,

Thank you for your quick response!

It is a regression. I regularly had 300 Mbps speeds on this very access 
point, but it was years ago, in the 2.6 kernel series. However, I 
believe, from extensive online searches, that Intel has disabled the N 
functionality in the firmware on Linux, ostensibly until they (you? :-) 
) can fix whatever problem they were seeing. With the demise of the 
Intel Linux Wireless bug tracker, though, public tracking of the bug has 
been impossible. There are now-dead links to the defunct bug tracker 
over this very issue.

Sadly I only get 2 MByte/s on N, and under 1 MByte/s G.

I have not tried another access point in ages. Tired of replacing fried 
Netgears and Dlinks and Belkins, I've converted all my friends and 
families to Apple's access points. I'll try to locate something else and 
see how it goes.

Thanks again,

Steve

On 07/09/13 22:35, Grumbach, Emmanuel wrote:
>>> I understand that it's well-known that N is broken for Linux on this
>>> wireless chipset. You can add me to the list of those suffering under
>>> it. Can you provide me with a status update on work performed towards
>>> resolution of this issue?
>>>
>>> I'm on Debian unstable, kernel 3.9 amd64, using iwlwifi wireless
>>> firmware version 9.221.4.1 build 25532 on a Thinkpad T410, and I'm
>>> connected to an Apple Airport Extreme base station (3rd generation).
>>>
> Is this a regression?
> Has it worked better before?
>
> Also - did you try another access point? I seem to remember that we have had issues against Apple's access points.


  reply	other threads:[~2013-07-10  5:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51BBF4F1.1050301@newportit.com>
2013-07-10  4:04 ` Slow throughput on Ultimate-N 6300 Steve Freitas
2013-07-10  5:35   ` [Ilw] " Grumbach, Emmanuel
2013-07-10  5:44     ` Steve Freitas [this message]
2013-07-10  5:55       ` Grumbach, Emmanuel
2013-07-10  5:56         ` Steve Freitas
2013-07-12 18:02         ` Mariano Aliaga
2013-07-15 15:27           ` Emmanuel Grumbach

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=51DCF4BF.5010900@newportit.com \
    --to=steve@newportit.com \
    --cc=emmanuel.grumbach@intel.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).