ipw2200-bss.fw request_firmware failed: Reason -2

lwfinger · July 1, 2010, 4:51pm

On 07/01/2010 04:46 AM, dgg3ps wrote:
>
> Thanks for continued support!
> My udevd daemon seems to be running.
>
> Code:
> --------------------
>
> maja@obsidian:~> ps ax | grep udev
> 324 ? S<s 0:00 /sbin/udevd --daemon
> 3300 ? S< 0:00 /sbin/udevd --daemon
> 3301 ? S< 0:00 /sbin/udevd --daemon
> 7093 pts/0 R+ 0:00 grep udev
>
> --------------------
>
>
> I found this, is this it?
> ‘http://wireless.kernel.org’
> (http://wireless.kernel.org/en/users/Download/stable/)
>
> the oldest tarball is for kernel 2.6.32.15 while I have 2.6.31.5, is
> this a problem?

No. The upstream kernel maintains only certain releases as “stable”. At
the moment, those are 2.6.34 and 2.6.32, but any fixes for regressions are
backported to all kernels that are affected. The person that handles this
for upstream also does it for openSUSE, thus your 2.6.31.5 is likely
current; however, any fixes that are not regressions are not backported.
You will find them in compat-wireless.

> I didn’t find a rpm package on ‘PackMan :: home’
> (http://packman.links2linux.org/)

You can find the RPM for compat-wireless at

http://download.opensuse.org/repositories/driver:/wireless/openSUSE_11.2/

Download the file for your architecture (i586 os x86_64) and your kernel
as shown by ‘uname -r’. After it is downloaded, install it with


sudo rpm -iv <path_to_rpm_just_downloaded>

After that finishes, then reboot.

dgg3ps · July 1, 2010, 11:52pm

Hi, I think we are getting there

I tried to install
sudo rpm -iv compat-wireless-kmp-default-2.6.34_2.6.31.5_0.1-2.1.i586.rpm

and had a unresolved dependecy.:

compat-wireless-scripts-2.6.34-2.1.noarch.rpm

was required, so I installed this:


obsidian:/media/USB DISK # rpm -iv compat-wireless-scripts-2.6.34-2.1.noarch.rpm 
warning: compat-wireless-scripts-2.6.34-2.1.noarch.rpm: Header V3 DSA signature: NOKEY, key ID 4073bdbe
Preparing packages for installation...                                          
compat-wireless-scripts-2.6.34-2.1                                              
A little hack to fix detection of wireless interfaces by ifup scripts,          
otherwise your interface will not be detected as wireless using                 
traditional method with ifup for configuration of your wireless card.           
Creating a backup file /etc/sysconfig/network/scripts/functions-20100701-2157.bak.....
.... and working around missing detection of wireless interfaces using latest compat-wireless drivers
Done. If you experience problems, copy the backup file to /etc/sysconfig/network/scripts/functions and restart network service.

then I did:


obsidian:/media/USB DISK # rpm -iv compat-wireless-kmp-default-2.6.34_2.6.31.5_0.1-2.1.i586.rpm                
warning: compat-wireless-kmp-default-2.6.34_2.6.31.5_0.1-2.1.i586.rpm: Header V3 DSA signature: NOKEY, key ID 4073bdbe                                                                                                        
Preparing packages for installation...                                                                         
        package compat-wireless-kmp-default-20100617_2.6.31.5_0.1-11.1.i586 (which is newer than compat-wireless-kmp-default-2.6.34_2.6.31.5_0.1-2.1.i586) is already installed                                               
        file /lib/modules/2.6.31.5-0.1-default/updates/compat/compat.ko from install of compat-wireless-kmp-default-2.6.34_2.6.31.5_0.1-2.1.i586 conflicts with file from package compat-wireless-kmp-default-20100617_2.6.31.5_0.1-11.1.i586                                                                                                
        file /lib/modules/2.6.31.5-0.1-default/updates/compat/compat_firmware_class.ko from install of compat-wireless-kmp-default-2.6.34_2.6.31.5_0.1-2.1.i586 conflicts with file from package compat-wireless-kmp-default-20100617_2.6.31.5_0.1-11.1.i586                                                                                 
        file /lib/modules/2.6.31.5-0.1-default/updates/drivers/bluetooth/ath3k.ko from install of compat-wireless-kmp-default-2.6.34_2.6.31.5_0.1-2.1.i586 conflicts with file from package compat-wireless-kmp-default-20100617_2.6.31.5_0.1-11.1.i586
...

Which came a bit as a surprise, however I rebooted before doing anything else and had a look at dmesg, which was promising:


maja@obsidian:~> dmesg | grep ipw
   10.726153] libipw: 802.11 data/management/control stack, git-1.1.13
   10.726158] libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
   10.740222] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kdmprq
   10.740227] ipw2200: Copyright(c) 2003-2006 Intel Corporation
   10.953289] ipw2200 0000:02:04.0: PCI INT A -> Link[LNKE] -> GSI 10 (level, low) -> IRQ 10
   10.955431] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
   11.260328] ipw2200: Radio Frequency Kill Switch is On:
   11.260888] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)

