Recent content by vesalius

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.

So with the help of @aarononeal and the How to build a kernel module with DKMS on Linux webpage I have DKMS autoinstall working with the last kernel upgrade. apt-get install proxmox-default-headers build-essential dkms gcc make cd /tmp wget...

Now can be found: https://images.linuxcontainers.org/images/openwrt/

Taking a shot in the dark, but pve-headers are no longer what you need. I think that was deprecated somewhere in the last year or so. As mentioned above you now need proxmox-default-headers.

How to download and install ixgbe driver on Ubuntu or Debian Commands below are what I adapted for proxmox from that page to install the latest out of tree intel ixgbe driver and fix this issue for now. Mainly need to install proxmox-default-headers instead of linux-headers-$(uname -r) sudo...

So all the not found errors after reboot is because you are running the modinfo ./ixgbe.ko command from the wrong directory. Prior to reboot when you ran modinfo ./ixgbe.ko you were already in /tmp/ixgbe-5.19.9/src folder where ixgbe.ko was physically located. After reboot you are only at /...

Both of those links you listed are really old relative to the kernel version you are currently running. I needed to do this because linux kernels used in PVE 8 and above do not work with x553 based networking. Not sure if that is the case with x540 based cards or whether you are haveing a...

Created bug report for this issue: Bug 5103 - intel x553 SFP+ ixgbe does not link up on pve8 or pve8.1

No response from anyone at @proxmox on this one, likely too small of an affected installed base so far. Have seen this Linux kernel commit suggested as the culprit. An amazon employee states reverting this commit and recompiling the kernel allows their similar network hardware to use the...

Hello all, Currently running Proxmox 8.0.4 with kernel 5.15.108 on 2 of my Proxmox nodes as that is the last working kernel for them. The Atom c3758 cpu with on MB x553 10g SFP+ x4 fails networking on all the proxmox 6.2 kernels. Similar issues seen from others on the intel x553 SFP+ adapter...

Up to the proxmox devs, but shouldn’t be too much longer. Historically they always pin a post at the top of this forum stating the new kernel is available in the pve-no-subscription repository (or just change the notification post regarding the Test repository availability) so more folks can...

You can use it for now. I have had to stick with the 5.15 kernel on 2 of my nodes after updating to pve 8 because the Linux Kernel 6.* has a bad intel module for x553 sfp+ so my networking dies on both of those.

These quit working with the shift to linux kernel 6.*. I reported initially here, but no luck with any of the PVE8 kernels either. I am currently using the last 5.15.108-1-pve kernel successfully otherwise software is latest pve8. Bringing this up again because I have been following along with...

As long as all PVE nodes have access to both the 192.168.3.0/24 and 192.168.2.0/26 networks using similarly named network adapters/bridges, it should not be an issue. Easiest to setup if all ProxMox nodes are the exact same config. but not hard to do even if they are not.