From: Dan Williams <dcbw@redhat.com>
To: Alistair John Strachan <alistair@devzero.co.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k working, almost
Date: Sun, 27 Jul 2008 10:59:21 -0400 [thread overview]
Message-ID: <1217170761.2700.12.camel@localhost.localdomain> (raw)
In-Reply-To: <200807261742.15693.alistair@devzero.co.uk>
On Sat, 2008-07-26 at 17:42 +0100, Alistair John Strachan wrote:
> Hi,
>
> The newly announced ath9k driver works great on an AR5418 Core 2 Duo Macbook,
> WPA2-TKIP/AES et al all work fine. It would be good to see this driver in
> wireless-testing, it completely replaces madwifi for me. I used linux.git
> (2.6.26) + wireless-testing.git + my-wireless-testing.git with success.
>
> The only thing that I couldn't get working was the signal strength meter in
> knetworkmanager. The AP signal strength shows up in iwlist ath0 scanning, but
> whatever NM uses doesn't seem to work. All is good with madwifi, by
> comparison.
>
> Any ideas? NM issue?
The signal strength code in NM hasn't changed for quite a long time.
Chances are it's the driver not reporting correctly. What's the
iwconfig output for while you're connected to your AP?
Link Quality=92/100 Signal level=-36 dBm Noise level=-91 dBm
That's the line I care about.
Dan
next prev parent reply other threads:[~2008-07-27 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 16:42 ath9k working, almost Alistair John Strachan
2008-07-26 18:15 ` Luis R. Rodriguez
2008-07-26 19:30 ` Alistair John Strachan
2008-07-26 19:36 ` Luis R. Rodriguez
2008-07-26 19:55 ` Alistair John Strachan
2008-07-27 14:59 ` Dan Williams [this message]
2008-07-27 15:07 ` Luis R. Rodriguez
2008-07-27 16:20 ` Alistair John Strachan
2008-07-27 16:30 ` Luis R. Rodriguez
2008-07-27 19:11 ` Stefanik Gábor
2008-07-27 23:11 ` Russell Senior
2008-08-04 18:30 ` Luis R. Rodriguez
2008-08-04 18:29 ` Luis R. Rodriguez
2008-08-04 18:32 ` Luis R. Rodriguez
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=1217170761.2700.12.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=alistair@devzero.co.uk \
--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).