[SOLVED] bios update breaks network connection on debian 9.3, windows 10 and mx linux unaffected

ppcthug · 03-22-2018, 04:41 PM

I have a multi boot computer with debian 9.3, mx linux 17 and windows 10
I updated my bios and now debian can't see the network.

ifconfig -a
enp30s0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 4c:cc:6a:ff:c5:ce txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 4 bytes 240 (240.0 B)
Rx errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 240 (240.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I couldn't find any problems like this searching google

BW-userx · 03-23-2018, 10:39 AM

what BIOS ver and what motherboard as in what brand PC? as it shouldn't, of course, if the BIOS update wasn't for anything to do with your nic. if anything it may have changed something but then that should just need an adjustment to your Linux system to get it to see your nic again and load the drivers for it and such.

because you have one out of three that now cannot see your network.
debian 9.3, mx linux 17 and windows 10, and it is only Debian that is no longer working. it may just be something that just happened to have happened somewhere within the time when you where flashing your BIOS.

I'd be looking harder at Debian then what the flash to the BIOS did because it is one out of three that was effected. If your Flashing the BIOS messed with the NIC which I've never seen one do, then all three would have seen the changes within that which caused the NIC to no longer connect to the network and should have given all three issues.

Seeing this did not happen, then the logical place to look would then be at Debian and something else that would cause this to happen.

ppcthug · 03-23-2018, 01:09 PM

the motherboard is an msi tomahawk b350, the old bios version was 17, the new version is 1f. ( 17, 18, 19, 1c, 1f) weird version numbering scheme but whatever.

here is my /etc/network/interfaces
it doesn't match the ifconfig -a output, enp33s0 instead of enp30s0
interfaces.d directory is empty

Code:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug enp33s0
iface enp33s0 inet dhcp

BW-userx · 03-23-2018, 02:18 PM

so make it match up then see how that works out for you.
comment out your predefined in that file then add what your output to your ifconfig -a output is telling you, or wherever it needs to be, and maybe have to reboot so it catches then try it again.

ppcthug · 03-23-2018, 05:46 PM

tried changing the interfaces file to match ifconfig and restarted, didn't seem to help.
I looked in the Wicd network manager preferences, the wired interface also had an entry for enp33s0, changed that to enp30s0 and got connected.
restarted the computer, still have a connection. problem solved apparently.
thank you.

BW-userx · 03-23-2018, 06:42 PM