Bug 393441

Summary: KNetworkManager doesn't handle rfkill switch on wlan cards
Product: [openSUSE] openSUSE 11.0 Reporter: Alexander Rössler <alexanderroessler>
Component: Mobile DevicesAssignee: Christian Zoz <zoz>
Status: RESOLVED NORESPONSE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P2 - High CC: clarkt, suse, wstephenson
Version: Beta 3   
Target Milestone: ---   
Hardware: i586   
OS: openSUSE 11.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Alexander Rössler 2008-05-22 06:20:21 UTC
If you turn off the WLAN Card per a hardware button on the notebook the Networkmanager dont finds the Network automatically if you turn it on, you must start it manually.
Comment 1 Helmut Schaa 2008-05-26 07:16:23 UTC
Alexander, could you please attach /var/log/NetworkManager one minute after enabling wireless using the killswitch?
Comment 2 Alexander Rössler 2008-05-26 17:52:19 UTC
No change in the logfile

PS: the bug only appears if you started the notebook up with WLAN switched to off
Comment 3 Helmut Schaa 2008-05-28 13:53:04 UTC
Which wireless card do you use?
Comment 4 Alexander Rössler 2008-05-28 14:23:39 UTC
Intel PRO/Wireless 3945ABG
Comment 5 Alexander Rössler 2008-05-28 14:24:46 UTC
The Notebook is Fujitsu Siemens Amilo Pi1536
Comment 6 Helmut Schaa 2008-05-28 14:36:04 UTC
Could you please check if "iwlist scan" finds your access point after turning wireless off and on again using the killswitch?

Maybe a duplicate of bug #391774.
Comment 7 Alexander Rössler 2008-05-28 14:53:48 UTC
It wirtes:
wlan0 Interface doesn't support scanning: Network is down
Comment 8 Helmut Schaa 2008-06-18 15:56:50 UTC
*** Bug 367902 has been marked as a duplicate of this bug. ***
Comment 9 Dirk Mueller 2008-07-14 09:00:12 UTC
please run ifconfig wlan0 up before then and rerun iwlist scan then
Comment 11 Christian Zoz 2008-10-16 14:32:36 UTC
No information provided since some month.
Feel free to reopen this bug if this problem still persists and you can provide the information requested in comment 9.