What exactly have you tried about 5 times already?
This would not work. I’ve looked there. The other option aside from Wicked Service is labeled “disabled Network Manager”. That doesn’t look promising.
No, the other options aside from “Wicked Service” are “NetworkManager Service” and “Network Services Disabled”. You need to choose the former obviously.
If you still don’t have a network icon in the panel afterwards, it might be disabled or hidden. Right-click on the small up-arrow next to the digital clock and choose “System Tray Settings”. Make sure that “Networking” is enabled and set to “Always Shown” or “Auto”, not “Hidden”.
No, I can’t. In Yast I find under the tab just a read-only list of hardware items. Nothing which allows a change to be made. Nothing. Zilch.
Then you probably have activated NetworkManager or disabled Network Services completely. For this to be changeable, you have to switch to “Wicked Service”, but it will be respected by NetworkManager as well.
Although we should probably do one step at a time, as you seem to get confused.
So, switch back to “Wicked Service”, run “modprobe ndiswrapper”, and enter Yast to get your wireless working.
Then enter YaST again, select your wireless card on “Overview”, click on “Edit”, and switch to the “Hardware” tab in the new window.
You can change the device/interface name by clicking on “Change” beside the “Device Name” on the top-left, but that’s not important now. Below (under “Kernel Module”) there’s a text field labelled “Module Name”. What does this say? Try to click on the down arrow and select “ndiswrapper” if possible. If that’s not in the list, just enter it into the text field (the left one “Module Name”, not “Options”).
http://wstaw.org/m/2015/05/27/yast.png
Does the wireless work after a reboot then?
OTOH, Wicked does/did have problems with wireless in particular that might be solved by just entering YaST and clicking OK as you did.
So I still think you should rather try with NetworkManager, even if the above doesn’t help.
I looked in the internet and found that I could change the name of my enp0s18f2u1u4 to wlan0 by editing /etc/udev/rules.d/70-persistent-net.rules
I did this and now upon reboot I have now no internet connection at all. No modprobe ndiswrapper and Yast Edit / Next / Next / OK helps. Changing this 70-persistent-net.rules file is not good.
That’s exactly what YaST does. But if you do it manually and make a mistake, this will cause problems of course.
Remove that file again, to be sure.
There’s no need to rename the interface to make it work. I just mentioned it because it’s easier to type “wlan0” than “enp0s18f2u1u4”…
Back to square one.
Well, have you told your system to load ndiswrapper at boot now or not?
fwlan is the driver.
Yes, the Windows driver.
ndiswrapper is the wrapper.
Yes, it allows to use Windows drivers in Linux.
enp0s18f2u1u4 is the device. Also your interface.
It is the interface, yes.