Re: New network naming schema in systemd 197

I am on a new dell inspirion 15r. I managed to boot arch in uefi mode, all works well. The only problem is that the network interfaces have weird names, this does not prevent them to work, but it's sill annoying for me having to remember weird strings.This is the output I get from lspci|grep -i net:

Re: New network naming schema in systemd 197

Hmm... you shouldn't need a link to /dev/null although that does work. All you need to do is add the following to /etc/udev/rules.d/80-net-name-slot.rules

# This file masks persistent renaming rules for network devices. If you
# delete this file, /usr/lib/udev/rules.d/80-net-name-slot.rules may
# rename network devices according to ID_NET_NAME_{ONBOARD,SLOT,PATH}
# properties of your network devices, with priority in that order. See
# the output of 'udevadm test-builtin net_id /sys/class/net/$interface'
# for details on what that new name might be.
#
# http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames

Re: New network naming schema in systemd 197

Re: New network naming schema in systemd 197

I have just re-installed Arch on my ThinkPad e430. I've had no with networking before, everything has just worked out of the box. However, I'm having trouble with eth0 and wlan0 being started on boot. If I run "ifconfig" after startup, all that is shown is lo. Running "wifi-menu" brings up the message "No such interface: wlan0". Doing some googling, I've found running the command "ip link set wlp3s0 up" brings up my wifi-card, and I can proceed to get a connection using netcfg, etc. Why isn't it recognising this as just wlan0 on boot, and is there any downside (other that it being annoying) to this workaround? Below is the output of "lspci | grep -i net"

Re: New network naming schema in systemd 197

Note that the thread on the mailing list suggests that I can give it my own name:

2) provide your own udev rule that applies a NAME to the interface. As long as this rule is ordered lexically before 80-net-name-slot.rules, then the upstream rule will have no effect. For example, providing a file called 70-net-naming.rules will trump 80-net-name-slot.rules.

I put this in a rule called 20-network.rules in /etc/udev/rules.d, but the system complained that names of kernel devices cannot be changed, and the naming did not take effect.The rule I had was:

ATTR{idVendor}=="xxxx", ATTR{idProduct}=="xxxx", NAME:="wlan_my"

For the USB vendor/product of my USB wifi adapter.

Also, admin suggested that "most users will have read the mailing list..." -- that's probably not true :-) Most users use computers to get sh*t done, not to use it for its own sake. I use Arch because it is a rolling release distro that's not as annoying as Gentoo. I do not have time for a verbose mailing list in my life; I expect my computer to keep working!

Also, admin suggested that users would have read the output of the update, and taken action. Sometimes, when you update, there are more lines of text than there is scrollback buffer on the console, and even if there isn't, amid all the non-essential spam written from a monthly pacman -Syu, do you really think most users will find some particular line? I don't.

Re: New network naming schema in systemd 197

Sorry, this is a bit outside my knowledge of Linux. Looking through that, and other, pages on the Wiki, I seem to have all the network tools I need installed.Booting from the Arch 2012.12.01 ISO, everything works out-of-the-box. Is there a command I could run to see which drivers have been loaded to compare to my install?

Re: New network naming schema in systemd 197

jwatte wrote:

Also, admin suggested that users would have read the output of the update, and taken action. Sometimes, when you update, there are more lines of text than there is scrollback buffer on the console, and even if there isn't, amid all the non-essential spam written from a monthly pacman -Syu, do you really think most users will find some particular line? I don't.

Then you could just open /var/log/pacman.log with your favourite text editor

Re: New network naming schema in systemd 197

Re: New network naming schema in systemd 197

Hi,

I did a fresh install of 2013 Arch install via USB on my acer aspire one, I setup wifi with no issue using wifi-menu without the need to install any firmware and then choosing my accesspoint etc, completed the rest of the install and rebooted.

Once the system came back up I logged in as root tried to ping google and get unknown host,

lspci | grep net - reveals the network adapter

iwconfig - lists no wireless extensions

I am slightly confused at this stage as to why wireless is working during the install but not upon reboot, I have also rebooted into the install media again and wifi is working with no issues.