Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
I have a RX 6800 XT connected to a LG B9 TV via HDMI. As both these devices are HDMI 2.1, I should be able to send a 4k 120hz signal. However 120hz support is only available for 1440p resolution, and only 60hz is available for 4k. This is the case for both Wayland and Xorg.
AMD has the Kernel patches but cannot merge them into the Kernel because they didn't secure the license deal. That's fine. Can't we create our own patch? We can, just somebody has to develope the code and then share it on a forum somewhere.
I have the same issue with an RX 6800 graphics card and an LG C1 TV.
I can transmit 4K @ 120Hz but it gets transmitted in YCbCr 4:2:0 (which is within HDMI 2.0 specs) instead of YCbCr 4:4:4 or RGB.
Could the AMDGPU driver be utilizing only TMDS and not the new FRL (Fixed Rate Link) transmission protocol required for the new HDMI 2.1 signals?
I can transmit 4K 10bit Full RGB @ 120hz on Windows with no problems.
That's worrying. What are the plans for this? Linux being stuck at HDMI 2.0 forever is not a viable option.
How is Nvidia, Intel, and other GPU vendors tackling this?
Intel's drivers are also fully open-source, am I correct?
If that is the case, I am curious to see what comes out of this, as it is inconceivable for Intel to just drop further HDMI support.
There is no closed source AMD display driver. The same open source kernel driver is used by the open source user mode drivers and closed source user mode drivers.
Somewhat off topic, but do you know if DP to HDMI 2.1 adapters are supposed to work on Linux+AMD now? I've got the Club3d CAC-1085 (which afaik is the only DP 1.4 to HDMI 2.1 adapter on the market) and it still only does 4k60 4:4:4 on Linux on Fedora 36 beta (with kernel 5.17 that contains that patch, a 6800xt, and an LG CX with a certified cable that does 4k120hz 10bit 4:4:4 on Windows).
I would be surprised if this would actually add FRL support for even just the Club3D adapter (I have one too). I believe this is one of the parts that is not allowed to be implemented by the HDMI forum in an open-source driver. Hence why NVIDIA and probably Intel will not add proper HDMI 2.1 support in Linux. Me and others shared a fair bit of critique on NVIDIA for not adding HDMI 2.1 support in their proprietary binary-only driver on Linux even though they are allowed to. I even bought an RTX 3700 just to give this a try.
For now I have given up on HDMI 2.1 / FRL support on Linux and will wait on the next iteration of graphics cards with DisplayPort 2.0 and possibly an adapter. Read about some already being developed and other than the DP 1.4 -> HDMI 2.1 adapter, DP 2.0 has a lot more bandwidth than HDMI 2.1 so I hope for a proper adapter this time.
I don't know about the upcoming DP 2.0->HDMI 2.1 adapters, but the existing DP1.4->HDMI 2.1 adapter doesn't support VRR. No idea about the latency though.
Yeah I'm in much the same boat. Bought a 6800xt then afterwards bought a LG C1 HDMI2.1 screen to only discover this issue. ATM Linux will default support back to CYB420 which is HDMI2.0 mode of poorer quality then RGB.
If you force RGB mode it can only do 4k@60hz instead of 120hz as desired.
I know some HDMI2.1 code has landed in the NVIDIA open-source drivers somehow; not sure what will happen with that. Either HDMI2.1 forum license guys change it to allow open-source support or they sue NVIDIA (which would be entertaining for sure)
HDMI2.1 needs to support use in Open-Source drivers!!!
Depending on what happens, my next GPU will likely be a RTX4080 (if HDMI2.1 gets support) as I don't want to deal with this crap no more!
PS. I've tried DP to HDMI2.1 adapters and it only gets you 4k@60hz RGB modes; IF they even work at all!!!
its not optimal in any way or shape .... but i got the club3d dp1.4 to hdmi adapter, and my 6700xt and LG C1 seem to behave better ... i can get 120hz rgb444 ... no VRR and the amd memclk is always max ...but text looks sharper ... way way better looking chroma subsampling test image now.... i still hope amd finds a way to enable hdmi2.1 support .....
I can confirm that with the latest 1.07 firmware, the Club3d CAC-1085 works on linux at 4k120hz 4:4:4 with a 6800xt. You need to contact Club3d's support to get the new firmware, and you'll have to use Windows to update the firmware, but it does finally work now (at least, it worked for me on Fedora with kernel 5.18.something).
Wait, is there more information about that anywhere? Where can I read about it?
Did AMD put the licensed HDMI code on the firmware instead of the drivers?
I have an MSI RX 6800 and I hope I get a similar firmware update.
Oh my bad, I read it wrong. I thought his graphics card had gotten a firmware update that implemented the closed part of HDMI 2.1.
There is no HDMI2.1 for AMD open-source drivers, and likely never will be.
Neither for Intel. But it's a bit hard to believe that the both Intel and AMD will drop support for future HDMI versions and won't coerce the HDMI forum to allow at least the FRL mode. Together they are by far the largest share of PC HDMI vendors.
all i know is that i got sick of tinkering and while i did get 4k120hz in rgb444 with the adapter ... i kept having moments where it will dump lots of kernel errors and I'll have to reboot .... so ...i got a rtx3070 ... 4k120hz rgb444 was what it did by default ..with vrr enabled and working ... it took about 1/1000 of the time i spend to get my 6700xt to sort of work ... i guess I'm giving up on amd gpus for now ... if nvidia can make hdmi2.1 work ...in their open source driver ... AMD can surely find a way
no clue - i compiled this: https://github.com/NVIDIA/open-gpu-kernel-modules/ .... it is very likely that they have a huge binary blob in there ... but how does that change anything ? One driver worked and the other did not... on top of that all my resume from sleep issues went away ... and that is after i spend what feels like years making my 5700xt and then 6700xt work. I want to use amd cards, hence all the effort i put and i know that the eng team does all that they can and are more than capable, but at the end it did not work even after paying premium (more $ than nvidia and way more time spend). just fyi - i had rgb444 issues with my old-er displayport monitor too ... had to spend hours messing with custom edid and kernel patches, so its not just the hdmi2.1 issue.
The day has finally come: NVIDIA IS PUBLISHING THEIR LINUX GPU KERNEL MODULES AS OPEN-SOURCE! To much excitement and a sign of the times, the embargo has just expired on this super-exciting milestone that many of us have been hoping to see for many years.
NVIDIA now provide both an open and closed kernel driver. Their userspace drivers remain closed source, but those are irrelevant, because the kernel driver(s) are what handle HDMI support. No, no one here is referring to Nouveau. These are official, Nvidia kernel drivers. And as several people have pointed out, the OPEN NVIDIA GPU Kernel driver seems to support HDMI 2.1. @amd_user literally posted a direct link to the very line in the code.
@agd5f can a vendor implement FreeSync on top of HDMI 2.1 so that it works with amdgpu? I'm asking because I just connected my Samsung TV (GQ75Q70AATXZG) with my 6800 XT and both 4k 120Hz and FreeSync somehow work fine...
Could you be doing 4k 120Hz at HDMI 2.0 bandwidth using chroma subsampling? Since it's a bandwidth problem, reducing color information lets the system do higher refresh rate with the same bandwidth.
Additionally, I've found Wayland will typically automatically do this if asked to do an impossible bandwidth. In Gnome on Wayland for example, you just configure it to use the higher refresh rate and it automatically switches to 1:2:4 chroma subsampling without saying anything about it.
The text is all equally clear with no chroma subsampling, but some of the text can get very jumbled if it is enabled.
For FreeSync - I believe FreeSync is just straight up supported on HDMI 2.0. It doesn't use the dedicated VRR protocol, but it's existed and worked on HDMI since before that existed.
Some of the text does look fuzzy. What confuses me about it is that I just tested the HDMI 2.0 ports on the TV and with those I only get 60Hz ¯\_(ツ)_/¯
Additionally, I've found Wayland will typically automatically do this if asked to do an impossible bandwidth
The compositor has no influence over that yet. The driver does that - if you use the modesetting driver on Xorg, it should do the same.
What confuses me about it is that I just tested the HDMI 2.0 ports on the TV and with those I only get 60Hz
@Zamundaaa Your TV most likely has a different EDID for the HDMI 2.1 and 2.0 ports. The 2.0 ports probably don't advertise any 120hz capability.
And yeah, if the text looks fuzzy, you're probably outputting YCbCr with chroma subsampling, which is another issue in itself, discussed here: #476
You can force RGB by editing your EDID and removing the YCbCr capability, but you won't be able to do 120hz. But!! You might want to take a look at this: #1417 (comment 1552622)
Can anyone here explain what he's doing exactly? Is he going out of spec? Do those code changes perhaps trigger the card's firmware to change to FRL instead of TMDS? The TV states he is in TMDS mode though.
How risky is this? Are we risking frying anything, or would this just give us an unstable connection at worst?
I'm surprised the TV is accepting the signal at all.
Current Intel Arc Graphics (DG2/Alchemist) only natively support HDMI 2.0 but HDMI 2.1 can be an option with some of the cards where the board vendor chooses to use a PCON for converting a DisplayPort 2.0 output from the GPU to an HDMI 2.1 interface. But now for Meteor Lake integrated graphics (and presumably for DG3/Battlemage) there will be native HDMI 2.1.
So probably proprietary firmware, I doubt it'll work for DG3 though since it'll be native 2.1.
Is there any technical limitation on the RX 6000 cards that stops AMD from doing the same Intel and Nvidia are doing?
AMD will become the only GPU vender without HDMI 2.1 FRL support on Linux.
There is 1 company that has or is making a DP2.0 to HDMI 2.1 adapter with VRR and HDR but I forgot their name. They are using a NEW chip to do it so supply is probably awful. I wouldn't be surprised if the adapter costs $100 or more.
There was a few articles about it I found via Google Search. Never followed up on it as that was while ago.
Could be that PS196 thing... but again, I don't see anyone selling anything. Must be quite an exclusive item to get your hands on. Also you need a DP2.0 card afaik....
Well if your display setting is below 32.4Gbps (DP1.4 max) it should be fine. But these new adapters may not quite function that way, won't know until they become available.
First, none of us are AMD, so I don't think that's super relevant.
Second, though, why wouldn't that work for 4k 120hz? DisplayPort 1.4 fully support 4k 120hz, even without DSC. As long as you have a connector that car convert DP 1.4 to HDMI of equivalent bandwidth, 4k 120hz is definitely possible.
DP 1.4 can even do 4k 144hz if using DSC (which is a lossless compression).
DP 2.0 is only needed if you're going for 8k 144hz.
@nfp0 Yeah same boat. Basically if you have Intel or NVIDIA card you get HDMI2.1 no problem.
If we run the display it pushes it to 4:2:0 as we all know in order to achieve 120hz at 4k setting on AMD.
I have not been using Linux for a while mainly for this reason. I do intend to buy a 4090 at some point and be done with all the issues, but who knows how bad 2023, maybe all stock will go poof, maybe prices will triple... anything goes at this point.
@daboross I was under the impression AMD reads these issues here. Am I wrong?
And yeah, you're right. DP 1.4 is enough for 4K@120hz at 8bpc. I was checking the Wikipedia table for HDR (10bpc).
Then an adapter would mostly work. But I don't know any that supports VRR.
@Riddick I'll email AMD support complaining. Do the same. The more the merrier.
They should not advertise this feature if they can't fully support it.
@nfp0 Have you tried their AMD PRO driver suite off the website? does it have working HDMI2.1?
I've only tried the Encoder/Vulkan component of it not the full driver itself.
Here we are all talking about the lack of support for HDMI2.1 in MESA drivers which isn't the only option.
Basically if AMD supports HDMI2.1 in their closed or own drivers via their website then they technically are giving support.
But I've been so long out of the loop with their own drivers that I have no idea if AMDGPU-PRO or whatever it is on their website supports 2.1 (NOT amdvlk driver, that is separate thing).
UPDATE: I checked, looks like there may not be a option since AMDGPU-PRO works on top of Kernel driver which is open-source. So your right AMD provides no method for HDMI2.1 under Linux which is EXTREMELY BAD! They need to change all their advertisement to say HDMI2.1 (Windows ONLY).
@ironashram That looks promising as it does indeed use the PS196. It is usb-c however, and therefore only DP 1.4
Would probably work if I could confirm that it supports VRR...
I guess we'll have to wait for a while. Until HDR is supported on Linux I don't really need a solution to this issue. Hopefully AMD has fixed this by then, or a generally available adapter exists.
@bernharl It should as its using USB-C DP1.4 Alt-Mode.
But what color options do you get at 4k 120hz is the question, is it 8bit 444 or 10bit 444, what about HDR enabled at same time?
Lots of questions and unfortunately often you don't truly know until somebody technical buys one and tries it.
DP -> HDMI adapter
I would buy one in a heartbeat if I can find one that supports VRR. Anyone knows one?
@nfp0 I don't think it's possible to support VRR easily with DP -> HDMI2.1 because VESA adaptive sync (used by DP) is a different protocol to HDMI 2.1 VRR (and freesync over HDMI is different again).
The adapter itself would need to convert it, and that would add complexity/cost. Hopefully the Paradetech chip does became a real thing, although I suspect it will indeed be quite expensive.
It should as its using USB-C DP1.4 Alt-Mode. But what color options do you get at 4k 120hz is the question, is it 8bit 444 or 10bit 444, what about HDR enabled at same time?
I've only tested on Windows so far but this adapter supports everything but VRR (4k@120hz, 10-bit 4:4:4, and HDR) although I had to force enable 10-bit for HDR when normally it would enable it on it's own.
As someone already said, there is no such thing as a proprietary AMD GPU kernel driver. The PRO drivers only contain proprietary USERSPACE (OpenGL, Vulkan, OpenCl) components. It still uses the FOSS amdgpu kernel driver.
The kernel driver is what handles all resolution/refresh rate/display protocol stuff. There is no workaround.
So your right AMD provides no method for HDMI2.1 under Linux which is EXTREMELY BAD! They need to change all their advertisement to say HDMI2.1 (Windows ONLY).
@Riddick They really don't, though. Every single retail page for every single GPU, motherboard, CPU, etc use "PC = Windows." Even though that's not actually true, it doesn't matter because the overwhelming consensus is that PC = Windows. Linux is never mentioned, except VERY rarely.
Go look at the official web page for your motherboard. Look at the specs and see what OS it says it supports. I almost guarantee it will only say Windows 10/11 (or just Windows). I've never owned a motherboard that has its webpage mention Linux. That's just the way things are.
@daboross I was under the impression AMD reads these issues here. Am I wrong?
It's a bit late, but I wanted to say: you're right. I was wrong here, and under the wrong impression about this repository and its issues.
The fact that this is explicitly the place for community feedback to AMD makes it even more puzzling that, as far as I can tell, no one from the AMD team has acknowledged nor commented on any way to fix this.
no one from the AMD team has acknowledged nor commented on any way to fix this.
@daboross there isn't any way currently for the user to fix this. And the only open driver that supports HDMI 2.1 uses a hardware-level DP -> HDMI converter, so it might not be possible unless a firmware only implementation is legally and technically viable.
Nevertheless, I agree that this issue tracker seems to only be monitored sporadically which is unfortunate. You might try asking on Phoronix as there are a few people from AMD that hang out there. Or try on /r/AMD.
there isn't any way currently for the user to fix this.
Right, yeah - I mean them commenting on if/when they can fix it.
firmware only implementation is legally and technically viable.
This is the route I'd expect if they do fix it. Nvidia does this, in my understanding, though to a much greater extent - their current official open source driver delegates nearly everything to firmware.
I don't know if Nvidia also has a hardware DP->HDMI converter, but if they don't, then I would expect that's a good proof for the legality of the firmware approach? Only question is how easy it is to integrate that into AMD's driver structure and if whatever runs their firmware blobs is powerful enough to do that.
@nfp0 I don't have a nvidia gpu to test but it appears the open kernel drivers are not the default and don't support all features (including G-Sync). See here:
However, in the current release, some display and graphics features (notably: G-SYNC and SLI), as well as power management, and NVIDIA virtual GPU (vGPU), are not yet supported.
So it's hard to say whether they actually support HDMI 2.1, particularly if users are actually using the prop. stack when they think they are using the open one. Users with Nvidia cards would need the follow the instructions above, as well as having a recent enough GPU, access to HDMI 2.1 display, and ability to verify it's using 4:4:4 and not chroma subsampling.
@nfp0 AMD's code also has references to FRL from a quick grep, although it's not clear if it's only for DP -> HDMI without reading more deeply. More references are in recent DCN so maybe that's an indicator of recent/future support (I'm not sure what gen DCN31 maps to). There's also some recent commits in the staging kernel indicating support for Freesync over PCON (DP -> HDMI converter presumably) which is interesting.
Anyway, that looks like some kind of support for Nvidia. I'd like to see confirmation of it actually working but I'll assume it's working for now.
Just a quick update for those desperate to resolve the subchroma issue 4k@120. I can confirm that after several different approaches to try and work around this (including using an ARC/Nvidia card as a scanout card with the RDNA rendering; with limited success, and a direct 8K Displayport->HDMI2.1 cable as pictured above) the working combination I have is to use the motherboard displayport in from the RDNA2/3 output, and a Thunderbolt4/USBC DP Alt mode adaptor. - This one specifically https://www.amazon.com.au/dp/B08MSWMXT4?ref_=pe_19115062_429603572_302_E_DDE_dt_1
I was surprised that out of the box even VRR and Freesync premium syncs and works via this pathway. Which I am guessing is a by product of the DP in on the motherboard (Asus Proart X570) as other reviewers have stated they cannot use VRR with the same adaptor.
Technically they can just support freesync which should be same on both DP and HDMI2.1
My understanding is that they are not the same, but I've found scant documentation on the protocol(s). Probably just looking at the source code would be the simplest way. You'd also think that freesync over DP -> HDMI2.1 would just work if the protocols were the same, but I could be wrong. If they are different, I wonder if a non-standard DP output could be sent from the source, using freesync-over-hdmi instead of freesync-over-dp.
As an aside, it seems that Intel's new GPUs don't actually support HDMI 2.1 through firmware, but through a dedicated DP1.4 -> HDMI2.1 chip. I've seen mixed views as to whether VRR/freesync actually works on those cards but if so, it would indicate it's possible and hopefully we get converters in the future (as well as being included on new AMD GPUs to sidestep this nonsense).