Realtek 8723BE wireless adapter establishes connection then unstable and intermittent

English Network/Internet
1

Hi,

The wireless device on my laptop is able to connect to networks but within between 1 to 5 minutes, the connection slows to a stop. Sometimes it disconnects completely, most of the time it will appear connected in NetworkManager but no activity registers, iptraf or wireshark shows some packet activity but not much. If I try to ping my router I get destination host unreachable. After another ten minutes or so it might burst into life briefly, enough time for a couple of web pages to load maybe, and then the activity graph flatlines for another ten minutes. If I try to disconnect and reconnect it usually gets stuck setting the network address (according to the NM widget), or appears to connect but activity is flat and I still cant ping my router.

When its connected and working well the bit rate shows as 72Mb/s in iwconfig, when it slows down it shows as 7.2Mb/s, and if I try to force the speed back up with by running iwconfig wlo1 rate 72M it drops to 1Mb/s.

The Getting Wireless to Work sticky recommends disabling ipv6 but I’m not clear how to do that with NM or otherwise. I also have VMWare player installed which has created two network devices, vmet1 and vmnet8, which appear connected in NM at startup so I figured these may have been interfering with things, but disabling them has no apparent affect.

Hard wired connections are fine and it is definitely not a physical problem with the wireless hardware because I’m dual booting with Windows 10 and no such problems there. It is not specific to any router that I’m connecting to, I get the same problem whether connecting to my home router, mobile hotspot or public wifi hotspot.

I found a post that recommended updating kernel-firmware which I did, and that seemed to fix the problem for two days, then it reverted back to type with the same intermittent-ness. I tried that again today and again the connection seemed stable for about an hour, then died again. It’s driving me mad.

