NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
[SOLVED] 516 gets "CPU temp exceeded safety threshold"
I've seen temps hit 86C+ with two PLEX (v0.9.9.0) transcodes running at once. I saw it peak up near 72C with just a single transcode, where CPU usage was reported by top at up to 250% (for the process).
I'm also inquiring on the PLEX end of things, since this behavior wasn't observed (or as significant) under earlier PLEX releases... BUT... despite this temperate spike and the warning, the system fan on the 516 stubbornly says at ~800RPM! WTH? I'm wondering if it was forced at some point and isn't auto-adjusting, which in these cases could lead to serious problems.
Any thoughts, similar experiences, or suggestions? Thanks!
I'm also inquiring on the PLEX end of things, since this behavior wasn't observed (or as significant) under earlier PLEX releases... BUT... despite this temperate spike and the warning, the system fan on the 516 stubbornly says at ~800RPM! WTH? I'm wondering if it was forced at some point and isn't auto-adjusting, which in these cases could lead to serious problems.
Any thoughts, similar experiences, or suggestions? Thanks!
19 Replies
Replies have been turned off for this discussion
- I was looking around and caught up on recent threads. Already have it downloaded but will wait to apply until I get home. Wanted to give PLEX a chance to finish pre-transcoding about 60 episodes for syncing later. :)
After tweaking the pwm1 way up, temps are holding between 58-65C with fan RPM 1600-1900 (loud, but effective). CPU usage has been holding up between 320-360% for the transcode process. :) - I'm thinking now the change might be just for the fan speed being below the threshold. Still if you can try it to make sure that would be good.
- Hmm.. we'll see. Fan was still at ~800 at reboot. Grew only to 815 as CPU got to 60. I set pwm1 to 120 and fan it 1500, and has stayed there as I'm watching something using live transcode. I guess I'll keep an eye on it... can't say I have trust just yet.
- I think the fix in 6.1.9 RCs was just for the Pro 6 fan being too slow not for the 516.
- Well, I think the 516 needs a little of this love, too. Why would there be a fix in 6.1.9 for Pro6? Is that officially supported now?? :)
After tweaking up PWM1 (before my trip, so my PLEX sync didn't melt the CPU), I woke from my post-return-flight nap to a series of CPU temperature warnings. PLEX was batch transcoding some new programs that came in, for later syncing. So even though I tweaked PWM1 way up, something else tweaks it down... over which I guess we have no manual control.
I am running 6.1.9 RC... perhaps I should cross-link to beta forum? - We still support running 4.2.x on the Pro 6.
The changes to better support older models in the software are done as time permits. The focus is still on the new models which the OS was designed for. mdgm wrote: We still support running 4.2.x on the Pro 6.
The changes to better support older models in the software are done as time permits. The focus is still on the new models which the OS was designed for.
I'll have to re-check then. The only thread I ever saw about doing this very clearly indicated "UNSUPPORTED" in the heading. I guess by supported I mean "a user could call Netgear and expect to get phone support for their configuration."- Still not supported on the Pro 6, by that definition. There is some unofficial support for the legacy hardware in the OS.
- Tested again in 6.1.9 RC10 and it works! Seems to hold temp around 78-80C during very high CPU, but the fan gets near 1300 RPM. Which I found really wasn't that loud in a quiet room. Once CPU activity and temp drops, so does fan speed. Big improvement thanks!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
