HDMI audio cuts when I interact with the desktop (KDE Plasma 6.5, Nvidia GPU)

Issue:

HDMI Audio briefly cuts / drops during specific desktop environment interactions in Fedora KDE Plasma 43, including:

  • Switching workspaces

  • Opening, maximizing, minimizing, and scrolling windows

  • Loading new pages in Firefox

  • Searching for a program in the application launcher menu

After a drop, there won’t be another one until some time has gone by, but the issue is very predictable and easy to reproduce. Otherwise, audio playback is stable if I’m just working in one window and not interacting with the desktop.

System information:

inxi -A -C -G

CPU:
  Info: 10-core (6-mt/4-st) model: 12th Gen Intel Core i5-12600K bits: 64
    type: MST AMCP cache: L2: 9.5 MiB
  Speed (MHz): avg: 1188 min/max: 800/4900:3600 cores: 1: 1188 2: 1188
    3: 1188 4: 1188 5: 1188 6: 1188 7: 1188 8: 1188 9: 1188 10: 1188 11: 1188
    12: 1188 13: 1188 14: 1188 15: 1188 16: 1188
Graphics:
  Device-1: Intel Alder Lake-S GT1 [UHD Graphics 770] driver: i915 v: kernel
  Device-2: NVIDIA AD104 [GeForce RTX 4070] driver: nvidia v: 580.119.02
  Display: wayland server: Xwayland v: 24.1.9 compositor: kwin_wayland
    driver: gpu: nv_platform,nvidia,nvidia-nvswitch resolution: 3840x2160~60Hz
  API: EGL v: 1.5 drivers: iris,nvidia,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.119.02
    renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
  API: Vulkan v: 1.4.328 drivers: nvidia,intel,llvmpipe surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake-S HD Audio driver: snd_hda_intel
  Device-2: NVIDIA AD104 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.18.5-200.fc43.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.10 status: active

Logs:

Despite the predictability and ease of reproducing this issue, I haven’t found a way to log the issue as it’s happening.

pw-top doesn’t show any errors even after reproducing the issue multiple times:

pw-top

S   ID  QUANT   RATE    WAIT    BUSY   W/Q   B/Q  ERR FORMAT           NAME 
S   30      0      0    ---     ---   ---   ---     0                  Dummy-Driver
S   31      0      0    ---     ---   ---   ---     0                  Freewheel-Driver
S   52      0      0    ---     ---   ---   ---     0                  Midi-Bridge
S   57      0      0    ---     ---   ---   ---     0                  bluez_midi.server
I   71      0      0   0.0us   0.0us  ???   ???     0    S16LE 1 44100 speech-dispatcher-dummy
R   78   2048  48000 161.0us  36.7us  0.00  0.00    0    S32LE 2 48000 alsa_output.pci-0000_01_00.1.hdmi-stereo
R   36   3600  48000  44.2us  41.9us  0.00  0.00    0    F32LE 2 48000  + Firefox

journalctl gives no output at all:

journalctl --user -f | grep -i pipewire

Troubleshooting:

To start, I copied the base pipewire conf file to ~/.config/pipewire/ and increased the buffer size:

nano ~/.config/pipewire/pipewire.conf

context.properties = {
    default.clock.allowed-rates = [ 48000 ]
    default.clock.quantum = 2048
    default.clock.min-quantum = 1024
    default.clock.max-quantum = 4096
    default.clock.rate = 48000
    default.clock.force-quantum = true

    core.daemon = true
    core.name = pipewire-0
    core.realtime = true
    core.realtime.priority = 88
}

Then I tried setting Pipewire to run with higher priority. I checked that pipewire could request realtime and added my user:

sudo dnf install realtime-setup
sudo systemctl enable --now realtime-setup

sudo usermod -aG realtime $USER
sudo usermod -aG pipewire $USER

ulimit -r

99

Then I confirmed the pipewire process:

ps -o pid,cls,rtprio,cmd -C pipewire

   PID CLS RTPRIO CMD
   2382  FF     88 /usr/bin/pipewire

Still no luck. From there I got advice from ChatGPT to start tinkering with the Nvidia drivers, but I don’t know much about fixing Nvidia driver issues in Linux. I still haven’t been able to get an actual log of what is happening either.

To recap, audio generally works fine, and the only issue I’m experiencing is this brief (approx 300ms?) audio dropout problem whenever I specifically DO something on the desktop.

Any insight would be much appreciated, thanks.

