Anyone runnig 2560x1440 on X5000 ?

[Oldsmobile_Mike]

.
I see these Dual Link cables online but confusing as they have like a Y cable with two DVI ends and one HDMI end.  My 7750 only has 1 DVI port so...

That is not a dual link DVI cable. Go to Wikipedia, it explains the difference. Long story short, dual link has more pins. I don't have any experience with an Amiga at this screenmode but have had similar problems with a PC - the higher resolution screenmode did not become available in display prefs until I switched to the correct cable. Even HDMI didn't work because with the particular monitor I was using (a 27" Dell display) it had a maximum input resolution of 1920x1080 through its HDMI port. A limitation of that particular model which was only resolved by using the correct cable. Good luck!

[Hans_]

In fact, when I have Auto Detect on, I only get PAL 640x480 and BootVGA:Productivity modes appear and my X5K only boots to a very LARGE 640x480 .

That sounds like a faulty cable to me, although you've already tested it with two cables. Or, perhaps you made a mistake when setting the monitor's tool-types (HINT: ScreenMode prefs has a Monitors tab for this). BOOTVGA remains if the auto-detection either doesn't happen due to bad settings, or the monitor's DDC data couldn't be fetched.

I see these Dual Link cables online but confusing as they have like a Y cable with two DVI ends and one HDMI end.  My 7750 only has 1 DVI port so...

I just looked up your monitor's specs. Forget about dual-link DVI cables. Yours is an HDMI monitor, and it's single-link.

Hans

[amigasociety]

Yeh, tried two different HDMI to HDMI cables and also one DVI-D (single link) to HDMI cable.  Not sure if I buy a DVI-D (Dual Link) to HDMI if that would change anything for me.

Per DVI Wiki it tells me this:

"Dual link DVI adds six additional pins (located in the center of the connector) for a second transmitter increasing the bandwidth and supporting resolutions up to 2560 × 1600 at 60 Hz."

Wonder if I find a DVI Dual Link to HDMI cable if I can at least manually get the 2560x1440 to work even if Auto Detect does not seem to be working for me.

Same results with all 3 cables I own, with Auto Detect on boots to 640x480 and with it off, I can go as high as 1920x1080 on this display.

Auto detect does not seem to get any monitor data via any of the 3 cables and I have to turn off Auto Detect in ScreenMode as it only gets these 640x480 modes.

So doubt all 3 cables are bad.  Wondering of there is just some hiccup Amiga OS and ScreenMode grabbing the data from the monitor to populate my choices.

Han's, you mention forget the DVI Dual Link cable.... does this mean I just will max out at 1920x1080 then even though this display on Mac or Linux works fine in 2560x1440 via HDMI cables?

Wll a better video card help?

TJ

That sounds like a faulty cable to me, although you've already tested it with two cables. Or, perhaps you made a mistake when setting the monitor's tool-types (HINT: ScreenMode prefs has a Monitors tab for this). BOOTVGA remains if the auto-detection either doesn't happen due to bad settings, or the monitor's DDC data couldn't be fetched.


I just looked up your monitor's specs. Forget about dual-link DVI cables. Yours is an HDMI monitor, and it's single-link.

Hans

[amigasociety]

Here is my info after I get info on the Dev/Monitor/Radeon HD Series 7000.

These are all the ones I manually select after turning off Auto Detect in Screen Mode Prefs.  I made the two 2560x1440 options.



TJ

[amigasociety]

Maybe something like this cable?

http://tinyurl.com/yd6drmq4

TJ

[amigasociety]

As a side note, I have 3 displays.  Dell 28" that is 4K, Samsung 27" that is 1080p, etc....  2 of them via HDMI and Auto Detect on Screen Mode for monitors, Neither the Dell 4K or new HP Omen auto detect anything.  This is on 2 different displays and trying 3 different cables.

The older 1080P Samsung does work on Auto Detect though.

Is it possible even though my Tool Types appear OK data wise, something is not quite right (or driver up to date to handle newer displays with higher resolutions) with something else not allowing Auto Detect to work on 2 of the 3 displays like this?

Seems odd???

TJ

[Hans_]

Wonder if I find a DVI Dual Link to HDMI cable if I can at least manually get the 2560x1440 to work even if Auto Detect does not seem to be working for me.

Wait, so manually adding the modes doesn't let it work? What do you get? A blank screen? Or are half the pixels missing (which is what happens in dual-link mode)?

Try experimenting with adding +RB/-RB to the modes. You'll find this as "Reduced Blanking" in ScreenMode prefs.

Hans, you mention forget the DVI Dual Link cable.... does this mean I just will max out at 1920x1080 then even though this display on Mac or Linux works fine in 2560x1440 via HDMI cables?

No. As I said, the latest drivers support HDMI's higher pixel clocks when an HDMI 1.3+ monitor is detected. AFAIK, nobody has made a dual-link HDMI monitor (which uses a different size connector), so a dual-link cable will do nothing.

Wll a better video card help?

Your graphics card is UHD capable. I think your problem really comes down to DDC not working. The driver needs DDC to work in order to detect HDMI 1.3+ monitors. Do your other machines auto-detect the monitor and its modes with the same cables?

I assume you've already tried plugging it in to every possible port on the graphics card. There is a possibility that the graphics card ROM's DDC connection table is wrong, resulting in it not working. However, it would be incredibly rare for it to fail on all ports.

Hans

[Hans_]

As a side note, I have 3 displays.  Dell 28" that is 4K, Samsung 27" that is 1080p, etc....  2 of them via HDMI and Auto Detect on Screen Mode for monitors, Neither the Dell 4K or new HP Omen auto detect anything.  This is on 2 different displays and trying 3 different cables.

The older 1080P Samsung does work on Auto Detect though.

Okay, that's even weirder. So, DDC is working with your card.

Is it possible even though my Tool Types appear OK data wise, something is not quite right (or driver up to date to handle newer displays with higher resolutions) with something else not allowing Auto Detect to work on 2 of the 3 displays like this?

Maybe something has changed with DDC that AmigaOS doesn't handle yet?

Anyway, I spotted something in your monitor's tool-types that could kill the high resolution modes:
- VSYNCMAX=60 - rais to 75Hz if you want that 75 Hz mode to be included
- HSYNCMAX=85000 could kill the higher resolution modes if their hsync frequency is above 85 KHz. I'm not sure what your monitor's limit is, or what 2560x1440 needs, but try raising this.

EDIT: 2560x1440 @60 Hz definitely requires a higher h-sync than 85 KHz, so raise that. And try using an HDMI port first (instead of DVI).

Hans

[amigasociety]

After creating and adding the two 2560x1440 modes in the ScreenMode Prefs "Monitor" tab, and click the Save Monitor, then go over under the Available Modes tab, neither the 2560 modes even show up.  Reboot the system still does not show them.  So, they never show up as an option to select even though I created them.

So the last Available mode I see is the Board 0:1920x1080 ARGB32 and that is the one I am on right now.

Maybe I am not "creating" them right?

I am just click the Add button in the Monitors tab and typing the Width as 2560, the Height as 1440, vertical refresh is left at 60, Mode is Active is checked, Type of Reduced Blanking is on None, and DoubleScan is left unchecked.  I then save it.

Am I doing that right to add it?

I will adjust the Maximum HSync higher to see if that helps but they never show on the Available Modes side so not sure it will.

And yes, my Radeon HD 7750 only has two ports.... 1 HDMI and 1 DVI so both have been tried with many cables.

TJ

Wait, so manually adding the modes doesn't let it work? What do you get? A blank screen? Or are half the pixels missing (which is what happens in dual-link mode)?

Try experimenting with adding +RB/-RB to the modes. You'll find this as "Reduced Blanking" in ScreenMode prefs.


No. As I said, the latest drivers support HDMI's higher pixel clocks when an HDMI 1.3+ monitor is detected. AFAIK, nobody has made a dual-link HDMI monitor (which uses a different size connector), so a dual-link cable will do nothing.


Your graphics card is UHD capable. I think your problem really comes down to DDC not working. The driver needs DDC to work in order to detect HDMI 1.3+ monitors. Do your other machines auto-detect the monitor and its modes with the same cables?

I assume you've already tried plugging it in to every possible port on the graphics card. There is a possibility that the graphics card ROM's DDC connection table is wrong, resulting in it not working. However, it would be incredibly rare for it to fail on all ports.

Hans

[amigasociety]

I read the manual for the HP Omen 32" and it shows this for preset mode on the 2560x1440.

2560 × 1440 HSync 88.787 Vsync 59.951

So I adjusted my Max to 75 on Vsync and 89000 on Max HSync saved the setting rebooted but still these two 2560x1440 options do not show under Available Modes.

TJ

[Hans_]

I read the manual for the HP Omen 32" and it shows this for preset mode on the 2560x1440.

2560 × 1440 HSync 88.787 Vsync 59.951

So I adjusted my Max to 75 on Vsync and 89000 on Max HSync saved the setting rebooted but still these two 2560x1440 options do not show under Available Modes.

Try using reduced blanking, as suggested earlier. You could try raising the HSYNCMAX further too.

Also, Vsync 59.951 < 60 Hz, in which case your VSYNCMIN would kill the mode. It shouldn't happen since you're specifying 60 Hz, but I have no idea how it works internally.

I'm pretty sure that it's the sync min/max settings that are causing the modes to be rejected, so continue experimenting with different settings.

Hans

[amigasociety]

You are a Genius!  ;-)

Something my wife never tells me.  hehe  :roflmao:

Thanks so much with sticking with me on this and offering advise!

Setting the one 60hz to +RB and after a hard reboot, the 2560x1440 at 60Hz shows.  

Sweetness.

Now I have the real estate size of California on my desktop.  :laughing:

Would be nice if auto detect works but must be something with newer displays and Amiga OS I guess.  Manually setting it works for me.

TJ

Try using reduced blanking, as suggested earlier. You could try raising the HSYNCMAX further too.

Also, Vsync 59.951 < 60 Hz, in which case your VSYNCMIN would kill the mode. It shouldn't happen since you're specifying 60 Hz, but I have no idea how it works internally.

I'm pretty sure that it's the sync min/max settings that are causing the modes to be rejected, so continue experimenting with different settings.

Hans

[Hans_]

@amigasociety
Awesome!

I've submitted a bug ticket regarding the graphics library's inability to automatically get the modes.

Hans