New network naming schema in systemd 197

jasonwryan · 2013-01-28 17:05:14

Merging with the stickied thread...

z_Zelman · 2013-01-30 22:34:04

Hello, I am new to Arch. I think I have everything installed correctly but when I reboot out of the live CD and onto the hard drive I have no internet with either WiFi or Ethernet.

I have a Acer Aspire TimelineX 4830TG-6808 laptop and here is what I did when I installed Arch:

cfdisk /dev/sda
(first partition is 10GB root, and the second is the rest of the hard drive. I don't need a swap because I have 16GB of ram)
mkfs.ext4 /dev/sda1
mkfs.ext4 /dev/sda2
mount /dev/sda1 /mnt
mkdir /mnt/home
mount /dev/sda2 /mnt/home
pacstrap -i /mnt base base-devel
genfstab -U -p /mnt | sed 's/rw,relatime,data=ordered/defaults,relatime/' >> /mnt/etc/fstab
arch-chroot /mnt
ln -s /usr/share/zoneinfo/America/Denver /etc/localtime
hwclock --systohc --utc
echo myhostname > /etc/hostname
systemctl enable dhcpcd@eth0.service
pacman -S wireless_tools wpa_supplicant wpa_actiond dialog
passwd
pacman -S grub-bios
grub-install /dev/sda
cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
grub-mkconfig -o /boot/grub/grub.cfg
exit
reboot
(and then log in as root)
pacman -S xorg-server xorg-xinit xorg-server-utils
pacman -S mesa
pacman -S sudo
nano /etc/sudoers

My problem is when I am in chroot in the live CD, I have internet access over Ethernet, but when I am on my hard drive I don't have internet access.

Please tell me what I did wrong on my install because I cant find it :-(

jasonwryan · 2013-01-30 23:02:18

Read the stickied thread I am merging this into...

-Syu · 2013-01-31 20:39:36

Try a Google search for that. It's not like I can't get my network adapters up, they're just gone. It's also no hardware problem, as other operating systems do detect the NIC's.

Unfortunately, I don't have a clue of what went wrong. I've been editing a lot of the system config files, then the network cards went undetected, then I tried to work my way back... I really don't know what I did to get here.

So, I'm guessing I can solve this one as soon as I find out how exactly to troubleshoot missing devices. Anyone?

karol · 2013-01-31 21:41:47

Is it https://bbs.archlinux.org/viewtopic.php … 3#p1218383 ?

jasonwryan · 2013-01-31 21:42:53

Merging with the stickied thread...

z_Zelman · 2013-02-01 05:41:51

Yep, it was because of the new systemd 197 that was my problem. Thanks for the help.

nadman10 · 2013-02-01 08:44:01

Pardon and speeling or grammar error. I'm writing this from my phone. After upgrading and configuring systemd, I no longer have any network functionality. Running " systemctl status network" returns an error saying that it didn't load and th reason being "no such file or directory". Under that it claims that there is a legacy rc script being used and I should remove it from my DAEMONS array and enable it natively through systemd. I don,t know what that means, especially because I don't have an rc.conf file anymore. Any help would be appreciated.

Scimmia · 2013-02-01 08:52:23

Did you read the systemd wiki page? It's all covered there.

jasonwryan · 2013-02-01 09:02:33

Merging with the stickied thread...

nadman10 · 2013-02-01 09:41:32

Scimmia: I did. It was a misspelled file name.I'm up and running now.

Everyone in this post seems to have the name of the network interface changing as the root of their issue. Mine is still eth0 for some reason. I guess I don't really understand why I had to manually create the /etc/conf.d/network and /etc/systemd/system/network.service files since I use a static IP. It seems to me that these files should have been automatically created during the upgrade process. I'm sure there is a valid reason, I'm just curious as to why it is. I'm sure I can't be the only one that came across this problem(although a lack of Google results suggests I might).

Scimmia · 2013-02-01 09:44:30

nadman10 wrote:

It seems to me that these files should have been automatically created during the upgrade process. I'm sure there is a valid reason, I'm just curious as to why it is. I'm sure I can't be the only one that came across this problem(although a lack of Google results suggests I might).

This is Arch, things don't happen automatically like that. You have complete control and complete responsibility for your own system.

cirbafe · 2013-02-03 06:15:06

I just installed Arch Linux on my notebook using cable internet, free wireless throughout the OS installation it worked fine, but when I reboot and removed the boot usb internet stopped working, when I type "ip link set etho0 up" I get the message "Can not find device etho0" that same message also appears when I'm using arch boot, but the internet works

jasonwryan · 2013-02-03 06:25:25

Merging with the stickied thread...

nomorewindows · 2013-02-06 20:46:28

cirbafe wrote:

I just installed Arch Linux on my notebook using cable internet, free wireless throughout the OS installation it worked fine, but when I reboot and removed the boot usb internet stopped working, when I type "ip link set etho0 up" I get the message "Can not find device etho0" that same message also appears when I'm using arch boot, but the internet works

Etho0? It supposed to be eth0.

I haven't noticed anything different with my update to systemd 197, it's still the same ethX and wlanX it has been.

Anywho, all the *BSDs call the interfaces based on the name of the driver, so if you have two different vendors in the box, homework done! But if you have the same adapters, then you have driverX. *BSDs are sensible in some areas, but the overall feel is still antiquated.

jasonwryan · 2013-02-06 21:10:20

nomorewindows wrote:

I haven't noticed anything different with my update to systemd 197, it's still the same ethX and wlanX it has been.

Go back and read pacman's log for that update; you will see why...

nbob · 2013-02-07 00:47:00

During a fresh install of Arch. I successfully pinged google.com at the outset but when I got to the part where I install alsa-mixer (right after my base install and first reboot) I got a ton of errors. These errors are essentially ""failed retrieving file " +"could not resolve host" errors. (Apparently Arch is going down the list of mirrors one by one and failing on every one of them) Now, I can't seem to ping anything. When I try to ping google, I get a "ping: unkown host www.google.com" error.

I tried adding a DNS server to /etc/resolv.conf (8.8.8.8) to no avail.

Any help would be appreciated.

Last edited by nbob (2013-02-07 01:40:09)

nomorewindows · 2013-02-07 00:50:28

jasonwryan wrote:

nomorewindows wrote:
I haven't noticed anything different with my update to systemd 197, it's still the same ethX and wlanX it has been.
Go back and read pacman's log for that update; you will see why...

==>Persistent net naming rules have been shipped as disabled.

That's been about a month ago, and I think I remember seeing it, not sure what the implication was.
I haven't had to fuss with udev rules all that much, but I have I think modified them one time for a net device switcheroo on booting.
I guess I delete /etc/udev/rules.d/80-net-name-slot.rules and it does its' thing.
Running udevadm test-builtin net_id /sys/class/net/$interface:
eth0 gave a response for ID_NET_NAME_PATH as to what it would look like, but not on my wlan0.
I don't think I'm too worried about switcheroo on this one, so I'll just leave it, but the other machine wants to switcheroo (sometimes). All I'll have to do with that one is change my netcfg@ scripts to match the systemd naming scheme and I'm off to the races.

--I just remembered--
I'll have to update my iptables rules also.

Last edited by nomorewindows (2013-02-08 13:49:40)

cfr · 2013-02-07 00:54:10

Welcome to Arch!

You have not provided nearly enough information to allow people to help you. Please see the links in my signature for help in asking effective questions.

For example, what errors?

I don't really understand what you have done, either. Why are you installing alsa-mixer during the initial install? Which "part" are you referring to?

Trilby · 2013-02-07 02:26:07

Did you put the network up before trying to ping/download? Did you run dhcpcd?

headkase · 2013-02-07 02:28:49

sudo systemctl enable dhcpcd.service

Then reboot.

nbob · 2013-02-07 02:47:59

I had previously run the following command:

systemctl enable dhcpd@etho0.service

and all was well until I rebooted and then I lost the connection.

When I try to run that command at this point, I get an error that there is no such file.

Last edited by nbob (2013-02-07 02:51:44)

headkase · 2013-02-07 02:51:09

And enable dhcpcd@eth0 is broken. Systemd will rename your network adapter on boot to something other than eth0, and it will never be named eth0. Enabling dhcpcd@eth0 is also hardwired to be eth0 no matter what you put after the @. You can see the brokenness there. So, just enable dhcpcd.service will bind the dhcp client to all available interfaces. There are cleaner solutions but the given command should just work and you don't need to care about the wart.

Edit: if you have to do

sudo systemctl disable dhcpcd@eth0.service

before enabling again without the @ interface.

Last edited by headkase (2013-02-07 02:55:31)

jasonwryan · 2013-02-07 03:07:32

nbob wrote:

and all was well until I rebooted and then I lost the connection.

Merging with the stickied thread...

imbob · 2013-02-08 07:35:21

Hello, I've just installed arch and I was able to connect to the internet automatically via the boot disk, however after running the following commands on my newly built system (after reboot):

systemctl  enable dhcpcd@eth0.service

systemctl start dhcpcd@eth0.service

I got the following errors in journal

 
Timeout waiting for device sys-subsystem-net-devices-eth0.device.
Subject: Unit sys-subsystem-net-devices has failed.
Defined-By: systemd


The result is timeout.
Dependency failed for dhcpcd on eth0.
Subject: Unit dhcpcd@eth0.service has failed
Defined-By: systemd

Any ideas on what the dependency is and what I can do to solve it? Like I said, I was able to ping google from the bootdisk...

Last edited by imbob (2013-02-08 07:39:31)

Arch Linux

#76 2013-01-28 17:05:14

Re: New network naming schema in systemd 197

#77 2013-01-30 22:34:04

Re: New network naming schema in systemd 197

#78 2013-01-30 23:02:18

Re: New network naming schema in systemd 197

#79 2013-01-31 20:39:36

Re: New network naming schema in systemd 197

#80 2013-01-31 21:41:47

Re: New network naming schema in systemd 197

#81 2013-01-31 21:42:53

Re: New network naming schema in systemd 197

#82 2013-02-01 05:41:51

Re: New network naming schema in systemd 197

#83 2013-02-01 08:44:01

Re: New network naming schema in systemd 197

#84 2013-02-01 08:52:23

Re: New network naming schema in systemd 197

#85 2013-02-01 09:02:33

Re: New network naming schema in systemd 197

#86 2013-02-01 09:41:32

Re: New network naming schema in systemd 197

#87 2013-02-01 09:44:30

Re: New network naming schema in systemd 197

#88 2013-02-03 06:15:06

Re: New network naming schema in systemd 197

#89 2013-02-03 06:25:25

Re: New network naming schema in systemd 197

#90 2013-02-06 20:46:28

Re: New network naming schema in systemd 197

#91 2013-02-06 21:10:20

Re: New network naming schema in systemd 197

#92 2013-02-07 00:47:00

Re: New network naming schema in systemd 197

#93 2013-02-07 00:50:28

Re: New network naming schema in systemd 197

#94 2013-02-07 00:54:10

Re: New network naming schema in systemd 197

#95 2013-02-07 02:26:07

Re: New network naming schema in systemd 197

#96 2013-02-07 02:28:49

Re: New network naming schema in systemd 197

#97 2013-02-07 02:47:59

Re: New network naming schema in systemd 197

#98 2013-02-07 02:51:09

Re: New network naming schema in systemd 197

#99 2013-02-07 03:07:32

Re: New network naming schema in systemd 197

#100 2013-02-08 07:35:21

Re: New network naming schema in systemd 197

Board footer