I meant that I don't use NetworkManager or systemd, so it would be blind-leading-blind in terms of specific software or gui help. Comparing the output of lspci (no wireless devices) and lsusb (sees the ralink device) seems rather confusing, but I guess it signifies that s/he has removed the intel card already? Also, the network card is on the list in the WiFi/rt73 page, verbatim from the lsusb output, so that's a good sign.Thorny wrote:n_hologram I don't think it is, trust your tests.n_hologram wrote:... This is probably outside my expertise,
I'm an old guy and I won't be here much longer, it is to everyone's benefit that you become adept because you put in the effort to help.
Based on my own (quick) readings of predictable network interfaces, it seems like a clue could be embedded in the interface name (wlx000ee8d4194e): that is, if I'm reading this correctly, the MAC address might be 00:03:e8:d4:19:4e. If that's the case, and you can find the mac of the Ralink dongle (they're sometimes written on the physical device itself), you can at least determine if the card is the one that's showing up.
know that some network managers (like wicd) require you to specify your network device in their settings; my guess is that you want to make sure
wlx000ee8d4194e is configured properly in NetworkManager, because you switched from an intel wireless card, which would have had a different "predictable network interface" name -- in other words, NM might still be trying to look for wlxi[intel mac address], and if my prediction earlier based on the lspci output (that you removed the intel card) is correct, then NM is looking for a nonexistent device.
However, if you've done all that and NM doens't work out, I would also advise following Bulkley's suggestion to try another network manager, whether it be wicd, wpa_supplicant, or network/interfaces. (You're welcome to try out my awful networking script, too!)
Also, Thorny: stick around as long as you can