linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Cheek <joseph@cheek.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] 2.6.27 with compat-wireless-2008-12-31 stops transmitting every 2-3 mins
Date: Mon, 5 Jan 2009 15:01:32 -0500	[thread overview]
Message-ID: <4962671C.9080605@cheek.com> (raw)
In-Reply-To: <20090105181250.GD6834@tesla>

thanks, Luis!  comments below...

Luis R. Rodriguez wrote:
> Thanks for the details, this seems to be related to noise and therefore
> could be due to some issues with how we deal with ANI. We will have to
> try to reproduce this ourselves now and try to fix it.
>   

great!  i wish you luck!  would it help it i try the same test with the
problematic box right next to the AP?  I could move it upstairs to the
same room and retry an SCP or video serve.  not sure if that would give
you more useful data or not, but i can certainly move it.

if the box were quiet enough, i would keep it in the same room and just
connect via ethernet 8-).

>> I can try anything you need me to with respect to ath9k drivers or
>> kernels.  does it matter if bluetooth and/or ipv6 is enabled?  both are
>> enabled on this box but not on my laptop?
>>     
>
> Anything communication on the same spectrum affects your 802.11 connection,
> so using the microwave oven, using bluetooth, or a 2.4 GHz home phone should
> affet your connection. Not sure the freq used by Xbox / PS3 controllers...
> Bluetooth particularly should affect your 802.11 connection and we only recently
> added bluetooth coexistance to help with this but this is only available for
> more modern cards so your card does not have this feature.
>
> If you are using bluetooth then it should affect your connection if using the
> 2.4 GHz spectrum on your wirless AP.
>   

I didn't actually have the bluetooth in use, just the module built.  so
that might not be the problem.  the DIR-655 will do 5MHz only if it's in
n-only mode, and I have too many g devices in the house to want to
replace them all 8-).

>   Luis
>   

  parent reply	other threads:[~2009-01-05 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <495C7640.8060806@cheek.com>
2009-01-05 17:04 ` [ath9k-devel] 2.6.2{7, 8} with compat-wireless-2008-12-3{0, 1) drops link every 2-3 minutes Luis R. Rodriguez
2009-01-05 18:01   ` [ath9k-devel] 2.6.27 with compat-wireless-2008-12-31 stops transmitting " Joseph Cheek
2009-01-05 18:12     ` Luis R. Rodriguez
2009-01-05 19:47       ` Joseph Cheek
2009-01-05 19:51         ` Luis R. Rodriguez
2009-01-05 20:15           ` Luis R. Rodriguez
2009-01-05 20:01       ` Joseph Cheek [this message]
2009-01-06 15:42     ` Joseph Cheek
2009-01-15 18:37   ` [stable] [ath9k-devel] 2.6.2{7, 8} with compat-wireless-2008-12-3{0, 1) drops link " Greg KH
2009-01-15 20:25     ` Luis R. Rodriguez
2009-01-15 21:02       ` Greg KH

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=4962671C.9080605@cheek.com \
    --to=joseph@cheek.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.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).