>:(

I’m running openSuse 13.2, lspci reports the adapter is a Realtek RTL8723BE PCIe Wireless Network Adapter and lsmod | grep rtl says the following kernel modules are loaded:

rtl8723be 125219 0
btcoexist 54439 1 rtl8723be
rtl8723_common 27808 1 rtl8723be
rtl_pci 35670 1 rtl8723be
rtlwifi 95392 2 rtl_pci,rtl8723be
mac80211 691383 3 rtl_pci,rtlwifi,rtl8723be
cfg80211 547052 2 mac80211,rtlwifi

I’m no noob but no network analyst either, so I’m not sure where to look or how to interpret the things I do know like iptraf and wireshark. I’ve connected with wpa_supplicant and this appears to show frequent disconnects and reconnects but again I’m not sure how to interpret the output. I haven’t spent much time with networking for a few years, the whole transition from the old ifconfig to ip and NM passed me by and I’ve sort of managed to muddle along making connections with NM on my desktop since but now I want to use suse on my laptop this is a big barrier and it’s getting desperate, I might have to start using Windows. Here’s the full lspci output for the device and will provide logs on request, any help will be gratefully received.

02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter
Subsystem: Hewlett-Packard Company Device 804c
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 36
[size=1]Region 0: I/O ports at 3000
Region 2: Memory at f0c00000 (64-bit, non-prefetchable) [size=16]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Via message/WAKE#
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis+, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Device Serial Number 00-23-b7-fe-ff-4c-e0-00
Capabilities: [150 v1] Latency Tolerance Reporting
Max snoop latency: 0ns
Max no snoop latency: 0ns
Capabilities: [158 v1] L1 PM Substates
L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
PortCommonModeRestoreTime=150us PortTPowerOnTime=150us
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be

Cheers
Rob[/size][/size]

2

… more wierdness… I’ve tried configuring the interface in YaST by changing the management service to wicked and editing the interface configuration there. It must have connected to my home router because ip addr showed that it had been assigned an IP address, but when I tried pinging my router and I get ‘destination host unreachable’.

If I run iwlist wlo1 scan sometimes I get ‘no scan results’ but if I keep trying I get some meaningful output after a couple of tries. Here its is (for the router I’m trying to connect to):

      Cell 02 - Address: 4C:09:D4:E4:A8:F7
                Channel:1
                Frequency:2.412 GHz (Channel 1)
                Quality=30/70  Signal level=-80 dBm  
                Encryption key:on
                ESSID:"badgernet"
                Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                          24 Mb/s; 36 Mb/s; 54 Mb/s
                Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                Mode:Master
                Extra:tsf=00000104353ea9a8
                Extra: Last beacon: 922ms ago
                IE: Unknown: 00096261646765726E6574
                IE: Unknown: 010882848B962430486C
                IE: Unknown: 030101
                IE: Unknown: 050400010000
                IE: Unknown: 2A0100
                IE: Unknown: 2F0100
                IE: IEEE 802.11i/WPA2 Version 1
                    Group Cipher : TKIP
                    Pairwise Ciphers (2) : CCMP TKIP
                    Authentication Suites (1) : PSK
                IE: Unknown: 32040C121860
                IE: Unknown: 2D1A3C191BFFFF000000000000000000000000000000000000000000
                IE: Unknown: 3D1601001700000000000000000000000000000000000000
                IE: Unknown: 7F080000000000000040
                IE: Unknown: DD180050F204104A00011010440001021049000600372A000120
                IE: Unknown: DD090010180204000C0000
                IE: WPA Version 1
                    Group Cipher : TKIP
                    Pairwise Ciphers (2) : CCMP TKIP
                    Authentication Suites (1) : PSK
                IE: Unknown: DD180050F2020101840003A4000027A4000042435E0062322F00
3

In the wicked case: don’t forget to set your router’s ip as the gateway address in Yast.

4

On Sun 13 Sep 2015 12:26:01 PM CDT, hobrob wrote:

… more wierdness… I’ve tried configuring the interface in YaST by
changing the management service to wicked and editing the interface
configuration there. It must have connected to my home router because
ip addr showed that it had been assigned an IP address,
but when I tried pinging my router and I get ‘destination host
unreachable’.

If I run iwlist wlo1 scan sometimes I get ‘no scan
results’ but if I keep trying I get some meaningful output after a
couple of tries. Here its is (for the router I’m trying to connect to):

Cell 02 - Address: 4C:09:D4:E4:A8:F7
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=30/70 Signal level=-80 dBm
Encryption key:on
ESSID:“badgernet”
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00000104353ea9a8
Extra: Last beacon: 922ms ago
IE: Unknown: 00096261646765726E6574
IE: Unknown: 010882848B962430486C
IE: Unknown: 030101
IE: Unknown: 050400010000
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown:
2D1A3C191BFFFF000000000000000000000000000000000000000000
IE: Unknown:
3D1601001700000000000000000000000000000000000000
IE: Unknown: 7F080000000000000040
IE: Unknown:
DD180050F204104A00011010440001021049000600372A000120
IE: Unknown: DD090010180204000C0000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown:
DD180050F2020101840003A4000027A4000042435E0062322F00

Hi
Try adding the following file called 50-rtl8723be.conf
in /etc/modprobe.d/

In the file add the following line and reboot;


options rtl8723be fwlps=N ips=N

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel
3.12.44-52.10-default If you find this post helpful and are logged into
the web interface, please show your appreciation and click on the star
below… Thanks!

5

Good point, will try that.

6

I found an Ubuntu forum post that said power management is an issue and recommended the above which I tried and didn’t work, but without prefixing the file with 50-. Presumably that relates to the run order, I’ll try again with that prefix but not hopeful that will make a difference.

I’m currently running a software update, including updating kernel-firmware (again) so I’ll wait for that to finish.

modinfo says there is a debug parameter that can be set to 0-5, default 0. If I set this to a non-zero where will the debug output go? System log?

Many thanks

7

Hi
It should log and use the journalctl command to show log info.

Is this a kernel module,if so what kernel are you running, can you show the output from;


uname -a
/sbin/modinfo rtl8723be
8

The file in /etc/modprobe.d/ hasn’t worked. Yes it’s a kernel module, output as requested:

snowy:~ # uname -a
Linux snowy.site 3.16.7-24-desktop #1 SMP PREEMPT Mon Aug 3 14:37:06 UTC 2015 (ec183cc) x86_64 x86_64 x86_64 GNU/Linux
snowy:~ # modinfo rtl8723be
filename:       /lib/modules/3.16.7-24-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8723be/rtl8723be.ko
firmware:       rtlwifi/rtl8723befw.bin
description:    Realtek 8723BE 802.11n PCI wireless
license:        GPL
author:         Realtek WlanFAE <wlanfae@realtek.com>
author:         PageHe  <page_he@realsil.com.cn>
srcversion:     C94095C986767A931B924EF
alias:          pci:v000010ECd0000B723sv*sd*bc*sc*i*
depends:        rtlwifi,rtl8723-common,rtl_pci,btcoexist,mac80211
intree:         Y
vermagic:       3.16.7-24-desktop SMP preempt mod_unload modversions 
signer:         openSUSE Secure Boot Signkey
sig_key:        03:32:FA:9C:BF:0D:88:BF:21:92:4B:0D:E8:2A:09:A5:4D:5D:EF:C8
sig_hashalgo:   sha256
parm:           swlps:bool
parm:           swenc:using hardware crypto (default 0 [hardware])
 (bool)
parm:           ips:using no link power save (default 1 is open)
 (bool)
parm:           fwlps:using linked fw control power save (default 1 is open)
 (bool)
parm:           msi:Set to 1 to use MSI interrupts mode (default 0)
 (bool)
parm:           debug:Set debug level (0-5) (default 0) (int)

Cheers

9

I had problems with this card in 13.2, disabling bluetooth in the BIOS settings solved the problem. I have just tested leap42 on this laptop, a Lenovo B5400, and there both wifi and bluetooth works.

10

Thanks, I’ll try that and report back.

11

My BIOS doesn’t have an option to disable bluetooth. I turned it off once in KDE using a widget but that made no difference, but thats not the same as disabling it at a low level so not sure if that proves anything. Anything else I can do to disable it once I’m booted?

Things have gone from bad to worse though, it’s not even scanning for networks now. Can’t see any in YaST or NM and running

iwlist wlo1 scan

consistently returns ‘No scan results’.

12

Hi
Do you have a wireless button? Push that a couple of times they usually cycle through bluetooth, then wireless to enable/disable. Else check the output from the rfkill command to block and unblock (you may need to install rfkill).

13

Another possibility is to install a newer kernel and if that’s not possible, you might be dependent on a precompiled kernel module, install a newer driver.
Kernel here http://download.opensuse.org/repositories/Kernel:/stable/standard/ just add the repo.
Driver here https://github.com/lwfinger/rtlwifi_new

14

Hi,

Do you have a wireless button?
No

Else check the output from the rfkill command to block and unblock

rfkill showed no hard or soft blocking. I then used it to block bluetooth but no change.

Also can’t turn off ipv6 in BIOS either. How best to do this once booted?

Another possibility is to install a newer kernel and … install a newer driver.

I think my kernel is up to date - kernel-desktop 3.16.7-24.1. Do you think changing to kernel-default would make any difference? What do I need to do with the github url to get the driver? I can’t add it as a repository in YaST. If I go into the folder with the driver I want there are makefiles and headers and the like. Do I need to download these individually and compile them?

Running journalctl -r -u NetworkManager shows a successful dhcp exchange with my router, and then a disconnect four minutes later with reason code 7. Any ideas where I could find out more about reason 7? Google searches haven’t turned up much.

Sep 19 11:57:28 snowy.site NetworkManager[1578]: <info> (wlo1): supplicant interface state: 4-way handshake -> completed
Sep 19 11:57:27 snowy.site NetworkManager[1578]: <info> (wlo1): supplicant interface state: associated -> 4-way handshake
Sep 19 11:57:27 snowy.site NetworkManager[1578]: <info> (wlo1): supplicant interface state: associating -> associated
Sep 19 11:57:27 snowy.site NetworkManager[1578]: <info> (wlo1): supplicant interface state: authenticating -> associating
Sep 19 11:57:27 snowy.site NetworkManager[1578]: <info> (wlo1): supplicant interface state: completed -> authenticating
Sep 19 11:57:27 snowy.site NetworkManager[1578]: <warn> Connection disconnected (reason 7)
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> Activation (wlo1) successful, device activated.
Sep 19 11:53:33 snowy.site NetworkManager[1578]: bound to 192.168.1.84 -- renewal in 76789 seconds.
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> Policy set 'badgernet' (wlo1) as default for IPv4 routing and DNS.
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> NetworkManager state is now CONNECTED_GLOBAL
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> NetworkManager state is now CONNECTED_LOCAL
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> (wlo1): device state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> (wlo1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Commit) complete.
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> (wlo1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Commit) started...
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info>   domain name 'doubleudotcom.com'
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info>   nameserver '192.168.1.100'
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info>   hostname 'snowy'
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info>   lease time 172800
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info>   server identifier 192.168.1.100
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info>   gateway 192.168.1.100
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info>   plen 24 (255.255.255.0)
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info>   address 192.168.1.84
Sep 19 11:53:33 snowy.site NetworkManager[1578]: <info> (wlo1): DHCPv4 state changed preinit -> bound
Sep 19 11:53:33 snowy.site dhclient[2339]: bound to 192.168.1.84 -- renewal in 76789 seconds.
Sep 19 11:53:33 snowy.site NetworkManager[1578]: DHCPACK from 192.168.1.100 (xid=0x2b7f3c63)
Sep 19 11:53:33 snowy.site dhclient[2339]: DHCPACK from 192.168.1.100 (xid=0x2b7f3c63)
Sep 19 11:53:33 snowy.site NetworkManager[1578]: DHCPREQUEST on wlo1 to 255.255.255.255 port 67 (xid=0x2b7f3c63)
Sep 19 11:53:33 snowy.site dhclient[2339]: DHCPREQUEST on wlo1 to 255.255.255.255 port 67 (xid=0x2b7f3c63)
Sep 19 11:53:28 snowy.site NetworkManager[1578]: DHCPOFFER from 192.168.1.100
Sep 19 11:53:28 snowy.site dhclient[2339]: DHCPOFFER from 192.168.1.100
Sep 19 11:53:28 snowy.site NetworkManager[1578]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 4 (xid=0x2b7f3c63)
Sep 19 11:53:28 snowy.site NetworkManager[1578]: Sending on   Socket/fallback
Sep 19 11:53:28 snowy.site NetworkManager[1578]: Sending on   LPF/wlo1/70:77:81:2f:aa:93
Sep 19 11:53:28 snowy.site NetworkManager[1578]: Listening on LPF/wlo1/70:77:81:2f:aa:93
Sep 19 11:53:28 snowy.site dhclient[2339]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 4 (xid=0x2b7f3c63)

Thank you both for all your help so far, I’m learning a lot if not fixing the problem!

Cheers

15

Kernel-default would make no difference. Let’s try to update the driver. First make sure the kernel development tools are installed.
Open up Yast>Software management select patterns, scroll down to the development section and make sure that the pattern Linux Kernel Development is installed.
Open up a terminal and cd to your home folder and run the following command:

git clone https://github.com/lwfinger/rtlwifi_new

This will create a new folder rtlwifi_new, cd to that folder and, still as your ordinary user, run the following command:

make

If no errors su too root and run the following command:

make install

If no errors reboot and the new driver should be used.

16

Howdy,

Update:

No errors, booted, and basically same old story but lasted a bit longer than usual. Looking at journalctl, it looked as though one of the vmware interfaces was using grabbing wlo1 to use as a bridge so I’ve uninstalled vmware player and since then it’s been a lot more stable. Not perfect, it has dropped a couple of times, and then, as before, either gets stuck setting network network address or appears to connect but can’t ping router. But not before maintaining a connection for an hour or more.

For that reason I don’t think I’m out of the woods yet, and I really need vmware so at some point I’ll have to reintroduce it and figure out what’s happening, and maybe it was the driver update, just needed a bit longer to click into action. Will also set the debug level for the module and have a look at the output. I made the mistake of going straight to debug level 5 and it generated too much output to make sense of, but did appear to show repeated associations and disassociations so might be worth revisiting when I encounter the problem. Will try and find time later in the week, but for now I’m just happy to have made a bit of progress.

Cheers :slight_smile:

17

One step forward two steps back. Since removing VMWare player I was able to make a stable connection to my Android mobile phones hotspot which was good but connections to my home router and other hotspots were still problematic. When in a hotel I noticed that the number of networks being picked up when I was booted in Windows was far greater than when I was in Suse, this and the fact that I always have my phone close to the laptop led me to believe that the problem might be related to signal strength. The same is true at home, more networks are picked up in Windows.

I moved my router from a cupboard into the same room as the laptop and I had a stable connection for a whole three days. Unfortunately, I was getting slow transfer speeds over sftp with a workstation on my LAN, averaging out at about 30KB/s when my phone can connect with the same machine and sftp transfer speeds are measured in hundreds of KB/s. I found some advice to try changing the MTU on the client side and after that I couldn’t re-establish a connection with my router. That isn’t my current problem though, things have gone from bad to worse thanks to advice on the wireless HCL page.

To help isolate the problem I bought a usb wireless adapter, when I plugged it in it immediately found more networks that the inbuilt PCI adapter but when I tried to connect to them the system would hang. Fine, I thought, I probably just need to get drivers. This USB adapter is also a Realtek chipset, but rtl8192cu. The HCL advises using the driver in the compat-wireless package but no clear advice on where to get it, a few more searches and I found this has changed to wireless-drivers and then backports for OpenSuse 13.2.

The end of this thread says:

The thing to do is navigate to

http://www.kernel.org/pub/linux/kern…kports/stable/

and select the directory with the latest version. At the moment, that is
v3.10-rc1. Download the .bz2 file from that directory, unpack it with a “tar
jxvf” command, change to the resulting directory, and “make menuconfig”. After
selecting the driver(s) you want, do “make” and “sudo make install”.

I found the most recent version here:

Index of /pub/linux/kernel/projects/backports/stable/v4.2-rc1/

I untarred it, did make menuconfig and the rest. When I rebooted both the PCI and USB adapters had disappeared completely. They are no longer listed in hwinfo, no longer listed in lspci or lsusb, and YaST only detects my cabled Ethernet adapter. In short, it was a complete disaster. As I understand it, because it was a compile-install there is no easy way to roll it back, if at all. I’m very disappointed and I’m at a complete loss, the only way forward I can think of is a complete OS re-install so I’m eager to hear if anyone has any better ideas.

18

OK, you can forget the second half of my last post. I read the backports wiki here in a bit more detail and ran make uninstall, and all of my devices are back to their normal intermittent state, but at least they’re there.

If anyone can help me figure out how to get the rtl8192cu usb adapter to work I would be grateful. It can see a lot more networks than the inbuilt adapter so I think it could be the answer if I can just get it to work.

19

I installed in OpenSuse 13.2,Leap 42.1 the next WiFi adapter:
EW-7822UAC AC1200 USB3 Wireless Adapter using the next driver:

rtl8812AU_linux_v4.3.20_16317.20160108

I download the driver from Edimax web site:
http://us.edimax.com/edimax/download/download/data/edimax/us/download/for_home/wireless_adapters/wireless_adapters_ac1200_dual-band/ew-7822uac

But before they provided a driver I used the github one:
GitHub - gnab/rtl8812au: Realtek 802.11n WLAN Adapter Linux driver (these no longer works with kernel >3.x

To compile the driver open a Terminal (i.e.konsole)

cd /the_folder_of_drive /Command to change directory to where your driver is/

make clean

make /Command to compile/

make install /Command to compile/

Close and open session to allowed the kernel load the driver.

While compiling (make command) I get an error:

# make
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.1.12-1-default/build M=/home/user/rtl8812AU_linux_v4.3.20_16317.20160108  modules
make[1]: 

*** /lib/modules/4.1.12-1-default/build: No existe el fichero o el directorio.  Alto.
Makefile:1656: recipe for target 'modules' failed
make: *** [modules] Error 2
linux-pj:/home/user/rtl8812AU_linux_v4.3.20_16317.20160108 #

And what is in these post help me:
Open up Yast>Software management select patterns, scroll down to the development section and make sure that the pattern Linux Kernel
Development is installed.

After installed the patterns restart the system and try make command again.

I suggest to find the newest driver for your wireless adapter chipset.