Howdy all, First, if anyone is planning to switch a remote machine, you may want to delay that.
As some, most, know eudev is being removed. I can't say how much I dislike that but it seems to be happening despite some are saying it is still being maintained upstream. During my weekly update today, eudev was masked and the virtual wanted systemd, which I do not want at all, so I knew it was time to switch. I do my updates in a chroot so that I can just install binaries on my main system. Everything went well in the chroot. No problems there. However, when I switched in the real system, no network. Everything else seems to work but when I try to bring up net.eth0, it pukes on my keyboard about a missing driver. Keep in mind, I was using the same kernel as before. The only difference, switching to udev. Also, I switched to udev not systemd as a whole. I unmerged eudev, emerged udev with some little friends. I suspect there is some sort of name change, config change or something required that everyone else did ages ago. I'm still using as you might have noticed, net.eth0 for the name. Thing is, it's all I have here. By the way, switching back to eudev got me connected with no problems. Some info. root@fireball / # ifconfig eth0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 secret stuff prefixlen 64 scopeid 0x20<link> ether secret stuff txqueuelen 1000 (Ethernet) RX packets 7841 bytes 9076941 (8.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7436 bytes 748477 (730.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 34 memory 0xfe3c0000-fe3e0000 root@fireball / # ls -al /etc/init.d/net* lrwxrwxrwx 1 root root 6 Mar 1 2012 /etc/init.d/net.eth0 -> net.lo lrwxrwxrwx 1 root root 18 Oct 12 2013 /etc/init.d/net.eth1 -> /etc/init.d/net.lo -rwxr-xr-x 1 root root 19861 Nov 18 20:38 /etc/init.d/net.lo -rwxr-xr-x 1 root root 2071 Nov 19 06:38 /etc/init.d/netmount -rwxr-xr-x 1 root root 2278 Nov 19 06:38 /etc/init.d/net-online root@fireball / # Of course that is with eudev not udev. Hard to post udev when it isn't working. ;-) This is the emerge logs. 1638112926: Started emerge on: Nov 28, 2021 09:22:06 1638112926: *** emerge --oneshot --unordered-display --ask --backtrack=100 --jobs=5 --keep-going --with-bdeps=y --quiet-build=n --regex-search-auto=y --usepkg --verbose udev 1638112961: >>> emerge (1 of 9) acct-group/kmem-0-r1 to / 1638112961: >>> emerge (2 of 9) acct-group/tty-0-r1 to / 1638112961: >>> emerge (3 of 9) acct-group/audio-0-r1 to / 1638112961: >>> emerge (4 of 9) acct-group/cdrom-0-r1 to / 1638112961: >>> emerge (5 of 9) acct-group/dialout-0-r1 to / 1638112962: === (1 of 9) Merging Binary (acct-group/kmem-0-r1::/var/cache/portage/packages/acct-group/kmem-0-r1.tbz2) 1638112963: === (2 of 9) Merging Binary (acct-group/tty-0-r1::/var/cache/portage/packages/acct-group/tty-0-r1.tbz2) 1638112965: === (4 of 9) Merging Binary (acct-group/cdrom-0-r1::/var/cache/portage/packages/acct-group/cdrom-0-r1.tbz2) 1638112965: === (5 of 9) Merging Binary (acct-group/dialout-0-r1::/var/cache/portage/packages/acct-group/dialout-0-r1.tbz2) 1638112965: === (3 of 9) Merging Binary (acct-group/audio-0-r1::/var/cache/portage/packages/acct-group/audio-0-r1.tbz2) 1638112966: >>> emerge (6 of 9) acct-group/disk-0-r1 to / 1638112967: === (6 of 9) Merging Binary (acct-group/disk-0-r1::/var/cache/portage/packages/acct-group/disk-0-r1.tbz2) 1638112977: >>> emerge (7 of 9) acct-group/tape-0-r1 to / 1638112978: === (7 of 9) Merging Binary (acct-group/tape-0-r1::/var/cache/portage/packages/acct-group/tape-0-r1.tbz2) 1638112980: >>> AUTOCLEAN: acct-group/kmem:0 1638112982: >>> AUTOCLEAN: acct-group/cdrom:0 1638112991: === (1 of 9) Post-Build Cleaning (acct-group/kmem-0-r1::/var/cache/portage/packages/acct-group/kmem-0-r1.tbz2) 1638112991: ::: completed emerge (1 of 9) acct-group/kmem-0-r1 to / 1638112991: === (4 of 9) Post-Build Cleaning (acct-group/cdrom-0-r1::/var/cache/portage/packages/acct-group/cdrom-0-r1.tbz2) 1638112991: ::: completed emerge (4 of 9) acct-group/cdrom-0-r1 to / 1638113005: >>> AUTOCLEAN: acct-group/tty:0 1638113009: >>> AUTOCLEAN: acct-group/audio:0 1638113018: === (2 of 9) Post-Build Cleaning (acct-group/tty-0-r1::/var/cache/portage/packages/acct-group/tty-0-r1.tbz2) 1638113018: ::: completed emerge (2 of 9) acct-group/tty-0-r1 to / 1638113018: === (3 of 9) Post-Build Cleaning (acct-group/audio-0-r1::/var/cache/portage/packages/acct-group/audio-0-r1.tbz2) 1638113018: ::: completed emerge (3 of 9) acct-group/audio-0-r1 to / 1638113032: >>> AUTOCLEAN: acct-group/dialout:0 1638113035: >>> AUTOCLEAN: acct-group/disk:0 1638113043: === (5 of 9) Post-Build Cleaning (acct-group/dialout-0-r1::/var/cache/portage/packages/acct-group/dialout-0-r1.tbz2) 1638113043: ::: completed emerge (5 of 9) acct-group/dialout-0-r1 to / 1638113043: === (6 of 9) Post-Build Cleaning (acct-group/disk-0-r1::/var/cache/portage/packages/acct-group/disk-0-r1.tbz2) 1638113043: ::: completed emerge (6 of 9) acct-group/disk-0-r1 to / 1638113049: >>> AUTOCLEAN: acct-group/tape:0 1638113055: === (7 of 9) Post-Build Cleaning (acct-group/tape-0-r1::/var/cache/portage/packages/acct-group/tape-0-r1.tbz2) 1638113055: ::: completed emerge (7 of 9) acct-group/tape-0-r1 to / 1638113055: >>> emerge (8 of 9) sys-fs/udev-249-r3 to / 1638113056: === (8 of 9) Merging Binary (sys-fs/udev-249-r3::/var/cache/portage/packages/sys-fs/udev-249-r3.tbz2) 1638113063: >>> AUTOCLEAN: sys-fs/udev:0 1638113072: === (8 of 9) Post-Build Cleaning (sys-fs/udev-249-r3::/var/cache/portage/packages/sys-fs/udev-249-r3.tbz2) 1638113072: ::: completed emerge (8 of 9) sys-fs/udev-249-r3 to / 1638113072: >>> emerge (9 of 9) virtual/udev-217-r3 to / 1638113073: === (9 of 9) Merging Binary (virtual/udev-217-r3::/var/cache/portage/packages/virtual/udev-217-r3.tbz2) 1638113081: >>> AUTOCLEAN: virtual/udev:0 1638113081: === Unmerging... (virtual/udev-217-r3) 1638113087: >>> unmerge success: virtual/udev-217-r3 1638113093: === (9 of 9) Post-Build Cleaning (virtual/udev-217-r3::/var/cache/portage/packages/virtual/udev-217-r3.tbz2) 1638113093: ::: completed emerge (9 of 9) virtual/udev-217-r3 to / 1638113093: *** Finished. Cleaning up... 1638113098: *** exiting successfully. 1638113098: *** terminating. This is the network part of lspci -k and I'm using the top one: 03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection Subsystem: Intel Corporation Gigabit CT Desktop Adapter Kernel driver in use: e1000e 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet Kernel driver in use: r8169 This is the USE flags for both packages. I don't see anything obvious. [ebuild N ] sys-fs/udev-249-r3::gentoo USE="kmod (split-usr) -acl (-selinux) -test" ABI_X86="32 (64) (-x32)" 0 KiB [uninstall ] sys-fs/eudev-3.2.10-r1::gentoo USE="hwdb introspection kmod -rule-generator (-selinux) -static-libs -test" ABI_X86="32 (64) (-x32)" In case it matters, I also have these udev rules. root@fireball / # ls -al /etc/udev/rules.d/* -rw-r--r-- 1 root root 2064 Apr 27 2021 /etc/udev/rules.d/69-libmtp.rules -rw-r--r-- 1 root root 1903 Apr 4 2012 /etc/udev/rules.d/70-persistent-cd.rules -rw-r--r-- 1 root root 814 Jan 1 2008 /etc/udev/rules.d/70-persistent-net.rules -rw-r--r-- 1 root root 0 Mar 22 2015 /etc/udev/rules.d/80-net-name-slot.rules root@fireball / # Anyone have any ideas? Are the network interfaces called something else now? Some config file not correct? Thanks. Dale :-) :-)
