[arch-general] Device "eth0" does not exist - how to bring up?
All, After update that installed systemd, chrooting the system successfully starts the network and eth0 is present. However, when booting natively to the system no eth0 is present. Attempting /etc/rc.d/network restart results in "Device eth0 does not exist." According to https://wiki.archlinux.org/index.php/Systemd, until I append init=/usr/lib/systemd/systemd to the kernel line and reboot, the system should still process the initscripts normally. However this does not occur. 'cat /proc/1/comm' still shows 'init' so I cannot figure out why I do not have an eth0. Appending init=/usr/lib/systemd/systemd does bring up systemd and the system boots until X starts and the system hangs. It still responds to ctrl+alt+del, but will not switch to the graphical interface. It is just stuck. Is there a way to bring eth0 up under the old initscripts until I get the X hang sorted out? -- David C. Rankin, J.D.,P.E.
On 15.03.2013 18:24, David C. Rankin wrote:
All,
After update that installed systemd, chrooting the system successfully starts the network and eth0 is present. However, when booting natively to the system no eth0 is present. Attempting /etc/rc.d/network restart results in "Device eth0 does not exist." According to https://wiki.archlinux.org/index.php/Systemd, until I append init=/usr/lib/systemd/systemd to the kernel line and reboot, the system should still process the initscripts normally. However this does not occur. 'cat /proc/1/comm' still shows 'init' so I cannot figure out why I do not have an eth0.
With the installed systemd you should also have gotten a new udev version which might or might not give unique names to your network interfaces. Please check the output of ip link show to make sure there is eth0 and not enp0s3 or something like that. Greetings, Christoph
Is there a way to bring eth0 up under the old initscripts until I get the X hang sorted out?
As a side note this article explains why and how things changed, and some ways to go back (somewhat) to the old behavior: http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... -Martin
On 03/15/2013 03:00 PM, Martin Gignac wrote:
Is there a way to bring eth0 up under the old initscripts until I get the X hang sorted out?
As a side note this article explains why and how things changed, and some ways to go back (somewhat) to the old behavior:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface...
-Martin
Thanks Martin, that solved it. The solution was the 1st of the 3 mentioned: ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules I also read that in the wiki, but did not understand it was what was controlling the rename from 'eth0' to 'enp2s0'. -- David C. Rankin, J.D.,P.E.
2013/3/15 David C. Rankin <drankinatty@suddenlinkmail.com>:
the network and eth0 is present. However, when booting natively to the system no eth0 is present. Attempting /etc/rc.d/network restart results in "Device eth0
As Christoph suggests, try 'ip link', it will show you all devices.
Appending init=/usr/lib/systemd/systemd does bring up systemd and the system boots until X starts and the system hangs. It still responds to ctrl+alt+del,
To not start X with systemd try "systemd.unit=multi-user.target" or "systemd.unit=rescue.target" as kernel parameters. -- Krzysztof Warzecha
participants (4)
-
Christoph Vigano
-
David C. Rankin
-
Krzysztof Warzecha
-
Martin Gignac