NIC getting No Carrier despite being plugged in

[cyberpower678]

I have the latest 0.0.5 driver installed and the NIC showed up as aq0, but it would not become active. Instead it only displayed "No carrier". I had to switch back to the other NIC after extensive troubleshooting.

[Eypsilon312]

yea I'm with the same issues here,

aq0 (UP)
but no carrier, even if the network cable is connected and the link led is blinking.
I can add a static ip and ping the network card itself given ip, but not any other machine connected to this port in the same subnet.

[cyberpower678]

I have not been able to get the driver to function properly, so I threw the aquantia controller into a Windows machine and replaced my FreeBSD NIC with an Intel 10G NIC. Works flawlessly.

[Eypsilon312]

oh so you went for a hyper-v architecture?

[officialarindam]

I have the latest 0.0.5 driver installed and the NIC showed up as aq0, but it would not become active. Instead it only displayed "No carrier". I had to switch back to the other NIC after extensive troubleshooting.

can you enable "cpu pcie lanes unlock" settings in bios and check again?

[dnotq]

I'm having the same problem trying to get FreeBSD 14.0 working with the AQC107. The computer is a Lenovo P620 ThinkStation, AMD Chipset, AMD ThreadRipper Pro 3945WX, the NIC is on the motherboard and using lspci on Linux shows this:

01:00.0 Ethernet controller: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02)

The NIC works on Linux (kubuntu) and Win10. I checked the BIOS settings and I don't see anything related to unlocking PCIe lanes. I have included screenshots of the PCIe and Network Interface related settings.

I'm running FreeBSD on raw hardware, i.e. not in a VM or anything like that.