Bug 115176

installed firmware from ipw sourceforge site into /lib/firmware. nic now
operates. however... wifi on/off switch will totally lock up the computer if
pressed. also, wifi led does not work. if you edit /etc/modprobe.conf/local and
add "options ipw2200 led=1" to it, the led will light. but due to the switch
causing a total lockup of the laptop, I am unable to properly test the ipw2200
nic functions.

We can set led=1 as default option, but I don't know whether this may make   
trouble on some machines. Most machines are likely to have WLAN LEDs, though.   
   
I recently tried the WLAN hardware switch on an ASUS with an ipw2200 and it   
worked as expected, so the behavior you described seems not to be a general   
error. I'll have a look at this. 

well lets start by making sure the ipw2200 driver is properly loaded as well as
its matching firmware on a clean installation first. Maybe even add the set
led=1 option as well. This is too common an NIC nowadays to not have it working
out of the box. Thanks for getting things along this far. 

By the way.. the hardware I am using is an HP laptop NC6120. 

#lspci -vv output:

0000:02:04.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05)
        Subsystem: Hewlett-Packard Company: Unknown device 12f5
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (750ns min, 6000ns max), Cache Line Size: 0x10 (64 bytes)
        Interrupt: pin A routed to IRQ 21
        Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-

Are you by chance using asus_acpi module?

Please install the firmware from ftp.suse.com/pub/suse/i386/10.0/...
noarch/ipw-firmware-5-6.noarch.rpm

Do some messages of the ipw2200 made it into /var/log/messages before the  
machine died?  

Will do. I will install RC1 and check it out. if problem still exists, i will 
download and install the firmware and check it again.

I just tested it on another machine with ipw2200, and it also worked as it 
should. Seems the bug only occurs on a limited amount of machines, so I'm 
lowering severity to major.   

great news then. was the ipw-firmware loaded by default on installation or did 
you have to download / install it seperately after installation?
I have pulled down the rc1 release and will verify my end late tonight.

rc1 installed fine on this laptop. ipw-firmware was not loaded by default during
installation. downloaded the 5.6 ipw firmware from ftp.suse.com link (see above)
and after reboot all is well on an open wifi network ( No WEP ). Even the blue
led lights up fine. The gnome network applet has an issue when you select
"preferences" , "eth1" , "configure". dialog pops up that yast is not running
with root privs... so in short... usaer cannot configure the wifi iff needed.
for example, entering new wifi network info such as ssid or wep. going the
normal method by selecting yast from the menu works fine.
.
i will test WEP tomorrow at work and see how that goes along with the transition
between different networks.

Thanks so far for the help but i still strongly believe the ipw-firmware must be
installed by default when an ipw2200 card is detected during installation.

ipw2200 works with wep network too. unable to switch between open and wep
networks as the network manager (netapplet) does not even come up to let you
switch networks...

also... wifi on/off switch locks up X. hard reset required. Appears that keycode
is not recognized.

in short... ipw2200 nic does work once you install 5.6 firmware from ftp.suse.com 
should be installed out-of-the-box at installation.

wifi led works, wifi switch does not.

unable to switch between wifi networks. only possible by reconfiguring wifi nic
through yast

Sorry, I don't have an idea of network manager and netapplet. If you suspect a   
problem with them, please open a bug report.   
   
> wifi on/off switch locks up X.  
  
Are you sure it locks up X and not the kernel? Does it also happen on the  
console?  
  
> ipw2200 nic does work once you install 5.6 firmware from ftp.suse.com  
should be installed out-of-the-box at installation 
 
The 10.0 boxed product will have the firmware and therefore this problem 
shouldn't occur. The situation isn't optimal for openSUSE yet, but I'm sure 
this will be solved. 

I experienced the same problem here.

It was quite hard for me to find why ipw2200 wasn't working while ipw2200 module
was loaded. Just copying firmware from ipw2200.sourceforge.net worked as
described here.

