Whenever I reboot (not shutdown) my system, there’s a short and relatively loud click coming from the speakers. It happens only if the pipewire service is running before I reboot. I had had that issue in the past on Ubuntu.
Also, it sounds quite weird, but a line “audio.suspend-timeout-seconds = 0” inside the context.properties section of the pipewire.conf file prevents the issue from case to case, and suddenly stops working during debugging.
Any help is highly appreciated!
Did you find this?: Audio Pops and Clicks — The Linux Kernel documentation
If your audio chip is one of ALC22x/23x/25x/269/27x/28x/29x (and vendor-specific ALC3xxx models), it looks like there might be some kernel module parameters that might help:
lenovo-spk-noise
Workaround for speaker noise on Lenovo machines
...
dell-spk-noise
Workaround for speaker noise on Dell machines
source: HD-Audio Codec-Specific Models — The Linux Kernel documentation
Thanks for your reply! I’m sorry for a delay in answering.
I’ve visited the pages you kindly shared, but I couldn’t figure out their purpose. The first hyperlink leads to simply a description of an issue, without actually providing a solution. The second hyperlink brings me to a list of code names, such as lenovo-spk-noise (the manufacturer of my laptop is lenovo), with short descriptions. Likewise, there doesn’t seem to be anything that would be helpful for solving my original issue.
I’m grateful for your support, yet it seems like my knowledge is insufficient for self-navigation, which could be required for extracting helpful information from the sources you shared.
Nvm fixed it, here is the solution
Beware that changes to most files under /usr are likely to be overwritten with the package that owns them is next updated (i.e. /usr/lib/pm-utils/power.d/intel-audio-powersave).
I’m not familiar with pm-utils, but many programs have parallel configuration files and directories under /etc which are meant to be used by the end user for making persistent changes.
Look, the thing is that there’s nothing in /usr/lib64/pm-utils/power.d/, and /usr/lib/pm-utils/ doesn’t exist. For now, I couldn’t find a permanent solution.
So, I’ve automated the commands execution using a logon script. You know what… it’s stopped working. It genuinely feels like the system gets “vaccines” from my fixes and becomes immunable. There were 2 other techniques (related to pipewire) that would work at the beginning, but then stop being functional. It’s quite odd.
If you’re running tuned,
FYI, the script you shared on Reddit is missing the hash # symbol on the shebang line.
Thanks, I’ve fixed the crappy formatting