http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c16 Stefan Quandt <squan@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|squan@web.de | --- Comment #16 from Stefan Quandt <squan@web.de> 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.