2024-09-09 Fedora 41 Tuned

Tuned


Date	2024-09-09 to 2024-09-13
Time	all day

Website	QA/Test Days
Matrix	#test-day:fedoraproject.org
Mailing list	test

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

This Fedora Test Day will be focusing Testing Tuned

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. Use #fedora-test-day channels on libera chat. In case of problem related to test day organization/wiki/whatever, please reach out to sumantrom.

Development - Kate Hsuan, Jaroslav Škarvada
Quality Assurance - Adam Williamson (adamw),coremodule (coremodule), Sumantro Mukherjee (sumantrom)

Prerequisite for Test Day[edit]

A system (real or virtual) you can install Fedora to, and not mind if it breaks

How to test?[edit]

Install Fedora[edit]

Testing Tuned from a live environment is difficult and will likely wind up with the system exhausting available battery and failing in strange ways, so we recommend you install Fedora 41 VM for this Test Week.

Run the tests[edit]

Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

Reporting bugs[edit]

If you have problems with any of the tests, report a bug to Bugzilla usually for the component tuned. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

Test Results[edit]

Fedora 41 change[edit]

User	Profile	Tuned	References
Groogee	Sony Vaio, Intel i3-3217U (4)	pass ^[1]	↑ All test steps passed OK without error. Switched between profiles multiple times OK. Didn't notice any difference in power consumption/performance between balanced and performance. The PowerSaver profile did have a noticeably lower inactive power consumption due to display auto-dimming after 30 seconds.
Lemonzest	?	pass ^[1]	↑ Been running tuned-ppd on my Dell Latitude E7470 and Lenovo ThinkPad T470 for about a month now since It was suggested to me in the Fedora Discord on my Fedora 40 Cinnamon Install, Profile changes on AC/Battery status fine.
Markr217	Fully updated F41 VM on Silverblue host, hardware: Lenovo E15 laptop, i7, 40GB memory	pass ^[1]	↑ Steps 1-5 all complete as expected. Optional verification toggled between the different profiles several times without issues. Could not verify power consumption w/powerstat due to running in vm and do not have available hardware to install on at the moment.
Reinier	?	pass ^[1]	↑ I have been running tuned-ppd as a replacement of power-profiles-daemon without any problems since 2024-06-09. Fedora 40, KDE on a Dell XPS13 9316. Automatic changing based on battery status, manually changing using the systray app and changing the mapping to my-favourite-profile via /etc/tuned/ppd.conf all works fine.
abdujabbar	Fedora-Workstation-Live-x86_64-41_Beta-1.2 on Gnome Box	pass ^[1] pass ^[2]	↑ tuned-ppd was already active. The user can select power profiles in GNOME Control Center’s power panel without errors. Once user changed the "Power Mode" in the top-right corner, power profile changes to the selected mode correctly. In CLI, the command "tuned-adm active" shows the correct active profile that matches the selected profile. The name mapping in /etc/tuned/ppd.conf shows the selected profile correctly. ↑ 1. tuned-ppd was already active. 2. The user can select power profiles in GNOME Control Center’s power panel without errors. 3. Once user changed the "Power Mode" in the top-right corner, power profile changes to the selected mode correctly. 4. In CLI, the command "tuned-adm active" shows the correct active profile that matches the selected profile. 5. The name mapping in /etc/tuned/ppd.conf shows the selected profile correctly.
bmenant	Linux fedora 6.11.0-0.rc6.49.f41.x86_64	pass ^[1]	↑ Package `tuned-ppd` already installed on a fresh install (20240908 netinst build); dnf swap command has nothing to do. Switching multiple times from control panel or top-right corner are properly reflected in other places and `tuned-adm active`. Don’t know how to test effectiveness of different profiles on a VM.
clnetbox	Fedora 40 Workstation	pass ^[1]	↑ I replaced power-profiles-daemon with tuned-ppd a few weeks ago and everything works as expected.
derekenz	F41 Workstation VM on an AMD 5600g system	pass
ersen	Fedora 41 WS on KVM	pass
geraldosimiao	Fedora-41 Workstation Beta 1.2 - KVM	pass
gokulakannan	Workstation, KVM, en_US, x86_64, Fresh	pass ^[1]	↑ All the three power modes are working as expected after switching to tuned-ppd.
joaquinvacas	HP Elitebook 845 G9, Fedora Workstation 40	warn ^[1]	↑ Everything went fine. From overall switching through available profiles. Using tuned-ppd Switched between profiles multiple times, but PPD doesn't remember last profile, so at every reboot it goes to the default written on tuned-pdd config.
nicodelle	F41 workstation VM on amd ryzen7730U	fail ^[1]	↑ RHBZ #2312159 Trying the test immediatly after booting resulted in an inconsistency across the power mode shown in the settings, and the one shown in the control panel. Changing one did NOT affect the other, and the command "tuned-adm active" showed the same power profile as the settings. After going idle and trying again in a few minutes, the bug disappeared. I have no idea how to reproduce the bug, the featuer worked perfectly fine after rebooting the VM
nielsenb	Fully updated Fedora 41 compose, KVM (UEFI) on Dell XPS 9360	pass
romangherta	Fedora-Workstation-Live-x86_64-41-20240910.n.0 on KVM	pass
seaninspace	Lenovo T470; 6.11.0-0.rc6.49.fc41.x86_64; tuned-ppd-2.24.0-2.fc41.noarch	fail ^[1]	↑ Profile is not set to "performance" when setting /etc/tuned/ppd.conf's default to "performance" and restart tuned-ppm (or tuned itself). Maybe I'm doing something wrong? Also, when toggling XFCE4's "presentation mode" the profile does not change. The battery/charging detection works perfectly.
tasty0tomato		pass

