Fan always off

yaokong · 13 December 2020 16:23

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!

SGS · 13 December 2020 16:32

Please post

inxi -Fxxxza

read

and

yaokong · 13 December 2020 16:39

Thanks for the quick reply.

inxi -Fxxxza (PrivateBin)

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.

SGS · 13 December 2020 16:41

System:    Kernel: 5.9.12-97-tkg-bmq x86_64 bits: 64 compiler: gcc v: 10.2.0 
           parameters: intel_pstate=passive BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq 
           root=UUID=c0c1c348-f8ce-46ec-922d-c0ec104af2d6 rw [email protected] quiet splash 
           rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3 
           Desktop: i3 4.19 info: i3bar dm: LightDM 1.30.0 Distro: Garuda Linux 
Machine:   Type: Desktop System: CHUWI Innovation And (ShenZhen) product: LarkBox Pro v: N/A serial: <filter> 
           Mobo: N/A model: N/A serial: <filter> UEFI: American Megatrends v: GB01_ZW_1_05 date: 09/17/2020 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Wireless Touch Keyboard K400 Plus serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Info: Quad Core model: Intel Celeron J4125 bits: 64 type: MCP arch: Goldmont Plus family: 6 
           model-id: 7A (122) stepping: 8 microcode: 18 L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 15989 
           Speed: 128 MHz min/max: 800/1080 MHz Core speeds (MHz): 1: 127 2: 998 3: 998 4: 998 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel UHD Graphics 605 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3185 
           Display: x11 server: X.Org 1.20.10 compositor: picom v: git-dac85 driver: intel unloaded: modesetting 
           alternate: fbdev,vesa display ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") 
           Monitor-1: HDMI1 res: 1920x1080 hz: 60 dpi: 94 size: 520x290mm (20.5x11.4") diag: 595mm (23.4") 
           OpenGL: renderer: Mesa Intel UHD Graphics 600 (GLK 2) v: 4.6 Mesa 20.3.0 direct render: Yes 
Audio:     Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio vendor: Realtek 
           driver: snd_hda_intel v: kernel bus ID: 00:0e.0 chip ID: 8086:3198 
           Device-2: Audio-Technica ATR USB microphone type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus ID: 1-8.1:4 chip ID: 0909:001b 
           Sound Server: ALSA v: k5.9.12-97-tkg-bmq 
Network:   Device-1: Intel driver: iwlwifi v: kernel port: f000 bus ID: 00:0c.0 chip ID: 8086:31dc 
           IF: wlo2 state: up mac: <filter> 
Drives:    Local Storage: total: 564.13 GiB used: 10.21 GiB (1.8%) 
           SMART Message: Required tool smartctl not installed. Check --recommends 
           ID-1: /dev/mmcblk0 model: UY7CS0 size: 117.00 GiB block size: physical: 512 B logical: 512 B 
           serial: <filter> rev: 0x8 scheme: GPT 
           ID-2: /dev/sda model: KSN480 size: 447.13 GiB block size: physical: 512 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: 170 scheme: GPT 
Partition: ID-1: / raw size: 78.12 GiB size: 78.12 GiB (100.00%) used: 9.91 GiB (12.7%) fs: btrfs dev: /dev/sda5 
           ID-2: /home raw size: 78.12 GiB size: 78.12 GiB (100.00%) used: 9.91 GiB (12.7%) fs: btrfs 
           dev: /dev/sda5 
           ID-3: /var/log raw size: 78.12 GiB size: 78.12 GiB (100.00%) used: 9.91 GiB (12.7%) fs: btrfs 
           dev: /dev/sda5 
           ID-4: /var/tmp raw size: 78.12 GiB size: 78.12 GiB (100.00%) used: 9.91 GiB (12.7%) fs: btrfs 
           dev: /dev/sda5 
Swap:      Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100) 
           ID-1: swap-1 type: partition size: 4.00 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda4 
           ID-2: swap-2 type: zram size: 1.41 GiB used: 812 KiB (0.1%) priority: 32767 dev: /dev/zram0 
           ID-3: swap-3 type: zram size: 1.41 GiB used: 956 KiB (0.1%) priority: 32767 dev: /dev/zram1 
           ID-4: swap-4 type: zram size: 1.41 GiB used: 808 KiB (0.1%) priority: 32767 dev: /dev/zram2 
           ID-5: swap-5 type: zram size: 1.41 GiB used: 752 KiB (0.1%) priority: 32767 dev: /dev/zram3 
Sensors:   System Temperatures: cpu: 80.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 264 Uptime: 50m wakeups: 7 Memory: 5.63 GiB used: 2.61 GiB (46.4%) Init: systemd v: 247 
           Compilers: gcc: 10.2.0 clang: 11.0.0 Packages: pacman: 1205 lib: 288 flatpak: 0 Shell: Zsh v: 5.8 
           running in: xfce4-terminal inxi: 3.1.09

SGS · 13 December 2020 16:47

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?

yaokong · 13 December 2020 17:18

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.

I will test the live ISO later again.

SGS · 13 December 2020 17:23

Like always in Win dual boot, time, bluetooth ... fan? are blocked.

yaokong · 13 December 2020 17:24

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.

tbg · 13 December 2020 21:13

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.

petsam · 13 December 2020 22:59

True, but generalizing leads to conspiracy theories. We have enough of them with the pandemic .

You may not have lm-sensors installed. Install it if it isn't already.
Read more and try to configure, if your HW is compatible.

tbg · 13 December 2020 23:10

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.

petsam · 13 December 2020 23:24

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