[Bug 530264] New: WLAN connection with ipw2100 no longer possible
http://bugzilla.novell.com/show_bug.cgi?id=530264 Summary: WLAN connection with ipw2100 no longer possible Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: squan@web.de QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.1) Gecko/20090714 SUSE/3.5.1-2.3 Firefox/3.5.1 WLAN with ipw2100 was working flawless on openSUSE-11.1 even with WPA2. With openSUSE-11.2 it is no possible to establich a WEP, WPA2 or unprotected WLAN connection. This could be a NetworkManager, dbus or driver problem. Connection fails with both knetworkmanager and nm-applet. Below you find simultanous logs of an connection attempt (connection name 'MyWlan', SSID 'MySSID') from three sources (/var/log/NetworkManager, ipw2100 module debug messages and output of cnetworkmanager in monitoring mode): Device State PREPARE (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3, was DISCONNECTED) PROP State 4 (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3) SIG /o/f/NM: o.f.NM.PropertiesChanged(dbus.Dictionary({dbus.String(u'ActiveConnections'): dbus.Array([dbus.ObjectPath('/org/freedesktop/NetworkManager/ActiveConnection/22'), dbus.ObjectPath('/org/freedesktop/NetworkManager/ActiveConnection/26')], signature=dbus.Signature('o'), variant_level=1)}, signature=dbus.Signature('sv')),) ABBR /o/f/NM/AC/26 is /org/freedesktop/NetworkManager/ActiveConnection/26 SIG /o/f/NM/AC/26: o.f.NM.C.A.PropertiesChanged(dbus.Dictionary({dbus.String(u'State'): dbus.UInt32(1L, variant_level=1)}, signature=dbus.Signature('sv')),) PROP ActiveAccessPoint /org/freedesktop/NetworkManager/AccessPoint/87 (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3) Device State CONFIG (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3, was PREPARE) PROP State 5 (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3) WPAS DISCONNECTED (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was scanning) WPAS SCANNING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was disconnected) WPAS ASSOCIATING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was scanning) Aug 12 07:18:23 galapagos kernel: [34664.744499] ipw2100: U ipw2100_wx_set_scan Initiating scan... Aug 12 07:18:23 galapagos kernel: [34664.762652] ipw2100: U ipw2100_wx_set_mode SET Mode -> 2 Aug 12 07:18:23 galapagos kernel: [34664.893344] ipw2100: U ipw2100_wx_set_essid Setting ESSID: 'MySSID' (6) Aug 12 07:18:23 galapagos kernel: [34664.965124] ipw2100: U ipw2100_wx_set_wap SET BSSID -> 00:19:cb:4e:b9:42 Aug 12 07:18:23 galapagos NetworkManager: <info> Activation (eth1) starting connection 'MyWlan' Aug 12 07:18:23 galapagos NetworkManager: <info> (eth1): device state change: 3 -> 4 Aug 12 07:18:23 galapagos NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Aug 12 07:18:23 galapagos NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Aug 12 07:18:23 galapagos NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Aug 12 07:18:23 galapagos NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Aug 12 07:18:23 galapagos NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Aug 12 07:18:23 galapagos NetworkManager: <info> (eth1): device state change: 4 -> 5 Aug 12 07:18:23 galapagos NetworkManager: <info> Activation (eth1/wireless): connection 'MyWlan' requires no security. No secrets needed. Aug 12 07:18:23 galapagos NetworkManager: <info> Config: added 'ssid' value 'MySSID' Aug 12 07:18:23 galapagos NetworkManager: <info> Config: added 'scan_ssid' value '1' Aug 12 07:18:23 galapagos NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Aug 12 07:18:23 galapagos NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Aug 12 07:18:23 galapagos NetworkManager: <info> Config: set interface ap_scan to 1 Aug 12 07:18:23 galapagos NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected Aug 12 07:18:23 galapagos NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning Aug 12 07:18:23 galapagos NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating Aug 12 07:18:24 galapagos kernel: [34665.273611] ipw2100: U ipw2100_wx_set_scan Initiating scan... WPAS DISCONNECTED (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was associating) WPAS SCANNING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was disconnected) Aug 12 07:18:28 galapagos kernel: [34669.969938] ipw2100: U ipw2100_wx_set_scan Initiating scan... Aug 12 07:18:29 galapagos kernel: [34669.998012] ipw2100: U ipw2100_wx_set_mode SET Mode -> 2 WPAS ASSOCIATING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was scanning) Aug 12 07:18:29 galapagos kernel: [34670.133654] ipw2100: U ipw2100_wx_set_essid ESSID set to current ESSID. Aug 12 07:18:29 galapagos kernel: [34670.177436] ipw2100: U ipw2100_wx_set_wap SET BSSID -> 00:19:cb:4e:b9:42 Aug 12 07:18:29 galapagos NetworkManager: <info> (eth1): supplicant connection state: associating -> disconnected Aug 12 07:18:29 galapagos NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning Aug 12 07:18:29 galapagos NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating WPAS DISCONNECTED (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was associating) WPAS SCANNING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was disconnected) WPAS ASSOCIATING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was scanning) Aug 12 07:18:34 galapagos kernel: [34675.182227] ipw2100: U ipw2100_wx_set_scan Initiating scan... Aug 12 07:18:34 galapagos kernel: [34675.214269] ipw2100: U ipw2100_wx_set_mode SET Mode -> 2 Aug 12 07:18:34 galapagos kernel: [34675.345948] ipw2100: U ipw2100_wx_set_essid ESSID set to current ESSID. Aug 12 07:18:34 galapagos kernel: [34675.381779] ipw2100: U ipw2100_wx_set_wap SET BSSID -> 00:19:cb:4e:b9:42 Aug 12 07:18:34 galapagos NetworkManager: <info> (eth1): supplicant connection state: associating -> disconnected Aug 12 07:18:34 galapagos NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning Aug 12 07:18:34 galapagos NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating WPAS DISCONNECTED (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was associating) WPAS SCANNING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was disconnected) WPAS ASSOCIATING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was scanning) Aug 12 07:18:39 galapagos kernel: [34680.386504] ipw2100: U ipw2100_wx_set_scan Initiating scan... Aug 12 07:18:39 galapagos kernel: [34680.438528] ipw2100: U ipw2100_wx_set_mode SET Mode -> 2 Aug 12 07:18:39 galapagos kernel: [34680.570269] ipw2100: U ipw2100_wx_set_essid ESSID set to current ESSID. Aug 12 07:18:39 galapagos kernel: [34680.606064] ipw2100: U ipw2100_wx_set_wap SET BSSID -> 00:19:cb:4e:b9:42 Aug 12 07:18:39 galapagos NetworkManager: <info> eth1: link timed out. Aug 12 07:18:39 galapagos NetworkManager: <info> (eth1): supplicant connection state: associating -> disconnected Aug 12 07:18:39 galapagos NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning Aug 12 07:18:39 galapagos NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating WPAS DISCONNECTED (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was associating) WPAS SCANNING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was disconnected) WPAS ASSOCIATING (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was scanning) Aug 12 07:18:44 galapagos kernel: [34685.610882] ipw2100: U ipw2100_wx_set_scan Initiating scan... Aug 12 07:18:44 galapagos kernel: [34685.715438] ipw2100: U ipw2100_wx_set_mode SET Mode -> 2 Aug 12 07:18:44 galapagos kernel: [34685.846553] ipw2100: U ipw2100_wx_set_essid ESSID set to current ESSID. Aug 12 07:18:44 galapagos kernel: [34685.882356] ipw2100: U ipw2100_wx_set_wap SET BSSID -> 00:19:cb:4e:b9:42 Aug 12 07:18:44 galapagos NetworkManager: <info> (eth1): supplicant connection state: associating -> disconnected Aug 12 07:18:44 galapagos NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning Aug 12 07:18:44 galapagos NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating Device State FAILED (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3, was CONFIG) PROP State 9 (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3) SIG /o/f/NM: o.f.NM.PropertiesChanged(dbus.Dictionary({dbus.String(u'ActiveConnections'): dbus.Array([dbus.ObjectPath('/org/freedesktop/NetworkManager/ActiveConnection/22'), dbus.ObjectPath('/org/freedesktop/NetworkManager/ActiveConnection/26')], signature=dbus.Signature('o'), variant_level=1)}, signature=dbus.Signature('sv')),) SIG /o/f/NM/AC/26: o.f.NM.C.A.PropertiesChanged(dbus.Dictionary({dbus.String(u'State'): dbus.UInt32(0L, variant_level=1)}, signature=dbus.Signature('sv')),) WPAS DISCONNECTED (/fi/epitest/hostap/WPASupplicant/Interfaces/6, was associating) Device State DISCONNECTED (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3, was FAILED) PROP State 3 (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3) PROP Ip4Config / (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3) PROP ActiveAccessPoint / (/org/freedesktop/Hal/devices/net_00_04_23_98_22_a3) SIG /o/f/NM: o.f.NM.PropertiesChanged(dbus.Dictionary({dbus.String(u'ActiveConnections'): dbus.Array([dbus.ObjectPath('/org/freedesktop/NetworkManager/ActiveConnection/22')], signature=dbus.Signature('o'), variant_level=1)}, signature=dbus.Signature('sv')),) Aug 12 07:18:49 galapagos kernel: [34690.268980] ipw2100: U ipw2100_wx_set_essid Setting ESSID to ANY Aug 12 07:18:49 galapagos kernel: [34690.355682] ipw2100: U ipw2100_wx_get_mode GET Mode -> 2 Aug 12 07:18:49 galapagos NetworkManager: <info> Activation (eth1/wireless): association took too long, failing activation. Aug 12 07:18:49 galapagos NetworkManager: <info> (eth1): device state change: 5 -> 9 Aug 12 07:18:49 galapagos NetworkManager: <info> Activation (eth1) failed for access point (MySSID) Aug 12 07:18:49 galapagos NetworkManager: <info> Marking connection 'MyWlan' invalid. Aug 12 07:18:49 galapagos NetworkManager: <info> Activation (eth1) failed. Aug 12 07:18:49 galapagos NetworkManager: <info> (eth1): device state change: 9 -> 3 Aug 12 07:18:49 galapagos NetworkManager: <info> (eth1): deactivating device (reason: 0). Reproducible: Always Steps to Reproduce: 1. Try to connect with knetworkmanager or nm-applet 2. 3. Actual Results: Connection attempt fails Expected Results: WLAN connection for eth1 -- 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#c1 --- Comment #1 from Stefan Quandt <squan@web.de> 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#c2 --- Comment #2 from Stefan Quandt <squan@web.de> 2009-08-25 00:50:54 MDT --- Still not way to connect to my WLAN with 11.2 Milestone 6. bug 441511,comment 9 implicates that ipw2100 may also fail on _unencrypted_ networks. So this report may be a duplicate of bug 441511 (if so, summary of 441511 should be broadened accordingly). http://bugzilla.novell.com/show_bug.cgi?id=441511 -- 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 <squan@web.de> 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 User squan@web.de added comment http://bugzilla.novell.com/show_bug.cgi?id=530264#c4 --- Comment #4 from Stefan Quandt <squan@web.de> 2009-08-30 13:31:34 MDT --- Since NetworkManager claims "No secrets needed" for a WEP encrypted connection I wiped all networkmanager user connections from the .kde4/share subdirs. The behaviour on connection attempts (using KDE4 knetworkmanager client) was then _different_: 1) WEP now fails with Aug 30 21:16:50 galapagos NetworkManager: <info> (eth1): device state change: 5 -> 6 Aug 30 21:16:50 galapagos NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Aug 30 21:16:50 galapagos NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: Rejected send message, 9 matched rules; type="method_call", sender=":1.839" (uid=0 pid=14184 comm="/usr/sbin/NetworkManager) interface="org.freedesktop.NetworkManagerSettings.Connection.Secrets" member="GetSecrets" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManagerUserSettings" (uid=1002 pid=14197 comm="knetworkmanager)). 2) Unencrypted connection fails with like this Aug 30 21:12:29 galapagos NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating Aug 30 21:12:33 galapagos NetworkManager: <info> eth1: link timed out. Aug 30 21:12:34 galapagos NetworkManager: <info> (eth1): supplicant connection state: associating -> disconnected Aug 30 21:12:34 galapagos NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning Aug 30 21:12:34 galapagos NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating Aug 30 21:12:39 galapagos NetworkManager: <info> (eth1): supplicant connection state: associating -> disconnected Aug 30 21:12:39 galapagos NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning Aug 30 21:12:40 galapagos NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating Aug 30 21:12:43 galapagos NetworkManager: <info> Activation (eth1/wireless): association took too long, failing activation. Aug 30 21:12:43 galapagos NetworkManager: <info> (eth1): device state change: 5 -> 9 -- 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 <sqiu@novell.com> 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 lasse.penttinen@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=530264#c5 Lasse Penttinen <lasse.penttinen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lasse.penttinen@gmail.com --- Comment #5 from Lasse Penttinen <lasse.penttinen@gmail.com> 2009-10-16 13:36:50 MDT --- I tried the RC1 KDE4 live CD on my Thinkpad T41 with ipw2100 wirelees, and the WLAN did not function at all - it was totally disabled. Works fine with 11.1, which I am using to write this. -- 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 <squan@web.de> 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#c7 --- Comment #7 from Lasse Penttinen <lasse.penttinen@gmail.com> 2009-11-07 09:03:17 MST --- I tried again with the latest RC2 using the same ThinkPad T41 (ipw2100), and now the device seemed to be functional. However, I was not able to connect to WPA2 secured accesspoint. I do not have unsecured APs available, so I could not test further. -- 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 <lasse.penttinen@gmail.com> 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 <squan@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major --- Comment #9 from Stefan Quandt <squan@web.de> 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 <squan@web.de> 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#c9 Stefan Quandt <squan@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major Severity|Normal |Major --- Comment #9 from Stefan Quandt <squan@web.de> 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 <squan@web.de> 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#c11 Seppo Lehtikangas <novell.com@tankenao.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novell.com@tankenao.se --- Comment #11 from Seppo Lehtikangas <novell.com@tankenao.se> 2010-02-07 14:41:25 UTC --- In my system(HP Compaq nc8000) there is differens between traditional and Networkmanager. Traditional way I get both LAN and WLAN connections and everything works fine. At start system uses WLAN in ping. Later system uses that connection (LAN/WLAN) which was started first(perhaps this is what happens at primary start). NetworkManager connects only LAN and leaves WLAN unconnected.I need only check NetworkManager in Yast to get this result. Shifting back to traditional in Yast makes everything to work again. There is no way to get WLAN working under Networkmanager. -- 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 <gekker@novell.com> 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#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |bnc-team-gnome@forge.provo. |ovo.novell.com |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 <squan@web.de> 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#c Marcus Meissner <meissner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-gnome@forge.provo. |vbotka@novell.com |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#c14 Vladimir Botka <vbotka@novell.com> 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 <vbotka@novell.com> 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#c15 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |vbotka@novell.com InfoProvider| |squan@web.de --- Comment #15 from Vladimir Botka <vbotka@novell.com> 2010-07-29 10:02:40 UTC --- Could you turn the NetworkManager off in yast and try to isolate the problem as described in [1] ? [1] http://en.opensuse.org/SDB:Tracking_down_wireless_problems#How_to_set_up_a_c... -- 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 <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.
http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c17 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |squan@web.de --- Comment #17 from Vladimir Botka <vbotka@novell.com> 2010-07-29 20:40:34 UTC --- (In reply to comment #16)
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
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
There must some mess in the rfkill synchronization with the radio of the adapter. 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. You can always check with the rfkill utility. You can try wpa_gui from the package wpa_supplicant-gui instead of NM. To use wpa_gui you'll have to turn NM off in Yast and configure wpa_supplicant for wpa_gui to connect. The rfkill issue depends on the HW and BIOS of your computer. I'm afraid I can neither fix it nor forward you further. I'll keep this bug open for you to try. If it works for you then I suggest to close this bug. -- 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 <squan@web.de> 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#c19 --- Comment #19 from Vladimir Botka <vbotka@novell.com> 2010-07-30 17:02:52 UTC --- (In reply to comment #18)
When did this fix go into openSUSE?
ipw2100 is no longer supported by Intel AFAIK (the same as ipw2200). Unfortunately there are no resources on our side to fix Intel driver. -- 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 <squan@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|squan@web.de | --- Comment #20 from Stefan Quandt <squan@web.de> 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.
http://bugzilla.novell.com/show_bug.cgi?id=530264 http://bugzilla.novell.com/show_bug.cgi?id=530264#c21 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |squan@web.de --- Comment #21 from Vladimir Botka <vbotka@novell.com> 2010-08-02 19:11:51 UTC --- (In reply to comment #20)
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
bugzilla.kernel.org suggests: "An update of the BIOS to A03 solves the issue." Could you try to flash the latest bios ? -- 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 <squan@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|squan@web.de | --- Comment #22 from Stefan Quandt <squan@web.de> 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.
https://bugzilla.novell.com/show_bug.cgi?id=530264 https://bugzilla.novell.com/show_bug.cgi?id=530264#c23 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |WONTFIX --- Comment #23 from Vladimir Botka <vbotka@novell.com> 2010-09-06 11:36:35 UTC --- Unfortunately there is not much I can do when the BIOS blocks the card by default [1] as described in C16. I'd suggest to close here as WONTFIX. As a workaround you can start the script [2] (or modifications) on login. [1] 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no [2] #!/bin/bash sudo /usr/sbin/rfkill unblock all -- 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.
participants (1)
-
bugzilla_noreply＠novell.com