Can't assign NIC [Aquantia Corp. AQC107]
-
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
-
94c0 is not a listed device ID in the driver:
https://github.com/Aquantia/aqtion-freebsd/blob/master/aq_main.c#L92Not supported yet by the looks of it.
Steve
-
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 duplexkldstat 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) -
That pciconf error is probably unrelated.
Does it actually link at 2.5G? The other end reports that?
-
yes link at 2.5G
-
Then it's probably just a driver quirk and it will catch up in newer versions.
Steve
-
@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
-
Not easily. The available kmod package looks to be at 1.12.2 still.
-
-
-
-
-
-
-
-
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).
-
@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. ;-) -
@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.
-
@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
-
Not sure why you wouldn't see DNS there though. Is the service starting correctly?
-
@gertjan said in Can't assign NIC [Aquantia Corp. AQC107]:
@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
Thanks. I stand corrected. I didn't know I was supposed to create the .local file. I just did so and moved the if_atlantic_load declaration to it.
What about the directory for the module ? Is it really supposed to be /boot/kernel ? The package installed it in /boot/modules originally. I made a copy in /boot/kernel, but wondering if it really needs to be in two places.
-
@stephenw10 said in Can't assign NIC [Aquantia Corp. AQC107]:
Not sure why you wouldn't see DNS there though. Is the service starting correctly?
I believe the DNS service was starting properly, yes. In fact, at the console in the shell, DNS worked fine - I could ping internet hosts.
But my client box, connected to the LAN NIC, didn't have DNS.
This happened when was doing a manual kldload on the Aquantia module.Once I made it persistent and rebooted, the problem with DNS on the client went away, somehow. I don't see a good explanation for this, but it's resolved now.
-
Ah, OK. That would almost certainly have been because the interface was down or didn't exist when Unbound started.
-
@stephenw10 said in Can't assign NIC [Aquantia Corp. AQC107]:
Ah, OK. That would almost certainly have been because the interface was down or didn't exist when Unbound started.
That makes sense. Indeed the interface wouldn't have existed at boot time. But after the kldload, I had gone through the menu to reconfigure the interfaces and IP addresses, and still DNS didn't work. Anyway, it's taken care of now, thank you !
-
-
-
-
-
This was a deep rabbit hole but eventually rewarding!
Attaching the Aquantia driver for latest pfSense (2.7.2) – not that it's a good idea to download random binaries from strangers. ;)
Steps to reproduce successful compilation of
net/aquantia-atlantic-kmod
for pfSense.- Install Poudriere
- git clone https://github.com/freebsd/poudriere.git
- cd poudriere
- ./configure
- make
- make install
- cp /usr/local/etc/poudriere.conf.sample /usr/local/etc/poudriere.conf (check & update)
- Download & compile FreeBSD source code at correct version
- pkg install git
- rm -rf /usr/src
- git clone -o freebsd https://git.FreeBSD.org/src.git /usr/src
- cd /usr/src
- git checkout 0c783a37d5d5
- make buildworld -j number of CPU cores
- Create jail for compilation
- poudriere jail -c -j pf272amd64 -a amd64 -m src=/usr/src
- Compile
- cd
- cat "net/aquantia-atlantic-kmod" > pkglist.txt
- poudriere bulk -f pkglist.txt -j pf272amd64
- Profit
- find your binary at /usr/local/poudriere/data/packages/pf272amd64-default/All/aquantia-atlantic-kmod-0.0.5_3.pkg
-
Oh yeah, also wanted to thank to @Rico who gave me the idea that this might be possible and actually dig it. So happy, that I can now use the sweet 10g NIC, and learned a bunch along the way!