Are you saying that doing that doesn’t result in ‘rfkill list’ showing the ‘hp-wifi’ device? If not, please supply laptop model details (in case they’re relevant).
yes you got it right… after doing modprobe, rfkill list still shows phy0 ONLY…My HP model is 6-1011TU
Thanks. Is it possible for you to boot up in Windows and try to enable there? I have read accounts of others who say that this has been necessary for some hardware (which is a worry if true).
For example
Some relief… I rebooted windows…Swtched it on…then rebooted opsensuse… Now airplane mode gone… and connected to wifi network(although its UNSTABLE, as keep popping up password window to reconnect after some time). output of rfkill list all
ubiroute@linux-984x:~> sudo /usr/sbin/rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
I can do soft block wifi, but hardware switch still not working. means to say its not disabling wireless now. It used to work somehow in opensuse 12.2.
This suse version seems to have some problem.
Problem solved but partially…Sorry for engaging you for long time. Thanks for you time…
Good. As hoped. 
For others who come searching, a similar discussion here
(although its UNSTABLE, as keep popping up password window to reconnect after some time).
That is a different issue. I’ve seen simila funny behaviour in a KDE environment when kwallet not being used. Might be worth starting a new thread on that if necessary.
output of rfkill list all
ubiroute@linux-984x:~> sudo /usr/sbin/rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no
I can do soft block wifi, but hardware switch still not working. means to say its not disabling wireless now. It used to work somehow in opensuse 12.2.
This suse version seems to have some problem.
Problem solved but partially…Sorry for engaging you for long time. Thanks for you time…
I still think that has to do with ‘hp-wmi’ support somehow. Anyway, if you have connectivity for now, I guess that’s all that counts.
That is a different issue. I’ve seen simila funny behaviour in a KDE environment when kwallet not being used. Might be worth starting a new thread on that if necessary.
Yeah thats a different issue, and I am thinking to start a new thread.as that problem was encountered in previous version of opensuse also.
I still think that has to do with ‘hp-wmi’ support somehow. Anyway, if you have connectivity for now, I guess that’s all that counts.
I expect hp-wmi support gets improved over time… As of now my airplane problem is solved, as a bit relif. Thanks you your precious time, as I hope this extended thread would help some other guy in problem.
Thanks once again… Have a good time…
Try to setup the connection as “System connection” in KDE’s “Connection Manager”. KWallet is not used then, so if it is a KWallet issue this should fix it.
OTOH, NetworkManager asks for the password again (even if the correct one is saved) when there are problems in connecting.
So this could also be a driver issue.
en:users:drivers:brcm80211 [Linux Wireless] states this:
Please note: at least BCM4313 is not fully supported. Some models appears to work (users reported success), but some don’t, and there’s no indication that this is going to change.
You might want to try the proprietary broadcom-wl driver therefore (packages are available in the Packman repo), this should perfectly support your BCM4313 chip.
I have no idea about how hp-wmi comes into play though, or whether it works with wl.
@wolfi323 Thanks for helping once again
You might want to try the proprietary broadcom-wl driver therefore (packages are available in the Packman repo), this should perfectly support your BCM4313 chip.
I installed broadcom-wl from pacman, along with broadcom-wl-kmp-desktop also. Rebooted the system, and it works like BUTTER. Thanks again
Good to hear!