It sounds similar to this problem that was reported earlier:

Does that workaround work for your case?

Hi Gregory,

Thanks for getting back to me. I reviewed the thread that you linked, and I noticed some differences:

One major symptom that the user reported is not an issue that I am dealing with:

After pausing a video for ~10 seconds, the first 1–2 seconds of sound were missing when playback resumed.

I have not experienced this problem at all. Audio is always very snappy when I press play and pause, and I never experience loss when starting an audio track after a pause.

The next symptom is closer to what I am dealing with:

Occasionally, there were short random audio dropouts during playback, especially in Firefox and on YouTube (or other similar streaming sites).

This is what I am dealing with, except that I can replace “occasionally” and “random” with exact desktop environment interactions that I know will trigger a drop.

For example, I go to open a link in another browser window, and I think to myself, “the audio is going to cut,” and sure enough it does.

This issue for me is very predictable and reproduceable. It only happens when I initiate an action in the desktop environment. I can listen to an album on Youtube and play/pause it as much as I want in one window, and I never experience an issue.

But as soon as I do something with a window or a workspace, I get a gap.

The user in the thread you referred applied this solution:

Then I added this configuration:
~/.config/pipewire/client.conf.d/10-buffer.conf
context.properties = {
default.clock.rate = 48000
default.clock.allowed-rates = [ 44100 48000 ]
default.clock.quantum = 2048
default.clock.min-quantum = 1024
default.clock.max-quantum = 4096
}

This looks very much like my config file; however, the locations are slightly different. Here’s the relevant block from my pipewire config file:

cat ~/.config/pipewire/pipewire.conf

context.properties = {
    ## Configure properties in the system.
    #library.name.system                   = support/libspa-support
    #context.data-loop.library.name.system = support/libspa-support
    #support.dbus                          = true
    #link.max-buffers                      = 64
    link.max-buffers                       = 16                       # version < 3 clients can't handle more
    #mem.warn-mlock                        = false
    #mem.allow-mlock                       = true
    #mem.mlock-all                         = false
    #clock.power-of-two-quantum            = true
    #log.level                             = 2
    #cpu.zero.denormals                    = false
    #loop.rt-prio = -1            # -1 = use module-rt prio, 0 disable rt
    #loop.class = data.rt
    #thread.affinity = [ 0 1 ]    # optional array of CPUs
    #context.num-data-loops = 1   # -1 = num-cpus, 0 = no data loops
    #
    #context.data-loops = [
    #    {   loop.rt-prio = -1
    #        loop.class = [ data.rt audio.rt ]
    #        #library.name.system = support/libspa-support
    #        thread.name = data-loop.0
    #        #thread.affinity = [ 0 1 ]    # optional array of CPUs
    #    }
    #]
    ## Properties for the DSP configuration.
    default.clock.rate          = 48000
    default.clock.allowed-rates = [ 44100 48000 ]
    default.clock.quantum       = 2048
    default.clock.min-quantum   = 1024
    default.clock.max-quantum   = 4096
    #default.clock.quantum-limit = 8192
    #default.clock.quantum-floor = 4
    #default.video.width         = 640
    #default.video.height        = 480
    #default.video.rate.num      = 25
    #default.video.rate.denom    = 1
    #
    #settings.check-quantum      = false
    #settings.check-rate         = false
    core.daemon = true              # listening for socket connections
    core.name   = pipewire-0        # core name and socket name
    core.realtime = true
    core.realtime.priority = 88
}

Another important thing to note is that I experienced audio dropouts in other Linux distros (I tried Mint Cinnamon and XFCE too) before installing Fedora 43. With Fedora the issue is not as bad. This leans me more towards a hardware issue with Nvidia, even if Pipewire is implicated, but I’m not an expert.

While other threads have reported issues with audio, none seem to match my situation. My audio is stable and only drops when I personally interact with the desktop environment.

Yes, that does sound like it is more likely to be a hardware issue.

FWIW, I’ve heard reports of EM interference from monitors when poor quality (low shielding) HDMI cables were used. Could that be what you are experiencing? Maybe some of the monitor circuitry is going into a low-power mode when the visuals stop changing and then kicking back in when there is movement?

I’d disable IOMMU in BIOS and iommu=pt as a boot option, and disable CPU Hyperthreading/SMT (I suspect HT and realtime act odd on my computer and disabling HT has log-in boot sounds play fine vs a little stutter)

Whoops. I accidentally replied before finishing the post.

