1 |
>>>>>> I'm having a problem starting the USB network interfaces properly on |
2 |
>>>>>> one of my systems. I brought the problem to the udev list and they're |
3 |
>>>>>> indicating that it's a Gentoo problem: |
4 |
>>>>>> |
5 |
>>>>>> https://www.mail-archive.com/systemd-devel@×××××××××××××××××.org/msg18840.html |
6 |
>>>>>> |
7 |
>>>>>> Should I file a bug? |
8 |
>>>>>> |
9 |
>>>>>> - Grant |
10 |
>>>>>> |
11 |
>>>>> Like pointed out in the upstream thread, it's either wrongly built |
12 |
>>>>> net-misc/dhcpcd (should be with USE="udev") |
13 |
>>>>> and if not using dhcpcd, it might be a bug in net-misc/netifrc's |
14 |
>>>>> /etc/init.d/net.lo depend() { } section -- |
15 |
>>>>> it's possible it's missing dependency that forces /etc/init.d/udev start |
16 |
>>>>> first, specially if OpenRC is using parallel |
17 |
>>>>> startup |
18 |
>>>>> |
19 |
>>>>> So not really a udev bug, rather a misconfiguration in dhcpcd USE flags |
20 |
>>>>> OR bug in dependencies of netifrc's net.lo script |
21 |
>>>> I'm starting two interfaces, one that uses dhcpcd and one that does |
22 |
>>>> not. Both fail to start in the default runlevel until they are |
23 |
>>>> hotplugged later. I do have dhcpcd built with USE=udev. The string |
24 |
>>>> "udev" does not occur in /etc/init.d/net.lo so maybe that's the |
25 |
>>>> problem? Please confirm that I should file a Gentoo bug for this. |
26 |
>>>> |
27 |
>>>> - Grant |
28 |
>>>> |
29 |
>>> Try adding 'after udev' to net.lo's depend() { } section and see if that |
30 |
>>> helps, if it does, file a bug |
31 |
>>> saying so. |
32 |
>> |
33 |
>> I added it like this and rebooted: |
34 |
>> |
35 |
>> depend() |
36 |
>> { |
37 |
>> after udev |
38 |
>> |
39 |
>> but the result was the same. I also have udev and udev-mount in the |
40 |
>> sysinit runlevel. |
41 |
>> |
42 |
>> |
43 |
>>> It was more of an educated guess than 100% accurate knowledge. I can't |
44 |
>>> think of an another |
45 |
>>> way to force netifrc to behave, since it's not coded in C, and it can't |
46 |
>>> link to libudev, so... |
47 |
>>> |
48 |
>>> However since you say *both*, even the one with dhcpcd fail to start, |
49 |
>>> before filing that bug, |
50 |
>>> see if disabling netifrc hotplugging works: |
51 |
>>> |
52 |
>>> # ln -s /dev/null /etc/udev/rules.d/90-network.rules |
53 |
>> |
54 |
>> Will that disable interface renaming or hotplugging? The system with |
55 |
>> the issue is remote and if the interfaces aren't renamed or if |
56 |
>> hotplugging doesn't happen then I won't be able to access the system |
57 |
>> for up to 24 hours. That's fine and I'm happy to test stuff like this |
58 |
>> anyway but I don't think this particular test will be informative |
59 |
>> because: |
60 |
> |
61 |
> It will disable the hotplugging, it means you *must* have the net.* |
62 |
> stuff added |
63 |
> to the default to runlevel yourself, like eg. |
64 |
> |
65 |
> # rc-update add net.foooooobar default |
66 |
|
67 |
|
68 |
They're in the default runlevel: |
69 |
|
70 |
# rc-update|grep net.enp |
71 |
net.enp0s20u2u1 | default |
72 |
net.enp0s20u2u2 | default |
73 |
|
74 |
I can disable hotplugging with rc_hotplug in rc.conf. Hotplugging is |
75 |
actually disabled by default there and my network interfaces won't |
76 |
start automatically that way. |
77 |
|
78 |
- Grant |