On 04/11/2025 07:23, Patrick Wigmore wrote:
On Mon, 03 Nov 2025 20:49:18 +0000, Tim wrote:
The PC will not shutdown via the shutdown button of via the CLI
interface by issuing the sudo shutdown  -h now.
I have found that using

sudo shutdown -Ph now

from the CLI will shut the PC down.
I've always been under the impression that you need to specify -P if
you want the system to power off after shutting down, though the exact
behaviour could depend on the system firmware. In which case, the
behaviour you describe when running `shutdown -h now` is expected. But
this doesn't seem to explain why the shutdown button doesn't work.

The burping noise happens every time you play a sound or video, but
once it has burped at the start of the file the playback is
perfectly OK.
This is reminiscent of an issue I once had with my laptop, which would
make a pop sound whenever audio output was initiated. My workaround
was to disable the auto power-save function of the snd_hda_intel
kernel module.

The the relevant parameter values can be read/written in the files:

     /sys/module/snd_hda_intel/parameters/power_save
     /sys/module/snd_hda_intel/parameters/power_save_controller

The meaning of these parameters is described by the output of

     sudo modinfo snd_hda_intel

OK when I try I get the following info

mit@biggie:~~ $ sudo modinfo snd_hda_intel
filename:  /lib/modules/6.1.0-40-amd64/kernel/sound/pci/hda/snd-hda-intel.ko
description:    Intel HDA driver
license:        GPL
<snip> (Lots alias and signatures)parm:  power_save:Automatic power-saving timeout (in second, 0 = disable). (xint)
<snip


For some reason my notes on the matter do not cover how I made the
configuration persistent, but it looks like the usual way is to write
a *.conf file in /etc/modprobe.d/ containing, for instance, the line:

     option snd_hda_intel power_save=0

So my understanding is that I need to make a .conf file, saved in /etc/modprobe.d/

Which I did called it

intel_snd.conf

Rebooted still getting noise

I did a lsmod for intel and I get this

mit@biggie:~~ $ lsmod | grep intel
btintel                45056  1 btusb
bluetooth             962560  46 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
intel_rapl_msr         20480  0
intel_rapl_common      32768  1 intel_rapl_msr
intel_powerclamp       20480  0
kvm_intel             380928  0
snd_hda_intel          61440  2
snd_intel_dspcfg       36864  1 snd_hda_intel
snd_intel_sdw_acpi     20480  1 snd_intel_dspcfg
kvm                  1146880  1 kvm_intel
snd_hda_codec         184320  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_core          122880  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_pcm               159744  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
intel_cstate           20480  0
intel_pmc_bxt          16384  1 iTCO_wdt
snd                   126976  16 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
intel_uncore          212992  0
intel_pmc_core         53248  0
crc32c_intel           24576  13
ghash_clmulni_intel    16384  0
aesni_intel           393216  4
crypto_simd            16384  1 aesni_intel
cryptd                 28672  3 crypto_simd,ghash_clmulni_intel

I can see the intel snd module loaded, as my conf is an option I guess I won't see that, how do I know if it is being looked at during bootup?


See also the modprobe.d(5) man page.



Patrick

Tim H

--
 Next meeting: Online, Jitsi, Tuesday, 2025-11-04 20:00
 Check to whom you are replying
 Meetings, mailing list, IRC, ...  https://dorset.lug.org.uk
 New thread, don't hijack:  mailto:[email protected]

Reply via email to