Cannot scan wireless networks

English Network/Internet
1

Hello,

Recently I have installed OpenSUSE 13.2. However, it cannot detect my wireless networks, it doesn’t scan for wireless networks.
I read something about going to ‘Yast’, click ‘Network Settings’, go to ‘Global Options’ tab and then choose for the ‘Wicked Service’. From there I am stuck. I have read something about ‘User controlled with Network manager’ but there is no such option there for me. I have enclosed an image for further details.

Thanks in advance

http://i61.tinypic.com/104jk8z.jpg

2

in the General Network Settings, Network Setup Method box is shown ‘Wicked service’,
press the down button at the right side of the box and from the pull-down menu,
select ‘NetworkManager Services’ then press OK

then reboot

or give the cmds from a terminal,
systemctl stop wickedd.service
systemctl disable wicked.service
systemctl --force enable NetworkManager.service
systemctl start network.service

3

Similar situation: No Wi-Fi connectivity, and Net Manager in 13.2 doesn’t show the “Configure” button used in 13.1. The wired Enet LAN port works (or I might not be writing to you :-). My Toshiba NB has a button to turn Wi-Fi on and off; it is ON. In Net Mngr the two icons for Wi-Fi and Airplane Mode (?) have a red “X” on them.
Have looked at Services Manager in Yast and see that Wicked is disabled and inactive, Net Manager is active. Suggestions appreciated.

4

Check the ‘soft-block’ status of the wireless device with ‘rfkill’.

/usr/sbin/rfkill list

and unblock if necessary

sudo /usr/sbin/rfkill unblock wifi

That should take care of the red ‘X’ in NM.

5

Thanks for the quick response. I ran rfkill unblock, which didn’t confirm anything, just returned the the prompt in a terminal window. Rebooted, but still have the red “X” on the two icons and no Wi-Fi. rfkill list now says ‘soft blocked: no’ Did I miss something?

6

It won’t, but you should then have been able to confirm that it was unblocked with ‘rfkill list’ again.

Rebooted, but still have the red “X” on the two icons and no Wi-Fi. rfkill list now says ‘soft blocked: no’ Did I miss something?

No need to have rebooted, just proceed with configuring/connecting with NM. Anyway, it seems that upon booting up that the device is disabled again.

7

BTW, can you tell me if there is a systemd-rfkill service available with openSUSE 13.2?

systemctl list-units|grep rfkill

If there is, check it’s status

systemctl status systemd-rfkill

Just for informational purposes:
http://man7.org/linux/man-pages/man8/systemd-rfkill@.service.8.html

8

fwiw

after updating on hp-625 to 13.2_86x_64 the wireless card was not detected,
verified by cmd sudo lspci

in 13.1 the card was listed but not in 13.2

eventually after inserting a wireless card usb dongle, the hw detection showed both,
in wicked both could be seen

removed the usb dongle and deleted from wicked listing

then proceeded to set up internal wireless card as normal

for future reference, is there a way to force or restart hw detection?

any ideas why the wireless card was not detected initially after KDE-Live update?
(update via wired i/f)

cheers

9

in response to error message about my message being too short, I’m adding a line.

10

The file in /var/lib/systemd/rfkill/ is 2 B and when opened displays “0” only.

11

That happened because you tried to quote my entire post. You need to edit when responding, and break apart any instructions or questions, so that they are quoted separately, with your responses outside those quoted sections.

Anyway, I think that this is the service responsible for rfkill status

systemd-rfkill@rfkill0.service                                                            loaded active exited    Load/Save RF Kill Switch Status of rfkill0

I haven’t had any experience with systemd-rfkill, but from reading the man-page

KERNEL COMMAND LINE top

   systemd-rfkill understands the following kernel command line
   parameter:

   systemd.restore_state=
       Takes a boolean argument. Defaults to "1". If "0", does not
       restore the rfkill settings on boot. However, settings will still
       be stored on shutdown.

it is possible to restore the saved state (from boot) with

systemd-rfkill systemd.restore_state=1

Obviously, you’d want to make sure that the wifi was unblocked before shutting down though, so that hopefully, it boots up with the same wifi status. (I can’t test this, as I’m not using openSUSE 13.2)

Alternatively, it can be prevented from doing anything with

systemctl mask systemd-rfkill@rfkill1.service

or perhaps prevent it from restoring the rfkill state at boot with

systemd-rfkill systemd.restore_state=0

Then reboot.

12

One last detail needed: open Network Manager and click on the box next to the Wi-Fi icon with the red “X” on it. Once checked, Wi-Fi is enabled and automaticaly scans for access points.
Thanks for the help.

13

No problem. So, I assume all is good now? :slight_smile:

14

Yes! Speaking to you over Wi-Fi.