It looks as if this bit had worked. However there seems still to be a problem, since eth1 doesn’t get an IP and hence no connection. But now I think it is a configuration problem rather than a driver problem.


obsidian:/home/maja # ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 00:C0:9F:43:9B:52  
          inet Adresse:192.168.1.11  Bcast:192.168.1.255  Maske:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1                         
          RX packets:32294 errors:0 dropped:0 overruns:0 frame:0             
          TX packets:25195 errors:0 dropped:0 overruns:0 carrier:0           
          collisions:0 Sendewarteschlangenlänge:1000                         
          RX bytes:45532637 (43.4 Mb)  TX bytes:2175639 (2.0 Mb)             
          Interrupt:5 Basisadresse:0xe800                                    

eth1      Link encap:Ethernet  Hardware Adresse 00:0E:35:63:09:84  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1       
          RX packets:2 errors:109 dropped:111 overruns:0 frame:0   
          TX packets:34 errors:0 dropped:0 overruns:0 carrier:0    
          collisions:0 Sendewarteschlangenlänge:1000               
          RX bytes:298 (298.0 b)  TX bytes:10988 (10.7 Kb)         
          Interrupt:10 Speicher:e0204000-e0204fff                  

lo        Link encap:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:76 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:0              
          RX bytes:4244 (4.1 Kb)  TX bytes:4244 (4.1 Kb)       

obsidian:/home/maja # ifstatus eth1
    eth1      device: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
DHCP4 client (dhcpcd) is running                                                                   
. . . but is still waiting for data                                                                
eth1 is up
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0e:35:63:09:84 brd ff:ff:ff:ff:ff:ff


bssid=00:01:e3:f6:26:37
ssid=waldeggWL19791978
id=0
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED

any ideas?

deano_ferrari · July 2, 2010, 1:36am

You didn’t have your wired ethernet device plugged in (active) at the same time?

dgg3ps · July 2, 2010, 12:32pm

This is for the records now.
My Wireless adapter finally works (with the help of lwfinger and deano_ferrari), so this thread can be considered as closed.

So here just a quick summary how we found the solution.

Problem was:


Dmesg output:
-------------
 533.722858] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kdmprq
 533.722885] ipw2200: Copyright(c) 2003-2006 Intel Corporation
 533.723025] ipw2200 0000:02:04.0: PCI INT A -> Link[LNKE] -> GSI 10 (level, low) -> IRQ 10
 533.724606] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
 593.724145] ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
 593.724170] ipw2200: Unable to load firmware: -2
 593.724183] ipw2200: failed to register network device
 593.724309] ipw2200 0000:02:04.0: PCI INT A disabled
 593.724376] ipw2200: probe of 0000:02:04.0 failed with error -5

and this was although the correct driver and firmware where installed. So it was then suggested I should install “compat-wirelss” according to my kernel. Upon doing this I found noticed two things:

I was missing a package: “compat-wireless-scripts-2.6.34-2.1.noarch.rpm”
compat wireless was already installed, but not the scripts.

The solution then was to install the scripts, and now it works with WPA-PSK2 encryption, great (and I hope my wife is impressed ;-).

So, thanks for the support in the last days. It is also worth mentioning, that the sticky posts in this forum on what information to collect at the beginning where really useful. Peter

–
Suse 11.2, Kernel 2.6.31.5-0.1-default

lwfinger · July 2, 2010, 3:34am

On 07/01/2010 05:47 PM, dgg3ps wrote:

> any ideas?

Can you scan? Try


sudo  /usr/sbin/iwlist scan

If that finds your AP, then you are in business. Do you wish to use
NetworkManager or ifup? Select the one you want with YaST => Network
Devices => Network Settings. If using ifup, you configure everything
there. With NM, you use the applet in the system tray.