You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a modprobe.d file specifying to disable the audio power_save parameter (options snd_hda_intel power_save=0). After the update, this was not respected and reading /sys/module/snd_hda_intel/parameters/power_save gave back 10 instead of 0. Which is what I got previously.
What did you expect to happen?
I expected for my system to respect the modprobe file I have in place and to apply it to the system.
I have the same problem on my system. power_save parameter value is not applied also if specified using rpm-ostree kargs --append="snd_hda_intel.power_save=0".
Based on further research I suspect it might be caused by TuneD power management. Default tuned profile on fresh install is balanced (run tuned-adm active to find out). Turns out balanced profile overrides audio powersave timeout to 10 seconds: balanced/tuned.conf#L22
I suppose using a different or custom tuned profile might fix the issue we are experiencing. I'll do some more experiments in this direction.
Edit:
I was able to create customized balanced tuned profile. Activating this profile sets the required power_save=0.
But so far I was not able to make this profile persistent between reboots.
$ sudo cp -r /usr/lib/tuned/profiles/balanced /etc/tuned/profiles/balanced-no-audio-powersave
$ sudo vim /etc/tuned/profiles/balanced-no-audio-powersave/tuned.conf
$ cat /etc/tuned/profiles/balanced-no-audio-powersave/tuned.conf
## tuned configuration#
[main]
summary=General non-specialized tuned profile (no audio powersave)
include=balanced
[audio]
timeout=0
$ sudo tuned-adm profile balanced-no-audio-powersave
$ tuned-adm active
Current active profile: balanced-no-audio-powersave
Edit 2:
So the final piece to the puzzle is to edit /etc/tuned/ppd.conf and update PPD - TuneD profile mapping. This autoloads custom tuned profile on system boot.
Describe the bug
I have a modprobe.d file specifying to disable the audio power_save parameter (
options snd_hda_intel power_save=0
). After the update, this was not respected and reading/sys/module/snd_hda_intel/parameters/power_save
gave back10
instead of 0. Which is what I got previously.What did you expect to happen?
I expected for my system to respect the modprobe file I have in place and to apply it to the system.
Output of
rpm-ostree status
State: idle AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx-nvidia:stable Digest: sha256:55884509338bed4c483f7b4132c1f728e14136d32577e588cacfaf01b350d748 Version: 41.20241112.1 (2024-11-12T21:12:12Z) InitramfsEtc: /etc/crypttab ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx-nvidia:stable Digest: sha256:e8ae423bc45a10768fbe2ff3e95113715e0786b8287f3b121a657a925d523bf8 Version: 40.20241109.0 (2024-11-10T16:53:55Z) InitramfsEtc: /etc/crypttab
Output of
groups
Extra information or context
No response
The text was updated successfully, but these errors were encountered: