With the Gigabyte board, I did the following, without any effect except a single click. Note: no matter which HDMI device I specify, the click is most often in the TV speakers, not in the monitor output. But sometimes (rarely) the same aplay command produces a click both in the TV speakers and on the monitor output.
Created /lib/firmware/hda-init.fw with the following contents:
[hint]
stick_stream = false
Ran the following commands, without pulseaudio running:
fuser -k /dev/snd/* ; rmmod snd-hda-intel
modprobe snd-hda-intel patch=hda-init.fw
aplay -D hdmi:0,0 /usr/share/sounds/startup3.wav
aplay -D hdmi:0,2 /usr/share/sounds/startup3.wav # in another terminal
Both aplay commands complete very slowly by themselves and lead to "playback write error (DMA or IRQ trouble?)" in the dmesg.
With the Gigabyte board, I did the following, without any effect except a single click. Note: no matter which HDMI device I specify, the click is most often in the TV speakers, not in the monitor output. But sometimes (rarely) the same aplay command produces a click both in the TV speakers and on the monitor output.
Created /lib/firmware/ hda-init. fw with the following contents:
[hint]
stick_stream = false
Ran the following commands, without pulseaudio running:
fuser -k /dev/snd/* ; rmmod snd-hda-intel
modprobe snd-hda-intel patch=hda-init.fw
aplay -D hdmi:0,0 /usr/share/ sounds/ startup3. wav
aplay -D hdmi:0,2 /usr/share/ sounds/ startup3. wav # in another terminal
Both aplay commands complete very slowly by themselves and lead to "playback write error (DMA or IRQ trouble?)" in the dmesg.