Messages

Thanks for this @meyergru, the tunables you suggested worked a treat. I did try setting my PL1 and PL2 to 8 and 10 watts which did seem to reduce the temps from 65 to 55, but on the next boot it was back to 65! No idea why.

I've tried taking the Core CPU voltage down by 50 mwatts but it didn't help. Ideally I'd like it in the 50s before I put this into main router duties!

Thanks, that worked!!

Using OPNSense 22.1.8 typing in:

Code Select Expand

sysctl dev.hwpstate_intel.0.epp=100

which results in a nice drop in CPU temperature.

I want this setting to persist at reboot, but regardless of where I put it, it is ignored. I have tried

Code Select Expand

/boot/loader.conf.local
/etc/sysctl.conf
/etc/sysctl.conf.local
/etc/rc.conf.d/10-mysysctl

Interestingly, if I manually do a:

Code Select Expand

service sysctl restart

It immediately picks up the new setting and the temps drop.

So my question is, where can I put the setting so that it will be read at boot time?

Hi guys, I have recently bought one of these and am having CPU temperature issues with OPNSense. In Debian, I get CPU temps of around 55C idle, but in OPNSense, by default they are 85C and above, even with the hardware modifications regarding the head-spreader and thermal pads.

I get temps down to 65C by disabling powerd (apparently this is not needed with FBSD v13 with the Intel Speed Shift driver) and typing in:

Code Select Expand

sysctl dev.hwpstate_intel.0.epp=100
which puts it in maximum efficiency mode (for all cores at once). (At the moment I am struggling to get this setting to be applied at boot because it seems to be being ignored in /etc/systcl.conf!)

If you have this hardware, can you please let me know the output of the following?

Code Select Expand

sysctl dev.cpu.0.freq_levels

Which results, for mine in only showing a single frequency available even though we know it can boost up to 2900MHz:

Code Select Expand

dev.cpu.0.freq_levels: 1996/-1

There is some other weird stuff going on and I'm not sure whether there are conflicts between powerd and hwpstate_intel because if you run powerd -v if produces some strange outputs.

Note to self, I followed theses instructions:
https://www.neelc.org/posts/optimize-freebsd-for-intel-tigerlake/