It's common to have a few errors especially if it was recently disconnected. That looks high though. Check the cable.

That's not going to affect anything at 1G rates.

What is that port linked at on the modem? It's a 10Gbase-T port?

As I explained I would expect to find no way to set that adapter to 1G. It will only link correctly at 10G. That fact it works at all though seems to imply it probably is linked at 10G....

@uplink

How I’ve configured it works for my case and card and is easily tested as with it enabled I have 90% packet loss and with it disabled it works and zero loss

Thanks for all the help and to @stephenw10

That package includes a kernel module which means it has to be build against the pfSense kernel specifically. We don;t build that pkg so you would likely need to build it yourself which is non-trivial!

You might add a comment here: https://redmine.pfsense.org/issues/12300

@Iron_Man

Did this... and it works nicely.

Last year I got a used Mac mini 2014 with 8GB RAM for a great price. Installed two left over Thunderbolt Ethernet adaptors and ProxMox virtualisation software.
This runs pfSense, next to a few small VM for automation and other stuff. I even have a VM with macOS Monterey for occiasional testing purposes on it and this all works quite well.

For pfSense I assigned 2GB memory and 200GB virtual storage. And I added a few tweaks for better performance for multi core CPU's
https://docs.netgate.com/pfsense/en/latest/hardware/tune.html#pppoe-with-multi-queue-nics

pfSense works fast. Great throughput.

@Epimpin So, back to initial questions, which PCIe slot would be better in this certain case ?

Your opinion…

Excellent, thanks!

thanks all for trying to help! I'm giving up and looking for a new box.

You can't open a support ticket without a subscription, that's true.

@stephenw10 Well, 2.7.2 and 23.09.1 have the same kernel version, so the both versions should have the same set of compiled drivers. BTW, 2.6 CE also has ice_ddp on ISO, but not after installation ;)

Ah, nice! I run that at 80 on an i5-6400T for reference. Seems about optimal for my use but that's just a test box, it's not always on.

Good question, I've never seen one to find out. I imagine it would have to be in the QAT driver or possibly the crypto framework.

Thanks for all

I found a link on YouTube:
https://www.youtube.com/watch?v=q2mI0myAEXA
I will try booting from the Linux kernel.
If this is done perfectly, we will discuss the rest of the hardware.
It will be a fun experience

@stephenw10 said in Intel x550-t2 can not disable flow control properly:

hw.ix.flow_control=0

Thank you, this one worked 👍

@glippi Hello, after swapping out the intel 82599 10 gigabit dual port and moving this to the onboard ethernet with PCI passthrough to the VM, it seems everything is stable now.
the AHCI errors, however consistent with disks (as far as I can see), it seems that in this case it was with the ethernet controller.
My guess it was just a faulty card as since moving over I have had no issues now for 18 days.

If you would like any logs, please let me know which one you would like to see for further investigation on this.

@stephenw10 Thank you very much for the detailed response.

@stephenw10 said in NIC issues and advise:

It could be in a shellcmd:
https://docs.netgate.com/pfsense/en/latest/development/boot-commands.html?highlight=shellcmd#shellcmd-option

thanks i managed to find it and remove it.

issue has not happened in a week or so now.

Next step is to figure out the realtek nic issue.

The igc driver/hardware can only be autoselect. For some reason setting it to that specifically can cause it to go into a loop of some sort as your saw.

You could try setting it to 2.5G which will prevent it linking at 1G. It still negotiates that though so if the modem for some reason stops allowing 2.5G it will just fail to link.

@maxster This is the one that I used.

https://store.ui.com/us/en/pro/collections/unifi-accessory-tech-cable-sfp/products/10gbps-direct-attach-cable?variant=UACC-DAC-SFP10-0.5M

@MikeSpears @stephenw10

I confirmed I can issue commands directly from a shell to communicate with the A125 display with pfSense temporarity installed on an external USB SSD on my QNAP TS-653A.

Same shell scripts I created for TrueNAS CORE: https://github.com/elvisimprsntr/QnapFreeLCD

#!/bin/sh NAME="`hostname -s`" stty -f /dev/cuau1.lock 1200 stty -f /dev/cuau1.init 1200 stty -f /dev/cuau1 1200 # clear display printf '\115\015' > /dev/cuau1 sleep 1 # turn on display printf '\115\136\001' > /dev/cuau1 sleep 1 # print hostname on line 1 printf '\115\014\000 '$NAME > /dev/cuau1 sleep 1 # print message on line 2 printf '\115\014\001 System Booting' > /dev/cuau1

It seems there might be a bug in the icp_a106 driver

Mar 2 13:13:11 LCDd 20455 Could not open driver module /usr/local/lib/lcdproc/icp_a106.so: /usr/local/lib/lcdproc/icp_a106.so: Undefined symbol "ftime"

There was a commit in 2019 that appears to have addressed the issue, but was never merged.

https://github.com/lcdproc/lcdproc/commit/781b3113a592d75a29aa5024a94c2fd6b4592f87

Mar 2 13:13:11 LCDd 20298 LCDd version 0.5.9 starting Mar 2 13:13:11 LCDd 20298 Using Configuration File: /usr/local/etc/LCDd.conf Mar 2 13:13:11 LCDd 20455 Listening for queries on 127.0.0.1:13666 Mar 2 13:13:11 LCDd 20455 Could not open driver module /usr/local/lib/lcdproc/icp_a106.so: /usr/local/lib/lcdproc/icp_a106.so: Undefined symbol "ftime" Mar 2 13:13:11 LCDd 20455 Driver [icp_a106] binding failed Mar 2 13:13:11 LCDd 20455 Could not load driver icp_a106 Mar 2 13:13:11 LCDd 20455 There is no output driver Mar 2 13:13:11 LCDd 20455 Critical error while initializing, abort. Mar 2 13:13:12 php 20660 lcdproc: Start client procedure. Error counter: (0) Mar 2 13:13:13 php 20660 lcdproc: Failed to connect to LCDd process Connection refused (61) Mar 2 13:13:13 php 20660 lcdproc: Start client procedure. Error counter: (1) Mar 2 13:13:14 php 20660 lcdproc: Failed to connect to LCDd process Connection refused (61) Mar 2 13:13:14 php 20660 lcdproc: Start client procedure. Error counter: (2) Mar 2 13:13:15 php 20660 lcdproc: Failed to connect to LCDd process Connection refused (61) Mar 2 13:13:15 php 20660 lcdproc: Start client procedure. Error counter: (3) Mar 2 13:13:16 php 20660 lcdproc: Failed to connect to LCDd process Connection refused (61) Mar 2 13:13:16 php 20660 lcdproc: Too many errors, stopping client.

UPDATE

Submitted issue 211