Netgate 1537 "dev.pchtherm.0.temperature" high
-
Good morning!
First post here, just grabbed my new 1735 from Newegg and as I've been getting this setup I happened to notice that the dev.pchtherm.0.temperature pid reads158 - 161 °F where the CPU temps read barely 114 °F. Not sure if maybe pchtherm isn't a valid sensor on this model or if I have an issue. Any input of this would be greatly appreciated, even if it's a link to another thread that I missed (spent about 5 min trying to search at 1am so I may have missed something)
Appreciate everyone's time,
~Joe -
@jbowm21 Just realized after posting, that I butchered the model in my tiredness! Anywho, meant 1537. Thanks again!
-
Fixed the model name.
This is a known issue in the 1537 and 1541 among others. The value from the PCH thermal sensor wasn't read at all before 23.01. Now that a driver exists it is but for some reason shown incorrect values on some systems.
See: https://redmine.pfsense.org/issues/14467Steve
-
@stephenw10 Perfect, thanks for pointing me in the right direction. Appreciate your time, just glad there isn't a physical issue with the router. I wasn't even aware that Redmine was a thing, assuming based on the thread it's the bug tracker site for pfsense which is good to know about. I'll search there next time, again much appreciated!
-
@stephenw10 I'm experiencing the same issue with my new 1537. Do all 1537's experience this or only a select number? Does something like this warrant a return? The rest of my CPUs register between 137 and 139F, but dev.pchtherm.0.temperature is around 179F.
-
@johnclaus No reason to return the equipment sir, I'm still using the same 1537 without any issues. I'm sure they'll fix the reading in a future update. For now just ignore the inaccurate reading, curious to if someone that knows more has an update though? Obviously low priority regardless.
Enjoy your new router / firewall, it's a beast.
Much appreciated,
Joe -
Yup all 1537s return an invalid PCH temp value as far as I know. I don't know if it's the driver or the device itself that's incorrect. However it's not an indication of a fault just an incompatibility with that particular device.
