Can't Create Custom Resolution Using AMD Radion Software On Window$

Hello,

I have a dell U2711 monitor and I can’t get my computer with M$ Window$ and an AMD graphics card to output a 2560x1440 signal over HDMI to it!

I’ve tried creating a custom resolution using AMD’s AMD Radion Software and it tells me “The custom resolution settings are not compatible with this display. Reconfigure your settings and try again”.
Before anyone mentions it yes I know my display doesn’t report that it can do 2560x1440 @ 60Hz over HDMI, however it most definitely can!

I use the command cvt -r 2560 1440 under FreeBSD to generate a modeline and then use that modeline to create a new resolution using xrandr. Anyway it works fine doing that on FreeBSD / Linux.
I’ve read on another forum that someone managed to create a custom resolution for use with my model of monitor using Nvidia’s software. Anyway surely someone must have figured out how to do it using AMD’s software. It seems a bit ridiculous that when you go to create a custom resolution using AMD’s software that it wouldn’t let you just because the monitor doesn’t report that it can display that resolution!

Also I’m not interested in replies about the resolution “not being supported” by my monitor. As I’ve already stated it works perfectly fine when you send it the correct signal.

Anyway if anyone knows of any possible solutions I would very much appreciate it! :slight_smile:

I’ve never used it but Custom Resolution Utility (CRU) looks promising

1 Like

Hmm. I have tried to use that before and it didn’t seem to do anything. But IDK maybe I was doing something wrong. I’ll try it again but I’m not expecting it to work. Thanks for your reply though :slight_smile: .

I don’t think it’s working. That is I think I’m using it correctly but it’s not working.

What revision of HDMI does the monitor support? How about the GPU?

When you create the resolution, do you have the option of adjusting things like timings, polarity or (indirectly) pixel clock?

Well according to this (https://downloads.dell.com/manuals/all-products/esuprt_display_projector/esuprt_display/dell-u2711_user’s%20guide_en-us.pdf) it supports HDMI 1.3.
I use xrandr --newmode “2560x1440R” 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync and then xrandr --addmode HDMI-1 “2560x1440R” and then xrandr --output HDMI-1 --mode “2560x1440R” to get it to work on FreeBSD and it works perfectly fine. As I stated the reason I have to do this is because the monitor doesn’t report that it supports 2560x1440 over HDMI. But as I understand it HDMI is basically a passive interface and the monitor will try to display what you send it (although I guess that would be up to the firmware IDK.) Also the version of HDMI has enough bandwidth for it. Anyway it DOES work. I just don’t know how to / can’t get it to work on Window$. Honestly I’m not sure about all the timings and stuff. The modeline in the first command above should have all that information I think. But I’m don’t think CRU is working at all because I created a resolution and set it to use reduced blanking and then when I try to apply it the screen goes blank for a moment but then comes back in 1080p again and when I open back up the utility it seems to be set back to the default setting. But maybe I’m just not using it properly.

I have never managed to get an AMD GPU to use a custom resolution on Windows.

:confused:

Three characters :upside_down_face:

The card obviously supports the resolution since it works in FreeBSD so you’re just needing to force a resolution that the monitor’s firmware doesn’t support. Microsoft has a pretty dizzying article on how display mfg’s can override the EDID values in eeprom by creating an inf patch. But it honestly hurts my brain even thinking about trying create a patch to trick Windows into believing your monitor can do 1440p. I think this is what the CRU tool was suppose to do as a front-end tool but obviously they weren’t implementing something correctly. I believe this is the fix but I’m not now sure how to implementing it in a practical way without a lot of pain.

CRU adds the option to the windows registry, you still have to set it in windows display properties.

Hmm, okay thanks :). I’ll try doing that.

This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.