From: Christian Lamparter <chunkeey@googlemail.com>
To: Bernd Schubert <bernd.schubert@fastmail.fm>
Cc: linux-wireless@vger.kernel.org
Subject: Re: carl9170 does not like all frequencies
Date: Sat, 13 Aug 2011 22:34:16 +0200 [thread overview]
Message-ID: <201108132234.16886.chunkeey@googlemail.com> (raw)
In-Reply-To: <j26l8a$ea9$1@dough.gmane.org>
On Saturday 13 August 2011 22:02:18 Bernd Schubert wrote:
> I bought a new usb wifi device with 2 antennas to get a better
> connection to my router.
So, you are saying that there was something wrong with the old
stick as well, right!?
> From point of few of connection strength that worked out very well, from
> point of view of connection stability that is total disaster so far.
Sure, you are affected by constant "loud" noise on the frequency/band.
The hardware is unable to finish the noise floor calibration and therefore
gives up.
> With Ubuntus 2.6.38-something it connects and then entirely fails after
> sending a few bytes. So I checked git log and noticed carl9170 is being
> used in recent kernels and connection issues have been fixed in 3.1-git.
what commits are you talking about?
> > [ 1058.936551] cfg80211: Calling CRDA to update world regulatory domain
> > [ 1058.945510] cfg80211: World regulatory domain updated:
> > [ 1058.945519] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> > [ 1058.945529] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> > [ 1058.945538] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> > [ 1058.945547] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> > [ 1058.945555] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> > [ 1058.945563] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> > [ 1058.945604] cfg80211: Calling CRDA for country: 97
> > [ 1061.373997] ieee80211 phy1: channel change: 2417 -> 2422 failed (2).
> > [ 1061.682115] ieee80211 phy1: channel change: -1 -> 2422 failed (2).
> > [ 1061.682132] usb 10-1.2: restart device (7)
> > [ 1062.096523] cfg80211: Calling CRDA to update world regulatory domain
> > [ 1062.105469] cfg80211: World regulatory domain updated:
>
>
> Any idea what is going on here? Do I need a crda tool? Or is something
> else failing?
Yes, you need crda, if you haven't installed it already.
> Update: While writing this up and after I plugged in my zd1211rw device,
> eventually also my tp-link carl9170 device connected a few minutes
> later. Do I always have to wait for 20 minutes to get a connection now?
That's odd. TP-Link does not sell any AR9170 anymore, in fact they dropped it
more than a year ago and replaced the line-up with AR7010+AR9287? so where
did you get this obsolete device?
Regards,
Chr
next prev parent reply other threads:[~2011-08-13 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 20:02 carl9170 does not like all frequencies Bernd Schubert
2011-08-13 20:07 ` Bernd Schubert
2011-08-13 20:34 ` Christian Lamparter [this message]
2011-08-13 20:51 ` Bernd Schubert
2011-08-13 21:11 ` Christian Lamparter
2011-08-13 21:34 ` Bernd Schubert
2011-08-13 21:45 ` Bernd Schubert
2011-08-13 21:27 ` Bernd Schubert
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=201108132234.16886.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=bernd.schubert@fastmail.fm \
--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).