Not sure if this is network or hardware, but I’ll start here.
Had a USB dongle, and due to an accident, it broke (physically). No big deal, they’re cheap so I bought a new one, same brand/model but slightly newer version. Realtek chipset, using the rtl88x2bu module. No problems, good speed, BUT:
The wlp42s0f3u4 device is the one that works and is in the system, that’s the correct MAC address. The other is the one that WAS there, but now isn’t. But when the system boots, it’ll sit there and bang on the wlp3s0f0u6 device until it gives up, and I can then manually select the 4 device, which connects almost instantly.
I’ve tried going into network manager and deleting that device, which doesn’t work (won’t let me), and can’t find where on earth this is coming from. Using the latest, up-to-date Tumbleweed, KDE desktop.
Any ideas? This isn’t a huge deal, but it’s irritating.
NAME UUID TYPE DEVICE
WIFINAME 29236af8-d68a-4534-9422-26993bb67497 wifi wlp42s0f3u4
lo 3c0eb1ec-4d1a-44bf-8613-665e29ef0e24 loopback lo
VPN1 d02282e0-d350-41a0-9745-9c7081c8bd90 vpn --
VPN2 f7e91fc7-2c81-4d45-b279-d4e9e5cef974 vpn --
PhoneHotspot 332207fc-d645-4d20-9e7b-9ed01c06dd89 wifi --
PhoneBluetooth e40c5d4b-c73d-4936-bc17-ab21ed8e318f bluetooth --
VPN3 669f33f2-0506-4e48-9263-65b8346eff37 vpn --
VPN4 b01e32a1-a8d3-4c35-8637-441cfe5dea26 vpn --
Wired 05525c44-ab6c-3e60-9f19-978431709d85 ethernet --
Sanitized, obviously. But I see one wifi connection, which is correct, and this is going to the correct device (wlp42s0f3u4). The VPN connections are correct, as are the phone and wired. All working.
nmcli device show wlp3s0f0u6
GENERAL.DEVICE: wlp3s0f0u6
GENERAL.TYPE: wifi
GENERAL.HWADDR: 92:75:05:DF:D5:56
GENERAL.MTU: 1500
GENERAL.STATE: 30 (disconnected)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.GATEWAY: --
IP6.GATEWAY: --
# nmcli device delete wlp3s0f0u6
Error: Device 'wlp3s0f0u6' (/org/freedesktop/NetworkManager/Devices/3) deletion failed: This device is not a software device or is not realized
Error: not all devices deleted.
“Finally”? Is there a reason to sound snotty about this? It’s been a couple of days, and there isn’t a lot.
Exactly what do you expect to find from the ip link command? As stated earlier, two are there, one is up, the other isn’t (and won’t activate). Not going to bother posting the loopback device or the wired interface, since it’s not plugged in. Hope that’s ok with you.
2: wlp42s0f3u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 60:83:e7:3b:9b:d1 brd ff:ff:ff:ff:ff:ff
3: wlp3s0f0u6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether 1a:a1:4d:b3:fb:27 brd ff:ff:ff:ff:ff:ff permaddr 98:48:27:ce:96:d4
And not sure what’s to be gained by the lspci command, since it is, again, a USB device that’s having the issue. Posting the relevant part of the lspci.
03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller [1022:43b9] (rev 02)
21:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller [1b21:1343]
2a:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller [1022:145c]
The actual lsusb, with the only device for wifi: Bus 002 Device 002: ID 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]
Congratulations; you saw exactly what I describe. One working device and one that’s not, because it’s not even present.
Why bother showing all the USB devices for whatever else is plugged in? You need to see my keyboard mouse to determine something about a network dongle? Because (aside from the Linux Foundation 3.0 root hub), that’s all that’s there. And an entire dmesg output for what reason? Again, the device IS NOT PLUGGED IN OR EVEN PRESENT. What errors are going to be there for a device that’s not present?
I’ve looked in dmesg, and see ZERO to do with any network devices or kernel modules that are relevant.
Again, congratulations. You have determined that my USB device is, indeed, plugged in to one of my USB ports.
Flagging this as solved, and I will find a solution on my own.