linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Roth <joelz@pobox.com>
To: Bob Copeland <me@bobcopeland.com>, linux-wireless@vger.kernel.org
Subject: Re: ath5k and Atheros AR242x - No scan results
Date: Thu, 16 Jul 2009 06:54:53 +0000	[thread overview]
Message-ID: <20090716065453.GA3154@sprite> (raw)
In-Reply-To: <20090716061457.GA1576@sprite>

On Wed, Jul 15, 2009 at 08:14:57PM -1000, Joel Roth wrote:
> On Mon, Jul 13, 2009 at 10:08:52AM -0400, Bob Copeland wrote:
> > On Sun, Jul 12, 2009 at 4:34 PM, Joel Roth<joelz@pobox.com> wrote:
> > > Vista advised me to:
> > >
> > > 1) turn on the hardware wifi switch <blush>
> > >
> > > 2) use the hotkey combination to enable wifi
> > 
> > It might be worth trying compat-wireless or 2.6.31-rcX.  Support
> > for reading the card's internal rfkill state was added in the
> > post-2.6.30 time-frame.
>  
> I installed compat-wireless against my 2.6.30.1 kernel,
> and also the iw command.
> 
> I've read some docs, however I'm not sure what the next step should be. 
> 
> My general idea is that I should be able to see a list of
> access points, however iwlist doesn't tell me anything new.
> 
> # iwlist wlan0 ap
> 
> wlan0     Interface doesn't have a list of Peers/Access-Points

After some RTFM'ing,

# iw wlan0 scan

BSS 00:40:05:c5:4f:19 (on wlan0) -- associated
	TSF: 9251942689 usec (0d, 02:34:11)
	freq: 2412
	beacon interval: 100
	capability: ESS PBCC (0x0041)
	signal: -40.00 dBm
	SSID: default
	Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0 
	DS Paramater set: channel 1
BSS 00:16:b6:db:fd:78 (on wlan0)
	TSF: 629448825249 usec (7d, 06:50:48)
	freq: 2437
	beacon interval: 100
	capability: ESS ShortSlotTime (0x0401)
	signal: -105.00 dBm
	SSID: linksys
	Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 
	DS Paramater set: channel 6
	ERP: Barker_Preamble_Mode
	Extended supported rates: 6.0 9.0 12.0 48.0 

# iw wlan0 connect default 

# dhclient wlan0

And voila! I have an IP address on wlan0.
I can't think of anything more that I need. :-)

Oh, maybe a pointer for others.

Perhaps I was just missing the iw 'connect' incantation?
'iwlist' was a complete red herring; didn't help me 
find my AP.

http://linuxwireless.org/en/users/Documentation was the only
site of several I visited mentioning 'iw' at all! 

And at linuxwireless, I find no example of using 'iw' to set
up a connection.  I'd be glad to contribute one.

Thanks Bob, Nick and others for your tips.


-- 
Joel Roth

  reply	other threads:[~2009-07-16  6:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 17:09 ath5k and Atheros AR242x - No scan results Joel Roth
2009-06-30 17:52 ` Luis R. Rodriguez
2009-06-30 18:25   ` Joel Roth
2009-06-30 18:34     ` Luis R. Rodriguez
2009-06-30 21:16 ` Nick Kossifidis
2009-07-01  7:24   ` Joel Roth
2009-07-04 19:10     ` Joel Roth
2009-07-12 11:23 ` Joel Roth
2009-07-12 15:08   ` Nick Kossifidis
2009-07-12 20:34     ` Joel Roth
2009-07-13 14:08       ` Bob Copeland
2009-07-14  6:54         ` Joel Roth
2009-07-16  6:14           ` Joel Roth
2009-07-16  6:54             ` Joel Roth [this message]
2009-07-16  8:46             ` Johannes Berg
2009-07-16 10:07               ` Joel Roth
2009-07-16 10:13                 ` Johannes Berg
2009-07-17  6:06                 ` Holger Schurig
2009-07-17  8:18                   ` Johannes Berg

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=20090716065453.GA3154@sprite \
    --to=joelz@pobox.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.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).