View previous topic :: View next topic |
Author |
Message |
srd n00b
Joined: 13 Apr 2010 Posts: 38
|
Posted: Wed Mar 04, 2015 9:00 pm Post subject: ERROR: interface eno1 does not exist |
|
|
When trying to start my networking, I'm getting ...
Code: |
* Bringing up interface eno1
* ERROR: interface eno1 does not exist
* Ensure that you have loaded the correct kernel module for your hardware
* ERROR: net.eth0 failed to start
|
This was working until my latest "-uDN world". My kernel config is correct, NIC drivers built as modules for a Broadcom network card, so I know these are correct as they have been working.
I have a feeling it's something to do with eudev, or possibly some changes I made to keep systemd off. I added -systemd to the USE flags and "sys-apps/systemd" and "sys-fs/udev" to package.mask.
One thing I've noticed is that /etc/udev/rules.d is empty and I'm not sure why, but appears to have happened after the update. Anyone know how to repopulate /etc/udev/rules.d? Or what to try next? |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21489
|
Posted: Thu Mar 05, 2015 3:03 am Post subject: |
|
|
What is the current name of your Ethernet interface? |
|
Back to top |
|
|
n3bul4 Apprentice
Joined: 04 Nov 2003 Posts: 187
|
Posted: Thu Mar 05, 2015 6:58 am Post subject: |
|
|
If you know the module name, have you tried loading the module manually by modprobe?
Maybe the device appears after doing so... |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3103
|
Posted: Thu Mar 05, 2015 7:12 pm Post subject: |
|
|
Or maybe it's called differently now. Ask your kernel:
ls -l /sys/class/net/ |
|
Back to top |
|
|
srd n00b
Joined: 13 Apr 2010 Posts: 38
|
Posted: Thu Mar 05, 2015 7:27 pm Post subject: |
|
|
That's what the problem was. The interface name changed from eno1 to eth0.
Thanks, |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21489
|
Posted: Thu Mar 05, 2015 10:55 pm Post subject: |
|
|
The interface starts as eth0. If it is still eth0, then udev did not mangle your interface name. |
|
Back to top |
|
|
srd n00b
Joined: 13 Apr 2010 Posts: 38
|
Posted: Fri Mar 06, 2015 4:51 am Post subject: |
|
|
When I set this node up from a clean install, it started out as eno1. Then the updates changed it to eth0. Beyond that, I can't say what really happened. I'm quite confused when I see systemd-udev, eudev, udev, etc... but best I can tell, these udevs are changing my names (I guess pending which one is used). It happens on most all my systems as I keep them in close sync, and its been happening as of the last few months. Also noticed some messages while booting that says eth0, eth1, etc... are being changed to eno0, eno1, etc... in the boot output. So, yeah, I'm thoroughly confused as these names keep going back and forth on me. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21489
|
Posted: Sat Mar 07, 2015 1:55 am Post subject: |
|
|
The kernel assigns names from the eth* family (among others). As part of the "predictable network interface names" feature, systemd-udevd renames your interface from the kernel assigned name to en* (among others). You can, and usually should, disable this renaming. I suspect that eudev has disabled this naming automatically. |
|
Back to top |
|
|
srd n00b
Joined: 13 Apr 2010 Posts: 38
|
Posted: Mon Mar 09, 2015 12:44 am Post subject: |
|
|
Ok, this makes sense to me now. I take it, /etc/udev/rules.d/80-net-name-slot.rules is what does the renaming and via this is how its turned off? |
|
Back to top |
|
|
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Mon Mar 09, 2015 12:51 am Post subject: |
|
|
Quote: | /etc/udev/rules.d/80-net-name-slot.rules is what does the renaming and via this is how its turned off? |
Just create a blank file. Apparently this overwrites the default rules with blank rules. |
|
Back to top |
|
|
|