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. What can I do so it just works on startup? Thanks! |
When you first plug the device in,confirm that the wireless network interface is present
Code:
/sbin/ifconfig Code:
nmcli g More questions may follow. |
Sorry, duplicate posted...<removed>
|
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 |
Quote:
Code:
sudo systemctl restart network Code:
dmesg --follow Code:
sudo journalctl -f |
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. |
Yes, post back with the kernel output occurring when device is first plugged in..
|
Got it again here
Code:
[ 77.589770] usb 2-1.3: new high-speed USB device number 6 using ehci-pci |
Nothing reported a little after that?
For example, I get Code:
[ 95.994222] usb 3-1: new high-speed USB device number 3 using xhci_hcd Code:
wlp0s20u1 Link encap:Ethernet HWaddr A0:F3:C1:22:27:E5 |
I tried it again and got this:
Code:
[ 136.697454] usb 2-1.3: new high-speed USB device number 5 using ehci-pci Code:
lo Link encap:Local Loopback |
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 |
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
|
Sorry about the slow reply - I thought my last post went up.
Here's the output of that: Code:
Jun 29 21:23:54 linux-rnpk systemd[1]: Starting Network Manager... |
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.
|
All times are GMT -5. The time now is 08:57 PM. |