I have tried that option too. Rebooted after making the change but the pfSense portal still says hardware crypto is inactive. Anyone else running pfSense with hardware crypto enabled? I could temporarily fall back to pfSense 2.6 to try to verify whether this is an artifact of 2.7 dev.
Agreed. This was not what I expected. I need to look into this....
Ah great find. Makes total sense. I will focus on other things now....AES module not loading?
@jimp said in AES module not loading?: We're still working on that one. AES-NI is now in the kernel, and the output of pciconf changed so it isn't detecting loaded devices properly, so that's all a bit in flux. We haven't decided if we're keeping AES-NI ...forum.netgate.com
Yeah, like I said. It is on.
So you bought an N6005 & J6412, or did something get lost in translation?
Anyway, like others, I have been mucking around with different TIM(s) and heatsinks which did kinda start out life as me wondering if the case material was too thick. Anyway, as the good Sir Knight-of-Ni described with his results, in a room at 25*c I managed to do 20 minutes of the N5105 at 4 cores@2600MHz at a top of 65*c, and when 'stress --cpu 4' was stopped it dropped back quickly to 42*c and then further after that which I was fairly happy with.
To compare, here is a screenshot of a Zotac mini pc w/ Intel N3450 running pfSense 2.6:
it's a common pfsense/freebsd problem, it won't show the burst frequency, instead it shows 2001 (and not 2000).. the 1 at the end means whatever burst freq it can go.
same here, the 1 at the end of Max means that it burst to whatever the n3450 goes (2.2Ghz).
Which Noctua model exactly?!? I'm a bit overwhelmed with the selection of models . . . which one can do USB?!?
I'm actually using a non noctua 140mm fan that runs off a regular usb port
The bios it shipped with:
If you want to watch the frequency just cat out /proc/cpuinfo like you normally would. Your combination would then end up something like this with 1 second intervals.
watch -n.1 "grep \"^[c]pu MHz\" /proc/cpuinfo"FreeBSD does not have /proc filesystem, nor does the watch command work quite the same as on Linux. Looks like calling sysctl dev.cpu.0.freq has the desired information. One could sed or grep for just the raw value, then perhaps use gnu-watch to run that on an interval.... or just stick it in a while loop in shell script. Maybe there is a FreeBSD expert who knows exactly how to do this...