System takes ages to find WLANs with ipw2200

Bug #291711 reported by Christoph Langner
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

 I own a FSC Lifebook S-6120 with a Intel Corporation PRO/Wireless 2200BG network chipset.

<snip>
$ lspci | grep Net
01:0d.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
</snip>

Right after starting my notebook i can't find any WLANs

<snip>
$ iwlist scan
[...]
eth1 No scan results
[...]
</snip>

When i watch dmesg i see that the firmware is found everything seams ok:

<snip>
$ dmesg | grep ipw
[ 31.650611] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
[ 31.650616] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 31.652564] ipw2200 0000:01:0d.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
[ 31.652654] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[ 31.652715] firmware: requesting ipw2200-bss.fw
[ 35.593734] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels)
</snip>

After about 30-45 minutes working without WLAN i notice that the little planets of the network manager start spinning and i loose my ethernet connection. When i click on the network manager icon inside my panel i see the missing networks, "iwlist scan" confirms this.

<snip>
$ uptime
 15:08:17 up 46 min, 2 users, load average: 0.32, 0.33, 0.39
$ iwlist scan | grep ESSID
[...]
                    ESSID:"dukath-ub"
                    ESSID:"<hidden>"
                    ESSID:"<hidden>"
                    ESSID:"eduroam"
                    ESSID:"dukath-ubx"
                    ESSID:"belwue"
                    ESSID:"802.1X"
                    ESSID:"VPN/WEB"
</snip>

When i now look at the dmes log i see tons of messages saying "ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command."

<snip>
$ dmesg | grep ipw
[ 31.650611] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
[ 31.650616] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 31.652564] ipw2200 0000:01:0d.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
[ 31.652654] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[ 31.652715] firmware: requesting ipw2200-bss.fw
[ 35.593734] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels)
[ 2713.210821] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.
[ 2725.715568] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.
[ 2744.363038] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.
[...]
[ 3565.084008] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.
</snip>

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
LsUsb:
 Bus 004 Device 002: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux-image-2.6.27-7-generic 2.6.27-7.15
ProcCmdLine: root=/dev/mapper/hostname-root ro quiet splash i8042.reset i8042.nomux
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-7.15-generic
SourcePackage: linux

Tags: apport-bug
Revision history for this message
Christoph Langner (chrissss) wrote :
Revision history for this message
Christoph Langner (chrissss) wrote :
Revision history for this message
Christoph Langner (chrissss) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Christoph,

This actually looks like a duplicate of bug 264104, care to take a peek. There are also some mentioned workarounds that you may want to try. The last comment posted there - https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/264104/comments/22 seems to indicate this will be retargetted to Jaunty. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Andy Whitcroft (apw) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.