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:56:48 -0700 [thread overview]
Message-ID: <51DCF7A0.5000301@newportit.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB3019FFE28@HASMSX103.ger.corp.intel.com>
Wonderful, thank you for the tips. I'll wade back into it tomorrow or
the next day and let you know what I find.
Thank you,
Steve
On 07/09/13 22:55, Grumbach, Emmanuel wrote:
>> 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.
>>
> 11n hasn't been disabled in firmware, but rather in driver.
> There is a bug we know about the "fail to flush tx fifo" thing that people reports (through mailing list or bugzilla of RedHat).
> Can you please send the output of the kerne log (dmesg)?
>
>> 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.
> No need to. If you say that it worked, then it should still work. The issue I was thinking is the way they use some fancy feature of WiFi that no one implements (besides the wifi module of their devices of course).
> Also, can you please try different firmwares from http://wireless.kernel.org/en/users/Drivers/iwlwifi#Download ?
> I wonder if newer firmware has made things worse. You may want to try older firmware.
> To do so, open the tarball from that you'll download and copy iwlwifi-*.ucode to /lib/firmware.
next prev parent reply other threads:[~2013-07-10 5:56 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
2013-07-10 5:55 ` Grumbach, Emmanuel
2013-07-10 5:56 ` Steve Freitas [this message]
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=51DCF7A0.5000301@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.