Proxmox VE 9.0 NIC DOWN

[boyd1984]

I recently install version 9.0 to our new test server DELL R740 but all the NIC are using fiber of SFP no Ethernet.

The installation successful, but the interface status down. I change already the SFP both in DELL server and switches, change also the fiber cable used Multi-mode
and Single-mode type but the output still the same.

I tried different port on the server and restart network services, tried also the alternate name of the NIC but no luck.

attached the screenshots of the command " ip l" and config file.

Can I ask for your advise.

 

[jaminmc]

You could try installing the newest Linux Kernel of 6.17, as it has newer hardware support.

Thread 'Opt-in Linux 6.17 Kernel for Proxmox VE 9 available on test & no-subscription'

Monday at 10:46

We recently uploaded the 6.17 kernel to our repositories. The current default kernel for the Proxmox VE 9 series is still 6.14, but 6.17 is now an option.

We plan to use the 6.17 kernel as the new default for the Proxmox VE 9.1 release later in Q4.
This follows our tradition of upgrading the Proxmox VE kernel to match the current Ubuntu version until we reach an Ubuntu LTS release, at which point we will only provide newer kernels as an opt-in option. The 6.17 kernel is based on the Ubuntu 25.10 Questing release.

We have run this kernel on some of our test setups over the last few days...

• t.lamprecht
• kernel 6.17 linux 6.17 opt-in kernel
• Replies: 25
• Forum: Proxmox VE: Installation and configuration

• 

Since you don't have network connectivity, you can download the packages, and put them on a thumb drive, then install them on your server,

Kernel:
http://download.proxmox.com/debian/...ry-amd64/proxmox-kernel-6.17_6.17.1-1_all.deb
http://download.proxmox.com/debian/...roxmox-kernel-6.17.1-1-pve_6.17.1-1_amd64.deb
http://download.proxmox.com/debian/...kernel-6.17.1-1-pve-signed_6.17.1-1_amd64.deb

Headers (In case you need DKMS):
http://download.proxmox.com/debian/...y-amd64/proxmox-headers-6.17_6.17.1-1_all.deb
http://download.proxmox.com/debian/...oxmox-headers-6.17.1-1-pve_6.17.1-1_amd64.deb

Firmware:
http://download.proxmox.com/debian/...test/binary-amd64/pve-firmware_3.17-2_all.deb


The ones that end in _all.deb will make sure that future kernels and headers updates will update. the proxmox-kernel-6.17.1-1-pve-signed_6.17.1-1_amd64.deb is for secure boot. Make sure you have the firmware one also. In case it needs to load the firmware for your NIC's also.

 

[boyd1984]

I tried your suggestion, the firmware successfully installed and I install pve-signed, but still NIC DOWN

I have another new R740 server and install the proxmox version 8.4, same situation NIC DOWN, I try to install your suggestion all package successfully installed but still NIC DOWN

I'm out of luck on this

 

[shanreich]

It shows NO-CARRIER in your output, that usually means that there is no cable detected. Did you plug it into the correct port and did you check whether the cable is faulty?

 

[readyspace]

I recently install version 9.0 to our new test server DELL R740 but all the NIC are using fiber of SFP no Ethernet.

The installation successful, but the interface status down. I change already the SFP both in DELL server and switches, change also the fiber cable used Multi-mode
and Single-mode type but the output still the same.

I tried different port on the server and restart network services, tried also the alternate name of the NIC but no luck.

attached the screenshots of the command " ip l" and config file.

Can I ask for your advise.

Hi, this usually happens when Proxmox doesn’t load the right driver for your SFP NICs — common with Broadcom or Intel X710/XL710 adapters.

Check lspci -k | grep -A3 Eth to confirm which module is used (e.g., bnx2x, i40e, or ixgbe).

If none is loaded, install the latest pve-firmware or Dell’s vendor firmware bundle.

Ensure your SFP modules are on Dell’s approved list; unsupported optics will keep links DOWN. (which i think its likely the case)

You can also test link detection in Debian Live — if it works there, it’s a driver or firmware gap in PVE 9.0 which then need to file an issue at bugzilla.