Thank you, Eloich for the link. I managed to upgrade the BIOS and install pfSense in 620. Logging in every now and then, to check my new setup

The X520 does indeed connect at 1G or 10G only. Can we assume you need 2.5G?

@stephenw10 said in Unable to use BCM57810 properly, need new drivers: But to be clear that's the state it's in after boot? Not after changing the link speed or some other manual change? There's a good chance something is omitted during the boot process that otherwise gets run when the NIC comes up. Hi, Well, I need to enter into ODI cli and configure it manually the speed (I do that on a media converter) via putty (telnet): flash set LAN_SDS_MODE 6 To check: cat /proc/lan_sds/lan_sds_cfg lan_sds_mode = 6(2500BaseX) So, I perform a reboot, test it again, see that is working, only then I put it back on BCM57810. On BCM57810's side, I need to have enabled via UEFI, options 56 and 59 to 6: Under UEFI boot: ediag -b10eng dev 1 (port 1 where the ODI will be used) nvm cfg (enter config) 7 (on menu option, then) 56=6 59=6 save (NVRAM save) exit Options are: 5 for 1Gbps 6 for 2.5Gbps 7 for 10Gbps The only values you only need to setup once are 35 and 36 to 70, because 70 means: 1Gbps, 2.5Gbps and 10Gbps auto mode speeds. I managed to get a more up-to-date firmware for ODI, I'll try with that after, because the version I use, if I let it in 2.5Gbps mode, and my BCM is in 1Gbps mode, the ODI isn't capable to switch back to 1Gbps automatically. So the interface will never "wakes up". Also (as mentioned before), there's a bug on ODI part, in 2.5Gbps mode, the upload speed gets really slow, that I will check (if they fixed) with the last firmware release (june 2025). And then, I will check under pfSense boot if it will "wake up", or not, w/o touching ODI.

@Conjurer No worries, thank you for the reply. I was hoping you did the HWP on modification on your own and could help me achive it for my 13th ge. system since the bios from this forum will brick my machine.

I have a SG210 and I upgraded the cpu to Xeon E3-1225v3, and 16Gb of RAM. Then I install proxmox and allocated 4Gb of RAM to a VM for pfsense, with dedicated network ports and even the serial port to the LCDproc. It is happily running for the last 12 months. I have other stuff running such as Unifi controller, pi-hole and ngnix as LCX and it worked fine. Pfsense is very efficient and it allows the SG/XG to run a lot more stuff. [image: 1755451032670-screenshot-2025-08-17-101540.jpg]

Is it actually losing link? What do you see logged when that happens?

@dugeem It would be interesting to see how much PPPoE performance has improved with the new if_pppoe driver included in 2.8 CE and Plus 25.07. Previously with Netgraph/mpd5 it was limited to ~ 400 Mbps on the APU2.

Given that it's already in Intel's branch I'd expect it relatively soon. It's not like igc for example where there was no driver. There is work on going to include it and it looks like it's imminent: https://reviews.freebsd.org/D50067

Cloning the SSD should work, yes. But I would also just install clean and restore the config.

@stephenw10 No Sir, i have not tested it yet. Just finished building my M570, will test it on the M370 in the near future.

No, just ordered from Amazon.

@johnytb said in Gtek 2.5G (Intel I225 Controller) PCI-E x1 Network Card not recognized by the pfsense: can you explain to me what exactly is this interface that you show here ? That's pfSense most important interface The one that works when even all your NICs don't work. Its called : the console, which could be a serial connection, or, if you have VGA/HDMI build in, it could be that and a (USB) keyboard. Or : If the LAN NIC is working, you 'ssh' into your pfSense using a SSH client like putty or classic 'ssh'. Keep in mind : what happens when you have a disk drive issue ? => pfSense can't boot. => Network interfaces will all by down ... You the the console (serial or VG/HDMI/Keyboard) access. For command line commands I use the ... command line = console (or SSH) access.

For anyone interested in the exciting conclusions... it worked fine in the 16x slot for 2 weeks and is still in there now I put an I340-T4 in the 1x slot at the same time and left that running and that has been perfectly fine as well It seems to be an incompatibility between the 1x slot and the I350 specifically but i'm not sure why. In either case, the issue seems to be resolved It may be something specific to AM5 and the I350 in the 1x, or just the I350 and the 1x alone but if anyone else for some reason tries the same, at least you know what symptoms manifest and what the cause was Thanks again for those that helped and commented

Probably just that then. But you should see the set options and capabilities for those NICs like: [2.8.0-RELEASE][admin@t70.stevew.lan]/root: ifconfig -vm igb0 igb0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 description: WAN options=4e100bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG> capabilities=4f53fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,NETMAP,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG> So there you can see the NIC is both checksum offload and TSO capable but only checksum is enabled.

@stephenw10 I want to use 10GBIT DAC inside my rack and also directly attach to my ISPs Fiber. It'd be the perfect successor for the SG6100 with the SFP+ Addon installed.

@stephenw10 ok i sure will do thanks

So initially it booted and then failed after 48hrs and now doesn't boot at all? Do you have the actual boot logs showing the errors?

@jwt that is great news, thank you!