In the GUI, under System | Tunables
Normally you should place Kernel modules (drivers) in /boot/kernel .
You also should pay attention to the capitalization... I see you used if_atlantic_Load as the variable... that's not at all the same as if_atlantic_load.
I expect not, but feel free to investigate. Driver support tends to arrive rather slowly and only for "mainstream enterprise hardware". FreeBSD doesn't get a lot of love from hardware vendors and is often an afterthought if drivers are supplied at all. Those who treat it seriously get that respect returned in terms of driver inclusion, which makes its way to FreeNAS in reasonable time, but for less integrated vendors, it can take ages or not happen at all.So this driver still is not natively supported by FreeNAS?
I've been using Linux for years and this is my first experience with FreeBSD. It seems like the driver has been out there for a while based on the links that contributors have provided in this and other threads. I'm legitimately surprised that it hasn't been added to the base OS yet.I expect not, but feel free to investigate. Driver support tends to arrive rather slowly and only for "mainstream enterprise hardware". FreeBSD doesn't get a lot of love from hardware vendors and is often and afterthought if drivers are supplied at all. Those who treat it seriously get that respect returned in terms of driver inclusion, which makes its way to FreeNAS in reasonable time, but for less integrated vendors, it can take ages or not happen at all.
Installing port is as easy as typing pkg install aquantia-atlantic-kmod-0.0.5 and adding if_atlantic_load="YES" to /boot/loader.conf.
Tried this way and Luckas attached KO file with success on FreeNAS 11.2 and 11.3. The official package is compatible with FreeBSD 11, 12, 13.
# pkg search aquantia
aquantia-atlantic-kmod-0.0.5 Aquantia AQtion (Atlantic) Network Driver (Development Preview)
# pkg install aquantia-atlantic-kmod-0.0.5
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 2 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
aquantia-atlantic-kmod: 0.0.5 [FreeBSD]
Installed packages to be REINSTALLED:
pkg-1.12.0 [FreeBSD] (options changed)
Number of packages to be installed: 1
Number of packages to be reinstalled: 1
The operation will free 25 MiB.
3 MiB to be downloaded.
Proceed with this action? [y/N]: y
[1/2] Fetching pkg-1.12.0.txz: 100% 3 MiB 1.8MB/s 00:02
[2/2] Fetching aquantia-atlantic-kmod-0.0.5.txz: 100% 22 KiB 22.9kB/s 00:01
Checking integrity... done (0 conflicting)
[1/2] Reinstalling pkg-1.12.0...
[1/2] Extracting pkg-1.12.0: 100%
[2/2] Installing aquantia-atlantic-kmod-0.0.5...
[2/2] Extracting aquantia-atlantic-kmod-0.0.5: 100%
# kldload /boot/modules/if_atlantic.ko
# vi /boot/loader.conf
Issues:
- both ways (boot conf or your own pre-boot script to kldload) are wiped out after OS update (ok for me as i use 10gbit just between NAS and PC)
- performance is limited by
1) the hardware itself (max 3.5gbit for anyone i got report from) -- using 5gbit QNAP USB3 device at the moment and all tests are single user sequential
2) the driver or operating system, lacks more in single thread speed than other OS with the same hardware and "same" setup:
iperf3 to NAS 1 / 2 / 4 threads : 2.2 2.8 3.4
iperf3 -R 1 / 2 / 4 threads : 2.2 2.8 3.45
3) the freebsd services
samba big files read 390MBs vs 400MBs on debian ZFS (still not bad sequential performance given iperf above and lack of multithreads like in debian)
samba big files write 370MBs vs 400MBs on debian ZFS (again, there are some hiccups, it's never a flat line, without chopiness it'd be pure 3.5gbs)
above could be attributed to driver perhaps, but this sucks:
samba medium files up to 50% slower
samba tiny files up to 100% slower (no matter what, sync=disabled, encryption off etc)
on top of that, NFS is ~100% slower than freebsd samba, ironically, while non-kernel debian NFS was ~100% faster than samba, in other words, 4x faster than freenas NFS. i don't use it as i hate Win10Pro NFS client implementation.
Overall CPU usage is very nice on X3421 Gen10, hardly 50% used with encryption on at around laughable 20 watts.
ARC utilization doesn't really help with reads or writes. Did hundreds of tests, and i do read tests from cache (proven by monitoring) and from disk if needed. The small to medium files (MP3s and JPGs) are a big performance bottleneck, this is i think a limitation of samba. Debian pipelines single user somehow, freebsd only ZFS. No samba tweaks help. Writes rely on drive activity and i'd need 10gbit NIC to check if there's any boost as right now NIC speed <= drive speed. Using all types of drives - new NVME, SSD, and RAIDZ drives. Even direct benchmarks are lower (-50% on NVME dd vs debian). Freebsd needs to catch up to 10gbit era, soon people will upgrade to thunderbolt speeds and then higher. ideally 10gbit will be soon obsoleted like H264 and SATA, so we can build proper NVME-like RAIDs (hopefully non PCI in future), have to count on each client having an NVME drive with 3GBs speed...
I'm guessing they messed with the kernel version because I'm getting this message:I completely forgot about this issue before I upgraded to TrueNAS and I am unable to get the NIC working. Does anyone know if there's a workaround for this? It looks like they are further locking down the CLI.
KLD if_atlantic.ko: depends on kernel - not available or version mismatch
linker_load_file: usr/if_atlantic.ko - unsupported file type
I can definitely tell that you are an old school IT guy because you have absolutely no social skills or empathy whatsoever. Just because you think that the hardware "crappy" doesn't make it gospel. Typically, in my experience, developers don't make random drivers obsolete in new versions. I can't count the number of posts where people like you are condemning others for using the CLI. Apparently, you're not supposed to use it.They are in no way locking down the CLI.
Neither are they "messing" with the kernel version. TrueNAS simply runs on top of FreeBSD 12.2 at the moment while FreeNAS was 11.3 lately. Of course there is a new kernel version, there wouldn't be all the huge improvements without it.
So to fix your system get FreeBSD 12.2 compatible drivers from your vendor. If there aren't any, don't buy crappy hardware that is not supported by the OS.
Kind regards,
Patrick