I'm putting this out here just in case somebody else would be looking for it:
I put away my dear beloved an AMD 5800X3D CPU and my Nvidia RTX 3080 GPU because I'm taking a break from gaming. Instead, I installed a 5700G to conserve power. Upon booting for the first time, I had no internet connection. A quick glance at ip link and I noticed that the Ethernet interface no longer is called enp6s0 but enp5s0. Updating the interface name in my network config files solved the problem.
As a bonus, both the hardware and system clocks were also all over the place until I adjusted them...
I have no idea why a new CPU comes with these phenomena, but it did.
6 Comments
theit8514@lemmy.world · 14 pts · 232d
The p number refers to the pci bus that the port was detected on. It could be the cpu has a different process when detecting the pci bus layout.
pastermil@sh.itjust.works · 4 pts · 232d
So much for predictable naming scheme.
emotional_soup_88@programming.dev · 3 pts · 231d
I literally don't know what to do about my Arch install complaining about my
.networkfiles having potentially unpredictable names or whatever... 😂ikidd@lemmy.world · 2 pts · 231d
Yah, that changed decades ago and I'm still pissed.
emotional_soup_88@programming.dev · 1 pts · 232d
Sic! Thanks for your wisdom! :) 🔌
ikidd@lemmy.world · 3 pts · 231d
You're pretty much left with something like this for aliasing network names:
https://wiki.debian.org/NetworkInterfaceNames#CUSTOM_SCHEMES_USING_.LINK_FILES
You're fine with your setup there, but this is a major pain in the ass when you've hardcoded interfaces in a firewall conf or something.