Realtek 8192S not working since LE11

lomion · April 11, 2023 at 4:13 PM

I am using a USB dongle WLAN adapter for some time now.

Since upgrading to LE11 the adapter is not recognized by connman while the onboard WLAN adaper of my RPi3 is working fine (except the small antenna).

I can not recognize any error in dmesg

Code

[   33.299950] usb 1-1.5: new high-speed USB device number 5 using dwc_otg
[   33.395745] usb 1-1.5: New USB device found, idVendor=0bda, idProduct=8172, bcdDevice= 2.00
[   33.395774] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   33.395787] usb 1-1.5: Product: RTL8191S WLAN Adapter 
[   33.395797] usb 1-1.5: Manufacturer: Manufacturer Realtek 
[   33.395807] usb 1-1.5: SerialNumber: 00e04c000001
[   33.464638] r8712u: module is from the staging directory, the quality is unknown, you have been warned.
[   33.472084] r8712u: register rtl8712_netdev_ops to netdev_ops
[   33.472121] usb 1-1.5: r8712u: USB_SPEED_HIGH with 4 endpoints
[   33.472872] usb 1-1.5: r8712u: Boot from EFUSE: Autoload OK
[   33.965695] usb 1-1.5: r8712u: CustomerID = 0x000a
[   33.965727] usb 1-1.5: r8712u: MAC Address from efuse = 24:05:0f:6b:f2:ef
[   33.965744] usb 1-1.5: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
[   33.965951] usbcore: registered new interface driver r8712u

Display More

but in connman only the wired network is recognized as technology.