I swapped the HDMI cables, both from the PC to the receiver and the receiver to the TV, and unfortunately I didn’t notice a change. I was a bit vague in my last reply. When I mentioned a “hardware” issue, I also didn’t want to rule out the Nvidia drivers.

I was going to add more, but I can look into this BIOS idea first. Some quick info about previous systems to try to narrow it down though:

Windows 10: No problem at any time
Linux Mint Cinnamon: Consistent audio drops
Linux Mint XFCE: More issues than with Cinnamon
Fedora KDE: Fewer drops but still very consistent

Based on this, is a BIOS issue still likely? That’s a bigger change to make. I’m still hoping there’s a way I could investigate other common factors like the Linux kernel, audio stack, or the Nvidia drivers

Lastly, I played a few hours of a fairly GPU-intensive game tonight and had zero audio issues at all, but I moved the mouse inside this reply window and the audio cut instantly. What could possibly be happening? :weary_face:

What audio driver is being used? Are there others that you could try? The output from lspci -k -nn might answer those questions.

So this is not a direct connection between the PC and the TV?

If that is the case then it is possible that a direct cable connection between the PC and the TV may eliminate the issue. If it does then the device you call a receiver may be causing the problem.

1 Like

The two audio devices are here:

lspci -k -nn
00:1f.3 Audio device [0403]: Intel Corporation Alder Lake-S HD Audio Controller [8086:7ad0] (rev 11)
    DeviceName: Onboard - Sound
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:9d46]
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_soc_avs, snd_sof_pci_intel_tgl, snd_hda_intel
01:00.1 Audio device [0403]: NVIDIA Corporation AD104 High Definition Audio Controller [10de:22bc] (rev a1)
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:5137]
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel

Here’s the full output in case it helps:

lspci -k -nn
​
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4648] (rev 02)
    DeviceName: Onboard - Other
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
    Kernel modules: ie31200_edac
00:01.0 PCI bridge [0604]: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 [8086:460d] (rev 02)
    Kernel driver in use: pcieport
    Kernel modules: shpchp
00:02.0 Display controller [0380]: Intel Corporation Alder Lake-S GT1 [UHD Graphics 770] [8086:4680] (rev 0c)
    DeviceName: Onboard - Video
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
    Kernel driver in use: i915
    Kernel modules: i915, xe
00:08.0 System peripheral [0880]: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator [8086:464f] (rev 02)
    DeviceName: Onboard - Other
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
00:0a.0 Signal processing controller [1180]: Intel Corporation Platform Monitoring Technology [8086:467d] (rev 01)
    DeviceName: Onboard - Other
    Kernel driver in use: intel_vsec
    Kernel modules: intel_vsec
00:14.0 USB controller [0c03]: Intel Corporation Alder Lake-S PCH USB 3.2 Gen 2x2 XHCI Controller [8086:7ae0] (rev 11)
    DeviceName: Onboard - Other
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
    Kernel driver in use: xhci_hcd
    Kernel modules: xhci_pci
00:14.2 RAM memory [0500]: Intel Corporation Alder Lake-S PCH Shared SRAM [8086:7aa7] (rev 11)
    DeviceName: Onboard - Other
00:16.0 Communication controller [0780]: Intel Corporation Alder Lake-S PCH HECI Controller #1 [8086:7ae8] (rev 11)
    DeviceName: Onboard - Other
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
    Kernel driver in use: mei_me
    Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Alder Lake-S PCH SATA Controller [AHCI Mode] [8086:7ae2] (rev 11)
    DeviceName: Onboard - SATA
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
    Kernel driver in use: ahci
    Kernel modules: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation Alder Lake-S PCH PCI Express Root Port #1 [8086:7ab8] (rev 11)
    Kernel driver in use: pcieport
    Kernel modules: shpchp
