Linux Questions

3591 readers

21 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

stay on topic
be nice (no name calling)
do not post long blocks of text such as logs
do not delete your posts
only post questions (no information posts)

Tips for giving and receiving help

be as clear and specific
say thank you if a solution works
verify your solutions before posting them as facts.

Any rule violations will result in disciplinary actions

founded 2 years ago

MODERATORS

possiblylinux127@lemmy.zip

Ethernet interface name changed after changing CPU (programming.dev)

submitted 2 weeks ago by emotional_soup_88@programming.dev to c/linuxquestions@lemmy.zip

6 comments fedilink hide all child comments

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.

top 6 comments

sorted by: hot top controversial new old

[–] theit8514@lemmy.world 11 points 2 weeks ago (2 children)

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 points 2 weeks ago (2 children)

So much for predictable naming scheme.

[–] emotional_soup_88@programming.dev 3 points 2 weeks ago

I literally don't know what to do about my Arch install complaining about my .network files having potentially unpredictable names or whatever... 😂

[–] ikidd@lemmy.world 2 points 2 weeks ago

Yah, that changed decades ago and I'm still pissed.

[–] emotional_soup_88@programming.dev 1 points 2 weeks ago

Sic! Thanks for your wisdom! :) 🔌

[–] ikidd@lemmy.world 3 points 2 weeks ago

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.