Video summary

Elgato 4K60 Pro (Mk.2) on Linux

Main summary

Key takeaways

Technology

Overview

Support for the Elgato 4K60 Pro (Mk.2) on Linux is provided via a community-made PCIe capture driver, because Elgato/Aver Media don’t offer Linux-specific PCIe drivers. The tutorial covers installation/management of the driver, performance testing, and current Linux limitations.

What’s covered / key tutorial steps (technological workflow)

Why this is needed on Linux

  • USB capture cards typically work well on Linux thanks to widely compatible UVC drivers.
  • PCIe capture cards (like the Elgato 4K60 Pro) usually require dedicated drivers that are often missing on Linux.

Community driver installation (one-line script)

The walkthrough references a GitHub script that:

  • Downloads and builds the driver for the Elgato 4K 60 Pro Mark II
  • Adds the driver to the kernel
  • Loads the driver at boot
  • Enables use in OBS Studio and GUVC View
  • Supports multi-app usage simultaneously

Note: The script is likely not compatible with the original (non-Mk.2) model (not tested).

Kernel conflict handling

  • The installer may require a step to ignore kernel conflicts, because it expects an Arch-like kernel, not a specific distro/kernel variant.
  • A reboot after installation is recommended.

Driver management / diagnostics

Driver status and management are handled using SC0710-CLI, including:

  • Checking driver status
  • Rebooting the driver
  • Other maintenance/management tasks

Performance / review-style findings

Once running, the uploader was able to capture:

  • 1080p 60
  • 4K 60
  • PC and console sources with minimal issues

Supported resolution/fps modes that worked well on Linux

  • 4K 60
  • 1440p 144 Hz
  • 1080p 240 Hz
  • 1080p 60 Hz

A mode that didn’t work as expected

  • 1080p 120 Hz
    • Detected/pass-through in Windows
    • In Linux, capture programs couldn’t see a video feed (even though the card supports it)

Current Linux limitations called out

HDR is not supported

  • No HDR pass-through with automatic tone mapping to SDR, because the developer hasn’t reverse engineered the required onboard commands.
  • HDR capture also fails in required color spaces (P010/P016) due to missing hardware register map support.

EDID / monitor mode switching is not supported

  • The Linux driver cannot change EDID modes (the advertised supported formats).
  • This can cause problems when the card is configured using a different monitor’s EDID.
    • Example: a Dell 1080p 240 Hz EDID not matching the user’s display.
  • In Windows, the 4K Capture Utility can:
    • Use internal EDID vs plugged-in display EDID
    • Merge them
    • Import custom EDID profiles

Implication: Windows may still be needed at least for EDID/profile setup.

Resolution/frequency switching caution

  • When changing resolutions, close capture software first to avoid possible kernel panic or driver stalls.

Stability comparison with Windows

  • Windows reportedly showed “weird” refresh-rate/mode mapping issues during EDID switching (e.g., 59.94 Hz mapping incorrectly to other modes).
  • Those specific issues reportedly didn’t happen on Linux after configuration.

Recommendation / conclusion

  • If you’re buying specifically for Linux today, the uploader suggests alternatives like:
    • Magewell
    • USB capture cards (since USB cards now support 4K60)
  • If you already own the Elgato 4K60 Pro Mk.2 and it’s keeping you on Windows, the Linux driver approach is presented as worth trying.

Main sources / speakers

  • Primary source: The video uploader/narrator (author of the Linux driver walkthrough and personal testing)
  • Secondary source: The community GitHub repository containing the build/install script for the Elgato 4K60 Pro Mark II Linux driver
  • Tools mentioned: SC0710-CLI, OBS Studio, GUVC View, and the Elgato 4K Capture Utility (Windows EDID/profile tool)

Original video