Fan control on HP Pavillion Desktop Ubuntu 20.04 | pressku.com

Trending 2 months ago

I've been having immoderate problems pinch my desktop overheating and shutting off. I person a workaround for now utilizing thermald and intel_powerclamp to limit CPU utilization to 70% and agressively throttle erstwhile nan CPU temp sensor exceeds 60C (if it gets to 70C, nan thermal shutdown kicks successful and my PC shuts off, truthful I'm a spot fishy of nan accuracy of nan sensor).

I person a TG01-1183w HP Pavillion Desktop PC dualbooted pinch Windows 11 and Ubuntu 20.04

In Windows, I americium capable to power nan velocity of nan lawsuit fan, CPU fan, and GPU fan. However, successful Ubuntu, I americium only capable to power nan velocity of nan GPU instrumentality (with coolercontrol). Coolercontrol doesn't observe immoderate of nan motherboard fans.

I installed lm-sensors and ran sensors-detect:

# sensors-detect type 3.6.0 # System: HP HP Pavilion Gaming Desktop TG01-1xxx # Board: HP 8767 # Kernel: 5.15.0-94-generic x86_64 # Processor: Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz (6/165/3) This programme will thief you find which kernel modules you need to load to usage lm_sensors astir effectively. It is mostly safe and recommended to judge nan default answers to each questions, unless you cognize what you're doing. Some southbound bridges, CPUs aliases representation controllers incorporate embedded sensors. Do you want to scan for them? This is wholly safe. (YES/no): Module cpuid loaded successfully. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h powerfulness sensors... No AMD Family 16h powerfulness sensors... No Hygon Family 18h thermal sensors... No Intel integer thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips incorporate embedded sensors. We person to constitute to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O astatine 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found chartless spot pinch ID 0x8631 Probing for Super-I/O astatine 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) instrumentality IPMI, a group of communal interfaces through which strategy wellness information whitethorn beryllium retrieved, amongst different things. We first effort to get nan accusation from SMBIOS. If we don't find it there, we person to publication from arbitrary I/O ports to probe for such interfaces. This is usually safe. Do you want to scan for IPMI interfaces? (YES/no): Probing for `IPMI BMC KCS' astatine 0xca0... No Probing for `IPMI BMC SMIC' astatine 0xca8... No Some hardware monitoring chips are accessible done nan ISA I/O ports. We person to constitute to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do person ISA I/O ports moreover if you do not person any ISA slots! Do you want to scan nan ISA I/O ports? (YES/no): Probing for `National Semiconductor LM78' astatine 0x290... No Probing for `National Semiconductor LM79' astatine 0x290... No Probing for `Winbond W83781D' astatine 0x290... No Probing for `Winbond W83782D' astatine 0x290... No Lastly, we tin probe nan I2C/SMBus adapters for connected hardware monitoring devices. This is nan astir risky part, and while it works reasonably good connected astir systems, it has been reported to origin trouble on immoderate systems. Do you want to probe nan I2C/SMBus adapters now? (YES/no): Found chartless SMBus adapter 8086:06a3 astatine 0000:00:1f.4. Sorry, nary supported PCI autobus adapters found. Next adapter: SMBus I801 adapter astatine efa0 (i2c-0) Do you want to scan it? (YES/no/selectively): Client recovered astatine reside 0x4f Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... Success! (confidence 3, driver `lm75') Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP435'... No Probing for `Texas Instruments TMP441'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Client recovered astatine reside 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: Synopsys DesignWare I2C adapter (i2c-1) Do you want to scan it? (YES/no/selectively): Adapter doesn't support each probing functions. Some addresses won't beryllium probed. Next adapter: NVIDIA i2c adapter 1 astatine 1:00.0 (i2c-2) Do you want to scan it? (yes/NO/selectively): Next adapter: NVIDIA i2c adapter 2 astatine 1:00.0 (i2c-3) Do you want to scan it? (yes/NO/selectively): Next adapter: NVIDIA i2c adapter 5 astatine 1:00.0 (i2c-4) Do you want to scan it? (yes/NO/selectively): Next adapter: NVIDIA i2c adapter 6 astatine 1:00.0 (i2c-5) Do you want to scan it? (yes/NO/selectively): Next adapter: NVIDIA i2c adapter 7 astatine 1:00.0 (i2c-6) Do you want to scan it? (yes/NO/selectively): Next adapter: NVIDIA i2c adapter 8 astatine 1:00.0 (i2c-7) Do you want to scan it? (yes/NO/selectively): Now follows a summary of nan probes I person conscionable done. Just property ENTER to continue: Driver `lm75': * Bus `SMBus I801 adapter astatine efa0' Busdriver `i2c_i801', I2C reside 0x4f Chip `Dallas Semiconductor DS75' (confidence: 3) Driver `coretemp': * Chip `Intel integer thermal sensor' (confidence: 9) To load everything that is needed, adhd this to /etc/modules: #----cut here---- # Chip drivers coretemp lm75 #----cut here---- If you person immoderate drivers built into your kernel, nan database supra will contain excessively galore modules. Skip nan due ones! Do you want to adhd these lines automatically to /etc/modules? (yes/NO) Unloading cpuid... OK

However, erstwhile I tally pwmconfig, I get nan pursuing output:

# pwmconfig type 3.6.0 This programme will hunt your sensors for beat width modulation (pwm) controls, and trial each 1 to spot if it controls a instrumentality on your motherboard. Note that galore motherboards do not person pwm circuitry installed, moreover if your sensor spot supports pwm. We will effort to concisely extremity each instrumentality utilizing nan pwm controls. The programme will effort to reconstruct each instrumentality to afloat speed after testing. However, it is ** very important ** that you physically verify that nan fans person been to afloat speed after nan programme has completed. /usr/sbin/pwmconfig: There are nary pwm-capable sensor modules installed

I tin spot 5 "fan" devices erstwhile I tally feline /sys/class/thermal/cooling_device*/type:

Fan Processor Processor Processor Processor Processor Processor Processor intel_powerclamp TCC Offset Fan Fan Fan Fan Processor Processor Processor Processor Processor

I tried adding nan kernel parameter acpi_enforce_resources=lax to grub and rebooting, but still didn't spot immoderate change.

I saw this post: 20.04 doesn't support Intel Core i5 10400? and thought possibly I request to update my kernel. I person a 22.04 unrecorded USB which I will effort tomorrow to spot if that works.

lscpu output:

CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 12 On-line CPU(s) list: 0-11 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 165 Model name: Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz Stepping: 3 CPU MHz: 800.002 CPU max MHz: 4300.0000 CPU min MHz: 800.0000 BogoMIPS: 5799.77 Virtualization: VT-x L1d cache: 192 KiB L1i cache: 192 KiB L2 cache: 1.5 MiB L3 cache: 12 MiB NUMA node0 CPU(s): 0-11 Vulnerability Gather information sampling: Mitigation; Microcode Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Mmio old data: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Retbleed: Mitigation; Enhanced IBRS Vulnerability Spec rstack overflow: Not affected Vulnerability Spec shop bypass: Mitigation; Speculative Store Bypass abnormal via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Vulnerability Srbds: Mitigation; Microcode Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc creation arch_perfm connected pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 show ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe p opcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify h wp_act_window hwp_epp md_clear flush_l1d arch_capabilities

uname -a:

Linux trilobyte 5.15.0-94-generic #104~20.04.1-Ubuntu SMP Tue Jan 16 13:34:09 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
More
close