View previous topic :: View next topic |
Author |
Message |
kartana n00b
Joined: 18 Aug 2017 Posts: 9
|
Posted: Tue Mar 20, 2018 4:04 pm Post subject: Network interface disappeared after bios update |
|
|
Hi Everyone,
I hope someone can help. I have updated my computer with the newest BIOS and now networking stop working. Before I made the BIOS update my network interface was working fine - 6 months plus. It is a r8169 Gigabit Ethernet and named enp33s0 (looking in dmesg, it seems to be called eth0 now but I have tried to add it as eth0 and still not working).
Syslog tells that the interface net.enp33s0 does not exits and therefore fails to start.
To be sure, I have recompiled (with the same settings as before) the kernel and modules but no luck.
All help is appreciated.
Regards Stig |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9679 Location: almost Mile High in the USA
|
Posted: Tue Mar 20, 2018 4:23 pm Post subject: |
|
|
It looks like you're back to as if you were installing the network for the first time once more.
Assuming you're using static setup, openrc. So you have /etc/conf.d/net with config_eth0=xxx and the symlinks from /etc/init.d/net.eth0 -> net.lo ?
If you manually set up that eth0 device, does it work?
This is strange that the persistent device names didn't work, but with an ACPI/BIOS change, all bets are off. I've had one motherboard whose ethernet simply died with a bios change... that was annoying. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
|
Back to top |
|
|
kartana n00b
Joined: 18 Aug 2017 Posts: 9
|
Posted: Tue Mar 20, 2018 4:36 pm Post subject: |
|
|
Jaglover wrote: | I suspect the interface got another new "persistent" name. Just look what it is called now and adjust your setup. |
Thank to both of you. How do I find the new persistent name? Do you know a cmd? |
|
Back to top |
|
|
kartana n00b
Joined: 18 Aug 2017 Posts: 9
|
Posted: Tue Mar 20, 2018 5:29 pm Post subject: |
|
|
kartana wrote: | Jaglover wrote: | I suspect the interface got another new "persistent" name. Just look what it is called now and adjust your setup. |
Thank to both of you. How do I find the new persistent name? Do you know a cmd? |
You are right. It did change the persistent name to enp30s0. The command I used to find the name was:
Thank you again - this solved my problem. |
|
Back to top |
|
|
|