SolarFlare SFN5122/6122 incompatible with Epyc 3000 M11SDV-4C-LN4F ?

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

Pakna

Member
May 7, 2019
50
3
8
I've recently been experimenting with swapping out the Intel X520-DA2 with SolarFlare SFN5122 and I found out that for some reason the SolarFlare NIC seems to get stuck on M11SDV-4C-LN4F board during POST (more precisely, the POST hangs for a very long time at BIOS enumeration 94 step).

The only suggestion I've found was to take the CMOS battery out and reset the BIOS by shorting out a couple of leads on the MBO. I did that, it did reset the BIOS settings but that also didn't seem to help. The BIOS is fairly recent (vintage 2021) but not absolutely most recent one. There is also a WD SN550 NVMe drive plugged in together with one SATA SSD.

The reason I had tried to swap these out is that I'd like to remove the ISP router + CAT6 completely and just plug in the ISP's SFP ONT (which is a Nokia brand) but alas X520-DA2 works only with Intel-branded transcievers. That would cut out the unnecessary middle man, reduce the power consumption a bit and yield true FTTR (fibre-to-the-router) instead of FTTH (fibre-to-the-home). I recall from my past experiments that somehow I've been able to get the board to boot with SF NIC and that plugging it in directly worked well with pfSense.

Moving forward, the available options/questions I see are:
  • has anyone gotten this NIC to work with Supermicro M11SDV?
    • perhaps there is a BIOS setting/combination that results in POST getting stuck at BIOS enumeration step?
  • is there another NIC with SFP+ that would be tolerant of transciever branding and that is know to work with M11SDV?
    • I am fairly sure I can't buy another SFP ONT, have fs.com re-code as Intel and call it a day. I believe ISP's ONTs are coded with custom firmware specific to an ISP and the firmware signature has to match the expected one on the other end
  • upgrade BIOS blindly to latest and hope for the best
    • since this machine is the sole firewall for the house, that would be my last option
    • I am also skeptical this would work; the NICs are 10 year-old obsolete hardware, chance of that getting a fix in an Epyc 3000? Looks like slim at best
Any further ideas to explore or general thoughts are more than welcome!
 

zac1

Well-Known Member
Oct 1, 2022
432
358
63
Sanity check: are you certain the NIC is not defective?
 

Pakna

Member
May 7, 2019
50
3
8
Sanity check: are you certain the NIC is not defective?
Good call. I believe so - I've tried two different NICs that are working just fine on Supermicro X10CRH board. An SFN5122 and an SF6122. I've tried it with a third NIC that works right now in that same board (a SFN5122). It just halts on POST at BIOS enumeration. I have a a couple of HP NICs (560FLR-SFP+ and 530FLR-SFP+) but these are both Intel chipsets. Come to think of it, they do work with third-party transcievers, perhaps I could try these...

If you have a linux box available, there's another option: https://forums.servethehome.com/ind...-eeprom-to-unlock-all-sfp-transceivers.24634/

Some people have also reported that the X520-DA cards aren't always locked in the first place.
Mine seems to be - at least that is what I have observed when plugging in the SFP ONT into it; pfSense acts as if the port is unused. Is there a way to check whether the lock exists? Or a way to remove the lock if it's there? Perhaps a firmware upgrade? EDIT: Thank you, for some reason I missed the posted URL. I'll study this and consider it.
 
Last edited:

RolloZ170

Well-Known Member
Apr 24, 2016
5,426
1,640
113
Will report tomorrow morning.
I believe it was set to Legacy as pfSense boots on this machine with non-UEFI bootloader (can't remember anymore why I did that).
pfSense 2.4 is the first with UEFI support.
try disabling legacy OpROM.