http://bugzilla.novell.com/show_bug.cgi?id=530264 User squan@web.de added comment http://bugzilla.novell.com/show_bug.cgi?id=530264#c1 --- Comment #1 from Stefan Quandt 2009-08-25 00:25:07 MDT --- Meanwhile I did some variation on involved connection partiies 1) I could connect with my ipw2100 HW to another unencrypted WLAN => ipw2100 is not generally broken (s.a. bug 441511) 2) I could connected with another hardware to my WLAN => my router HW is fine and this bug is not invalid Thus I suspect Networkmanager to be the cause of trouble. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 User squan@web.de added comment http://bugzilla.novell.com/show_bug.cgi?id=530264#c3 --- Comment #3 from Stefan Quandt 2009-08-28 14:44:42 MDT --- Today I did another attempt with WEP encryption. After configuring _both_ my router and the corresponding NetworkManager connection accordingly (WEP with 128 bit key) the NM logs of the connection attempt showed "No secrets needed" (see below). Why this? I have no clue. May be there is a problem in the NetworkManager configuration backend. Aug 28 22:27:03 galapagos NetworkManager: <info> Activation (eth1) starting connection 'MyWlan' Aug 28 22:27:03 galapagos NetworkManager: <info> (eth1): device state change: 3 -> 4 Aug 28 22:27:03 galapagos NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Aug 28 22:27:03 galapagos NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Aug 28 22:27:03 galapagos NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Aug 28 22:27:03 galapagos NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Aug 28 22:27:03 galapagos NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Aug 28 22:27:03 galapagos NetworkManager: <info> (eth1): device state change: 4 -> 5 Aug 28 22:27:03 galapagos NetworkManager: <info> Activation (eth1/wireless): connection 'MyWlan' requires no security. No secrets needed. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 shuang qiu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |gekker@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 User squan@web.de added comment http://bugzilla.novell.com/show_bug.cgi?id=530264#c6 --- Comment #6 from Stefan Quandt 2009-10-18 14:06:54 MDT --- Being still on MS8 I switched from NetworkManager to wicd today. wicd shows all reachable networks but no wireless connection is possible. The behaviour in my home network is exactly the same as with NetworkManager: Only wired connection is possible, WLAN with WPA2 and unencrypted fail. I even tried switching channels with no effect. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 User lasse.penttinen@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=530264#c8 --- Comment #8 from Lasse Penttinen 2009-11-13 14:32:54 MST --- I installed the GM KDE4 and the WLAN failed, even though knetworkmanager showed that connection would be up, IP address obtained and so on. Still no application was able to connect to the internet. Reinstalled with Gnome and works like charm... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c9 Stefan Quandt changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major Severity|Normal |Major --- Comment #9 from Stefan Quandt 2010-01-24 16:33:38 UTC --- Now I switched with yast2 to traditional (ifup) based network setup. This did not change anything: Still ethernet based connection works, but 'ifup eth1' (for WLAN) fails on getting an IP address: Starting DHCP4 client on eth1. . . . . . . eth1 DHCP4 continues in background It is still possible to list access points with "Netzwerk durchsuchen" on a page of the 'yast2 lan' configuration module. Thus my WLAN hardware is not broken. The only single visible difference compared with Networkmanager setup is a polling which starts immediately after switching to traditional setup (which shows up my /var/log/messages because of my ipw2100 module debug flags): Jan 23 14:56:44 host ifup: eth1 device: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) Jan 23 14:56:44 host ifup: eth1 Startmode is 'manual' Jan 23 14:56:44 host ifup: vboxnet0 Jan 23 14:56:44 host ifup: No configuration found for vboxnet0 Jan 23 14:56:44 host kernel: [17505.185248] ipw2100: U ipw2100_wx_get_name Name: unassociated Jan 23 14:56:44 host kernel: [17505.185260] ipw2100: U ipw2100_wx_get_freq GET Freq/Channel -> 0 Jan 23 14:56:44 host kernel: [17505.185278] ipw2100: U ipw2100_wx_get_essid Getting essid: ANY Jan 23 14:56:44 host kernel: [17505.185284] ipw2100: U ipw2100_wx_get_mode GET Mode -> 2 Jan 23 14:56:44 host kernel: [17505.185296] ipw2100: U ipw2100_wx_get_name Name: unassociated Jan 23 14:56:44 host kernel: [17505.185303] ipw2100: U ipw2100_wx_get_freq GET Freq/Channel -> 0 Jan 23 14:56:44 host kernel: [17505.185312] ipw2100: U ipw2100_wx_get_essid Getting essid: ANY Jan 23 14:56:44 host kernel: [17505.185318] ipw2100: U ipw2100_wx_get_mode GET Mode -> 2 Jan 23 14:56:44 host kernel: [17505.185331] ipw2100: U ipw2100_wx_get_range GET Range Jan 23 14:56:44 host kernel: [17505.185353] ipw2100: U ipw2100_wx_get_wap Getting WAP BSSID: 00:00:00:00:00:00 The messages stating 'unassociated' repeat every second. Why is associating not possible even though the access point is visible? --- Comment #10 from Stefan Quandt 2010-01-24 16:33:40 UTC --- Now I switched with yast2 to traditional (ifup) based network setup. This did not change anything: Still ethernet based connection works, but 'ifup eth1' (for WLAN) fails on getting an IP address: Starting DHCP4 client on eth1. . . . . . . eth1 DHCP4 continues in background It is still possible to list access points with "Netzwerk durchsuchen" on a page of the 'yast2 lan' configuration module. Thus my WLAN hardware is not broken. The only single visible difference compared with Networkmanager setup is a polling which starts immediately after switching to traditional setup (which shows up my /var/log/messages because of my ipw2100 module debug flags): Jan 23 14:56:44 host ifup: eth1 device: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) Jan 23 14:56:44 host ifup: eth1 Startmode is 'manual' Jan 23 14:56:44 host ifup: vboxnet0 Jan 23 14:56:44 host ifup: No configuration found for vboxnet0 Jan 23 14:56:44 host kernel: [17505.185248] ipw2100: U ipw2100_wx_get_name Name: unassociated Jan 23 14:56:44 host kernel: [17505.185260] ipw2100: U ipw2100_wx_get_freq GET Freq/Channel -> 0 Jan 23 14:56:44 host kernel: [17505.185278] ipw2100: U ipw2100_wx_get_essid Getting essid: ANY Jan 23 14:56:44 host kernel: [17505.185284] ipw2100: U ipw2100_wx_get_mode GET Mode -> 2 Jan 23 14:56:44 host kernel: [17505.185296] ipw2100: U ipw2100_wx_get_name Name: unassociated Jan 23 14:56:44 host kernel: [17505.185303] ipw2100: U ipw2100_wx_get_freq GET Freq/Channel -> 0 Jan 23 14:56:44 host kernel: [17505.185312] ipw2100: U ipw2100_wx_get_essid Getting essid: ANY Jan 23 14:56:44 host kernel: [17505.185318] ipw2100: U ipw2100_wx_get_mode GET Mode -> 2 Jan 23 14:56:44 host kernel: [17505.185331] ipw2100: U ipw2100_wx_get_range GET Range Jan 23 14:56:44 host kernel: [17505.185353] ipw2100: U ipw2100_wx_get_wap Getting WAP BSSID: 00:00:00:00:00:00 The messages stating 'unassociated' repeat every second. Why is associating not possible even though the access point is visible? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c Gary Ekker changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|gekker@novell.com |tambet@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c13 --- Comment #13 from Stefan Quandt 2010-07-29 07:08:18 UTC --- While with opwnSUSE-11.2 I could scan access points with 'yast2 lan' with ipw2100 this no longer works with openSUSE-11.3. Currently (openSUSE-11.3) iwlist reports more then 10 access points with link 'Quality' in a range from 16 to 84 but no NetworkManager frontend does show them. I think 'iwconfig eth1 essid <My ESSID>' shoud associate my acess point but it does not. Even after 'iwconfig eth1 ap <MAC address>' the interface remains 'Not-Associated'. Meanwhile I also found a relevant bug report on ubuntu launchpad (#482291) which indicates that ipw2100 and ipw2200 did not get ported to a new 'rfkill infrastructure' in kernel-2.6.31. This has been fixed there in november 2009. I would expect that the fixes would automatically appear in openSUSE updates at some point of time. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c14 Vladimir Botka changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED Component|Network |Network Version|Factory |Final AssignedTo|vbotka@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 11.2 |openSUSE 11.3 Severity|Major |Normal --- Comment #14 from Vladimir Botka 2010-07-29 10:01:47 UTC --- (In reply to comment #13)

