:: Re: [DNG] Ethernet names revisited
Forside
Slet denne besked
Besvar denne besked
Skribent: Antony Stone
Dato:  
Til: dng
Emne: Re: [DNG] Ethernet names revisited
On Sunday 13 December 2020 at 11:23:21, Florian Zieboll via Dng wrote:

> Am 13. Dezember 2020 10:45:56 MEZ schrieb Antony Stone:
> > From Ascii onwards I get the errors:
> >
> > udevd[441]: Error changing net interface name eth2 to eth0: File exists
> > udevd[441]: could not rename interface '4' from 'eth2' to 'eth0': File
> > exists
> >
> > and so on.
>
> Does the bootlog give a hint, which service did assign the conflicting
> ifnames udevd can't change?


Well, here's the output from "dmesg | grep eth". It shows the r8169
interfaces being given names eth0, eth1 (the ones I want as eth1 and eth2),
then the tg3 interface gets called eth2 (which I want as eth0).

At 6 seconds in, you can see my 70-persistent-net.rules file kicking in and
renaming then to xeth2, xeth1 and xeth0; then finally at 12 seconds, the second
rename in /etc/network/interfaces sets them back to eth0, eth1 and eth2 in the
order I want them.

[    3.374572] r8169 0000:04:00.0 eth0: RTL8168e/8111e, 00:e0:4c:80:21:6b, XID 
2c200000, IRQ 30
[    3.374576] r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx 
checksumming: ko]
[    3.433052] r8169 0000:05:00.0 eth1: RTL8168e/8111e, 00:e0:4c:80:21:6c, XID 
2c200000, IRQ 31
[    3.433056] r8169 0000:05:00.0 eth1: jumbo features [frames: 9200 bytes, tx 
checksumming: ko]
[    3.488464] tg3 0000:07:00.0 eth2: Tigon3 [partno(BCM95723) rev 5784100] 
(PCI Express) MAC address 78:ac:c0:f7:89:f7
[    3.488468] tg3 0000:07:00.0 eth2: attached PHY is 5784 (10/100/1000Base-T 
Ethernet) (WireSpeed[1], EEE[0])
[    3.488471] tg3 0000:07:00.0 eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] 
TSOcap[1]
[    3.488474] tg3 0000:07:00.0 eth2: dma_rwctrl[76180000] dma_mask[64-bit]
[    6.139566] r8169 0000:05:00.0 xeth2: renamed from eth1
[    6.168205] r8169 0000:04:00.0 xeth1: renamed from eth0
[    6.186586] tg3 0000:07:00.0 xeth0: renamed from eth2
[   10.930250] IPv6: ADDRCONF(NETDEV_UP): xeth0: link is not ready
[   12.460422] tg3 0000:07:00.0 eth0: renamed from xeth0
[   12.533793] r8169 0000:04:00.0 xeth1: unable to load firmware patch 
rtl_nic/rtl8168e-2.fw (-2)
[   12.645721] IPv6: ADDRCONF(NETDEV_UP): xeth1: link is not ready
[   12.672414] r8169 0000:04:00.0 eth1: renamed from xeth1
[   12.742780] r8169 0000:05:00.0 xeth2: unable to load firmware patch 
rtl_nic/rtl8168e-2.fw (-2)
[   12.853714] IPv6: ADDRCONF(NETDEV_UP): xeth2: link is not ready
[   12.880384] r8169 0000:05:00.0 eth2: renamed from xeth2
[   13.727991] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   13.961821] bond0: Enslaving eth1 as an active interface with a down link
[   14.081838] bond0: Enslaving eth2 as an active interface with a down link
[   16.522996] tg3 0000:07:00.0 eth0: Link is up at 1000 Mbps, full duplex
[   16.523020] tg3 0000:07:00.0 eth0: Flow control is on for TX and on for RX
[   16.523074] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready


If I can post anything else which shows the detail you're after, please let me
know where it would be recorded.


Thanks,


Antony.

--
This email was created using 100% recycled electrons.

                                                   Please reply to the list;
                                                         please *don't* CC me.