Temperature Reading on AMD
-
when is 2.3 due out?
-
According to the FreeBSD Release Page, 10.3 was going to be released at the end of March 2016. But only RC3 is available now. Once stable is released, I'd imagine pfSense 2.3 work could really ramp up. Aren't they working on a console redesign/modernization too?
-
According to the FreeBSD Release Page, 10.3 was going to be released at the end of March 2016. But only RC3 is available now. Once stable is released, I'd imagine pfSense 2.3 work could really ramp up. Aren't they working on a console redesign/modernization too?
Just to answer your question, not meaning to steer this topic astray…
pfSense 2.3 is in RC stage right now... it's VERY sharp looking (I've been running the betas for over a month on my primary box)... The FreeBSD version line in the pfSense RC is "FreeBSD 10.3-RELEASE". So it may not be stable yet, but it's very close I'm sure.
-
I just upgraded to pfSense 2.3 tonight (which was easy, flawless, and without issue). However, the temp sensor readout broke again. It looks like the amdtemp fix didn't make it into FreeBSD 10.3. So I recompiled the FreeBSD 10.3 kernel and got a new amdtemp.ko file.
-
Unload the module first: kldunload amdtemp.ko
-
Rename the attached file to amdtemp.ko and copy it to /boot/kernel/amdtemp.ko and /boot/modules/amdtemp.ko
-
Load the module: kldload amdtemp.ko
-
Test sensor from command line: sysctl -a | grep temperature
-
Enjoy the new Temp Sensor readout
-
-
I just upgraded to pfSense 2.3 tonight (which was easy, flawless, and without issue). However, the temp sensor readout broke again. It looks like the amdtemp fix didn't make it into FreeBSD 10.3. So I recompiled the FreeBSD 10.3 kernel and got a new amdtemp.ko file.
-
Unload the module first: kldunload amdtemp.ko
-
Rename the attached file to amdtemp.ko and copy it to /boot/kernel/amdtemp.ko and /boot/modules/amdtemp.ko
-
Load the module: kldload amdtemp.ko
-
Enjoy the new Temp Sensor readout
How is your CPU temp so low ?
I have the fitlet-X and it idles at 54 C. -
-
I purchased the heatsink for the i-A10, and also have it sitting on a "rack" I built with a low RPM, 80mm fan blowing on it ;D
-
LOL nice !
Was kinda hoping you had some BIOS trickery going on to cool it so much.
I already installed the heatsink, it did cool it a bit, but…meh.
54-56 isn't too bad. I'm hoping it doesn't mess with the mSata SSD in there.I guess I could hack a usb powered fan, but that would negate the low-power aspect of this machine.
-
I think it should be good up to 70°C. The fan is connected to a USB port on the wifi access point, so the power consumption doesn't count against the Fitlet :P
-
Any performance figures for this interesting cpu setup? Routing throughput & openvpn?
-
Thanks Fahrenhe1t for the help :). Mine is working great now… It's nice to have temp readings...
-
Any performance figures for this interesting cpu setup? Routing throughput & openvpn?
I have a Netgear Nighthawk router plugged into the Fitlet pfSense box using bridge mode. I use that as my wifi access point.
Between two wired boxes connected locally there, using iPerf3, I get close to theoretical max throughput:
$ iperf3 -c fitlet -f m -n 1024M iPerf Client Connecting to host fitlet, port 5201 [ 5] local 192.168.x.x port 54552 connected to 192.168.x.x port 5201 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 113 MBytes 947 Mbits/sec [ 5] 1.00-2.00 sec 112 MBytes 940 Mbits/sec [ 5] 2.00-3.00 sec 112 MBytes 940 Mbits/sec [ 5] 3.00-4.00 sec 112 MBytes 940 Mbits/sec [ 5] 4.00-5.00 sec 112 MBytes 940 Mbits/sec [ 5] 5.00-6.00 sec 112 MBytes 940 Mbits/sec [ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec [ 5] 7.00-8.00 sec 112 MBytes 940 Mbits/sec [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec [ 5] 9.00-9.13 sec 14.4 MBytes 940 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 5] 0.00-9.13 sec 1.00 GBytes 941 Mbits/sec sender [ 5] 0.00-9.13 sec 1024 MBytes 941 Mbits/sec receiver
I don't have a stellar Internet connection (Comcast, 170Mbps down/12Mbps up) but I'm able to get those speeds through pfSense with xfinity speedtest:
I have OpenVPN setup…I'll try and get on wifi somewhere else and do an iPerf while VPN'd in.
-
That test tells us the switching speed of your night hawk :)
If possible you should setup an additional interface on the firewall on its own subnet, plug a pc into that and measure with another pc on the lan/different subnet.
You could then probably enable an openvpn server on this new interface, connect to that from a pc/openvpn-client then do a speed test to a client on the lan. -
Just sent you a PM.
-
Using AT&T 4G, I VPN'd back home. I have iPerf3 running on another box internally and ran a test. I got 3.61 Mbits/sec.
Connecting to a wifi network with 10mbps up and down, I ran the test again and got 8.47mbps. I'll see if I can find a faster wifi network to test on.
**Update, got 17.9mbps connecting back to VPN on a friend's wifi with 40down/20up.
-
Just upgraded to 2.3.1 and temp widget is broken again… :(
redid your procedure and it's back... :) -
Just upgraded to 2.3.1 and temp widget is broken again… :(
redid your procedure and it's back... :)Thanks for the heads up, mine just did the same thing on 2.3.1 (not to be confused with 2.3_1 :o)
-
haven't done 2.3.1_1 yet…
-
I just did, and had to reload amdtemp.ko. I ended up writing a shell script to copy the files and enable the service.
-
Wish they would include your mod. 2.3.2 time….
-
Wish they would include your mod. 2.3.2 time….
Same. I think FreeBSD has to include it in their release though. Someone else already submitted a bug (https://lists.freebsd.org/pipermail/freebsd-bugs/2016-February/066274.html); not sure how to get FreeBSD to include the fix in a release though…