I just installed Garuda Linux with i3 for the first time. Everything seems to be working fine, apart from the CPU fan, it is always off, my CPU is running really hot now, currently at 83C, and the fan just does not turn on, no matter how high the temperature. On other distros it usually jumps on at around 60C.
On one hand I like the silence, on the other hand I am a bit worried about the longevity of my mini PC (Larkbox Pro).
Please let me know if this is intentional and/or if it can be adjusted. Thanks!
To confirm: this issue was present from the start, I have not modified the system in any way, apart from installing a couple programs (vivaldi, sublime-text) that do not control fan speed, cpu freq etc.
Currently CPU usage is at 7%, yet the CPU temp does not drop from 76C without the fan, due to the PC being so tiny and having almost no heat sink the fan is really the only way to carry the heat away.
I have tested Win10 (came with it) , Manjaro KDE, Pop_OS! and the fan is working in all those OSs.
Befor or after install i3wm?
Can you run the live ISO to see if it is the same there, if so also another OS, so we can rule out a hardware failure/dust?
I just booted into Win10 again, fan is working fine. Actually the very moment I start rebooting Garuda the fan turns on, so it must be some program blocking it. The fan turns on when the reboot process is initiated, way before actually halting the system.
Really not sure what you mean. As mentioned, the fan immediately kicks on while I am shutting down Garuda, so I don't see what Windows has to do with anything.
Windoze often interferes on a hardware level with Linux. Windoze has developed the nasty habit of disabling hardware at the bios or onboard firmware level.
Windows often turns off devices at shutdown or suspend to conserve power. These changes persist after a reboot into Linux. Sometimes the changes persist even after Windows is uninstalled. In these cases Windows actually needs to be reinstalled to allow the device to be turned on again.
You would best to go through as many of Windows advanced power saving feature settings as you can find and disable them.
I beg to differ, we always have room for a few more conspiracy theories.
Which inevitably brings me back to:
While not everything can be proved to be Windoze fault, why do so many that dual boot with Windows have so many problems?
If it’s not Windows causing all these bizzare quirks, are all the people who dual boot Windows simply as a group the most unlucky people on the planet.
Just saying, statistically if you search the forum for “Windows Dual Boot” you’ll basically find almost without exception every topic is cursed with some strange issue.
Coincidence, conspiracy, or just terrible luck. I’ll leave it for you to decide.
It’s just coincidence, WinOS is a comparison reference. It’s an unavoidable step to Linux switching.
It’s mostly boot issues (related to Win ties to UEFI) and a couple of HW switches, due to vendors MS interconnection (for easy profit).
We have solutions for most of them and continue to scrap out more.
I left WinOS on my new laptop for my only vulnerability, my kids, until they switch too (which is difficult with University ties to all MS products). We are still on discussions