Here’s the revised request formatted for a GitHub issue: Description: This is a feature request to add driver support for the Aquantia AQC113 and AQC113C Ethernet controllers in FreeBSD. These devi...
Here’s the revised request formatted for a GitHub issue:
This is a feature request to add driver support for the Aquantia AQC113 and AQC113C Ethernet controllers in FreeBSD. These devices are widely used in modern high-performance networking scenarios, and adding support would enhance FreeBSD's hardware compatibility for servers, NAS systems, and workstations.
no driver attached when checked via pciconf or dmesg.aquantia-atlantic-kmod driver does not currently support the AQC113 family.Example pciconf -lv output:
none3@pci0:7:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x1d6a device=0x14c0 subvendor=0x1d6a subdevice=0x0001
vendor = 'Aquantia Corp.'
device = 'AQC113C NBase-T/IEEE 802.3an Ethernet Controller [Marvell Scalable mGig]'
class = network
subclass = ethernet
The AQC113 and AQC113C devices should be recognized and functional under FreeBSD, with support for the advanced features these controllers offer, such as NBase-T and 10GBase-T networking.
Device Details:
0x04c00x14c0Relevant Resources:
aq driver supports AQC113 and AQC113C (source code).atlantic driver includes support for these devices.Use Cases:
FreeBSD’s Current Limitations:
aquantia-atlantic-kmod driver supports the AQC107 family but not the AQC113.Please consider adding support for the AQC113 family to the aquantia-atlantic-kmod driver or create a new driver for these devices. If testing or hardware access is required, I am happy to assist in debugging and validation.
Logs & System Details:
pciconf -lv: See above example.dmesg | grep -i ethernet: Reports devices as detected but unsupported.Thank you for your time and consideration. Adding support for the AQC113 family would be a significant enhancement to FreeBSD’s hardware compatibility.
Useful for anyone using FreeBSD with one of the 10GbE chipsets, as commonly found in minipcs these days.
This driver seems to be working well for people. :)
Just curious, most people that use FreeBSD are either experts or hardcode enthusiasts. It used to include FreeNAS/TrueNAS users, but they migrated to Linux as the product moved to Linux. That means the users of FreeBSD are not the ones I would expect to purchase and use these controllers, but other options like 10 Gbps with SFP+ (AOC or Fiber Optic) or even 25Gbps and higher. Is there a significant demand for this driver? A 10 Gbps SFP+ card is cheaper and more flexible, I have a few in several computers and even a few laying around as spares, they are also more compatible with all sorts of OS-es and usually more capable.
Quite a lot of popular, widely deployed firewalls are based upon FreeBSD.
And for them it's a problem that miniPCs well suited for firewall use have been been coming out (for a while now) using this chipset. Which FreeBSD didn't support.
So for those projects, this may provide an avenue of hope or future potential. ;)
I use cards like those described by you (with DAC cables) for connections between FreeBSD servers (actually between servers, regardless if they run FreeBSD or Linux).
However, I also need to connect some desktop/laptop PCs to a FreeBSD server, either for management or for transferring backups, where a cheaper Aquantia NIC is perfectly adequate, especially when the PC has only a 2.5 Gb/s or 5 Gb/s Ethernet interface.
In the past, I had to buy an Intel server NIC for one of my FreeBSD servers, despite the fact that I had a spare Aquantia NIC that would have worked fine, due to this driver problem.
I was not happy about it, so I am glad to hear now that a working driver is available.
Shouldn't AI be smart enough now to translate drivers from Linux to FreeBSD? It's mostly plumbing after all.
No, AI is anything but "smart". And my understanding is that the network stack is so well done in FreeBSD that it is a shame to touch it with AI code.
Well it doesn't cost much to try it, and you can always replace it by a handcrafted version later.
It cost me my weekly Claude usage! I was on Claude timeout for like 4 days.
I had one of these interfaces and the driver kept freezing in Linux. Me ‘n Claude were not able to figure out why. Super sad.