Recent content by mawcs

No. Intel Dual 82576.

My solution was to install Debian, then ProxMox on top of Debian.

$ uname -ar Linux [redacted] 5.4.60-1-pve #1 SMP PVE 5.4.60-1 (Mon, 31 Aug 2020 10:36:22 +0200) x86_64 GNU/Linux $ pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.60-1-pve) pve-manager: 6.2-11 (running version: 6.2-11/22fb4983) pve-kernel-5.4: 6.2-6 pve-kernel-helper: 6.2-6...

I assume so, but maybe you can tell me. I followed these instructions: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster Is there a way to verify?

Debian 10.5.0 installs and the network interface works after reboot. I installed the ProxMox packages on top of this Debian install and the network continues to start after boot. So, I think the problem is the result of the ProxMox ISO installer and not the ProxMox packages themselves.

My first ProxMox server is old consumer-grade hardware with a single processor, and a single on-board NIC. This new (to me) hardware is server-grade hardware with multiple processors, and multiple NICs (details below). Since yesterday, I've successfully installed Kubuntu and Arch Linux on this...

Installed 6.1-2 on this hardware and got the same result. Since I have 6.1 installed on other hardware without issues, I'm assuming that there's something about this hardware. I will continue to investigate.

I appreciate your reply. I'm curious about your line of thinking. Wouldn't a failed driver prevent the network from working at all? The network just fails to start during boot, but can start post-boot. It seems as if it's trying to start before dependencies are available. Notable syslog...

I have this same issue. I built and set up a new server with 6.2-4 and I have to stop and start all networks to get the network running on the PVE host after boot. I have PVE 6.1-3 running on different hardware without issue this issue. I'm wondering if I should attempt to install an older...