Ubuntu
linux-source-2.6.15 package

ipw2200 card is not working

Bug #41570 reported by Manuel Teira
10
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

On my Toshiba Satellite L20, centrino based laptop, wireless card is not longer working since updated to dapper (it worked under breezy). I'm using wep in my AP with 64 bits key length.
It seems it is not able to associate with the AP, as kismet is able to get packets from the card and iwlist eth0 scan is able to locate my access-point.

Significant syslog messages are:

[4294685.008000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[4294685.010000] 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
[4294685.190000] ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 17 (level, low) -> IRQ 169
[4294685.190000] PCI: Setting latency timer of device 0000:00:1e.2 to 64
[4294685.222000] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
...
[4294685.620000] ieee80211_crypt: registered algorithm 'WEP'
...
[4294686.735000] eth1: NETDEV_TX_BUSY returned; driver should report queue full
via ieee_device->is_queue_full.

iwconfig returns:

eth1 unassociated ESSID:"VIGO"
          Mode:Managed Channel=0 Access Point: Not-Associated
          Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0
          Retry limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          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 ifconfig eth1:

eth1 Link encap:Ethernet HWaddr 00:13:CE:3D:CF:77
          inet addr:172.26.0.3 Bcast:172.26.0.255 Mask:255.255.255.0
          inet6 addr: fe80::213:ceff:fe3d:cf77/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1976 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2372 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:169 Base address:0x8000 Memory:b0102000-b0102fff

iwlist eth1 scan:

mteira@piton:~$ iwlist eth1 scan
eth1 Scan completed :
          Cell 01 - Address: 00:16:38:89:39:91
                    ESSID:"VIGO"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:12
                    Encryption key:on
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
                    Quality=86/100 Signal level=-44 dBm
                    Extra: Last beacon: 712ms ago
          Cell 02 - Address: 00:16:38:89:39:91
                    ESSID:"<hidden>"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:12
                    Encryption key:on
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
                    Quality=95/100 Signal level=-31 dBm
                    Extra: Last beacon: 241ms ago

See original description
Tags: ipw2200
Manuel Teira (manuel-teira-telefonica)
description: updated
Revision history for this message
Matthias Niess (mniess) wrote :

Looking in the forums several people seem to habe problems with ipw2200 since upgrade to dapper. Strangely most of them have completely different errors. Mine is:

[4294693.025000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.1
[4294693.026000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[4294693.026000] Warning: PCI driver ipw2200 has a struct device_driver shutdown method, please update!
[4294693.026000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[4294693.565000] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)

Anyway.. Everything works perfectly when I use wpa_supplicant and its "wext" drivers instead of ipw. Still this driver issue should be fixed, though, since the ipw is a VERY common chipset.

Revision history for this message
Manuel Teira (manuel-teira-telefonica) wrote :

Well, perhaps this could help to some people having the same problem:
The thing is that the problem seems to be the channel. I don't know why, but since dapper, channel 12 couldn't be used anymore by the driver (the same happened to me under windows XP, where I cannot select channel 12, and that gaves me the idea). I selected a different channel in my AP, and inmediatly , I got link.

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.

Changed in linux-source-2.6.15:
status: New → Incomplete
Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-source-2.6.15:
status: Incomplete → Invalid
Revision history for this message
Matthias Niess (mniess) wrote :

Sorry for not replying sooner. Yes, you can close this bug. wext is the default driver for for Intel Pro Wireless now (iirc the ipw driver is deprecated).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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