Can't assign NIC [Aquantia Corp. AQC107]

daplumber

@rico I think I spy a bug in the IPV6 link local address:

inet6 fe80::XXX:XXXX:XXXX:XXXX%aq0 prefixlen 64 scopeid 0x1

I'm pretty sure the "%aq0" shouldn't be part of the address? ;-)

Workaround: Check the "Only request an IPv6 prefix, do not request an IPv6 address" box on the WAN Interface panel. Obviously that means the pfSense box itself no longer has a WAN IPV6 address, but at least now the LAN side IPV6 systems will work.

stephenw10

Compiled with debug options or something similar?

VAMike

@daplumber said in Can't assign NIC [Aquantia Corp. AQC107]:

@rico I think I spy a bug in the IPV6 link local address:
inet6 fe80::XXX:XXXX:XXXX:XXXX%aq0 prefixlen 64 scopeid 0x1
I'm pretty sure the "%aq0" shouldn't be part of the address? ;-)

That's completely normal syntax, indicating the scope of the address. See RFC4007.

daplumber

@vamike my bad. Forehead slap, forgot all about that.

Still no idea why IPv6 dhcp client is not picking up an address with the exact same configuration that worked with igb0...

Rico

As per request FreeBSD 12.3 (pfSense 22.01): if_atlantic0.0.5_freebsd12.3.zip

-Rico

donfox

tried the build on 22.01-RELEASE

[22.01-RELEASE][admin@metalcore.fox]/root: kldstat
Id Refs Address                Size Name
 1   13 0xffffffff80200000  3aefff8 kernel
 2    1 0xffffffff83cf0000    16ba0 if_atlantic.ko
 3    1 0xffffffff83d07000   11d288 if_re.ko
 4    1 0xffffffff860b5000     1000 cpuctl.ko
 5    1 0xffffffff860b6000     2150 acpi_wmi.ko

but there is no new interface :(

stephenw10

What hardware are you trying to use it with?

donfox

@stephenw10

ASUS XG-C100C 10gbit

none5@pci0:1:0:0:       class=0x020000 card=0x88121043 chip=0x94c01d6a rev=0x03 hdr=0x00
    vendor     = 'Aquantia Corp.'
    class      = network
    subclass   = ethernet
    bar   [10] = type Memory, range 64, base 0xa1400000, size 524288, enabled
    bar   [18] = type Memory, range 64, base 0xa14a0000, size 4096, enabled
    bar   [20] = type Memory, range 64, base 0xa1000000, size 4194304, enabled

stephenw10

94c0 is not a listed device ID in the driver:
https://github.com/Aquantia/aqtion-freebsd/blob/master/aq_main.c#L92

Not supported yet by the looks of it.

Steve

yorke

pfSense version 2.6.0

I have a Aquantia (AOM-AQS-107-B0C2-CX) Installed the drivers provided here
Everything seem to be working fine can get ip and connect, the only issue I am having
is that 5GBASE-T, 2.5GBASE-T aren't listed under the interface speed and duplex
and on the dashboard its listed as unknown full duplex

kldstat 19e28 if_atlantic.ko

ifconfig for the interface shows
media: Ethernet auto select (unknown <full-duplex)

tested under windows and 5GBASE-T, 2.5GBASE-T are listed

pciconf -i and shows the error listed below
link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1)

stephenw10

That pciconf error is probably unrelated.

Does it actually link at 2.5G? The other end reports that?

yorke

@stephenw10

yes link at 2.5G

stephenw10

Then it's probably just a driver quirk and it will catch up in newer versions.

Steve

yorke

@stephenw10
There was an issue with intel drivers for FreeBSD
ixl driver shows "unknown" for link rate when using 2.5/5Gbps modes
that was fix in the driver 1.12.24 link below
can i install these drivers and how would i install them thanks.

https://www.intel.com/content/www/us/en/download/18331/25160/intel-network-adapter-driver-for-intel-ethernet-controller-700-series-under-freebsd.html?

https://community.intel.com/t5/Ethernet-Products/Latest-1-12-16-ixl-driver-shows-quot-unknown-quot-for-link-rate/m-p/1270923

stephenw10

Not easily. The available kmod package looks to be at 1.12.2 still.

yorke

@stephenw10

Thank you

Here is hoping that kmod package get to driver 1.12.24

madbrain

I'm a newbie to pfSense & FreeBSD.

I realize this is an old topic, but I am having a hell of a time trying to use my two AQN-107 NICs with pfSense 2.6 .
I downloaded the driver from https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/aquantia-atlantic-kmod-0.0.5_1.pkg .
I installed it with pkg install -f -y .
I loaded it manually with kldload .
I have 2 major problems :

the module doesn't automatically reload upon reboot. How can I force it to do so ?
my clients (off the LAN side, using the pfSense DHCP server) don't have DNS when I use the Aquantia NIC.
If I use other NICs (Realtek 1 Gbps USB, Intel I211 PCIe on the motherboard), I don't have any DNS problem.
This is a really strange one. I have not done any manual configuration for DNS and certainly am not doing anything different when I switch NIC (same IP address for LAN side, same subnet, etc).
Any idea about this one ?
I'd like to make sure I'm using the best possible driver. Is there another build I should be using ? I'm on x64 (AMD Ryzen 2700).

Gertjan

@madbrain said in Can't assign NIC [Aquantia Corp. AQC107]:

the module doesn't automatically reload upon reboot. How can I force it to do

Can answer one : as it has been answered already above :

@rico said in Can't assign NIC [Aquantia Corp. AQC107]:

How the Installation should work (dry run / not tested, I don't own this NIC):
Unzip the file and place if_atlantic.ko into the /boot/kernel/ folder.
Change permissions via console or SSH: chmod 555 /boot/kernel/if_atlantic.ko
Edit /boot/loader.conf.local and add to the end of the file: if_atlantic_load="YES"
Reboot pfSense and see what happens. ;-)

madbrain

@gertjan Thank you ! The file to edit was actually /boot/loader.conf . Not /boot/loader.conf.local .
I copied the driver to /boot/kernel, but not sure if it's really required - it was already copied in /boot/modules , with the correct permission, from the package installer .

In any case, I was able to persist the changes for the WAN & LAN interfaces, and now the second problem (DNS issue) is gone after rebooting.

Gertjan

@madbrain said in Can't assign NIC [Aquantia Corp. AQC107]:

The file to edit was actually /boot/loader.conf . Not /boot/loader.conf.local

Noop.
The file /boot/loader.conf can be rewritten 'at any moment' by pfSense itself, discarding your edits.
Your own additions should be placed in /boot/loader.conf.local, which will not be touched.
If needed, you have to create this file.
This file will also get parsed at kernel boot time.

See, for example Hardware Tuning and Troubleshooting