[systemd-devel] udev too late renaming network interfaces

[Tom Gundersen]

On Tue, May 13, 2014 at 3:43 PM, Grant <emailgrant at gmail.com> wrote:
>>> I'm on Gentoo and when the system tries to start my network interfaces
>>> at boot, I get:
>>>
>>> Cannot find device "enp0s20u2u1"
>>>  *   ERROR: interface enp0s20u2u1 does not exist
>>>  *   Ensure that you have loaded the correct kernel module for your hardware
>>>  * ERROR: net.enp0s20u2u1 failed to start
>>>  * Bringing up interface enp0s20u2u2
>>> Cannot find device "enp0s20u2u2"
>>>  *   ERROR: interface enp0s20u2u2 does not exist
>>>  *   Ensure that you have loaded the correct kernel module for your hardware
>>>  * ERROR: net.enp0s20u2u2 failed to start
>>>
>>> It seems udev is taking too long to rename my USB ethernet interfaces
>>> from eth0 and eth1 to the above names.  Once the system is booted, I
>>> can start the interfaces just fine.  I do like the renaming
>>> functionality so I can plug any USB ethernet adapter into a particular
>>> USB port and it will work without changes so I'd rather not disable
>>> that.  Everything is built into the kernel, I'm not loading any
>>> modules.  I have 5 Dell XPS 13 systems and only one is exhibiting this
>>> problem.
>>
>> Is your network configuration system waiting at all for network devices
>> to show up? If not, it's not really compatible who modern network
>> devices work, in particularly USB devices.
>>
>> It needs to wait with libudev until the network devices it is interested
>> in have been reported initialized by udev.
>
>
> Thank you Tom and Lennart.  I'm not sure what to call my network
> configuration system.  It's default Gentoo stuff, just initscrips in
> runlevels.  To confirm, I should file a Gentoo bug?


Sounds like it. If nothing else, they should at least be able to tell
you where to go next.

Cheers,

Tom