$ cat /sys/module/snd_hda_intel/parameters/power_save 0 On Fri, 2021-01-01 at 14:29 +0100, Lars-Peter Clausen wrote: > > > On 1/1/21 2:25 PM, Christian Labisch wrote: > > Hi Takashi, > > > > Thanks for your suggestion - unfortunately it does not work. > > Still no sound after adding the boot parameter and a reboot. > > Can you run `cat /sys/module/snd_hda_intel/parameters/power_save` and > check whether it is still 0 when the system is running? > > > > > Regards, > > Christian > > > > On Fri, 2021-01-01 at 13:09 +0100, Takashi Iwai wrote: > > > On Fri, 01 Jan 2021 12:10:23 +0100, > > > Christian Labisch wrote: > > > > Hi Lars, > > > > > > > > Thanks for your response, as requested I ran alsa-info while playing audio. > > > > Please check the attached information - to me it looks like it being a bug. > > > > It should affect many users, will it be solved in the next release 5.10.5 ? > > > It's likely some runtime PM-related changes that caused this behavior > > > change. But, there must be some program that sets the power_save > > > option explicitly on your system. As dmesg shows, the default > > > power_save to this device has been suppressed, but it's activated by > > > the later action. On, 5.9.x, this didn't take effect, but on 5.10.x, > > > this became effective, as it seems. > > > > > > You can try to pass power_save=0 option to snd-hda-intel module (or > > > boot with snd_hda_intel.power_save=0 boot option). It could work > > > around the issue, although it's no solution. > > > > > > > > > thanks, > > > > > > Takashi > >
