USB Wi-Fi Adapter Won't Activate on Plugin or Start
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
USB Wi-Fi Adapter Won't Activate on Plugin or Start
Hi all,
I'm on Tumbleweed, and for the last month or so my USB Belkin Realtek Wi-Fi adapter won't work on startup or plugin. Before in Tubmeweed, and in Leap and most other popular distros it'll instantly work on plugin or startup, but in this Tumbleweed install it doesn't.
To get it running I have to, after every startup, go into YaST and temporarily switch the Network Manager to wicked, then go back in and set it to NetworkManager.
When ran these, I didn't see "wlan1" listed, which is the one that the KDE Network Manager applet connects me to once I do my convoluted trick and then connect. Here's the output:
Code:
linux-rnpk:/home/jared # /sbin/ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:280 (280.0 b) TX bytes:280 (280.0 b)
p3p2 Link encap:Ethernet HWaddr D0:67:E5:1C:C6:AA
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)
wlan0 Link encap:Ethernet HWaddr 38:59:F9:C4:04:EC
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)
linux-rnpk:/home/jared # nmcli g
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
disconnected none enabled enabled enabled enabled
linux-rnpk:/home/jared # nmcli d
DEVICE TYPE STATE CONNECTION
wlan0 wifi disconnected --
p3p2 ethernet unavailable --
lo loopback unmanaged --
linux-rnpk:/home/jared #
When ran these, I didn't see "wlan1" listed, which is the one that the KDE Network Manager applet connects me to once I do my convoluted trick and then connect
That's what I was kind of hoping to see - I wanted a 'snapshot' of the situation when the device is first plugged in, before your switching to wikced and back. So, the wlano0 interface is not present (active) initially? BTW, I wonder if restarting network.service would do the same as your switching trick?
Code:
sudo systemctl restart network
Anyway, for more detail it might be useful to open a terminal and run
Code:
dmesg --follow
or
Code:
sudo journalctl -f
Plug the USB dongle in again, and observe/capture the kernel output resulting.
Interestingly, the systemctl restart of network services didn't work. I do have, however, the network log of when I first switch (using YaST) to wicked from Network Manager, then back to Network Manager when it starts working. Oddly it lights up after I switch it to wicked (207-209), but doesn't connect (can't ping router or Google) until I switch it back to Network Manager (265 and later).
Code:
[ 207.108905] No iBFT detected.
[ 207.822260] r8712u 2-1.3:1.0 wlan1: 1 RCR=0x153f00e
[ 207.823116] r8712u 2-1.3:1.0 wlan1: 2 RCR=0x553f00e
[ 209.130042] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 265.463473] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 265.480925] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 265.482383] IPv6: ADDRCONF(NETDEV_UP): p3p2: link is not ready
[ 265.588344] r8169 0000:03:00.0 p3p2: link down
[ 265.588399] IPv6: ADDRCONF(NETDEV_UP): p3p2: link is not ready
[ 265.589974] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 266.894600] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 266.958863] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 266.969484] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 266.976041] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 276.970446] r8712u 2-1.3:1.0 wlan1: r8712u: wpa_set_encryption: crypt.alg = WEP
[ 277.309420] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
I can post what it looks like when I initially plug it in, if it's still relevant after this. I rebooted and forgot to save it
[ 77.589770] usb 2-1.3: new high-speed USB device number 6 using ehci-pci
[ 77.684817] usb 2-1.3: New USB device found, idVendor=050d, idProduct=845a
[ 77.684824] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 77.684826] usb 2-1.3: Product: Belkin USB Wireless Adaptor
[ 77.684829] usb 2-1.3: Manufacturer: Manufacturer Realtek
[ 77.684831] usb 2-1.3: SerialNumber: 00e04c000001
[ 77.685504] r8712u: register rtl8712_netdev_ops to netdev_ops
[ 77.685510] usb 2-1.3: r8712u: USB_SPEED_HIGH with 4 endpoints
[ 77.686149] usb 2-1.3: r8712u: Boot from EFUSE: Autoload OK
[ 78.091129] usb 2-1.3: r8712u: CustomerID = 0x0000
[ 78.091136] usb 2-1.3: r8712u: MAC Address from efuse = 94:10:3e:b0:9c:dd
[ 78.091139] usb 2-1.3: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
[ 95.994222] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[ 96.160075] usb 3-1: New USB device found, idVendor=0bda, idProduct=8176
[ 96.160082] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 96.160086] usb 3-1: Product: 802.11n WLAN Adapter
[ 96.160089] usb 3-1: Manufacturer: Realtek
[ 96.160091] usb 3-1: SerialNumber: 00e04c000001
[ 97.338580] rtl8192cu: Chip version 0x10
[ 97.370081] rtl8192cu: MAC address: a0:f3:c1:22:27:e5
[ 97.370089] rtl8192cu: Board Type 0
[ 97.370157] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 97.370193] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[ 97.370391] usbcore: registered new interface driver rtl8192cu
[ 97.377929] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
[ 97.378562] rtlwifi: wireless switch is on
[ 97.399236] rtl8192cu: MAC auto ON okay!
[ 97.411602] rtl8192cu: Tx queue select: 0x05
[ 97.770357] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
and /sbin/ifconfig reports the new network device node
Code:
wlp0s20u1 Link encap:Ethernet HWaddr A0:F3:C1:22:27:E5
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)
[ 136.697454] usb 2-1.3: new high-speed USB device number 5 using ehci-pci
[ 136.792552] usb 2-1.3: New USB device found, idVendor=050d, idProduct=845a
[ 136.792558] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 136.792561] usb 2-1.3: Product: Belkin USB Wireless Adaptor
[ 136.792563] usb 2-1.3: Manufacturer: Manufacturer Realtek
[ 136.792565] usb 2-1.3: SerialNumber: 00e04c000001
[ 137.870392] r8712u: module is from the staging directory, the quality is unknown, you have been warned.
[ 137.871791] r8712u: register rtl8712_netdev_ops to netdev_ops
[ 137.871796] usb 2-1.3: r8712u: USB_SPEED_HIGH with 4 endpoints
[ 137.872315] usb 2-1.3: r8712u: Boot from EFUSE: Autoload OK
[ 138.261923] usb 2-1.3: r8712u: CustomerID = 0x0000
[ 138.261929] usb 2-1.3: r8712u: MAC Address from efuse = 94:10:3e:b0:9c:dd
[ 138.261932] usb 2-1.3: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
I then ran ifconfig and got
Code:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1140 errors:0 dropped:0 overruns:0 frame:0
TX packets:1140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:93032 (90.8 Kb) TX bytes:93032 (90.8 Kb)
p3p2 Link encap:Ethernet HWaddr D0:67:E5:1C:C6:AA
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)
wlan0 Link encap:Ethernet HWaddr 38:59:F9:C4:04:EC
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)
linux-rnpk:/home/jared #
Okay, so the wlan0 network interface is present as expected. So it should be possible to get NetworkManager to connect. The output from NM can be monitored using
Code:
sudo journalctl -fu NetworkManager
Then attempt to connect manually and observe the output. Ctrl+C to terminate Copy/paste the output here if there are any issues.
I should have specified that I have a non-functional (due to completely hardware related issues) Wi-Fi card that shows up as wlan0, and the USB dongle I want is wlan0. I'll still try that though and get back about it
Okay, from that I see the device is actually wlp0s29u1u3 (with wlan0 being your on-board device). It does connect, but it's not clear to me why NM doesn't handle it as soon as it becomes available. I'm wondering if perhaps you just need to recreate the NM connection and restrict it to the particular wireless device (wlp0s29u1u3) when configuring.
Perhaps it just needs more time to initialise when first plugged in? Or does it only become available after switching to wicked first? A bug report may be required if so.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.