00:1f.0 ISA bridge [0601]: Intel Corporation B660 Chipset LPC/eSPI Controller [8086:7a86] (rev 11)
    DeviceName: Onboard - Other
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
00:1f.3 Audio device [0403]: Intel Corporation Alder Lake-S HD Audio Controller [8086:7ad0] (rev 11)
    DeviceName: Onboard - Sound
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:9d46]
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_soc_avs, snd_sof_pci_intel_tgl, snd_hda_intel
00:1f.4 SMBus [0c05]: Intel Corporation Alder Lake-S PCH SMBus Controller [8086:7aa3] (rev 11)
    DeviceName: Onboard - Other
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
    Kernel driver in use: i801_smbus
    Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Alder Lake-S PCH SPI Controller [8086:7aa4] (rev 11)
    DeviceName: Onboard - Other
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
    Kernel driver in use: intel-spi
    Kernel modules: spi_intel_pci
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (17) I219-V [8086:1a1d] (rev 11)
    DeviceName: Onboard - Ethernet
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d46]
    Kernel modules: e1000e
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD104 [GeForce RTX 4070] [10de:2786] (rev a1)
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:5137]
    Kernel driver in use: nvidia
    Kernel modules: nouveau, nvidia_drm, nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation AD104 High Definition Audio Controller [10de:22bc] (rev a1)
    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:5137]
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel
02:00.0 Non-Volatile memory controller [0108]: ADATA Technology Co., Ltd. LEGEND 960 NVMe SSD [1cc1:622a] (rev 03)
    Subsystem: ADATA Technology Co., Ltd. LEGEND 960 NVMe SSD [1cc1:622a]
    Kernel driver in use: nvme
    Kernel modules: nvme

Jeff, correct, I have always run the PC HDMI output (along with other devices such as a PS5 and Raspberry Pi) into an AV receiver, and the receiver goes out to the TV’s HDMI input (4K). I’ve never had any problems with the receiver, but I did bypass it just to check.

The result: No HDMI output from my PC.

All but one of the next steps involve a complete power cycle of the PC in between because hot-plugging the HDMI cable almost never worked:

Power cycled the PC again repeatedly: no video

Switched to a different HDMI input on the TV: no video

Switched to the Intel onboard graphics HDMI output on my PC: no video

Switched to an old 720p TV: no video

Rebooted again with the 720p TV: finally got video (in 720p)

Tried again with the NVIDIA 4070’ HDMI to the 720p TV: still had video

Switched back to the original input on my 4K TV: no video

Switched back to the 720p TV without rebooting or power cycling: got 720p video

Reconnected original input on 4K TV: no video

Hooked up the AV receiver to the 4K TV again: got video back, detected 720p at first, but adjusted automatically back to 4K

So now it’s back to normal with the original connection.

As for the original audio issue, I did not experience it when connected to the 720p TV. It’s only happening when the display settings are on 4K.

I’m glad I tried this because it revealed other issues with HDMI. It’s notable that the only time I could hotplug the HDMI cable and get a signal without rebooting was going from the PC directly into a pretty old TV. So the PC’s HDMI connection isn’t properly discovering devices, and the only way to get a signal is to restart the PC. I’m still not sure why I could never get the PC to work with a direct connection to my TV either.

But obviously the HDMI drivers/settings on the PC aren’t behaving as they should. Just for the record, in the past I’ve used all sorts of combinations of devices on different TV inputs, with and without the receiver, and they’ve always behaved the way HDMI is expected to, so I don’t expect that it’s my TV or the receiver.

OK, so the snd_hda_intel driver is handling both your on-board sound chip and your NVIDIA sound chip (AD104). It’s just a shot in the dark, but I wonder if disabling the handling of the on-board sound chip would help? I think the following file might work to disable the on-board sound.

In /etc/modprobe.d/sound.conf:

options snd_hda_intel enable=0,1

You’ll probably need to reboot to activate the change. Use cat /sys/module/snd_hda_intel/parameters/enable to confirm that the settings took after you reboot.

You have an nvidia RTX 4070 gpu according to that output.
Please show the output of dnf list --installed \*nvidia\* and inxi -Fzxx as well as cat /proc/cmdline and cat /etc/kernel/cmdline

It may be beneficial to run sudo dnf upgrade --refresh to ensure the system is 100% fully upgraded followed by a reboot. Assuming you installed the nvidia driver from rpmfusion (which will be shown by the dnf command) then possibly sudo akmods --rebuild --force after the upgrade has completed

I have both onboard sound and an RTX 3050 gpu and no issues with sound; but my onboard sound is an AMD chipset and not intel. As with yours the snd_hda_intel driver is used for both.

There is a bandwidth issue to be aware of with HDMI cables. I wonder if 4K video + the audio streams is too much for the cable you are using? The way video is encoded, identical or nearly identical video frames are highly compressed and reuse a lot of data from the previous frame, but when “large” changes happen, whole frames/images start being transmitted which requires more bandwidth. That wouldn’t explain why you don’t see the problem with the games though. Unless they are running at a lower frame rate or something. Have you experimented with settings that might reduce the required bandwidth, such as reducing the video frame rate, color depth, or reducing the number of audio channels?

1 Like

This leads me to wonder if the same may be related using the receiver between the PC and the TV. As well as the fact that connected directly to the TV he only gets 720P while with the receiver he gets 4K implies some interaction there..

I’ll continue with the next steps soon, but I’ll clarify some things first.

Here’s a link to the exact cable I’m using, both into the reciever and into the TV. You’ll have to bear with Traditional Chinese, but I think the message should come across :joy:

Edit: Here’s the specs section in case it’s easier to translate here

產品規格

**產品型號:**HD2-1.5MX 真正支援4K(4096x2160)@60Hz
CEC(消費性電子控制)增強功能 Dual Viewing 雙影像同步顯示
Multi-Stream Audio 多語系獨立選擇 21:9 Aspect Ratio 影院級超寬比例
Dynamic Auto Lip-Sync人聲動態自動對嘴 支援支援HDR高動態範圍
高傳輸頻寬:18Gbps 音訊通道:32 channel
音源取樣率:1536kHz Color Space 色彩空間 4:2:0
抗電磁干擾 (EMI PASS) 向下相容1.4版HDMI 3D、HEC乙太網路、ARC音頻回傳

Also, the 720p picture came from an actual old 720-native TV that I have laying around from a decade ago. Funny how things like this come in handy.

Some TVs will report that they support 120 FPS/Hz, but that cable is only rated for 4K (4096x2160)@60Hz. Are you sure your PC isn’t trying to send a 120Hz video stream?

1 Like

The display is for sure set to 4K/60Hz, and the 4K TV is 60Hz as well.

1 Like

Jeff, here’s the info:

dnf list --installed \*nvidia\*

Installed packages
akmod-nvidia.x86_64                       3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
kmod-nvidia-6.18.3-200.fc43.x86_64.x86_64 3:580.119.02-1.fc43 @commandline
kmod-nvidia-6.18.4-200.fc43.x86_64.x86_64 3:580.119.02-1.fc43 @commandline
kmod-nvidia-6.18.5-200.fc43.x86_64.x86_64 3:580.119.02-1.fc43 @commandline
nvidia-gpu-firmware.noarch                20260110-1.fc43     updates
nvidia-modprobe.x86_64                    3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
nvidia-persistenced.x86_64                3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64                    3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia.x86_64                3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda.x86_64           3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.i686        3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64      3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64        3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.i686             3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64           3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64          3:580.119.02-1.fc43 rpmfusion-nonfree-nvidia-driver
inxi -Fzxx

System:
  Kernel: 6.18.5-200.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Fedora Linux 43 (KDE Plasma Desktop Edition)
Machine:
  Type: Desktop Mobo: Micro-Star model: B660M BOMBER DDR4 (MS-7D46) v: 1.0
    serial: <superuser required> Firmware: UEFI vendor: American Megatrends LLC.
    v: 2.11 date: 01/03/2022
CPU:
  Info: 10-core (6-mt/4-st) model: 12th Gen Intel Core i5-12600K bits: 64
    type: MST AMCP arch: Alder Lake rev: 2 cache: L1: 864 KiB L2: 9.5 MiB
    L3: 20 MiB
  Speed (MHz): avg: 800 min/max: 800/4900:3600 cores: 1: 800 2: 800 3: 800
    4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800
    14: 800 15: 800 16: 800 bogomips: 117964
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-S GT1 [UHD Graphics 770] vendor: Micro-Star MSI
    driver: i915 v: kernel arch: Xe ports: active: none empty: DP-1, DP-2,
    DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3, HDMI-A-4, HDMI-A-5 bus-ID: 00:02.0
    chip-ID: 8086:4680
  Device-2: NVIDIA AD104 [GeForce RTX 4070] vendor: Micro-Star MSI
    driver: nvidia v: 580.119.02 arch: Lovelace pcie: speed: 16 GT/s lanes: 16
    ports: active: HDMI-A-6 empty: DP-4,DP-5,DP-6 bus-ID: 01:00.0
    chip-ID: 10de:2786
  Display: wayland server: Xwayland v: 24.1.9 compositor: kwin_wayland
    driver: gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: HDMI-A-6 model: Denon DENON-AVAMP res: 3840x2160 hz: 60 dpi: 85
    diag: 1321mm (52")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: iris
    device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland:
    drv: nvidia x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.119.02
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
    display-ID: :0.0
  API: Vulkan v: 1.4.328 surfaces: N/A device: 0 type: discrete-gpu
    driver: nvidia device-ID: 10de:2786 device: 1 type: integrated-gpu
    driver: mesa intel device-ID: 8086:4680 device: 2 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Micro-Star MSI driver: N/A
    bus-ID: 00:1f.3 chip-ID: 8086:7ad0
  Device-2: NVIDIA AD104 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:22bc
  API: ALSA v: k6.18.5-200.fc43.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: N/A port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:1a1d
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 3.0 speed: 5 Gb/s lanes: 1 bus-ID: 2-2:2 chip-ID: 0bda:8153
  IF: enp0s20f0u2 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
  Device-1: TP-Link TP-Jd`+ Bluetooth USB Adapter driver: btusb v: 0.8
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-8.3:6
    chip-ID: 2357:0604
  Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.1
    lmp-v: 10
Drives:
  Local Storage: total: 6.43 TiB used: 3.06 TiB (47.5%)
  ID-1: /dev/nvme0n1 vendor: Seagate model: XPG GAMMIX S70 PRO
    size: 1.86 TiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 27.9 C
  ID-2: /dev/sda vendor: Western Digital model: WD4003FRYZ-01F0DB0
    size: 3.64 TiB speed: 6.0 Gb/s serial: <filter>
  ID-3: /dev/sdb vendor: Gigastone model: SSD 1TB size: 953.87 GiB
    speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 238.42 GiB used: 32.98 GiB (13.8%) fs: btrfs dev: /dev/sdb3
  ID-2: /boot/efi size: 953 MiB used: 19.4 MiB (2.0%) fs: vfat
    dev: /dev/sdb1
  ID-3: /home size: 238.42 GiB used: 15.5 GiB (6.5%) fs: btrfs
    dev: /dev/sdb4
  ID-4: /opt size: 238.42 GiB used: 32.98 GiB (13.8%) fs: btrfs
    dev: /dev/sdb3
  ID-5: /var size: 238.42 GiB used: 32.98 GiB (13.8%) fs: btrfs
    dev: /dev/sdb3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 1.86 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sdb2
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 64 GiB available: 62.58 GiB used: 7.2 GiB (11.5%)
  Processes: 488 Power: uptime: 1h 25m wakeups: 1 Init: systemd v: 258
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 15
    Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.40
cat /proc/cmdline

BOOT_IMAGE=(hd1,gpt3)/root/boot/vmlinuz-6.18.5-200.fc43.x86_64 root=UUID=24abe4f0-c0f8-408a-b01e-8797fc8ca16c ro rootflags=subvol=root rhgb quiet rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core
cat /etc/kernel/cmdline

root=UUID=24abe4f0-c0f8-408a-b01e-8797fc8ca16c ro rootflags=subvol=root rhgb quiet rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core

I made the change and went from all Y’s to

cat /sys/module/snd_hda_intel/parameters/enable 

N,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y

No change with the dropouts

1 Like

I didn’t have problems running 4K + audio on my PS5 with this setup, and I’ve gone through various cables and I haven’t seen any variation in the quality. It’s always been seamless.

Same when I ran Windows 10, again on the exact same hardware. Definitely true about the compressed nature of video saving information, but I’ve still watched 4K HEVC files with HD audio and it was butter smooth.

Zooming and smoothly panning high res photography with audio running in the background was the same. In that case, I think the display would have been rendering the whole image at 60Hz because there’s no frame-to-frame compression.

And from there, it’s the same with games. 4K resolution at a stable 60fps with none of these noticable drops.

Another quick example of this problem:

I opened Discover to track down MediaInfo, and the instant I clicked in the Discover icon, the music I was playing on Youtube cut for a few hundred milliseconds.

This is exactly the kind of thing that keeps happening. It’s very specific to these kinds of interactions with the desktop environment.

That’s why when I played FF7 last night, I had zero issues. I was just in the same window the whole time.

But at one point, out of curiosity I switched workspaces away from FF7, and at that exact instant, the audio dropped.

When I went back to the game after that, it was completely smooth.

I’m happy to put to rest any doubts about the hardware. I wouldn’t mind getting cables that are guaranteed to be rated for higher than what I need on my system. I’ll see if I have time tomorrow to go to a store and get cables that are used in competitive gaming, but if there are any specs I should particularly look for, do let me know and I’ll handle the Chinese translation. :joy:

But I hope you can see why I’m inclined to there being something something software-related, because this is very specific to trying out various linux distros.

1 Like