HDMI 2.1 Linux Support: AMD, NVIDIA and Intel in 2026
Table of contents
HDMI 2.1 on Linux works in late 2026, but how well depends on your graphics card. NVIDIA’s proprietary driver has handled HDMI 2.1 Fixed Rate Link (FRL) for years. AMD’s open-source amdgpu driver was blocked by the HDMI Forum in 2024, got FRL in Linux 7.2 with the feature switched off by default, and Linux 7.4 turns it on along with HDMI VRR and ALLM. Intel’s native HDMI 2.1 code for Linux was still in review. If your setup falls short, DisplayPort or an active DisplayPort to HDMI 2.1 adapter gets you to 4K 120Hz today.
Why HDMI 2.1 is a special problem on Linux
HDMI 2.1 is a problem on Linux because its full specification is private. Only members who license it from the HDMI Forum can read it, and the Forum sets the terms for how drivers may use it. That clashes with an open-source kernel driver, where every line of code is public.
The part that matters most is FRL. HDMI 2.0 sends video with an older method called TMDS, which tops out at 18 Gbps. HDMI 2.1 adds FRL, which carries up to 48 Gbps. A 4K signal at 120Hz with full 8-bit color needs more than HDMI 2.0 can carry, so without FRL the driver either drops to 60Hz or squeezes the color to fit.

