You are not logged in.
I am wondering what scheme the Arch Linux live environment is using to name network interface names.
When I boot into the live environment and run
ip -br link
I see
lo UNKNOWN 00:00:00:00:00:00 <LOOPBACK,UP,LOWER_UP>
eno1 DOWN 1c:69:7a:06:ff:85 <BROADCAST,MULTICAST>
wlan0 DOWN 04:ea:56:82:55:b9 <BROADCAST,MULTICAST>
However, after installing Arch Linux and booting into the new system, running
ip -br link
produces
lo UNKNOWN 00:00:00:00:00:00 <LOOPBACK,UP,LOWER_UP>
eno1 DOWN 1c:69:7a:06:ff:85 <BROADCAST,MULTICAST>
wlp0s20f3 DOWN 04:ea:56:82:55:b9 <BROADCAST,MULTICAST>
I am guessing that both the live environment and the installed are using the predictable network interface naming, but if this was the case then I would expect both systems to name the wireless interface the same way. So, what is causing the difference?
Last edited by Bidski (2020-01-14 21:37:07)
Offline
It seems udev decides to make it difficult. This bugged me too and caused issues, but you can easily revert it to wlan0. Check the wiki. I went for the kernel parameters option.
Offline
It seems udev decides to make it difficult. This bugged me too and caused issues, but you can easily revert it to wlan0. Check the wiki. I went for the kernel parameters option.
Reverting wlp0s20f3 to wlan0 is not what I desire. I would desire to have the live environment bring up wlp0s20f3 which is what I think it should be doing.
Ultimately, what I desire is to have the freshly installed environment match the environment seen in the live environment so that I can reliably set up network interfaces during installation so that the system is fully operational from the first boot.
Offline
@Bidski in the live environment does the journal contain any entries indicating the interface is renamed?
Offline
@Bidski in the live environment does the journal contain any entries indicating the interface is renamed?
Not sure what other commands to run or what to look for? Does this answer your question?
$ journalctl -xb | grep wl
Dec 10 01:48:22 archiso kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
Dec 10 01:48:22 archiso kernel: iwlwifi 0000:00:14.3: Found debug destination: EXTERNAL_DRAM
Dec 10 01:48:22 archiso kernel: iwlwifi 0000:00:14.3: Found debug configuration: 0
Dec 10 01:48:22 archiso kernel: iwlwifi 0000:00:14.3: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm
Dec 10 01:48:22 archiso kernel: wl: loading out-of-tree module taints kernel.
Dec 10 01:48:22 archiso kernel: wl: module license 'MIXED/Proprietary' taints kernel.
Dec 10 01:48:22 archiso kernel: wl: module verification failed: signature and/or required key missing - tainting kernel
Dec 10 01:48:22 archiso kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, REV=0x318
Dec 10 01:48:22 archiso kernel: iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
Dec 10 01:48:22 archiso kernel: iwlwifi 0000:00:14.3: Allocated 0x00400000 bytes for firmware monitor.
Dec 10 01:48:22 archiso kernel: iwlwifi 0000:00:14.3: base HW address: 04:ea:56:82:55:b9
Dec 10 01:48:23 archiso kernel: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
$ journalctl -xb | grep udevd
Dec 10 01:48:21 archiso systemd-udevd[382]: /usr/lib/udev/rules.d/11-dm-lvm.rules:40 Invalid value for OPTIONS key, ignoring: 'event_timeout=180'
Dec 10 01:48:21 archiso systemd-udevd[382]: /usr/lib/udev/rules.d/11-dm-lvm.rules:40 The line takes no effect, ignoring.
-- Subject: A start job for unit systemd-udevd.service has finished successfully
-- A start job for unit systemd-udevd.service has finished successfully.
Dec 10 01:48:21 archiso audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 10 01:48:21 archiso kernel: audit: type=1130 audit(1575942501.785:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 10 01:48:22 archiso systemd-udevd[393]: Using default interface naming scheme 'v243'.
Dec 10 01:48:22 archiso systemd-udevd[393]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 10 01:48:22 archiso systemd-udevd[396]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 10 01:48:22 archiso systemd-udevd[394]: Using default interface naming scheme 'v243'.
Dec 10 01:48:22 archiso systemd-udevd[397]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
Dec 10 01:48:23 archiso systemd-udevd[389]: Using default interface naming scheme 'v243'.
Dec 10 01:48:23 archiso systemd-udevd[389]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Offline
I was looking for a message containing:
wlp0s20f3: renamed from wlan0
Offline
I was looking for a message containing:
wlp0s20f3: renamed from wlan0
The only line containing the word "renamed" is
Dec 10 21:31:35 archiso kernel: e1000e 0000:00:1f.6 eno1: renamed from eth0
The installed system has a line for both the wired and the wireless interfaces being renamed.
Offline
Does anyone have any idea as to why the interfaces are not being named correctly in the live environment?
Offline
Offline
The solution in this post solves my issues.
Offline