ipw2200 Firmware Error on Install

Bug #27778 reported by Greg Taylor
28
Affects Status Importance Assigned to Milestone
linux-firmware (Ubuntu)
Fix Released
Medium
Ben Collins

Bug Description

Getting a new error with the new ipw2200 driver included in the latest Dapper
snapshot. Previously the wireless ethernet device wasn't even being detected, so
this is an improvement even if it's still not working. Here is my dmesg output:

[4294704.481000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8
[4294704.481000] ipw2200: Copyright(c) 2003-2005 Intel Corporation
[4294704.481000] Warning: PCI driver ipw2200 has a struct device_driver shutdown
method, please update!
[4294704.481000] PCI: Found IRQ 11 for device 0000:06:04.0
[4294704.481000] PCI: Sharing IRQ 11 with 0000:00:1d.3
[4294704.481000] PCI: Sharing IRQ 11 with 0000:01:00.0
[4294704.481000] PCI: Sharing IRQ 11 with 0000:02:00.0
[4294704.481000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[4294714.482000] ipw2200: ipw-2.4-boot.fw load failed: Reason -2
[4294714.482000] ipw2200: Unable to load firmware: -2
[4294714.482000] ipw2200: failed to register network device
[4294714.482000] probe of 0000:06:04.0 failed with error -5
[4294717.914000] floppy0: no floppy controllers found

As per lspci, 0000:00:1d.3 is my "USB Controller: Intel Corporation
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04). 0000:01:00.0 is my
"VGA Compatible controller: ATI Technologies Inc M22 [Radeon Mobility M300],
0000:02:00.0 is my "Ethernet controller: Marvell Technology Group Ltd. 88E8053
Gigabit Ethernet Contoller (rev 15)", my hardwired ethernet interface.
0000:06:04.0 is my "Network controller: Intel Corporation PRO/Wireless 2200BG
(rev 05)."

Revision history for this message
Werner Schulte (w1) wrote :

Mre bad,
since I installed Dapper on a new partiotion to fix the Toshiba HD LED bug,
the ipw2200 driver does not work on breezy any more (though it did before installing dapper).

Here the dmesg output.

[4294987.583000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6
[4294987.583000] ipw2200: Copyright(c) 2003-2004 Intel Corporation
[4294987.584000] ACPI: PCI Interrupt 0000:06:02.0[A] -> GSI 22 (level, low) -> IRQ 22
[4294987.584000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[4294997.584000] ipw2200: ipw-2.3-boot.fw load failed: Reason -2
[4294997.584000] ipw2200: Unable to load firmware: 0xFFFFFFFE
[4294997.584000] ipw2200: failed to register network device
[4294997.584000] ACPI: PCI interrupt for device 0000:06:02.0 disabled
[4294997.584000] ipw2200: probe of 0000:06:02.0 failed with error -5

Revision history for this message
Tor Harald Thorland (linux-strigen) wrote :

Hi,

I will just confirm that I have the same error. I had a working Breezy install, and did an dist-upgrade to Dapper today, wich broke half of my hardware including the Intel Wifi card wich uses the IPW2200. Only a couple of days ago, I did the same thing (dist-upgrade from breezy to Dapper) and the card did work.

Why it is broken today... I don't know. If I can supply any more info, please advice me howto.

The driver works with the old breezy kernel (wich i still have installed), but the card doesn't show up in the network config utility.

Jan 22 21:45:13 localhost kernel: [4294912.470000] ieee80211: 802.11 data/management/control stack, 1.0.3
Jan 22 21:45:13 localhost kernel: [4294912.470000] ieee80211: Copyright (C) 2004-2005 Intel Corporation <email address hidden>
Jan 22 21:45:13 localhost kernel: [4294912.564000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6
Jan 22 21:45:13 localhost kernel: [4294912.564000] ipw2200: Copyright(c) 2003-2004 Intel Corporation
Jan 22 21:45:13 localhost kernel: [4294912.564000] ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 17 (level, low) -> IRQ 17
Jan 22 21:45:13 localhost kernel: [4294912.564000] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
Jan 22 21:45:23 localhost kernel: [4294922.565000] ACPI: PCI interrupt for device 0000:03:03.0 disabled
Jan 22 21:45:23 localhost kernel: [4294922.565000] ipw2200: probe of 0000:03:03.0 failed with error -5

Revision history for this message
Matthew Garrett (mjg59) wrote :

Error 2 is ENOENT - do you have /lib/firmware/kernelversion/ipw-2.4-boot.fw ?

Revision history for this message
Tor Harald Thorland (linux-strigen) wrote :

Some add. comment..

There must be some unstable things here...

The card does show up in network config now, but ubuntu sometimes activates this card during boot, and sometimes my other network card... I don't know why it is not using the same as when I shut down my system.

So when it boot's with the correct one, I can NOT surf the web, I have to deactivate it and activate it to work again...

Revision history for this message
Matthew Garrett (mjg59) wrote :

Greg, the error implies that the firmware is missing. Do you have the appropriate linux-restricted-modules package installed? If you rmmod/modprobe, can you paste the kernel output?

Revision history for this message
Greg Taylor (gtaylor) wrote :

I don't have the restricted modules package installed currently as I can't maintain connectivity long enough to do so. But lsmod shows the presence of ipw2200, do I actually need the restricted modules package if it's showing the module there just fine?

Here's the errors:
ipw2200: Failed to send ASSOCIATE: Command time out.
ipw2200: Failed to send CARD_DISABLE: Command timed out.
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.1
PCI: Found IRQ 11 for device 0000:06:04.0
PCI: Sharing IRQ 11 with 0000:00:1d.3
PCI: Sharing IRQ 11 with 0000:01:00.0
PCI: Sharing IRQ 11 with 0000:02:00.0
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Unable to initialize device after 5 attempts.
ipw2200: failed to register network device
ipw2200: probe of 0000:06:04.0 failed with error -5

Revision history for this message
Matthew Garrett (mjg59) wrote : Re: [Bug 27778] Re: ipw2200 Firmware Error on Install

Hm. Without the restricted-modules package, I'm somewhat amazed that you
have any firmware at all. But anyway, if you're getting those errors,
the problem is elsewhere. Does this problem happen everywhere? ipw2200
seems "sensitive" to some network conditions.

Revision history for this message
Greg Taylor (gtaylor) wrote :

I'm afraid it does happen everywhere that I've been so far. But as mentioned, everything is fine during the install, it pulls packages from the net without a hitch. I actually had to use my wireless connection to complete a install from a corrupt Dapper nightly CD a week ago.

As far as specifics on my primary wireless network:
non-broadcasted ESSID
WEP encryption, open/managed

I've been all over campus (hundreds of access points) and returned home to give this a try with the same results. Regardless of whether it can pull a signal, those errors look to be something lower level than signal/IP acquisition.

Revision history for this message
Greg Taylor (gtaylor) wrote :

I was able to dig this up at the Intel site for the Wireless chipset.

http://support.intel.com/support/wireless/wlan/sb/cs-022509.htm

Symptoms:
Some wireless LAN client connections are intermittently dropped from some networks followed by a new client association to either the same Access Point or another Access Point. Some applications may lose their connections.

Cause:
A timing issue in the driver causes clients to sometimes drop frames for a long enough period to cause disconnects in some environments.

Revision history for this message
Greg Taylor (gtaylor) wrote :

Is there anything further I can provide to help debug this?

Revision history for this message
Ben Collins (ben-collins) wrote :

Can you confirm it on 2.6.15-26.46?

Revision history for this message
KeithCu (keithcu) wrote :

I can confirm it still happens in my dmseg log:
uname -a
Linux keithcul-1 2.6.15-26-server #1 SMP Thu Aug 3 04:09:15 UTC 2006 i686 GNU/Linux

Here are the various messages I'm seeing:
 grep ipw2200 dmesg.txt | more
[42949386.500000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.1
[42949386.500000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[42949386.500000] Warning: PCI driver ipw2200 has a struct device_driver shutdown method, please update!
[42949386.580000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[42949387.320000] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
[42960606.400000] ipw2200: Failed to send SCAN_ABORT: Command timed out.
[42960607.890000] ipw2200: Firmware error detected. Restarting.
[42964652.960000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.1
[42964652.960000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[42964652.960000] Warning: PCI driver ipw2200 has a struct device_driver shutdown method, please update!
[42964652.960000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[42964653.130000] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
[42971501.090000] ipw2200: Firmware error detected. Restarting.
[43038384.960000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.1
[43038384.960000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[43038384.960000] Warning: PCI driver ipw2200 has a struct device_driver shutdown method, please update!
[43038384.960000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[43038385.140000] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)

Revision history for this message
Matthew Garrett (mjg59) wrote :

Greg,

could you attach a new dmesg from current edgy please? Thanks!

Revision history for this message
Greg Taylor (gtaylor) wrote :
Revision history for this message
Matthew Garrett (mjg59) wrote :

There's no obvious errors in there. When do they get generated? Can you
attach /proc/interrupts after an error has been generated?

Revision history for this message
Greg Taylor (gtaylor) wrote :

Here's the /proc/interrupts file after the error.

Revision history for this message
Greg Taylor (gtaylor) wrote :

And here's the dmesg with the error at the bottom (TX_POWER).

Revision history for this message
Greg Taylor (gtaylor) wrote :

Ok, this is a default bootup with no options. Notice the TX_POWER error messages again. The interface is not visible on ifconfig or iwconfig.

Revision history for this message
Kryten (karlkristian-markman) wrote :

according to this site http://ipw2200.sourceforge.net/

The firmware will show as error im going to try the drivers now (havent got anything but wireless network here)

Revision history for this message
Kryten (karlkristian-markman) wrote :

Also see

http://ubuntuforums.org/showthread.php?t=240065

for Toshiba users (might work on others as well)

Revision history for this message
Greg Taylor (gtaylor) wrote :

It looks like there may be a fix for this in the latest version of ipw2200 at http://ipw2200.sourceforge.net/. Gutsy is currently running 1.2.0, perhaps we could look into backporting 1.2.2, which fixes two of the issues crippling the Tecras and a number of other laptops.

Revision history for this message
zhanzh@shanghai (zhanzh-sh) wrote :

Dell Inspiron 1300

zhanzh:~$ uname -r
2.6.22-14-386

zhanzh:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

eth0 -->wired interface
eth1 -->wireless interface

Problem:
zhanzh:~$ dmesg | grep ipw
[ 24.840000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2dmprq
[ 24.856000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 24.888000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[ 25.144000] ipw2200: Unable to load ucode: -62
[ 25.160000] ipw2200: Unable to load firmware: -62
[ 25.176000] ipw2200: failed to register network device
[ 25.208000] ipw2200: probe of 0000:02:03.0 failed with error -5

Tried
1) sudo tar zxvf ipw2200-fw-2.3.tgz -C /lib/firmware/2.6.22-14-386
2) installed ieee80211-1.2.18.tgz & ipw2200-1.2.2.tgz (http://www.waraey.com/blog/?p=10)

Still now working yet... (cf, working well when booting into Win XP)

Revision history for this message
GeneW (etwilson) wrote :

I'm seeing firmware errors after I upgraded to Hardy Heron, I never had them before.

ewilson@ewilson-laptop:~$ uname -a
Linux ewilson-laptop 2.6.24-17-generic #1 SMP Thu May 1 14:31:33 UTC 2008 i686 GNU/Linux

ewilson@ewilson-laptop:~$ dmesg | grep 2200
[ 4.882200] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 23.138542] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
[ 23.138546] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 24.304357] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[ 26.236780] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
[ 26.237694] ipw2200: Firmware error detected. Restarting.
[ 26.468054] ipw2200: Firmware error detected. Restarting.
[ 30.103255] audit(1212200913.926:2): type=1503 operation="inode_permission" requested_mask="a::" denied_mask="a::" name="/dev/tty" pid=4845 profile="/usr/sbin/cupsd" namespace="default"
[ 56.812276] ipw2200: Firmware error detected. Restarting.
[ 154.444922] ipw2200: Firmware error detected. Restarting.
[ 74.036683] ipw2200: Firmware error detected. Restarting.
[ 74.282572] ipw2200: Firmware error detected. Restarting.

Revision history for this message
Greg Taylor (gtaylor) wrote :

Yep, that's what I've been getting too. I've been waiting on this particular issue for about a year and a half now, so I'm really not sure what to tell you on this one. It seems to be something to do with encryption, as I rarely have the problem on unsecured wireless.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

I recently ran into this bug. One of the Interpid updates caused this (I'm sorry I cannot tell which one). My ipw2200 card was working fine since 7.10, but it stopped suddenly. I hope it will be fixed in the upcoming 2.6.27 kernel,

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

Not fixed in 2.6.27. Still no wi-fi interface.

Changed in linux:
status: New → Confirmed
Revision history for this message
Denis Rut'kov (dendron2000) wrote :

It's not in the kernel. I just booted good old 2.6.22 and wi-fi is not working! It got broken elsewhere, but I have no ideas where and when. I still get the same error during startup even in 2.6.22:

[ 27.072000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmprq
[ 27.072000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 27.256000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[ 27.432000] ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
[ 27.432000] ipw2200: Unable to load firmware: -2
[ 27.432000] ipw2200: failed to register network device
[ 27.432000] ipw2200: probe of 0000:06:06.0 failed with error -5

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

I got it. Restricted modules from both of my kernels were missing, I had to install them manually. It seems they were mistakenly removed by one of the updates. I have a network interface now, but I cannot test connection.

Revision history for this message
Paul Gevers (paul-climbing) wrote :

I upgraded to Intrepid two days ago. My ipw2200 was working fine in Hardy. Now it stopped working. Just like the comment above, I needed to install linux-restricted-modules-common to get rid of the request_firmware failed (in Hardy the firmware packages were in linux-ubuntu-modules-2.6.24-19-generic)

At least the transition might be improved.

But apart from that, I am also not able to connect or scan. I use wpa_supplicant in between, so I don't know where my problem is yet.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Firmware files have now moved to the 'linux-firmware' package so this bug should be fixed. Make sure this package is installed if you get these error still.

Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
MilchFlasche (robertus0617) wrote :

I have installed Intrepid on an Asus S5000 which seems to use Intel 2200 too, and I have check that linux-firmware is there installed, but Intel 2200 firmware is still getting problems.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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