Turtlewit
Turtlewit
PostsComments
UBUniversal Blue
Created by Raevenant on 10/16/2024 in #🛟bazzite-help
[RESOLVED] Tuned power manager tunes too low
The new Bazzite 41 release should contain a workaround for this issue, as the variables previously set in 65-memory.conf have moved to now be set as part of the default throughput-performance and balanced TuneD profiles as of this commit: https://github.com/ublue-os/bazzite/commit/b2e4c8bb13edcf4eb2a5f3af527a1a098313d1ba I haven't tested this yet, but this bug should now no longer occur without my posted workaround after updating to the newest bazzite. I am curious about the behavior of the powersave profile now though, as it doesn't set the vm variables at all
30 replies
UBUniversal Blue
Created by TheMCNerd2018 on 10/16/2024 in #🛟bazzite-help
Various KDE and system issues in 40.20241013 and 40.20241014 while device is in Power Saver mode
I'm not quite sure, the values seem to affect disk write caching behavior, so disk speed and other hardware factors may affect performance when the bug occurs
89 replies
UBUniversal Blue
Created by TheMCNerd2018 on 10/16/2024 in #🛟bazzite-help
Various KDE and system issues in 40.20241013 and 40.20241014 while device is in Power Saver mode
That is the correct behaviour. Pre-workaround, the value will always be zero after switching to performance for the first time.
89 replies
UBUniversal Blue
Created by TheMCNerd2018 on 10/16/2024 in #🛟bazzite-help
Various KDE and system issues in 40.20241013 and 40.20241014 while device is in Power Saver mode
zero is bad
89 replies
UBUniversal Blue
Created by TheMCNerd2018 on 10/16/2024 in #🛟bazzite-help
Various KDE and system issues in 40.20241013 and 40.20241014 while device is in Power Saver mode
No, non-zero is good!
89 replies
UBUniversal Blue
Created by TheMCNerd2018 on 10/16/2024 in #🛟bazzite-help
Various KDE and system issues in 40.20241013 and 40.20241014 while device is in Power Saver mode
Nice! Hopefully it works now, but it's possible there are other issues with the various profiles. To anyone having issues after workaround, it is worth checking that cat /proc/sys/vm/dirty_bytes does not print 0 when on balanced or powersave. If it does, the workaround isn't working (the value is failing to be restored to the system default). tuned-adm verify may be helpful when troubleshooting.
89 replies
UBUniversal Blue
Created by TheMCNerd2018 on 10/16/2024 in #🛟bazzite-help
Various KDE and system issues in 40.20241013 and 40.20241014 while device is in Power Saver mode
Yep, just added a note about restarting after changing ppd.conf. Glad it seems to be working!
89 replies
UBUniversal Blue
Created by Raevenant on 10/16/2024 in #🛟bazzite-help
[RESOLVED] Tuned power manager tunes too low
There is a pull request open to fix this issue in the TuneD github which you can follow here: https://github.com/redhat-performance/tuned/pull/688
30 replies
UBUniversal Blue
Created by TheMCNerd2018 on 10/16/2024 in #🛟bazzite-help
Various KDE and system issues in 40.20241013 and 40.20241014 while device is in Power Saver mode
Looks like there is already a pull request to fix this exact issue! https://github.com/redhat-performance/tuned/pull/688
89 replies
UBUniversal Blue
Created by TheMCNerd2018 on 10/16/2024 in #🛟bazzite-help
Various KDE and system issues in 40.20241013 and 40.20241014 while device is in Power Saver mode
If a TuneD github issue hasn't been created for this already, I am going to create one
89 replies
UBUniversal Blue
Created by Raevenant on 10/16/2024 in #🛟bazzite-help
[RESOLVED] Tuned power manager tunes too low
The workaround I am using is to override the throughput-performance profile with a custom profile. I created a new directory and config file at /etc/tuned/profiles/throughput-performance-custom/tuned.conf with these contents: 
[main]
include=throughput-performance

[sysctl]
replace=1
vm.dirty_bytes = 0
vm.dirty_ratio = 40
vm.dirty_background_bytes = 0
vm.dirty_background_ratio = 10
vm.swappiness=10
net.core.somaxconn=>2048
[main]
include=throughput-performance

[sysctl]
replace=1
vm.dirty_bytes = 0
vm.dirty_ratio = 40
vm.dirty_background_bytes = 0
vm.dirty_background_ratio = 10
vm.swappiness=10
net.core.somaxconn=>2048
replace=1 is unfortunately necessary, as the order in which the variables are set is important. This means future updates to the "sysctl" section of the default performance profile will not be propagated to this profile while the profile override exists. In order for desktop environments to use this profile as the new default performance profile, /etc/tuned/ppd.conf must be updated to change the performance= line to: 
performance=throughput-performance-custom
performance=throughput-performance-custom
If you named your profile differently, replace throughput-performance-custom with the name of your custom profile. Edit: forgot to mention, you should restart your system after adding the new profile and editing ppd.conf. I found restarting tuned-ppd with systemctl didn't work when I tried it, I could only restart it with a system reboot
30 replies
UBUniversal Blue
Created by Raevenant on 10/16/2024 in #🛟bazzite-help
[RESOLVED] Tuned power manager tunes too low
I have been experiencing a similar issue, and I believe I found the bug causing it, and potentially a workaround. The issue I observed was that my system performed normally when it starts on either powersave or balanced, but performance would degrade significantly if I switched to performance, then back to either powersave or balanced (frequent long hitches when interacting with the taskbar, start menu, launching programs, etc). Performance would not improve until I switched back to performance or rebooted my system. It seems this is caused by a bug with how TuneD manages sysctl variables in the sysctl plugin. The default throughput-performance profiles sets the variables vm.dirty_ratio and vm.dirty_background_ratio. However, when either of these variables are set, they set vm.dirty_bytes and vm.dirty_background_bytes to 0 respectively, as the variables are incompatible. When TuneD switches to a different profile, it restores the values of the _ratio variables to 0, but it doesn't restore the original values of the _bytes variables. Bazzite by default sets the _bytes variables and not the _ratio variables (in /usr/lib/sysctl.d/65-memory.conf). The result of all of this is that all 4 variables are set to 0 when switching away from the performance profile, resulting in severely degraded performance.
30 replies
UBUniversal Blue
Created by Turtlewit on 7/20/2024 in #🛟bazzite-help
Color Banding in Game Mode HDR
Did a system update, but the bug is still present on kernel 6.9.8-204. The force composite setting does fix it and is nicer than disabling color management, so I'll be patient and wait for the fix to hit stable. Thank you for the help!
61 replies
UBUniversal Blue
Created by Turtlewit on 7/20/2024 in #🛟bazzite-help
Color Banding in Game Mode HDR
Good to know, thank you for the information! I'll update and try that if the fix isn't in stable yet.
61 replies
UBUniversal Blue
Created by Turtlewit on 7/20/2024 in #🛟bazzite-help
Color Banding in Game Mode HDR
6.9.8-202.fsync.fc40.x86_64
61 replies