linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: linux-wireless@vger.kernel.org, ipw3945-devel@lists.sourceforge.net
Subject: Re: iwl3945 doesn't work
Date: Wed, 17 Oct 2007 15:59:28 +0200	[thread overview]
Message-ID: <20071017135928.GL5043@kernel.dk> (raw)
In-Reply-To: <20071017135452.GJ5043@kernel.dk>

On Wed, Oct 17 2007, Jens Axboe wrote:
> Hi,
> 
> Seeing that iwl3945 is now merged, I decided to switch my x60 to use
> that instead of ipw3945. That would leave me with zero kernel
> dependencies.
> 
> Unfortunately it doesn't work. Loading the module reveals the device:
> 
> 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.

I should mention that ipw3945 has always worked fine for me. And please
don't drop me from the CC list, I'm not subscribed to either of the
lists.

-- 
Jens Axboe


  reply	other threads:[~2007-10-17 13:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 13:54 iwl3945 doesn't work Jens Axboe
2007-10-17 13:59 ` Jens Axboe [this message]
2007-10-17 14:07 ` John W. Linville
2007-10-17 14:08 ` Ismail Dönmez
2007-10-17 14:11   ` Jens Axboe
2007-10-17 14:15     ` Ismail Dönmez
2007-10-17 14:17       ` Jens Axboe
2007-10-17 14:18     ` Dan Williams
2007-10-17 14:22       ` Jens Axboe
2007-10-17 15:16         ` Dan Williams
2007-10-17 16:35           ` Jens Axboe
2007-10-17 20:06             ` [ipw3945-devel] " Stephen Clark
2007-10-18  6:57               ` Jens Axboe
2007-10-18 12:23                 ` Stephen Clark
2007-10-18 12:33                   ` Johannes Berg
2007-10-18 13:02                     ` Tomas Winkler
2007-11-10  2:18                       ` Ian Schram
2007-11-15  0:53                         ` Ismail Dönmez
2007-11-15  9:39                           ` Jens Axboe
2007-11-15 10:23                             ` Pablo Sanchez
2007-11-15 10:26                               ` Jens Axboe
2007-11-15 10:30                                 ` Pablo Sanchez
2007-11-15 11:08                                   ` Jens Axboe
2007-11-15 15:05                                   ` Mike Kershaw
2007-11-15 15:09                                     ` Jens Axboe
2007-11-15 18:36                                     ` Pablo Sanchez
2007-11-15 15:10                             ` John W. Linville
2007-11-15 15:14                               ` Jens Axboe
2007-11-15 17:36                                 ` Ian Schram
2007-10-18 12:34                   ` Jens Axboe
2007-10-17 14:11 ` Dan Williams
2007-10-17 14:16   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2007-10-17 22:15 bmoss

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=20071017135928.GL5043@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --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).