So I've decided to finally make a switch from Ubuntu to Debian this past week. On the Ubuntu installation, I always was able to access the typical three power profiles (power saver, balanced, and performance) per default, without issue and with their intended effects. Power Efficiency is rather important to me, as I'm using the laptop on a day-to-day basis in University. The laptop in question is an ASUS Zenbook with an AMD Ryzen 7 5800HS.
On the Debian installation however, only 'power saver' and 'balanced' appeared, and they did not make any difference in terms of the actual battery life of the laptop, with both leading the Battery to drain from 100% to near 0 in about 5 hours of regular use, as opposed to almost 8 on Ubuntu. The output of `acpi` is pretty accurate on the Ubuntu installation, but generally overshoots by multiple hours on the Debian install.I kept the Ubuntu installation on a small partition, luckily, and was able to compare a few things.
First of all, the output of `powerprofilesctl` on Ubuntu yields three profiles, and lists 'intel_pstate' under the Driver section for some reason.
The output of `cpufreq-info --driver` also differed:
I've managed to make some progress by updating my kernel via a backport, to version 6.6.By making this jump, the kernel now includes an amd-specific driver:I also followed some other post I found, proposing to add an
This is the output of `cpupower` when the system is set to battery saver:Somewhere I've also seen a reference to the `amd_pmf` driver, which appearantly also plays a role in management of amd cpus. And on the Debian install, this appearantly is not installed.Meanwhile on the Ubuntu install:---
Throughout all of this, `powerprofilesctl`, without exception, always yielded the same output with the 'placeholder' driver as in the very beginning, and of course, the power profiles options of Gnome also stayed the same two options without effect. I reinstalled the power-profiles-daemon (also from the backport repository, just in case) in hopes that helps, but it didn't. I also have not found any hint as to any possibility to force-configure the daemon to use a specific driver over the placeholder.
I'm still fairly new to the linux world, and I hope that some more experienced users maybe have some more ideas as to how I could further approach this problem ^^ I have the feeling I'm only missing one more small piece to the puzzle, but I'm unable to find it myself.
On the Debian installation however, only 'power saver' and 'balanced' appeared, and they did not make any difference in terms of the actual battery life of the laptop, with both leading the Battery to drain from 100% to near 0 in about 5 hours of regular use, as opposed to almost 8 on Ubuntu. The output of `acpi` is pretty accurate on the Ubuntu installation, but generally overshoots by multiple hours on the Debian install.
powerprofilesctlalso appears to not be registering the correct drivers, as this was (and still is) the output:
Code:
$powerprofilesct balanced: Driver: placeholder* power-saver: Driver: placeholderlFirst of all, the output of `powerprofilesctl` on Ubuntu yields three profiles, and lists 'intel_pstate' under the Driver section for some reason.
The output of `cpufreq-info --driver` also differed:
- Ubuntu: amd_pstate_epp
- Debian: acpi-cpufreq
- Ubuntu: 6.5
- Debian: 6.1
I've managed to make some progress by updating my kernel via a backport, to version 6.6.
Code:
$ uname -r6.6.13+bpo-amd64Code:
$ cpufreq-info --driveramd-pstate-eppamd_pstate=[active/passive/guided]kernel boot parameter. Whilst it did change the listed cpufreq driver, that's about all it did.
Code:
$ cpufreq-info --driveramd-pstateThis is the output of `cpupower` when the system is set to battery saver:
Code:
$ cpupower frequency-infoanalyzing CPU 0: driver: amd-pstate-epp CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: noCode:
$ sudo modinfo amd_pmfmodinfo: ERROR: Module amd_pmf not found.Code:
$ modinfo amd_pmffilename: /lib/modules/6.5.0-28-generic/kernel/drivers/platform/x86/amd/pmf/amd-pmf.kodescription: AMD Platform Management Framework Driverlicense: GPLsrcversion: 496E132C66E38477138D0C0alias: acpi*:AMDI0103:*alias: acpi*:AMDI0102:*alias: acpi*:AMDI0100:*depends: platform_profileretpoline: Yintree: Yname: amd_pmfvermagic: 6.5.0-28-generic SMP preempt mod_unload modversions sig_id: PKCS#7signer: Build time autogenerated kernel keysig_key: 0B:58:66:1F:8F:66:CD:90:C5:95:EC:65:01:8E:89:E3:D4:9A:26:80sig_hashalgo: sha512signature: EE:9F:3C:C5:23:BC:86:EE:F1:84:EC:DE:77:1E:E1:F1:86:4E:A9:7C:A3:C2:E9:8C:13:31:26:60:65:85:E9:B5:9E:CE:F5:90:94:E5:08:FD:75:E9:EE:BF:F8:95:57:B1:E2:D5:1F:3D:E4:E9:2B:8D:13:A7:02:03:55:BF:4B:23:7C:1B:76:5F:32:D9:2E:07:95:0A:A9:5A:49:B3:75:22:CB:8F:74:90:49:51:87:E3:57:EF:2C:B4:3D:B4:4D:5B:5D:C2:31:0B:7D:3A:77:D1:42:CD:54:FC:6E:87:38:B0:68:79:5A:60:27:D2:8B:A8:EE:02:F0:0B:1A:4B:39:F0:BF:AB:86:2F:62:46:BA:55:3D:1E:31:43:34:5F:ED:12:EA:83:94:59:57:2F:84:FB:58:EC:11:1E:76:75:4B:D4:A2:AA:7F:27:E7:CB:4D:20:BE:2D:F1:86:86:32:64:88:7C:74:51:63:25:3C:E5:EC:3C:4C:45:4D:B6:AB:BD:70:D0:24:92:5D:B5:7B:27:DB:3C:6C:E8:71:5B:E6:EF:24:DD:BD:DE:42:1A:0E:1B:35:3A:FD:FC:87:E6:25:57:92:9F:32:55:D6:61:83:F4:A8:A9:A6:5C:46:E5:59:BB:79:36:78:3C:FD:5A:B2:81:50:84:BE:71:C0:60:AE:4C:72:36:91:EE:2E:8C:0C:5C:22:6D:F1:E3:78:27:7D:EB:B4:97:B8:AE:70:F3:7D:6D:EE:C1:73:95:1C:9F:76:9E:37:56:72:4E:AC:82:6E:2D:59:54:22:50:D9:0F:A8:C9:78:47:5C:66:04:78:44:D3:B8:07:D5:69:D7:A5:47:41:B9:D6:9E:4F:52:A5:CC:35:4E:4F:C4:67:6F:1D:A9:85:B5:D5:2B:32:4B:BB:91:42:49:BC:10:D0:59:AE:FC:AE:EF:6C:3C:D7:B6:EC:9A:40:1C:79:1A:2F:E3:F2:D6:0E:EE:23:A0:59:F6:84:A0:31:8D:8E:0A:79:10:14:1C:94:09:D7:4F:8D:28:F1:29:62:D8:2F:EE:47:D0:4F:5E:1E:7D:90:0E:1C:23:DB:2C:88:3B:FC:10:AC:43:07:38:BF:6B:4A:96:C5:D6:8A:29:33:7F:52:51:9B:79:3C:EA:62:47:AE:65:D6:E8:E4:92:DE:7A:2C:66:8E:FC:54:1C:14:5F:82:BE:DD:7E:DF:F0:6B:BE:E5:56:72:6B:A0:64:6A:40:79:75:5E:38:82:20:02:88:3A:24:40:81:22:18:04:53:29:01:C4:51:75:14:B3:74:51:15:F4:3F:41:C9:5E:F2:61:88:D7:08:68:9C:D8:DE:64:61:22:43:E3:74:73:92parm: metrics_table_loop_ms:Metrics Table sample size time (default = 1000ms) (int)parm: force_load:Force load this driver on supported older platforms (experimental) (bool)Throughout all of this, `powerprofilesctl`, without exception, always yielded the same output with the 'placeholder' driver as in the very beginning, and of course, the power profiles options of Gnome also stayed the same two options without effect. I reinstalled the power-profiles-daemon (also from the backport repository, just in case) in hopes that helps, but it didn't. I also have not found any hint as to any possibility to force-configure the daemon to use a specific driver over the placeholder.
I'm still fairly new to the linux world, and I hope that some more experienced users maybe have some more ideas as to how I could further approach this problem ^^ I have the feeling I'm only missing one more small piece to the puzzle, but I'm unable to find it myself.
Statistics: Posted by heofthetea — 2024-05-09 19:53 — Replies 0 — Views 28