linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas <messier31@gmx.net>
To: linux-wireless@vger.kernel.org
Subject: Re: carl9170 802.11n-AP
Date: Sun, 12 Dec 2010 18:47:56 +0100	[thread overview]
Message-ID: <ie31sg$rqv$1@dough.gmane.org> (raw)
In-Reply-To: AANLkTimiNLZ8EFPEwbKW3UA7FMSxmJOV-B9pWY4h9c34@mail.gmail.com

Hi,

thanks for your answer.
I am afraid I am too much of a linux noob to solve this on my own.
Its not the Intel driver that crashes but carl9170. But I am going to test 
this with other wifi cards as well and then post the results here.

Get well soon! (for carl9170 sake :D)

Regards,

Thomas

Christian Lamparter wrote:

> On Sun, Dec 12, 2010 at 11:14 AM, thomas
> <messier31@gmx.net> wrote:
>> I just saw that there could be "aggregation stalls" with "any Intel N
>> Wifi Link".
>> I am using Intel Wifi Link 5100 and the driver frequently restarts under
>> heavy load.
> 
> see Intel's bugzilla, lots of angry posts there:
> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2214#c19 (etc...)
> 
> I am ill, so you'll have to do the research on iwlwifi vs. carl9170 on
> your own, but it's all there just take a look at the original vendor
> driver(otus)+firmware(ar9170fw).
> 
> Regards,
>    Chr
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
> in the body of a message to
> majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2010-12-12 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12  9:17 carl9170 802.11n-AP thomas
2010-12-12 10:14 ` thomas
2010-12-12 17:05   ` Christian Lamparter
2010-12-12 17:47     ` Thomas [this message]
2010-12-13 17:24     ` Thomas
  -- strict thread matches above, loose matches on Subject: below --
2011-01-20 10:28 Helge Lenz
2011-01-20 18:31 ` Christian Lamparter

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='ie31sg$rqv$1@dough.gmane.org' \
    --to=messier31@gmx.net \
    --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).