[jaunty] Network Manager doesn't trigger a wlan scan

[Per Buer]

Binary package hint: network-manager

Upon login or resume Network Manager sometimes doesn't connect to the wireless network. "sudo iwlist wlan1 scanning" normally trigges something which makes NM detect the network.

This might be related - doing a "sudo iwlist wlan1 scanning" immediately after resume can sometimes return an empty list.

perbu@thimk:~$ uname -a
Linux thimk 2.6.28-11-generic #36-Ubuntu SMP Fri Mar 20 19:40:40 UTC 2009 i686 GNU/Linux
perbu@thimk:~$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

This is a IBM Thinkpad X60. lspci -vvv attached.

[Alexander Sack (asac)]

please reboot system, reproduce and attach your full syslog. Thanks.

[Alexander Sack (asac)]

actualy i only want to know which wifi driver you use and which chipsets.

[Per Buer (perbu)]

The driver involved is the iwl3945, the driver logs the following:
[ 13.182742] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
[ 13.182746] iwl3945: Copyright(c) 2003-2008 Intel Corporation
[ 13.182865] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 13.182879] iwl3945 0000:03:00.0: setting latency timer to 64
[ 13.182952] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
[ 13.238020] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels

I believe the chipset is 82801G.

This only happends in approx 10% of the resumes.

[Victor Vargas (kamus)]

Since this report have a long time without activity, could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]