SolarFlare SFN5122F Driver Issues

kexodus

New Member
Feb 9, 2020
2
0
1
28
To preface this I am very new to Proxmox and I don't have a lot of Linux knowledge :confused:

I have been using Proxmox without issue since late last year with standard 1Gb networking from my freeNAS box. I bought a pair of these cards after seeing that some folks had been using SolarFlare cards in both freeNAS and Proxmox without issue. Since freeNAS now includes the necessary drivers in with SolarFlare cards it was literally plug and play. Proxmox so far has been a bit difficult considering my lack of knowledge with the platform.

Basically, the sfc drivers that are on 4.15.5.1007 will not "claim" my SolarFlare NIC:

Code:
root@proxmox:/# modinfo sfc
filename:       /lib/modules/5.3.13-3-pve/updates/dkms/sfc.ko
version:        4.15.5.1007
license:        GPL
description:    Solarflare network driver
author:         Solarflare Communications and Michael Brown <mbrown@fensystems.co.uk>
srcversion:     F93359540E5B39B4E8D2CF2
alias:          pci:v00001924d00001B03sv*sd*bc*sc*i*
alias:          pci:v00001924d00000B03sv*sd*bc*sc*i*
alias:          pci:v00001924d00001A03sv*sd*bc*sc*i*
alias:          pci:v00001924d00000A03sv*sd*bc*sc*i*
alias:          pci:v00001924d00001923sv*sd*bc*sc*i*
alias:          pci:v00001924d00000923sv*sd*bc*sc*i*
alias:          pci:v00001924d00001903sv*sd*bc*sc*i*
alias:          pci:v00001924d00000903sv*sd*bc*sc*i*
alias:          pci:v00001924d00000813sv*sd*bc*sc*i*
alias:          pci:v00001924d00000803sv*sd*bc*sc*i*
depends:        mdio,mtd
retpoline:      Y
name:           sfc
vermagic:       5.3.13-3-pve SMP mod_unload modversions
(additional output can be given if asked. There's a TON of parm outputs.

and here's my lshw output:

Code:
root@proxmox:/# lshw -c network
  *-network:0 UNCLAIMED
       description: Ethernet controller
       product: SFC9020 [Solarstorm]
       vendor: Solarflare Communications
       physical id: 0
       bus info: pci@0000:01:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd cap_list
       configuration: latency=0
       resources: ioport:e100(size=256)
  *-network:1 UNCLAIMED
       description: Ethernet controller
       product: SFC9020 [Solarstorm]
       vendor: Solarflare Communications
       physical id: 0.1
       bus info: pci@0000:01:00.1
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd cap_list
       configuration: latency=0
       resources: ioport:e000(size=256)
  *-network
       description: Ethernet interface
       product: Ethernet Connection (2) I218-V
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: eno1
       version: 00
       serial: 1c:87:2c:55:c7:df
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.1-4 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:39 memory:f7900000-f791ffff memory:f793c000-f793cfff ioport:f080(size=32)
  *-network
       description: Ethernet interface
       physical id: 2
       logical name: vmbr0
       serial: 1c:87:2c:55:c7:df
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=192.168.50.180 link=yes multicast=yes

So it is showing up as a PCIe card on my system at the very least. Proxmox 6.1 ships with SFC version 4.2(?) however by following SolarFlare documentation this is easy enough to upgrade via DKMS, but either version doesn't make a difference.

I have also installed SolarFlare's own tools for Linux in an attempt to update the card's firmware, when I got this message:

Code:
root@proxmox:/# sfupdate
Solarstorm firmware update utility [v8.0.3]
Copyright Solarflare Communications 2006-2018, Level 5 Networks 2002-2005
No Solarstorm adapters found

That return really has me stumped. I imagine that the core issue is that for whatever reason the sfc drivers are not hooking onto the NIC, so I looked and see what the dmesg output was for this, then I found this:
Code:
[    0.851076] Solarflare NET driver v4.15.5.1007
[    0.851124] sfc 0000:01:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected: device 1924:0803 subsys 1924:6206
[    0.851128] sfc 0000:01:00.0: enabling device (0000 -> 0001)
[    0.851197] sfc 0000:01:00.0 (unnamed net_device) (uninitialized): ERROR: No BAR2 mapping from the BIOS. Try pci=realloc on the kernel command line
[    0.851325] sfc 0000:01:00.1 (unnamed net_device) (uninitialized): Solarflare NIC detected: device 1924:0803 subsys 1924:6206
[    0.851328] sfc 0000:01:00.1: enabling device (0000 -> 0001)
[    0.851367] sfc 0000:01:00.1 (unnamed net_device) (uninitialized): ERROR: No BAR2 mapping from the BIOS. Try pci=realloc on the kernel command line

I eventually passed along the pci=realloc into grub, pushed an update-grub and rebooted. The error still persists. Can anyone give any insight as to why this is happening?

Also, I can verify that when the machine with the exact same hardware is running ESXi, after applying a "legacy" VIB package from SolarFlare and a reboot the NIC comes up and I can get a VM to max out at 8Gbs. That being said I would rather run with Proxmox given its awesome feature-set without any cost.

Any assistance greatly appreciated!
 
Hi, try to update the firmware with an old kernel.
I would try the kernel of PVE 5.4 aka 4.15.
 
I know this thread is pretty old but I am having the same issue and I am totally stuck. I built and installed pve kernel 4.15.18-30 and added the dkms for sfc @ v4_15_10_1003, but still no dice; still show up UNCLAIMED and I get the same thing out of sfupdate as you had. Today I built kernel 4.10.17-5 and I'll have some time this weekend to try it on that kernel but I dont have high hopes...

Did you ever solve this issue? Funny enough I bought 2 of the same card from one seller on ebay and one works totally fine in any machine I have that has a pci slot and the other has this issue. From lshw I can see that they might be different board/firmware revisions, so I figure if I can actually get sfupdate to update the firmware then it might work

Edit: I ended up trying pve kernel 4.10.17-5 this weekend and no dice. I think one could probably get it to work but since it's for such an old kernel you would need old versions of binutils, gcc, and dkms, which proved to be a HUGE pain to install on a modern system (the sign for this issue is a 'unknown rela relocation 4' message at boot, means the dkms was compiled with a too new version of gcc/binutils). I was able to get it to almost work by installing the OpenOnload drivers by xilinx; the card didn't show 'unclaimed' anymore but it broke the whole network stack and I couldn't actually see that card as an interface... So I have bought an HP card on eBay and I'm moving on...
 
Last edited:
I know this thread is pretty old but I am having the same issue and I am totally stuck. I built and installed pve kernel 4.15.18-30 and added the dkms for sfc @ v4_15_10_1003, but still no dice; still show up UNCLAIMED and I get the same thing out of sfupdate as you had. Today I built kernel 4.10.17-5 and I'll have some time this weekend to try it on that kernel but I dont have high hopes...

Did you ever solve this issue? Funny enough I bought 2 of the same card from one seller on ebay and one works totally fine in any machine I have that has a pci slot and the other has this issue. From lshw I can see that they might be different board/firmware revisions, so I figure if I can actually get sfupdate to update the firmware then it might work

Edit: I ended up trying pve kernel 4.10.17-5 this weekend and no dice. I think one could probably get it to work but since it's for such an old kernel you would need old versions of binutils, gcc, and dkms, which proved to be a HUGE pain to install on a modern system (the sign for this issue is a 'unknown rela relocation 4' message at boot, means the dkms was compiled with a too new version of gcc/binutils). I was able to get it to almost work by installing the OpenOnload drivers by xilinx; the card didn't show 'unclaimed' anymore but it broke the whole network stack and I couldn't actually see that card as an interface... So I have bought an HP card on eBay and I'm moving on...
One thing you could do. With A LOT of effort I got both my cards working on a Windows 10 machine and updated the firmware and BIOS on them no problem that way. Currently stuck with one in my proxmox and it shows as DISABLED and has no network number so I'm looking into that. But thought I'd let you know if you still wanted to update them.
 
I too have the same issue with my SolarFlare SF432 10GB NIC.
I'm on the current Kernel Version Linux 5.4.114-1-pve #1 SMP PVE 5.4.114-1 (Sun, 09 May 2021 17:13:05 +0200)

Does anyone have any tips on how to get going with installing the generic SolarFlare driver? I think I've heard of a compiled Linux driver for all their NICs.

It would be extremely handy to be able to add drivers for the most common types of devices via the GUI that people might add to Proxmox, such as NICs, SAS controllers etc
 
I too have the same issue with my SolarFlare SF432 10GB NIC.
I'm on the current Kernel Version Linux 5.4.114-1-pve #1 SMP PVE 5.4.114-1 (Sun, 09 May 2021 17:13:05 +0200)

Does anyone have any tips on how to get going with installing the generic SolarFlare driver? I think I've heard of a compiled Linux driver for all their NICs.

It would be extremely handy to be able to add drivers for the most common types of devices via the GUI that people might add to Proxmox, such as NICs, SAS controllers etc
I am also not used to Linux command line.
I found that the driver indeed was loaded and had claimed the NIC and its two ports.

It turned out that is was just a matter of enabling the ports
sudo ifconfig enp1s0f0np0 up
 
  • Like
Reactions: tetsujin

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!