[1] All test steps passed OK without error. Switched between profiles multiple times OK. Didn't notice any difference in power consumption/performance between balanced and performance. The PowerSaver profile did have a noticeably lower inactive power consumption due to display auto-dimming after 30 seconds.

[2] Been running tuned-ppd on my Dell Latitude E7470 and Lenovo ThinkPad T470 for about a month now since It was suggested to me in the Fedora Discord on my Fedora 40 Cinnamon Install, Profile changes on AC/Battery status fine.

[3] Steps 1-5 all complete as expected. Optional verification toggled between the different profiles several times without issues. Could not verify power consumption w/powerstat due to running in vm and do not have available hardware to install on at the moment.

[4] I have been running tuned-ppd as a replacement of power-profiles-daemon without any problems since 2024-06-09. Fedora 40, KDE on a Dell XPS13 9316. Automatic changing based on battery status, manually changing using the systray app and changing the mapping to my-favourite-profile via /etc/tuned/ppd.conf all works fine.

[5] tuned-ppd was already active. The user can select power profiles in GNOME Control Center’s power panel without errors. Once user changed the "Power Mode" in the top-right corner, power profile changes to the selected mode correctly. In CLI, the command "tuned-adm active" shows the correct active profile that matches the selected profile. The name mapping in /etc/tuned/ppd.conf shows the selected profile correctly.

[6] 1. tuned-ppd was already active. 2. The user can select power profiles in GNOME Control Center’s power panel without errors. 3. Once user changed the "Power Mode" in the top-right corner, power profile changes to the selected mode correctly. 4. In CLI, the command "tuned-adm active" shows the correct active profile that matches the selected profile. 5. The name mapping in /etc/tuned/ppd.conf shows the selected profile correctly.

[7] Package tuned-ppd already installed on a fresh install (20240908 netinst build); dnf swap command has nothing to do. Switching multiple times from control panel or top-right corner are properly reflected in other places and tuned-adm active. Don’t know how to test effectiveness of different profiles on a VM.

[8] I replaced power-profiles-daemon with tuned-ppd a few weeks ago and everything works as expected.

[9] All the three power modes are working as expected after switching to tuned-ppd.

[10] Everything went fine. From overall switching through available profiles. Using tuned-ppd Switched between profiles multiple times, but PPD doesn't remember last profile, so at every reboot it goes to the default written on tuned-pdd config.

[11] RHBZ #2312159 Trying the test immediatly after booting resulted in an inconsistency across the power mode shown in the settings, and the one shown in the control panel. Changing one did NOT affect the other, and the command "tuned-adm active" showed the same power profile as the settings. After going idle and trying again in a few minutes, the bug disappeared. I have no idea how to reproduce the bug, the featuer worked perfectly fine after rebooting the VM

[1]

[1]

[1]

[1]

[1]

[2]

[1]

[1]

[1]

[1]

[1]

[1]

Search

Test Day:2024-09-09 Fedora 41 Tuned

Contents