I just checked with my FreeNAS 11.3-U3.1 and, yes - no if_mxge.ko there.
So your best approach is probably a bug ticket in ixSystems' JIRA. The driver is part of FreeBSD in 11.3 and 12.1 so there is no reason why the module should not be in FreeNAS.
For a short term fix: install a stock FreeBSD 11.3 somewhere and copy all the modules over.
root@freenas-pmh[~]# uname -a FreeBSD freenas-pmh.local 11.3-RELEASE-p9 FreeBSD 11.3-RELEASE-p9 #0 r325575+c153e5c9a38(HEAD): Wed May 20 16:09:43 EDT 2020 root@mp20.tn.ixsystems.com:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64
...disk1.iso
IS the code you sent is it to get directly into freenas? also i am unable to connect to internet not sure why - I am saying this because i tried to change the NTP server details from 0.freebsd.pool.ntp.org to 0.uk.pool.ntp.org.. bt says "Server could not be reached. Check "Force" to continue regardless "You need the FreeBSD matching your FreeNAS kernel version.
Code:root@freenas-pmh[~]# uname -a FreeBSD freenas-pmh.local 11.3-RELEASE-p9 FreeBSD 11.3-RELEASE-p9 #0 r325575+c153e5c9a38(HEAD): Wed May 20 16:09:43 EDT 2020 root@mp20.tn.ixsystems.com:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64
So in my case that would be FreeBSD 11.3 ...
Any yes, you can use that image to install if the target VM or machine is connected to the Internet. If it is offline, you would need...disk1.iso
uname -a<ENTER>
. That will tell you the FreeBSD version as shown above. The second line is the output of that command on my system.oooh sorry ..You need a prompt/shell on your FreeNAS and then typeuname -a<ENTER>
. That will tell you the FreeBSD version as shown above. The second line is the output of that command on my system.
/boot/kernel
/boot/kernelPlease advise where i need to copy the FreeBSD 11.3 modules to ?
kldload if_mxge
Patrick M. Hausenkldload if_mxge
And who told you to copy all of the FreeBSD modules? You should have course only have added the missing mxge ones. You will probably have to reinstall your FreeNAS, but first let's get this interface detected.
ssh
and scp
to copy this stuff around. Again I thought this was obvious, because someone messing with kernel modules will have a good understanding of Unix already? No? Sorry, not meant as an insult, I really assumed you were familiar with all this.ssh
is the command line tool you use to login from one Unix system to another one, scp
copies files via the same transport mechanism. Login to your VM (I assume your FreeBSD is a VM), then e.g.cd /boot/kernel; scp if_mxge.ko <ip of your freenas>:/boot/kernel
kldload
the module, If that works, repeat for all the other ones.freebsd-update
.Usessh
andscp
to copy this stuff around. Again I thought this was obvious, because someone messing with kernel modules will have a good understanding of Unix already? No? Sorry, not meant as an insult, I really assumed you were familiar with all this.
So,ssh
is the command line tool you use to login from one Unix system to another one,scp
copies files via the same transport mechanism. Login to your VM (I assume your FreeBSD is a VM), then e.g.
cd /boot/kernel; scp if_mxge.ko <IP of your freenas>:/boot/kernel
Read up on these tools or we will be getting nowhere. Then on the FreeNAS try tokldload
the module, If that works, repeat for all the other ones.
If it still says "wrong kernel" your FreeBSD version does not match the FreeBSD in your FreeNAS. You might have to upgrade your FreeBSD to 11.3-p9 first. This can be done withfreebsd-update
.
You want to fiddle in an unsupported way with the intestines of a Unix system? Congrats, you are Unix system administrator now. Now hone those skills ...
Kind regards,
Patrick
P.S. It might be easier to get a supported 10GE card ...