From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ra.tuxdriver.com ([70.61.120.52]:2353 "EHLO ra.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752770AbXJQPJu (ORCPT ); Wed, 17 Oct 2007 11:09:50 -0400 Date: Wed, 17 Oct 2007 10:07:45 -0400 From: "John W. Linville" To: Jens Axboe Cc: linux-wireless@vger.kernel.org, ipw3945-devel@lists.sourceforge.net Subject: Re: iwl3945 doesn't work Message-ID: <20071017140745.GB5744@tuxdriver.com> (sfid-20071017_160953_763757_99F4487B) References: <20071017135452.GJ5043@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20071017135452.GJ5043@kernel.dk> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Oct 17, 2007 at 03:54:53PM +0200, Jens Axboe wrote: > iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for > Linux, 1.1.17ks > iwl3945: Copyright(c) 2003-2007 Intel Corporation > ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 21 > PCI: Setting latency timer of device 0000:03:00.0 to 64 > iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection > iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels > phy0: Selected rate control algorithm 'iwl-3945-rs' > > # iwconfig wlan0 > wlan0 IEEE 802.11g ESSID:"xxxxxxxxxxxxxx" > Mode:Managed Channel:0 Access Point: Not-Associated > Tx-Power=0 dBm > Retry min limit:7 RTS thr:off Fragment thr=2346 B > Encryption key:XXXX-XXXX-XX > Link Quality:0 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > and iwconfig sees it, essid/enc settings are fine, but I don't get a > link. Seems like "so far, so good" except for the "don't get a link" part...what is the output of iwlist wlan0 scan? John -- John W. Linville linville@tuxdriver.com