That's pretty hilarious. Until recently I didn't think of the CPU fan as an auditory cue for how hard your system is working. But now I can remember times that excessive fan noise has prompted me to investigate the cause of excessive usage.
I had a habit of touching the strip of metal above the keys on my old macbook air, since that heats up before the fan becomes audible.
The sensible approach, of course, is to add a load monitor to the menu bar; now with my new m1 macbook, I can simply make the appropriate noises myself, as necessary. This is the UNIX way.
"MenuBar Stats" has a versatile collection of widgets to add to the menu bar. I'd prefer something open source though, if anyone has recommendations, please share.
Once you're running a tool like that, it is interesting to see the efficiency cores often saturated and the performance cores usually sleeping.
You can do this with xbar [0] (which is also just a super cool app). Looks like someone even made one specifically for checking the CPU throttling speed [1]
Yes, I miss that calming crackle telling me that my PC didn't lock up and it's just chugging along. And the floppy boot sound. Objectively worse but still nostalgic.
Oh, yes. This has been an ongoing problem with "sleep mode", which users think means "off", but isn't really. Some Windows docs for hardware makers indicated that "sleep mode" should stop the fans, to maintain the illusion that the machine is "off". Some machines do that, and some stick to temperature-based fan control, so the fans continue to turn if the machine is warm. Some users then complain that sleep mode doesn't work because the fans are still turning.
Wait, why would the device get warm during suspend? Or do you mean a different kind of sleep mode? I'm thinking of the state where it just refreshes DRAM to keep its contents (this does not produce much heat at all) and everything else is off: that definitely does not require the cpu fan to run because the cpu is not processing any instructions during that state.
Hmm if that were necessary, then all power states should keep the fan on for a while after running, so a device that was shut down would also keep the fans on and there would be no need to put in a requirements document that the fans must turn off to give the illusion of having shut down? To my understanding though, if no new heat is created (usually mainly by processors like CPU or GPU), keeping the fans on is not necessary in regular laptops or desktops.
It might also be naive firmware that expects the same thermal/cooling constraints when everything else is otherwise going to cool passively. Or even a design choice to actively cool so a quick wake will be in a better thermal state.
That would be useful for me today. Systemd again gone into some of those inifinite loops consuming 100% CPU in one of its daemons that try to replace what already worked before (systemd-resolved) today, while I was sitting in the train without AC.
I only realized something was wrong when the pinebook got way too hot.
