On Fri, 12 Jul 2019 16:07:23 -0500 David Wright <deb...@lionunicorn.co.uk> wrote:
> On Fri 12 Jul 2019 at 12:36:33 (-0700), Patrick Bartek wrote: > > On Fri, 12 Jul 2019 06:22:16 -0000 (UTC) > > Bert Riding <rerid...@xmission.com> wrote: > > > > > Yes, I'm sorry I didn't mention that my device name was merely an > > > > Didn't have to. I understood. It's just wlan0 USED to be the default > > 1st wireless device, the last time I had to do this with another system > > about 15 years ago, and I used it as a first test to bring UP the > > device before reading the instructions. It failed, of course. Laziness. > > > > > example. I wonder if "ip link show" or "ls -l /sys/class/net" or the > > > obsolete "ifconfig a" give the same device name. Udevadm might > > > help, too. "udevadm info -e | grep .wl" for instance. The name you are > > > using is the name using the MAC address, which is the last match as udev > > > lists the names, and won't be used if udev finds another name first. See > > > https://major.io/2015/08/21/understanding-systemds-predictable-network-device-names/ > > > > > > > Here's what that all shows on my system (wireless parts only). > > Wireless USB dongle plugged in, but otherwise dormant. > > > > ip a > > > > 3: wlx00e04c2a23c4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state > > DOWN mode DEFAULT group default qlen 1000 link/ether 00:e0:4c:2a:23:c4 > > brd ff:ff:ff:ff:ff:ff > > > > ls -l /sys/class/net > > > > lrwxrwxrwx 1 root root 0 Jul 12 07:48 wlx00e04c2a23c4 > > -> > > ../../devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0/net/wlx00e04c2a23c4 > > > > /sbin/iw dev > > > > phy#0 > > Interface wlx00e04c2a23c4 > > ifindex 3 > > wdev 0x1 > > addr 00:e0:4c:2a:23:c4 > > type managed > > txpower 0.00 dBm > > > > udevadm info -e | grep .wl > > > > E: RFKILL_TYPE=wlan > > P: /devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0/net/wlx00e04c2a23c4 > > E: > > DEVPATH=/devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0/net/wlx00e04c2a23c4 > > E: DEVTYPE=wlan E: ID_NET_NAME=wlp0s18f2u3 > > E: ID_NET_NAME_MAC=wlx00e04c2a23c4 > > E: ID_NET_NAME_PATH=wlp0s18f2u3 > > E: INTERFACE=wlx00e04c2a23c4 > > E: > > SYSTEMD_ALIAS=/sys/subsystem/net/devices/wlx00e04c2a23c4 > > /sys/subsystem/net/devices/wlx00e04c2a23c4 > > > > As you can see, the wlx name is the only one that shows as far as I > > can find. ifconfig is not installed. > > Here's mine. As you can see, it lists the iwlwifi driver, > but I don't see anything for yours. > > E: DRIVER=iwlwifi > E: RFKILL_TYPE=wlan > P: /devices/pci0000:00/0000:00:1c.2/0000:02:00.0/net/wlp2s0 > E: DEVPATH=/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/net/wlp2s0 > E: DEVTYPE=wlan > E: ID_NET_DRIVER=iwlwifi > E: ID_NET_NAME=wlp2s0 > E: ID_NET_NAME_MAC=wlx0c8bfd0b67fb > E: ID_NET_NAME_PATH=wlp2s0 > E: INTERFACE=wlp2s0 > E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/wlp2s0 > /sys/subsystem/net/devices/wlp2s0 > E: RFKILL_NAME=ideapad_wlan > E: RFKILL_TYPE=wlan Thanks. Looks like your wifi is pci. Right? Mine's a USB and DOWN/inactive (I was on wired ethernet) when I did the udevadm. But the next time I bring it UP, I'll see what udevadm reports as the driver. Probably nl80211. Thanks, again, for the info. Every little bit helps to track down the problem. B