Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Soundcard power_save modprobe option not respected after upgrade to 41.20241112.1 #9

Open
sander2324 opened this issue Nov 14, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@sander2324
Copy link

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 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.

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

sander wheel docker lxd incus-admin libvirt

Extra information or context

No response

@dosubot dosubot bot added the bug Something isn't working label Nov 14, 2024
@castrojo castrojo transferred this issue from ublue-os/bluefin Dec 8, 2024
@jgroman
Copy link

jgroman commented Jan 1, 2025

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.

cat /etc/tuned/ppd.conf
[main]
# The default PPD profile
default=balanced
battery_detection=true

[profiles]
# PPD = TuneD
power-saver=powersave
balanced=balanced-no-audio-powersave
performance=throughput-performance

[battery]
# PPD = TuneD
balanced=balanced-battery

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants