Search results

Proxmox released proxmox-kernel-signed-6.8.12-1 to the no-subscription repository, which sources Ubuntu-6.8.0-43.43 (where ubuntu finally reverts the ixgbe 553 breakage from back in Linux Kernel 6.1). Try it out, installed and works after reboot without the OOT intel IXGBE installed for me...

After a couple of years Ubuntu seems to have recently reverted the Linux kernel regression causing this issue dating back to kernel 6.1 AND Proxmox may finally pick up the fix in an upcoming kernel. https://lists.proxmox.com/pipermail/pve-devel/2024-August/065041.html

Thanks, hopefully, this is a universal way forward. Copied your post to the bug report for this issue: Bug 5103 - intel x553 SFP+ ixgbe does not link up on pve8 or pve8.1

The naming structure changed somewhere after the switch to the early Linux 6 kernels Promox 7 or so, which this machine locked to linux 5.3 skipped. Not sure about the grub directory errors, but believe I have seen the same. When you're booting do you see GRUB or systemd-boot...

In order to get dkms automatically working again with ixgbe/5.20.10 and kernel 6.8.8-* updates, obviously need to replace 5.20.10 in the above steps, but also I had to rm -rf /var/lib/dkms/ixgbe (before going through the last 3 commands starting with sudo dkms add ixgbe/5.2.10) or DKMS would...

I should have mentioned, be prepared to potentially have some of your network interface names changed once booted into the latest kernel. If networking is off or not working, ip a and compare the interface names with what you have with the older naming conventions in /etc/network/interfaces...

at some point 5.3.10-1-pve was pinned given the proxmox-boot-tool kernel list output shown. proxmox-boot-tool kernel unpin and reboot will undo this or if you want to be cautious start with proxmox-boot-tool kernel unpin --next-boot and reboot for single use trial. If all good after reboot...

To start you may want to consider editing your /etc/network/interfaces with the changes below: auto vmbr0 iface vmbr0 inet static address 192.168.5.150/24 bridge-ports enp2s0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 auto vmbr1 iface vmbr1...

What doess the pfsense VM side look like under hardware? is pfsense pulling an IP from WAN (assume that is vmbr1). Whats the IP of the computer you are using to access the proxmox webgui? is it pulling an ip address from pfsense DHCP or at least manually set to be in the new pfsense LAN subnet?

Will second @rtorres. I ran pfsense for a couple of years then switched to opnsense for the last 3-4 years all running as a proxmox VM, in a config similar to his description. No issues with either going down on their own. Have come to have as much faith in this setup as any separate hardware...

yes like I did when I reported this originally. https://forum.proxmox.com/threads/intel-x553-sfp-ixgbe-no-go-on-pve8.135129/post-626516

Crazy the variability, this combo is not work for me at all. No link after reboot.

ixgbe stable / 5.20.9 released. 5.20.9 builds and installs without error for me on 6.8.8-1-pve, BUT the SFP+ ports are still down after a reboot into this kernel/driver combo. Don't have time to investigate much, hopefully others have better luck. reverted back to 6.5.13-5-pve/ixgbe-5.19.9...

Unless I am misunderstanding your suggestions, I did try already and the build errored out. See https://forum.proxmox.com/threads/intel-x553-sfp-ixgbe-no-go-on-pve8.135129/post-657758

Must be a different issue than what I am experiencing then, those out of tree intel drivers work fine to resurrect my SFP+ ports when installed in the Proxmox 6.5 kernel.

While this affects proxmox, it is not just a proxmox issue, it is a general Linux kernel driver issue, that affects every distribution using Linux kernel 6.* and above, so Ubuntu, debian, suse, etc .... you can pin the last proxmox 6.5 kernel and build/install the 5.20.3 driver there to regain...

Just doing a mv /usr/src/ixgbe-5.19.9/dkms.conf /usr/src/ixgbe-5.19.9/dkms.conf.bak should be enough. Then you can install the 6.8 kernel, though you will lose function of the sfp+ ports unless you pin the 6.5 kernel with the DKMS 5.19.9 driver.

I have been using all the 6.5.* kernels with DKMS autoinstalling ixgbe-5.19.9 drivers without issue following what I posted above. Could not manually get 5.19.9 to build for 6.8.* series though. Today Intel releases 5.20.3, but that fails with DKMS as well. Went back and pinned to 6.5.13 for...

Anyone affected by this try 8.2 yet ... either natively to see if the default driver for 6.8.4 works or with DKMS of the 5.19.9 intel driver?

Comment out rmmod ixgbe from the end of your script and try again. Don't think you should be running that at all with dkms. Or you can just try to run the commands from here at the CLI because with DKMS you should not ever have to run that script more than once.