DisplayPort has no such restriction on open drivers, which is why it has carried 4K at 120Hz and above on Linux for years.
HDMI 2.1 on AMD Linux: what changed in 2026
AMD Radeon cards on Linux can now use HDMI 2.1, after a two-year standoff. Here is the short history, with dates.
- February 2024: AMD engineer Alex Deucher wrote that the HDMI Forum had rejected AMD’s proposal, and that an open-source HDMI 2.1 implementation was not possible at that time without breaking the Forum’s requirements. Radeon cards on Linux stayed at HDMI 2.0 speed.
- May 2026: AMD posted new HDMI FRL patches for amdgpu, later revised to add Display Stream Compression (DSC) over FRL. AMD said the code had passed a representative part of HDMI compliance testing, with a full run in progress. AMD and the Forum have not published the terms that cleared the way.
- Linux 7.2 (mid 2026): The first FRL code was merged, but switched off by default. AMD held it back until HDMI variable refresh rate (VRR) support was ready, so users would not lose features they had over HDMI 2.0.
- Linux 7.4 (late 2026): The 7.4 graphics pull adds HDMI VRR, FreeSync over HDMI 2.1 and ALLM (auto low latency mode, which tells a TV to switch to game mode), and turns FRL on by default. Kernel.org listed 7.4-rc2 on November 9, 2026, so the final release is close.
On Linux 7.2 and 7.3, you can turn FRL on yourself through the amdgpu dcfeaturemask option. The amdgpu module parameters page describes that option as an override for display features. The FRL bit is 0x400. Read your current value with cat /sys/module/amdgpu/parameters/dcfeaturemask, add 1024 (0x400) to it, and set the result as a kernel option, for example amdgpu.dcfeaturemask=0x402 when the default is 0x2. Rebuild your initramfs if your distro loads amdgpu early, then reboot.
Keep two limits in mind. On 7.2 and 7.3, HDMI 2.1 VRR and ALLM are missing, since they only arrive in 7.4. And distro kernels can differ from mainline, since some distros enable or disable the feature themselves, so check the value on your own system after every kernel update. Once you move to 7.4, remove your override and test the new default first.
HDMI 2.1 on NVIDIA Linux
NVIDIA cards are the easy case. NVIDIA’s proprietary Linux driver has run HDMI 2.1 FRL displays since at least early 2021. The 460.39 release notes, dated January 26, 2021, already list a fix for link training on HDMI 2.1 FRL displays. GeForce RTX 30 series and newer cards have HDMI 2.1 ports, and with the proprietary driver they can run a 4K 120Hz TV or monitor over HDMI.
NVIDIA’s open kernel modules work the same way. Much of the HDMI 2.1 logic runs inside the GPU System Processor (GSP) firmware rather than in the public kernel code, so the open modules sidestep the problem AMD had.
The fully open drivers are behind:
- Nouveau, the community driver, got HDMI FRL patches from Red Hat’s David Airlie in April 2026. They rely on GSP firmware, so they target newer GPUs. Check your kernel’s changelog before you count on them.
- Nova, the Rust driver being built to replace Nouveau on newer NVIDIA GPUs, was not ready for everyday use in 2026. Display support was still on its to-do list.
The proprietary driver also supports G-SYNC Compatible VRR. Check the README for your driver version for the exact HDMI VRR rules, since they have changed over time. Our guide on using a FreeSync monitor with an NVIDIA GPU covers how that pairing works.
HDMI 2.1 on Intel Arc and Linux
Intel Arc is a mixed picture, because Intel’s GPUs have handled HDMI 2.1 in two different ways.
The Arc A-series (Alchemist) GPUs support HDMI 2.0 natively. Intel’s Arc HDMI explainer says its own Limited Edition A750 and A770 cards add HDMI 2.1 through a PCON, a chip on the card that converts a DisplayPort signal into HDMI 2.1. Partner cards and laptops have HDMI 2.1 only if their maker added that chip. Because the GPU only sends DisplayPort to the chip, this route avoids the Linux FRL problem. Intel’s kernel developers added code for training these PCONs at HDMI 2.1 speed back in 2020 and 2021.
Newer Intel graphics have native HDMI 2.1. Intel lists HDMI 2.1 for the Arc B580, for example. But Intel’s native FRL code for Linux, covering Meteor Lake and newer graphics, was still marked a work in progress in August 2026 and not merged. Until it lands, use DisplayPort on these chips if you need 4K above 60Hz on Linux, to be safe.
Workarounds that work on any driver
If your driver or kernel cannot do FRL yet, you have three practical options.
Use DisplayPort when the screen has it
DisplayPort is the simplest fix for a monitor. DisplayPort 1.4 carries 4K at 120Hz with 8-bit color uncompressed, and higher refresh rates or 10-bit color with DSC. Every major Linux GPU driver supports it, along with Adaptive-Sync. Most PC monitors have at least one DisplayPort input, and our monitor connection guide explains which port to use.
Use an active DisplayPort to HDMI 2.1 adapter
Most TVs have no DisplayPort input, so an active adapter is the main fix for a TV. The adapter takes DisplayPort from your GPU and does the FRL work itself, so the Linux driver never has to speak HDMI 2.1.
Two models are well known:
- Cable Matters 102101: the manual lists up to 8K at 60Hz and 4K at 240Hz. It needs a GPU with DisplayPort 1.4 and DSC, plus a certified HDMI 2.1 cable. The manual states that VRR, G-SYNC and FreeSync are not supported.
- Club3D CAC-1085: released in 2020, it converts DisplayPort 1.4 with DSC into HDMI 2.1 for 4K at 120Hz with HDR. Club3D lists no FreeSync or G-SYNC support.
So you trade VRR for refresh rate. Behavior can also change between adapter firmware versions, so buy where returns are easy and keep the adapter’s firmware tool handy.
Accept 4:2:0 chroma at 4K 120Hz
4:2:0 chroma subsampling is how a 4K 120Hz signal fits inside HDMI 2.0. Each pixel keeps its own brightness, but color is shared across a block of four pixels. That cuts the data enough to squeeze 4K 120Hz under the old 600 MHz HDMI 2.0 limit.

For games and movies on a couch, 4:2:0 is hard to spot. For a desktop it is a poor fit. Small text gets soft, thin colored lines fringe, and the signal usually runs in limited range, which can make blacks look gray. If your blacks turned gray at 4K 120Hz after a kernel update, a silent fallback to 4:2:0 is the likely cause.
How to check what your HDMI link is doing
A few commands tell you most of what you need.
- Mode and refresh rate: on X11, run
xrandr --verboseand look for a3840x2160line with120marked as active. On KDE Plasma, Wayland or X11, runkscreen-doctor -o. Our guide to checking your monitor’s refresh rate covers the desktop settings too. - AMD FRL setting:
cat /sys/module/amdgpu/parameters/dcfeaturemaskshows the feature mask in decimal. If 1024 is part of the value (for example 1026), FRL is allowed. - AMD bit depth: with root,
cat /sys/kernel/debug/dri/0/HDMI-A-1/output_bpcshows the bits per color the driver is sending. Your connector name and card number may differ. - Kernel version:
uname -rtells you whether you are on 7.2, 7.3 or 7.4.
A 120Hz mode in the list does not prove you are getting full color, since 4:2:0 also gives you 120Hz. The best final check is the display itself. Many TVs show the incoming signal format, such as RGB or YCbCr 4:2:0, in an info or HDMI signal menu.
Using a TV as a monitor on Linux
TVs are where HDMI 2.1 on Linux matters most, because almost none have DisplayPort. A 4K 120Hz TV on HDMI 2.0 speed gives you 4K 60Hz in full color or 4K 120Hz in 4:2:0, and neither is ideal for a desktop.

