Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Broken network after reboot (SOLVED)
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
andrewwalker27
l33t
l33t


Joined: 27 Jun 2005
Posts: 650

PostPosted: Thu Feb 28, 2019 12:52 pm    Post subject: Broken network after reboot (SOLVED) Reply with quote

I recently re-booted my machine after the holidays and it no longer starts up due to networking errors. I don't often power it down so many updates would have been carried out previously making it hard to track down the problem.
The service used to be called net.enp6s0 and used the tg3 driver I believe, dmesg shows the device as follows
Code:
eth0: Tigon 3 [partno(BCM95761) rev 5761100] (PCI Express) MAC address bc:30:5b:a8:cd:fa

the driver is compiled into the kernel so it's not a kernel module loading issue.
Could something have changed the naming of the device? shouldn't dmesg show enp6s0 rather than eth0 or is it something else that renames it?

It's also killed xorg so I can't easily copy log files over, I did read about Nvidia drivers having a bug that prevents modules loading, and there was an nvidia update at that time, but as it's compiled into the kernel that shouldn't affect it. I did purge the nvidia driver and switch to nouveau in case that helped but still no luck.
I'm using kernel 4.19.10 if that helps diagnose the fault.


Last edited by andrewwalker27 on Thu Feb 28, 2019 1:47 pm; edited 1 time in total
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7089
Location: Saint Amant, Acadiana

PostPosted: Thu Feb 28, 2019 1:12 pm    Post subject: Reply with quote

I'm not sure I understand your problem, you have eth0 (according to the line from dmesg), do you want it be renamed to something else? You should create a udev rule then.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
andrewwalker27
l33t
l33t


Joined: 27 Jun 2005
Posts: 650

PostPosted: Thu Feb 28, 2019 1:47 pm    Post subject: Reply with quote

The problem is that the network name used to be net.enp6s0 and not net.eth0 and now network won't start. I don't know why it has changed, can only assume an update did that.
Anyway, I've changed the rc-update entry to net.eth0 rather than net.enp6s0 and it's working again but thanks for replying!
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13831

PostPosted: Fri Mar 01, 2019 2:46 am    Post subject: Reply with quote

You were using systemd's "predictable network interface name" feature, which mangles the name based on hardware characteristics so that it is harder for us to predict. Now you are not, so you have the kernel-assigned name of eth0.
Back to top
View user's profile Send private message
andrewwalker27
l33t
l33t


Joined: 27 Jun 2005
Posts: 650

PostPosted: Fri Mar 01, 2019 8:38 am    Post subject: Reply with quote

What I actually found was that somehow I ended up with udev instead of evdev and that was why the device name changed. I still have no idea how it happened but I think I'll mask udev to prevent it happening again.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum