my laptop fans are running at max speed with 5% cpu usage and i changed the cpu governor to powersave with xenpm and changed max frequency to 800000 but i see no difference in fan speed. i have other distros on same computer that don’t have this problem so it is only qubes and even though i have set the maximum cpu frequency to 800000 the cpuinfo_frequency xenpm shows is still max[2601000] min [800000] cur [2601000] and the average cpu frequency is 4031550 and only the scaling_frequency max has changed to 800000 and i see no difference in fan speed
Maybe you need to install some specific driver in dom0 for your fans speed to be configurable on your hardware.
Search for fans driver info for your hardware.
I didn’t have to install a specific driver for my fans my other distros so were they preinstalled? xenpm doesn’t seem to make any changes to my cpu since i don’t notice any difference when i change anything with it and my cpu average frequency is the same with different cpu governors and max frequency set
Are your sensors detected correctly?
What does “sensors” and “sensors-detect” say?
$ sensors
nvme-pci-0700
Adapter: PCI adapter
Composite: +32.9°C (low = -0.1°C, high = +86.8°C)
(crit = +89.8°C)
Sensor 1: +32.9°C (low = -273.1°C, high = +65261.8°C)
BAT1-acpi-0
Adapter: ACPI interface
in0: 16.46 V
curr1: 0.00 A
pch_cometlake-virtual-0
Adapter: Virtual device
temp1: +44.0°C
nvme-pci-0600
Adapter: PCI adapter
Composite: +34.9°C (low = -273.1°C, high = +83.8°C)
(crit = +84.8°C)
Sensor 1: +34.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +32.9°C (low = -273.1°C, high = +65261.8°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +52.0°C (crit = +120.0°C)
$ sudo sensors-detect
sensors-detect version 3.6.0
System: Acer Predator PH315-53 [V2.04] (laptop)
Board: CML QX50_CMS
Kernel: 6.1.57-1.qubes.fc32.x86_64 x86_64
Processor: Intel(R) Core™ i7-10750H CPU @ 2.60GHz (6/165/2)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you’re doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
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 power sensors… No
AMD Family 16h power sensors… No
Hygon Family 18h thermal sensors… No
Intel digital thermal sensor… No
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 contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family National Semiconductor/ITE'... No Trying family SMSC’… No
Trying family VIA/Winbond/Nuvoton/Fintek'... No Trying family ITE’… No
Probing for Super-I/O at 0x4e/0x4f
Trying family National Semiconductor/ITE'... No Trying family SMSC’… No
Trying family VIA/Winbond/Nuvoton/Fintek'... No Trying family ITE’… No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for National Semiconductor LM78' at 0x290... No Probing for National Semiconductor LM79’ at 0x290… No
Probing for Winbond W83781D' at 0x290... No Probing for Winbond W83782D’ at 0x290… No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Found unknown SMBus adapter 8086:06a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn’t support all probing functions.
Some addresses won’t be probed.
Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn’t support all probing functions.
Some addresses won’t be probed.
Next adapter: i915 gmbus dpb (i2c-2)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus misc (i2c-4)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: AUX A/DDI A/PHY A (i2c-6)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA GPU I2C adapter (i2c-7)
Do you want to scan it? (YES/no/selectively): y
Next adapter: SMBus I801 adapter at efa0 (i2c-8)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Handled by driver ee1004' (already loaded), chip type ee1004’
(note: this is probably NOT a sensor chip!)
Client found at address 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)
Sorry, no sensors were detected.
This is relatively common on laptops, where thermal management is
handled by ACPI rather than the OS.
You could try sensors-detect and sensors on your working distros and import your sensors.conf into dom0.
As mentioned by apparatus you might be missing a specific package or kernel module.
Maybe try kernel-latest? Or intel firmware pacage?
This is on one of my working distros but I don’t know how to import it but to install intel firmware package i do sudo qubes-dom0-update intel-firmware? and for kernel-latest i have to reinstall qubesos?
sudo sensors-detect
# sensors-detect version 3.6.0
# System: Acer Predator PH315-53 [V2.04] (laptop)
# Board: CML QX50_CMS
# Kernel: 6.1.0-13-amd64 x86_64
# Processor: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (6/165/2)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
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 power sensors... No
AMD Family 16h power sensors... No
Hygon Family 18h thermal sensors... No
Intel digital 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 contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
/dev/port: Operation not permitted
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
/dev/port: Operation not permitted
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Found unknown SMBus adapter 8086:06a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at efa0 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Handled by driver `ee1004' (already loaded), chip type `ee1004'
(note: this is probably NOT a sensor chip!)
Client found at address 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): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: Synopsys DesignWare I2C adapter (i2c-2)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: nvkm-0000:01:00.0-bus-0000 (i2c-3)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-bus-0001 (i2c-4)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-bus-0002 (i2c-5)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-bus-0003 (i2c-6)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-aux-0003 (i2c-7)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-bus-0004 (i2c-8)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-aux-0004 (i2c-9)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-bus-0005 (i2c-10)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-aux-0005 (i2c-11)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-bus-0006 (i2c-12)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-aux-0006 (i2c-13)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-bus-0007 (i2c-14)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-aux-0007 (i2c-15)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-bus-0008 (i2c-16)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-aux-0008 (i2c-17)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-bus-0009 (i2c-18)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: nvkm-0000:01:00.0-aux-0009 (i2c-19)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: sor-0006-0f41 (i2c-20)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus dpb (i2c-21)
Do you want to scan it? (yes/NO/selectively): y
y
Next adapter: i915 gmbus dpc (i2c-22)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus misc (i2c-23)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpd (i2c-24)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: AUX A/DDI A/PHY A (i2c-25)
Do you want to scan it? (yes/NO/selectively): y
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)no
Unloading i2c-dev... OK
Unloading cpuid... OK
sudo modprobe coretemp
in dom0 would be too easy i guess?
I don’t have access to qubes rn, try:
sudo qubes-dom0-update --action=search intel
Or with other keywords than intel
$ sudo modprobe coretemp
modprobe: ERROR: could not insert ‘coretemp’: No such device
$ sudo qubes-dom0-update --action=search intel
eclipse-photran-intel.noarch : Intel Fortran compiler support for Photran
fence-agents-intelmodulat.noarch : Fence agent for devices with Intel Modular interfaces
intel-gmmlib.i686 : Intel Graphics Memory Management Library
intel-gmmlib.x86_64 : Intel Graphics Memory Management Library
intel-gmmlib-devel.i686 : Development files for intel-gmmlib
intel-gmmlib-devel.x86_64 : Development files for intel-gmmlib
intel-gpu-firmware.noarch : Firmware for Intel GPUs
intel-ipsec-mb.x86_64 : IPSEC cryptography library optimized for Intel Architecture
intel-ipsec-mb-devel.x86_64 : IPSEC cryptography library optimized for Intel Architecture
intel-mediasdk.x86_64 : Hardware-accelerated video processing on Intel integrated GPUs library
intel-mediasdk-devel.x86_64 : SDK for Hardware-accelerated video processing on Intel integrated GPUs
intel-mpi-benchmarks-license.noarch : License of Intel MPI benchmarks
intel-mpi-benchmarks-mpich.x86_64 : Intel MPI benchmarks compiled against mpich
intel-mpi-benchmarks-openmpi.x86_64 : Intel MPI benchmarjs compiled against openmpi
intel-undervolt.x86_64 : Intel CPU undervolting and throttling configuration tool
intelhex.noarch : Utilities for manipulating Intel HEX file format
intelhex-docs.noarch : Manuak for the IntelHex python library
libva-intel-hybird-driver.i686 : VA driver for Intel G45 & HD Graphics family
libva-intel-hybird-driver.x86_64 : VA driver for Intel G45 & HD Graphics family
python3-intelhex.noarch : A python3 library for manipulating Intel HEX file format
xorg-x11-drv-intel.x86_64 : Xorg X11 Intel video driver
xorg-x11-drv-intel.i686 : Xorg X11 Intel video driver
xorg-x11-drv-intel.src : Xorg X11 Intel video driver
xorg-x11-drv-intel-debuginfo.x86_64 : Debug information for package xor-x11-drv-intel
I can’t find the intel firware and it doesn’t insert coretemp
Unfortunately at this point I don’t think I can help you anymore.
I’ve had this problem too.
Xenpm is just not very good and the developers should find a way to gather more information and make power management better within dom0 instead of the mess that it is. It’s so hard to use and works so poorly and this is not a problem on other OSes.
I love Qubes and the developers of Qubes.