Any suggestions`?

**chewitt** · April 12, 2023 at 7:58 AM

Please you run "pastekodi" and share the URL so we can see the full log. The snipped you've shared appears to show the device being probed and the driver loaded. The difference between LE10 and LE11 is we've dropped the vendor driver in favour of an in-kernel driver that's in the process of replacing it.

lomion · April 12, 2023 at 8:59 PM

Here is the link: http://ix.io/4tih

**chewitt** · April 13, 2023 at 6:19 AM

Code

Feb 16 19:11:01.959281 LibreELEC kernel: usb 1-1.5: r8712u: CustomerID = 0x000a
Feb 16 19:11:01.960477 LibreELEC kernel: usb 1-1.5: r8712u: MAC Address from efuse = 24:05:0f:6b:f2:ef
Feb 16 19:11:01.961390 LibreELEC kernel: usb 1-1.5: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
Feb 16 19:11:01.962782 LibreELEC kernel: usbcore: registered new interface driver r8712u
...
Feb 16 19:11:02.386054 LibreELEC connmand[639]: wlan0 {create} index 3 type 1 <ETHER>
Feb 16 19:11:02.386091 LibreELEC connmand[639]: wlan0 {update} flags 4098 <DOWN>
Feb 16 19:11:02.386127 LibreELEC connmand[639]: wlan0 {newlink} index 3 address 24:05:0F:6B:F2:EF mtu 1500
Feb 16 19:11:02.386158 LibreELEC connmand[639]: wlan0 {newlink} index 3 operstate 2 <DOWN>
Feb 16 19:11:02.387214 LibreELEC connmand[639]: Adding interface wlan0 [ wifi ]

^ The MAC address of the USB NIC matches what ConnMan sees as wlan0. The only thing I see that looks abnormal is the interface not being brought to an UP state. What happens if you manually do "ifconfig wlan0 up" ?

lomion · April 13, 2023 at 11:05 AM

"ifconfig wlan0 up" results in the device listed in ifconfig:

Code

wlan0     Link encap:Ethernet  HWaddr 24:05:0F:6B:F2:EF
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

but connman does not change the operstate:

Code

Apr 13 12:02:00 LibreELEC systemd[1]: Started connman.service.
Apr 13 12:02:00 LibreELEC connmand[960]: Connection Manager version 1.41
Apr 13 12:02:00 LibreELEC connmand[960]: Checking loopback interface settings
Apr 13 12:02:00 LibreELEC connmand[960]: System hostname is LibreELEC
Apr 13 12:02:00 LibreELEC connmand[960]: lo {newlink} index 1 address 00:00:00:00:00:00 mtu 65536
Apr 13 12:02:00 LibreELEC connmand[960]: lo {newlink} index 1 operstate 0 <UNKNOWN>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {create} index 2 type 1 <ETHER>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {RX} 19987 packets 24142891 bytes
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {TX} 10971 packets 1271357 bytes
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {update} flags 36866 <DOWN>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {newlink} index 2 address B8:27:EB:7F:2D:31 mtu 1500
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {newlink} index 2 operstate 2 <DOWN>
Apr 13 12:02:00 LibreELEC connmand[960]: Adding interface eth0 [ ethernet ]
Apr 13 12:02:00 LibreELEC connmand[960]: wlan0 {create} index 3 type 1 <ETHER>
Apr 13 12:02:00 LibreELEC connmand[960]: wlan0 {update} flags 4098 <DOWN>
Apr 13 12:02:00 LibreELEC connmand[960]: wlan0 {newlink} index 3 address 24:05:0F:6B:F2:EF mtu 1500
Apr 13 12:02:00 LibreELEC connmand[960]: wlan0 {newlink} index 3 operstate 2 <DOWN>
Apr 13 12:02:00 LibreELEC connmand[960]: Adding interface wlan0 [ wifi ]
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {RX} 19987 packets 24142891 bytes
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {TX} 10971 packets 1271357 bytes
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {update} flags 36867 <UP>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {newlink} index 2 address B8:27:EB:7F:2D:31 mtu 1500
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {newlink} index 2 operstate 2 <DOWN>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {RX} 19987 packets 24142891 bytes
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {TX} 10971 packets 1271357 bytes
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {newlink} index 2 address B8:27:EB:7F:2D:31 mtu 1500
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {newlink} index 2 operstate 6 <UP>
Apr 13 12:02:00 LibreELEC connmand[960]: ipconfig state 3 ipconfig method 1
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {add} address 192.168.0.22/24 label eth0 family 2
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {add} route 192.168.0.0 gw 0.0.0.0 scope 253 <LINK>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {add} route 192.168.0.5 gw 0.0.0.0 scope 253 <LINK>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {add} route 0.0.0.0 gw 192.168.0.5 scope 0 <UNIVERSE>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {add} route 0.0.0.0 gw 192.168.0.5 scope 0 <UNIVERSE>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {add} route 192.168.0.0 gw 0.0.0.0 scope 253 <LINK>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {add} route 192.168.0.5 gw 0.0.0.0 scope 253 <LINK>
Apr 13 12:02:00 LibreELEC connmand[960]: eth0 {add} route 82.165.8.211 gw 192.168.0.5 scope 0 <UNIVERSE>
Apr 13 12:02:00 LibreELEC connmand[960]: ntp: adjust (slew): -0.003366 sec
Apr 13 12:02:13 LibreELEC connmand[960]: wlan0 {update} flags 4099 <UP>
Apr 13 12:02:13 LibreELEC connmand[960]: wlan0 {newlink} index 3 address 24:05:0F:6B:F2:EF mtu 1500
Apr 13 12:02:13 LibreELEC connmand[960]: wlan0 {newlink} index 3 operstate 2 <DOWN>
Apr 13 12:02:16 LibreELEC connmand[960]: eth0 {del} route 82.165.8.211 gw 192.168.0.5 scope 0 <UNIVERSE>
Apr 13 12:02:22 LibreELEC connmand[960]: wlan0 {update} flags 4098 <DOWN>
Apr 13 12:02:22 LibreELEC connmand[960]: wlan0 {newlink} index 3 address 24:05:0F:6B:F2:EF mtu 1500
Apr 13 12:02:22 LibreELEC connmand[960]: wlan0 {newlink} index 3 operstate 2 <DOWN>
Apr 13 12:02:27 LibreELEC connmand[960]: wlan0 {update} flags 4099 <UP>
Apr 13 12:02:27 LibreELEC connmand[960]: wlan0 {newlink} index 3 address 24:05:0F:6B:F2:EF mtu 1500
Apr 13 12:02:27 LibreELEC connmand[960]: wlan0 {newlink} index 3 operstate 2 <DOWN>

Display More

As you can see I switched the device between up and down but the operstate stays at 2.

I just tested the dongle with my notebook (Linux Mint - Kernel 5.15) and can verify that it works there.

**chewitt** · April 13, 2023 at 2:58 PM

Can you rm -rf the connman service folder for the NIC under /storage/.cache/connman/<name of service> and reboot. Any change?

And/Or try to use connmanctl to create a connection:

connmanctl

agent on

scan wifi

services

connect <service>

lomion · April 13, 2023 at 4:03 PM

No change after removing all wifi service folders.

connmanctl fails at "scan wifi" since the technology does not exist:

Code

Error /net/connman/technology/wifi: Method "Scan" with signature "" on interface "net.connman.Technology" doesn't exist

Code

connmanctl> technologies 
/net/connman/technology/ethernet
  Name = Wired
  Type = ethernet
  Powered = True
  Connected = True
  Tethering = False
  TetheringFreq = 0

I also tried manually scan in iwd but there as well is no device or adapter listed.

**jernej** · April 13, 2023 at 4:55 PM

Quote from lomion

Error /net/connman/technology/wifi: Method "Scan" with signature "" on interface "net.connman.Technology" doesn't exist

I got same error when iwd refused to start due to some missing driver. Can you check iwd service status with systemctl?

lomion · April 13, 2023 at 5:05 PM

iwd is running and WIFI is working with the internal WIFI adapter.

**jernej** · April 13, 2023 at 5:47 PM Best Answer

Ok. Driver is in staging and it seems that it doesn't use much of linux wifi kernel side framework, on which iwd relies heavily. Sorry to say, but it seems that driver is not iwd compatible. TODO.txt in kernel says this:

Code

A replacement for this driver with MAC80211 support is available
at https://github.com/chunkeey/rtl8192su

So it may be possible that driver mentioned above is in fact iwd compatible, but as a team policy, we won't add any out of tree wifi driver.

Realtek 8192S not working since LE11

Similar Threads

No video on RPI4 using LE11 with Haier le55b1381

LibreElec Update not available

WiFi issues after replacing wifi card