Nothing but network frustration with the 2.8.2 iso

I have a bunch of identical computers and the initial problem showed up when I did a complete install erasing 2.8.1 with the 2.8.2 iso. The bios was setup to boot off usb but cmos wasn't cleared.

When that didn't work, I commissioned a spare computer which required flashing bios including clearing the ME flash and clearing the CMOS. I had the same problems with the second computer.

I just did my fourth install of 2.8.2 iso following my install procedure to give better info for this thread. Of course this install seems to be working fine!!! No idea on what was different that it is now working. Could be an intermittent wire? But I could consistently get the setup to ping, readhmid and then the mesa network connection would go down.

I'm calling it a night as I now have my mill setup to boot into a working 2.8.2 install. I also installed a second ssd with a copy of 2.8.1 so I can change my boot order if this stops working.

Thanks to everyone that chimed in with ideas. Crossing my fingers that this continues to work and I can get back to actual projects.

I'm still getting network drops but now it's just losing first NIC connected to my computer network. The NIC connected to the mesa stays connected. I think there is something funny with the 2.8.2 networking.

Have you looked thru the system logs or dmesg to see if the kernel is reporting anything of note ?

Apart from an updated kernel there shouldn't be too much different as all the meat comes from Debian anyways.

Can you try this for each of your interfaces

[code]ethtool --show-eee <devname> [/cdoe]

Replace <devaname> with the name of your actual interfaces, and can you highlight which is which, ie one connected to LAN and the other MESA.

Maybe this link could be of use: unix.stackexchange.com/questions/532182/...ebian-10-kernel-4-19