linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Clark <Stephen.Clark@seclark.us>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "Dan Williams" <dcbw@redhat.com>,
	linux-wireless@vger.kernel.org,
	"Ismail Dönmez" <ismail@pardus.org.tr>,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] iwl3945 doesn't work
Date: Wed, 17 Oct 2007 16:06:55 -0400	[thread overview]
Message-ID: <47166B5F.1010804@seclark.us> (raw)
In-Reply-To: <20071017163519.GC15552@kernel.dk>

Jens Axboe wrote:

>On Wed, Oct 17 2007, Dan Williams wrote:
> =20
>
>>On Wed, 2007-10-17 at 16:22 +0200, Jens Axboe wrote:
>>   =20
>>
>>>On Wed, Oct 17 2007, Dan Williams wrote:
>>>     =20
>>>
>>>>On Wed, 2007-10-17 at 16:11 +0200, Jens Axboe wrote:
>>>>       =20
>>>>
>>>>>On Wed, Oct 17 2007, Ismail D=F6nmez wrote:
>>>>>         =20
>>>>>
>>>>>>Wednesday 17 October 2007 Tarihinde 16:54:53 yazm????t??:
>>>>>>           =20
>>>>>>
>>>>>>>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 de=
vice:
>>>>>>>
>>>>>>>iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection dri=
ver for
>>>>>>>Linux, 1.1.17ks
>>>>>>>iwl3945: Copyright(c) 2003-2007 Intel Corporation
>>>>>>>ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IR=
Q 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=3D0 dBm
>>>>>>>          Retry min limit:7   RTS thr:off   Fragment thr=3D2346 =
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 g=
et a
>>>>>>>link.
>>>>>>>             =20
>>>>>>>
>>>>>>Same issue here, try iwlist wlan0 scan first and then it should w=
ork.
>>>>>>           =20
>>>>>>
>>>>>Huh indeed, now it links fine! Thanks for the hint. Would be nice =
to
>>>>>have fixed, though :-)
>>>>>         =20
>>>>>
>>>>Odd, doesn't the driver need to do a scan _anyway_ to find the righ=
t
>>>>BSSID to associate with if the cached scan results are more than a =
few
>>>>seconds old?  Can you run '/sbin/iwevent' before trying a fresh
>>>>association, try to associate, ensure that it has failed, and repor=
t the
>>>>output?
>>>>
>>>>If you don't get something like:
>>>>
>>>>10:17:05.117937   eth1     Scan request completed
>>>>
>>>>shown there, then there's likely a bug in the driver because it's e=
ither
>>>>(a) not scanning before trying to associate, or (b) not sending out=
 scan
>>>>completion events after it's done a scan.
>>>>       =20
>>>>
>>>Indeed, there is now Scan request completed before I run the iwlist
>>>scan. iwevent output:
>>>     =20
>>>
>>Hmm, the output below doesn't show the scan request completed, right?
>>
>>   =20
>>
>>>Waiting for Wireless Events from interfaces...
>>>16:20:27.453588   wlan0    Set Mode:Managed
>>>16:20:27.462104   wlan0    Set Encryption key:off
>>>16:20:27.463940   wlan0    Set Encryption key:****-****-**   Securit=
y mode:open
>>>16:20:27.466535   wlan0    Set ESSID:"kjellbergaxboe"
>>>
>>>waiting, nothing else happens. Then run iwlist scan from another
>>>terminal.
>>>
>>>16:20:53.892549   wlan0    Scan request completed
>>>     =20
>>>
>>So you only get this when you manually scan right after setting the s=
sid
>>and key?
>>   =20
>>
>
>If you look at the time stamp, I ran the iwlist scan about 26 seconds
>after loading the module. When the module is loaded, the networking
>script sets the essid and encryption key.
>
>So yes, I only get that 'Scan request completed' line after running
>iwlist scan manually.
>
> =20
>
Don't know whether this is related, but I was having all kinds of=20
trouble getting associated,
iwlist eth1 scan would report no scan results, I then switched to=20
loading the kernel module with
the option that tells  iwl3945 to do software scanning and it works=20
everytime now.

Steve

--=20

"They that give up essential liberty to obtain temporary safety,=20
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty=20
decreases."  (Thomas Jefferson)



-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

Thread overview: 32+ 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
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             ` Stephen Clark [this message]
2007-10-18  6:57               ` [ipw3945-devel] " 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

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=47166B5F.1010804@seclark.us \
    --to=stephen.clark@seclark.us \
    --cc=dcbw@redhat.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=ismail@pardus.org.tr \
    --cc=jens.axboe@oracle.com \
    --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).