Before you blame the driver, check the TV. Most TVs only accept HDMI 2.1 signals on certain ports, and many need an enhanced or input signal plus mode turned on for that port. Set the input to PC or game mode so the TV does not add processing lag, which our guide to input lag on monitors explains. Use a cable certified as Ultra High Speed, since an older High Speed cable can cap you at HDMI 2.0.
For VRR, Linux 7.4 brings HDMI VRR and FreeSync over HDMI 2.1 to AMD, and it can drive TVs certified for HDMI Forum VRR. The adaptive sync guide explains how VRR ranges work.

TVs also have trade-offs as desk monitors that no driver fixes, such as size, viewing distance and burn-in risk on OLED. Our list of the disadvantages of using a TV as a computer monitor covers them. If your screen is a touch display on Ubuntu, the Ubuntu touch screen monitor guide handles the input side.
Which setup to choose
| GPU and driver | 4K 120Hz over HDMI | HDMI VRR | Best route |
|---|---|---|---|
| NVIDIA, proprietary or open modules | Yes | Check driver README | Native HDMI 2.1 |
| NVIDIA, Nouveau | Patches posted 2026 | Not yet | Proprietary driver or DisplayPort |
| AMD, Linux 7.2 and 7.3 | Yes, with dcfeaturemask | Not until 7.4 | Override, or DisplayPort |
| AMD, Linux 7.4 | Yes, by default | Yes, HDMI VRR and FreeSync | Native HDMI 2.1 |
| Intel Arc A-series with PCON | Yes, through the PCON | Varies by card | Card's HDMI 2.1 port or DisplayPort |
| Intel with native HDMI 2.1 | Not until FRL code is merged | Not yet | DisplayPort |
Conclusion
HDMI 2.1 on Linux is finally real on all three GPU brands, though at different stages. NVIDIA’s proprietary driver works today. AMD needs Linux 7.4 for FRL, VRR and ALLM by default, or a manual dcfeaturemask override on 7.2 and 7.3. Intel’s native support is still coming. If you need 4K 120Hz in full color right now, use DisplayPort for a monitor and an active DP to HDMI 2.1 adapter for a TV, and confirm the signal format on the display. For more connection help, browse our setup guides or the full SubInsider monitor knowledge base.
Frequently asked questions
Does Linux support HDMI 2.1?
Yes, but it depends on your GPU driver and kernel. NVIDIA's proprietary driver handles HDMI 2.1 FRL. AMD's open amdgpu driver has FRL from Linux 7.2, off by default until Linux 7.4. Intel's native FRL code was still in review in 2026. Without FRL, HDMI tops out at HDMI 2.0 speeds of 18 Gbps.
Why did the HDMI Forum block AMD on Linux?
The HDMI 2.1 specification is private, and the HDMI Forum controls how it can be implemented. In February 2024, AMD said the Forum had rejected its proposal for an open-source HDMI 2.1 driver. AMD kept working on it, and FRL patches reached the kernel mailing list in May 2026 after passing part of HDMI compliance testing.
Why is my Linux PC stuck at 4K 60Hz over HDMI?
The HDMI link is running at HDMI 2.0 speed. That happens when the driver has no FRL support, when FRL is turned off by default, or when the cable or TV port is not HDMI 2.1. Check your kernel version, the amdgpu dcfeaturemask value on AMD, and that the TV port is set to its enhanced signal mode.
Do DisplayPort to HDMI 2.1 adapters work on Linux?
Often, yes. An active adapter such as the Cable Matters 102101 or Club3D CAC-1085 does the FRL work itself, so the Linux driver only has to send DisplayPort. Both makers list 4K 120Hz support but no VRR. They also need a GPU with DSC over DisplayPort 1.4, and results can vary with adapter firmware.
Is 4:2:0 chroma at 4K 120Hz bad for a desktop?
For games and video it is usable, but small text looks soft and colored edges can fringe. 4:2:0 keeps full brightness detail but shares color between blocks of four pixels. It also tends to run in limited range, which can turn blacks gray. For a desktop you read all day, full RGB or 4:4:4 is much better.