So, if there are any legal issues with suppling firmware along with opensuse at
least there should be some clear advice on how to get the missing firmware (a
message in yast or something).

Keep up with the good work.

*** Bug 118953 has been marked as a duplicate of this bug. ***

The firmware is available at  
ftp.suse.com/pub/suse/i386/10.0/SUSE-Linux10.0-RC1-Extra/kernel-modules+firmware  
  
It's hard to have a special message in Yast since this would require to have  
different, special adapted versions for openSUSE (something we do not want).  
But we will make a page in the wiki during the next days mentioning the  
problem and pointing at the link mentioned.   

So, I don't get it.

Is it legal or not to provide firmware along with the distro ? If so then the
firmware just need to be installed by default (at least for ipw2200 users).

If it's not, then, is it legal to put it on your own ftp ? 

The main problem I see is that putting this on a wiki forces people to get
connected to internet to know what's going on... but the may have no internet
access if wireless connection is not available or they may be too lazy to search
for this...

I'm not a lawyer, sorry. 
I don't think the solution with the firmware and the openSUSE Wiki is optimal, 
but at the moment it looks like the only one valid. 
(On the final boxed SL10.0 the firmware is installed by default if you have 
the hardware, just to mention that) 

I use 10.0 Final out of the box.
I tried two Laptops with IPW2200BG.(1xAcer 661LCI, 1xAsus A3843GLP)

I don´t get the wlan working.
I use it with WEP 128bit HEX-Key.
With SUSE 9.2/9.3 everything worked well.

The Firmware is in /lib/firmware.
dmesg tells nothing about wrong firmware.
the modules ieee80211 and ipw2200 are loaded

iwconfig tells the MAC-Adress from Router, but tells not the encryption-Key.
 
I don´t know what is wrong in 10.0.

I've also installed SL10.0 (GA) on a Dell D600 with the Intel PRO/Wireless
2200BG... wireless does not work out of the box!

This system previously ran SL 9.3 and worked just fine out of the box.

I've also checked that the ipw firmware is located in /lib/firmware, and that
dmesg doesn't complain about anything when the ipw2200 module loads.

klj-d600:/lib/firware # rpm -qf ipw-2.3-boot.fw
ipw-firmware-5-6

klj-d600:/ # lsmod | grep ipw2200
ipw2200       171656  0
ieee80211      51140  1  ipw2200
firmware_class  9856  2  pcmcia,ipw2200

Any ideas?

I have the same problem as comment #18 and 19 states. Maybe this is another bug since we both seem to have the firmware installed.

I also have tried the patch specified in https://bugzilla.novell.com/show_bug.cgi?id=113634 with no success (i had the cycling they talk about there, but the card is still unassigned)

/Hans

Does it work when you add PREFER_WPA_SUPPLICANT='no' to /etc/sysconfig/network/ifcfg-wlan-* ?

Tried comment #21 with no change in behavior.

Could you attach /var/log/messages?

Created attachment 58493 [details]
/var/log/messages 

Attached is my /var/log/messages

Created attachment 58494 [details]
ifcfg for the wlan card (in /etc/sysconfig/network/)

For more info I have attached the conf file for my wlan card

Created attachment 58495 [details]
iwconfig output

...and the output from iwconfig.

Created attachment 58497 [details]
output from iwlist eth0 scanning

For even more information, this is the output from iwlist eth0 scanning.

I tried disabling WEP, and then it works, it gets assigned and I get an IP adress. Seems to be some problem with WEP then? Or am I missing something obvious?

Oops, forgot this bug, sorry. Please make sure setting the status back to assigned from needinfo when providing the information.

Is the bug still present? If yes, could you try whether it helps if you set WIRELESS_AUTH_MODE='open' (instead of 'sharedkey') in your ifcfg-file?

Ok, anything new here or is this now fixed?

Since there hasn't been any activity in this bug for more than a month, let's close this WORKSFORME. Feel free to repopen!