Currently (openSUSE-11.3) iwlist reports more then 10 access points with link

The driver must be working if iwlist can see the APs. This works for me too.

I think 'iwconfig eth1 essid <My ESSID>' shoud associate my acess point but it does not.

Yes, if the AP is OPEN, if the AP is encrypted then wpa_supplicant is needed.

Even after 'iwconfig eth1 ap <MAC address>' the interface remains 'Not-Associated'.

I can associate with OPEN AP. # iwconfig eth1 essid vlado-test-ap4 # iwconfig eth1 eth1 IEEE 802.11b ESSID:"vlado-test-ap4" Nickname:"ipw2100" Mode:Managed Frequency:2.462 GHz Access Point: 00:1C:F0:89:9D:CC Bit Rate=11 Mb/s Tx-Power:16 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=99/100 Signal level=-32 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:2

Meanwhile I also found a relevant bug report on ubuntu launchpad (#482291) which indicates that ipw2100 and ipw2200 did not get ported to a new 'rfkill infrastructure' in kernel-2.6.31. This has been fixed there in november 2009. I would expect that the fixes would automatically appear in openSUSE updates some point of time.

11.3 got kernel 2.6.34 and ipw2100 seems to be working fine for me. If you think there is a problem with the rfkill then you can install the rfkill utility. As root you can list and manipulate the available rfkill interfaces. # rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c16 Stefan Quandt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|squan@web.de | --- Comment #16 from Stefan Quandt 2010-07-29 20:18:30 UTC --- @Vladimir in reply to comment #14 and comment #15:

...

I think 'iwconfig eth1 essid <My ESSID>' shoud associate my acess point but it does not. Yes, if the AP is OPEN, if the AP is encrypted then wpa_supplicant is needed. Ah ok, I did not know that 'associate' is such high level in that it requires wpa_supplicant (wish I had found that info on your wiki or elsewhere).

...try to isolate the problem as described in [1] Thanks, that's a lot more helpful then the equivalent page in the KDE wiki

After polishing my wpa_supplicant.conf doing wpa_supplicant -dddt -Dwext -ieth1 -c /etc/wpa_supplicant/wpa_supplicant.conf gives me 1280421762.411272: Could not set interface eth1 flags: Unknown error 132 1280421762.411301: Failed to initialize driver interface 1280421762.411309: Failed to add interface eth1 1280421762.411342: Cancelling scan request 1280421762.411350: Cancelling authentication timeout Error 132 means ERFKILL Argh, I see this for the first time in my life because it does not get syslogged.

If you think there is a problem with the rfkill ... Yes, i think so because ERFKILL and because I can make my card connect with the rfkill command.. So read on.

I can associate with OPEN AP. Ok, you have ipw2100 and apparently not this problem. If i presume you are on 11.3 or at least on 11.2 (correct me if I'm wrong) i must conclude there is another unknown condition for reproducing this illegitemate rfkill state which applies to only a part of linux ipw2100/ipw2200 users.

As root you can list and manipulate the available rfkill interfaces. rfkill list all gives me 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no

which is bad, and after rfkill unblock 0 RF soft block goes away: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no After this another wpa_suppicant successfully associates and connects my ''PROWireless LAN 2100 3B Mini PICAdapter' for the first time after 11 months Just another anomaly to note is that after disabling radio (FN F2 on my dell) ipw2100 continues to do periodically futile network scans like this: 1280421354.346163: Starting AP scan for wildcard SSID 1280421354.356161: Scan requested (ret=0) - scan timeout 30 seconds 1280421384.381145: Scan timeout - try to get results 1280421384.381214: Received 0 bytes of scan results (0 BSSes) 1280421384.381233: BSS: Start scan result update 53 1280421384.381246: New scan results available 1280421384.381264: Selecting BSS from priority group 5 1280421384.381277: Try to find WPA-enabled AP 1280421384.381288: Try to find non-WPA AP 1280421384.381299: No suitable network found 1280421384.381316: Setting scan request: 5 sec 0 usec And before I forget: For all visible APs 'iwlist ethX scan' reports 'Quality' greater then zero but signal level zero, e.g. like this: Quality:84 Signal level:0 Noise level:0 which confused me for a while. Don't know wether this is generic or driver specific. Thanks Stefan -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c18 --- Comment #18 from Stefan Quandt 2010-07-30 04:12:06 UTC ---

There must some mess in the rfkill synchronization with the radio of the adapter. Why is this only a problem of some ipw2100 users and not all of them?

And yes there must be a rfkill state confustion as the rfkill command queries the file /sys/class/rfkill/rfkill0/name which contained the wrong state while /sys/bus/pci/drivers/ipw2100/0000\:02\:04.0/rf_kill always reports the correct state. Does this mean that ubuntu bug #482291 has been fixed incompletely? On http://marc.info/?l=linux-wireless&m=125796825803032&w=2 Matthew Garrett says libipw unconditionally calls wiphy_unregister, but it's up to the driver to register it in the first place. ipw2100 fails to do so. When did this fix go into openSUSE?

The rfkill issue depends on the HW and BIOS of your computer Yes, the BIOS would be a candidate, escpecially when doing a suspend/resume cycle. But after doing the 'rfkill 0 unblock' fix the rfkill state is not compromized on subsequent suspend/resume cycles and wireless remains connected and just fine.

...

after disabling radio (FN F2 on my dell) ipw2100 continues to do periodically futile network scans like this: Maybe the FN F2 just turns the radio off and the rfkill interface is not set thus NM does not know the adapter is down and keep scanning. No, i don't have NetworkManager running. So I'm afraid the driver does periodical scanning on its own.

-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c20 Stefan Quandt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|squan@web.de | --- Comment #20 from Stefan Quandt 2010-07-31 05:11:01 UTC ---

the rfkill command queries /sys/class/rfkill/rfkill0/name and also /dev/rfkill where the state information comes from.

The rfkill issue depends on the HW and BIOS of your computer. Yes, I found a kernel bugzilla report on this issue and all commenters use a similar wireless adapter: https://bugzilla.kernel.org/show_bug.cgi?id=14098

ipw2100 is no longer supported by Intel The original Intel driver has been merged to the kernel where is has been for a few years now

-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=530264 https://bugzilla.novell.com/show_bug.cgi?id=530264#c22 Stefan Quandt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|squan@web.de | --- Comment #22 from Stefan Quandt 2010-09-01 19:53:02 UTC --- Currently I have BIOS A06 (on a latitude X300). Latest available BIOS is A10 but none of the updates fixes something RF related. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.