And if it worked during the installation process, it should work in the installed system, too.
So, why do you think it is not working? How are you trying to establish a connection?
And which openSUSE version are you actually using?
In openSUSE there are two ways to manage/configure your network connections:
the traditional method (ifup), in 13.2 replaced by Wicked Service
Normally the first is default, if you use this you have to configure your connection in YaST. In this case the desktop’s network applet does not work, those are only frontends for NetworkManager.
So I would recommend to go into YaST->Network Devices->Network Settings->Global Options, and make sure this is set to NetworkManager, not ifup or Wicked.
Then you should be able to connect using your desktop’s means.
Great Info! After reinstalling (just to be sure) and switching to NetworkManager it started again but as it happened with Ubuntu it works only for a few seconds after each reboot, then the signal seems to die off and doesn’t connect anymore.
Any way i can get that fix i’ve mentioned in my original post in OpenSuse? as i now i’m able to execute it?
But you should install dkms first (for the dkms commands to work).
This is available from the Packman repo (YaST->Software Repositories->Add->Community Repositories), which you should add anyway for full featured multimedia stuff.
You probably could build it manually without dkms too, but you’d have to repeat it after each kernel update then.
No, the message means that you don’t have the kernel headers installed.
You’d probably need kernel-desktop-devel, matching your kernel version, i.e. 3.16.6. As there was a kernel update for 13.2 already, YaST/zypper will try to install the higher version, you’d have to select 3.16.6 manually (“Versions” tab in YaST, appending the version for zypper, or just update the kernel to the latest version)
Or better go into YaST->Software Management and install the “Kernel Development” pattern (“View”->“Patterns”).
But the same version problem might exist then, so make sure to update the kernel (“kernel-desktop”), or manually select the 3.16.6 versions for all automatically selected packages where applicable.
PS: all of that should be available on your installation medium, so if you still have that, just disconnect the internet connection and insert it. You won’t have any version problems then either.
Was being optimistic, i needed it after the second whole day trying this, i really appreciate your help! learning so much as i go!
Was referring to first blacklisting rtl8192cu,rtl8192c_common and rtlwifi and then (at least in ubuntu) add 8192 to /etc/modules to load at start which obviously in OpenSuse it’s just an empty modules-load.d folder, haha loving this.
A man modules-load.d showed me the way but i was way ahead of myself anyways…here’s the error when compiling the driver:
/home/Gendo/Documents/RTL8188C_8192C_USB_linux_v4.0.2_9000.20130911/driver/rtl8188C_8192C_usb_linux_v4.0.2_9000.20130911/os_dep/linux/os_intfs.c:999:2: warning: (near initialization for ‘rtw_netdev_ops.ndo_select_queue’) [enabled by default]
cc1: some warnings being treated as errors
/usr/src/linux-3.16.7-7/scripts/Makefile.build:273: recipe for target '/home/Gendo/Documents/RTL8188C_8192C_USB_linux_v4.0.2_9000.20130911/driver/rtl8188C_8192C_usb_linux_v4.0.2_9000.20130911/os_dep/linux/os_intfs.o' failed
make: *** [/home/Gendo/Documents/RTL8188C_8192C_USB_linux_v4.0.2_9000.20130911/driver/rtl8188C_8192C_usb_linux_v4.0.2_9000.20130911/os_dep/linux/os_intfs.o] Error 1
/usr/src/linux-3.16.7-7/Makefile:1359: recipe for target '_module_/home/Gendo/Documents/RTL8188C_8192C_USB_linux_v4.0.2_9000.20130911/driver/rtl8188C_8192C_usb_linux_v4.0.2_9000.20130911' failed
make: *** [_module_/home/Gendo/Documents/RTL8188C_8192C_USB_linux_v4.0.2_9000.20130911/driver/rtl8188C_8192C_usb_linux_v4.0.2_9000.20130911] Error 2
Makefile:195: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make: *** [__sub-make] Error 2
make: Leaving directory '/usr/src/linux-3.16.7-7-obj/x86_64/desktop'
Makefile:584: recipe for target 'modules' failed
make: *** [modules] Error 2
Compile make driver error: 2
Please check error Mesg
That’s not really openSUSE-specific btw, that’s how systemd does it (so it will be like this in the next Ubuntu as well probably).
here’s the error when compiling the driver:
Hm, I don’t really see the actual error message there, but the build clearly failed.
But as that driver is from 2013, it’s likely that it just doesn’t build with 3.16.
Maybe just copying that file 8192cu-disable-power-management.conf to /etc/modprobe.d/ as mentioned in the troubleshooting section on the github page would help too? You have to remove your blacklist though, of course.
Just download the corresponding .rpm package and install it, either with “rpm -i kernel-xxx.rpm”, “zypper in kernel-xxx.rpm”, or clicking on it in your file manager. Or add the repo in YaST->Software Repositories and install it with YaST->Software Management (via the “Versions” tab as mentioned).
Maybe that would solve your problems?
The older kernel will be kept, you can always select to boot that in “Advanced Options” in the boot menu.
Btw, the updated kernel-firmware package from the above repo (noarch subdirectory) might be needed too.
I’m now writing from OpenSuse! I was so obsessed with following a guy’s blog on how to fix his specific issue (without understanding what all of it meant) and adapt the whole thing to it that i didn’t see the simplest solution which was to follow the 3 steps on http://github.com/pvaret/rtl8192cu-fixes, of course i needed to know how to get Pacman, dkms and to update the Kernel beforehand but it didn’t need to be that hard!
I now know how to navigate Yast, how to navigate and manage files in the Terminal, use Nano, Pacman commands and plenty more just from this troubleshooting.
Thanks again for your help and time, i now have a different approach to problem solving and i’m an OpenSuse user!
Ah, ok. So basically everything from that github page.
Sorry, I misunderstood you a bit.
I thought, you got those error messages when building the driver from https://github.com/pvaret/rtl8192cu-fixes.
But apparently you tried to build a completely different driver at that point…
Btw, I somehow do have the feeling that just using the 8192cu-disable-power-management.conf might be sufficient.
As I wrote already, those rtl8192cu-fixes are from 2013 and intended for Kernel 3.11, so they might not be necessary any more.
And the “troubleshooting” text seems to describe exactly your problem, no?
There is a known issue with power management on some hardware. If your WiFi connection drops after a few minutes, install the following module setting file to disable power management in your WiFi interface: