I purchased a Linksys WUSB6400M dongle. From what I read, the rtl8812au module is correct. I installed the module from the main update repo. The trl8812au-preempt package was installed also as well as a kernel-preempt-devel if I remember correctly. When I modprobe it, I am given the following message:
The module loads, but is shown as “used by 0” when I lsmod. It is not being associated to the dongle.
When I insert the dongle with the driver already loaded, I get:
1827.738918] usb 1-3: new high-speed USB device number 17 using xhci_hcd
1827.890838] usb 1-3: New USB device found, idVendor=13b1, idProduct=0043, bcdDevice= 2.10
1827.890843] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
1827.890847] usb 1-3: Product: WUSB6400M
1827.890849] usb 1-3: Manufacturer: Linksys
I have added a file to /etc/modules-load.d to have it load during boot and rebuilt the inirtd. I’ll post back if it works, but I suspect that I am missing something.
I found the solution. I removed the Yast installed driver and installed the driver from git source. Still didn’t work. I searched the source files for the mac address 13b1:0043 and came to a file that referenced that 0043 required rtl8822bu driver:
I have an additional problem. The module works, but the way the source was made, there is no way to install it into the kernel. There is no “make install” available in the makefile. Every boot, I have to navigate to the source folder and run:
I am not familiar enough with working with the kernel to know how to possibly get the module to be installed.
Thank you. I added your repo and all is well. On your driver description page, it is safe for you to add Linksys WUSB6400M AC1200 dongle as a card for which it will work. Everything works, including the LED.
Due to the git driver requirements, I added a stanza to /etc/NetworkManager/NetworkManager.conf and have not removed it:
I also left cfg80211.conf within /etc/modules-load.d
I have an additional question. I am trying to install the same on my Lenovo laptop. The solver is forcing me to install kernel-preempt, when only kernel-preempt-devel is installed on my primary computer. Is that unusual? I am not sure about the practice of having multiple kernels. All repos are identical between the two machines.
I found my answer to the last question. I also installed rtl8822bu-preempt by mistake. I removed it and the preempt kernel.
One more problem. On my laptop, dmesg tells me that unsigned module loading is restricted and that the kernel locked it out. It associated to the dongle, but the kernel-default won’t allow it to load.
196.328000] usb 1-1.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
196.328005] usb 1-1.4.3: Product: WUSB6400M
196.328009] usb 1-1.4.3: Manufacturer: Linksys
196.328013] usb 1-1.4.3: SerialNumber: 123456
197.203538] Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7
This was dmesg output after I inserted the dongle. rtl8822bu driver is installed and modprobe sees that it is correct for my dongle, but the kernel sees it as unsigned and won’t allow it to load, if I am reading it correctly.
It was also requested that I ran a modprobe command to see if the system is identifying the dongle and correct driver. It is"
Full dmesg output would have shown also reason for lockdown, but I am sure it is UEFI Secure Boot. SUSE kernel will enforce signed modules if you boot with Secure Boot enabled. There is no way to override it. So the options are
Disable Secure Boot.
Ask maintainer of repository to sign modules during build. They will be signed by repository key and you can enroll this key using mokutil, so kernel will trust it and accept modules signed by this key. It is even possible to submit enrollment request as part of KMP installation like is done for kernel.
I posted exactly what dmesg showed after I plugged the dongle. Nothing was left out.
It’s actually no longer necessary to troubleshoot this. I was forced to do a fresh install of Windows 10, because it refused to activate. Windows didn’t like my partition scheme, so I also deleted my openSUSE partitions and started over. Whatever happened before must have been a fluke. The dongle is apparently working correctly now. I’ve still got to get to KDE or Mate to actually check it out, but dmesg now shows the driver is loaded and registered.