On Wed, 2007-10-17 at 16:22 +0200, Jens Axboe wrote: > On Wed, Oct 17 2007, Dan Williams wrote: > > On Wed, 2007-10-17 at 16:11 +0200, Jens Axboe wrote: > > > On Wed, Oct 17 2007, Ismail Dönmez wrote: > > > > Wednesday 17 October 2007 Tarihinde 16:54:53 yazm????t??: > > > > > 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. > > > > > > > > Same issue here, try iwlist wlan0 scan first and then it should work. > > > > > > Huh indeed, now it links fine! Thanks for the hint. Would be nice to > > > have fixed, though :-) > > > > Odd, doesn't the driver need to do a scan _anyway_ to find the right > > 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 report 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 either > > (a) not scanning before trying to associate, or (b) not sending out scan > > completion events after it's done a scan. > > Indeed, there is now Scan request completed before I run the iwlist > scan. iwevent output: Hmm, the output below doesn't show the scan request completed, right? > 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:****-****-** Security 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 So you only get this when you manually scan right after setting the ssid and key? Dan > 16:20:54.025085 wlan0 Custom driver > event:ASSOCINFO(ReqIEs=000e6b6a656c6c626572676178626f65010402040b16 > RespIEs=010482848b96dd0c00037f0201015b0002a44000) > 16:20:54.025123 wlan0 New Access Point/Cell address:00:13:46:97:33:E2 > > bingo, it associates and it now works. > - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
