Most of this data was reconstructed from phone photos.
Initial install of Proxmox 4 not working with the e1000e driver.
Edit: I can't update the hypervisor as it has no working ethernet ports, it is a vanilla install.
NIC: 80003ES2LAN
MOBO: Intel S5400SF
Kernel: 4.2.2-1-pve
Confirmed working with Fedora 22 live, Debian 8.2 live and Windows 7.
Fedora 22 and Debian 8.2 are both using the e1000e driver.
Tried copying the driver over from several different distros, without luck.
Tried using a different Proxmox 4 hypervisor as a build environment.
Built several different versions of the e1000e driver, including the latest on the Intel and Sourceforge websites (The latest Sourceforge one supposedly works with kernel 4.x).
We tried manually loading the module, as well as adding it to /etc/modules.
No mention of the driver, or the interface, in any log file.
During boot the lights on both networking ports turn off as soon as the initial install of Proxmox 4 starts to load.
After replacing the e1000e.ko in Proxmox 4 with the one from Fedora 22, the lights would stay on but nothing else changed.
The motherboard EFI was updated to the latest, and reset after the issue initially occured.
After force loading e1000e, lsmod shows it, and "ptp" shows it is using it.
I do not have an ifconfig photo to reconstruct the output from, but it looked good compared to a working hypervisor with a different NIC chipset.
/etc/network/interfaces
route -n
lspci | grep -i ethernet
Let me know if you need any more info, I will see if I have photos for anything else.
Initial install of Proxmox 4 not working with the e1000e driver.
Edit: I can't update the hypervisor as it has no working ethernet ports, it is a vanilla install.
NIC: 80003ES2LAN
MOBO: Intel S5400SF
Kernel: 4.2.2-1-pve
Confirmed working with Fedora 22 live, Debian 8.2 live and Windows 7.
Fedora 22 and Debian 8.2 are both using the e1000e driver.
Tried copying the driver over from several different distros, without luck.
Tried using a different Proxmox 4 hypervisor as a build environment.
Built several different versions of the e1000e driver, including the latest on the Intel and Sourceforge websites (The latest Sourceforge one supposedly works with kernel 4.x).
We tried manually loading the module, as well as adding it to /etc/modules.
No mention of the driver, or the interface, in any log file.
During boot the lights on both networking ports turn off as soon as the initial install of Proxmox 4 starts to load.
After replacing the e1000e.ko in Proxmox 4 with the one from Fedora 22, the lights would stay on but nothing else changed.
The motherboard EFI was updated to the latest, and reset after the issue initially occured.
After force loading e1000e, lsmod shows it, and "ptp" shows it is using it.
I do not have an ifconfig photo to reconstruct the output from, but it looked good compared to a working hypervisor with a different NIC chipset.
/etc/network/interfaces
Code:
auto lo
iface lo inet loopback
auto vmbr0
iface vmbr0 inet static
address 192.168.1.192
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_stp off
bridge_fd 0route -n
Code:
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 vmbr0
192.168.1.0 * 255.255.255.0 U 0 0 0 vmbr0lspci | grep -i ethernet
Code:
06:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
06:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)Let me know if you need any more info, I will see if I have photos for anything else.