Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
20712 Discussions

UHD770+13900T+Z790 Displayport+HDMI Resolution 2560x1600

phylax
Beginner
2,960 Views

Problem is, that UHD Graphics controller does not detect the default resolution 2560x1600 of my HP LP3065 monitor.

In Windows10/11, when the Intel UHD Graphics driver is enabled, the only available resolution is 1280x800, is recommended and is shown grayed.

When the Intel UHD Graphics driver is disabled, the default resolution is 2560x1600, is recommended and shown grayed.

 

All UHD770 drivers in Windows10/11 are up-to-date and are loaded from Intel download center.

Why does the Intel UHD770 driver not detect the native monitor resolution 2560x1600? I also could not find a way to override the default resolution setting of 1280x800 using Intel Graphic Control Room or other third party tools.

It seems that the Intel driver ignores the monitor's EDID data, that on the other hand is recognized and accepted by the default Windows driver. 

Please can someone explain this behaviour?

Any help would be appreciated.

Intel driver enabled:

Resolution_Intel_driver_enabled.jpg

 

Intel driver disabled:

Resolution_Intel_driver_disabled.jpg

 

 

0 Kudos
14 Replies
n_scott_pearson
Super User
2,928 Views

I would suggest that you attach a listing of the monitor's EDID, as seen through the iGFX driver. The DXDIAG report would help as well.

...S

0 Kudos
phylax
Beginner
2,923 Views

Detail monitor timing data from cru-1.5.1 :

 

lp3065_timing.jpg

Asset info with raw EDID data from Monitor Asset Manager:

asset_info.jpg

 

EDID Data from cru-1.5.1 :

lp3065_edid.jpg

 

The last byte in raw data (3e) and EDID data from cru-1.5.1 (59) is different. Could it be the reason for not detecting the LP3065 monitor?

0 Kudos
n_scott_pearson
Super User
2,916 Views

I never asked before: Is there an INF update or 'driver' package provided by HP?

0 Kudos
phylax
Beginner
2,910 Views

Yes, there was an old monitor driver from 2006, but this driver did not solve the problem:

hp_monitor_driver.jpg

0 Kudos
n_scott_pearson
Super User
2,908 Views

I cannot read the text on the picture, so cannot tell what I am looking at. If it was installing an INF that defined the resolutions, this should have addressed the issue.

How old is this monitor? I cannot see anything on the HP site regarding it. It appears to be old enough that they have removed it from their searches.

What specific motherboard and what specific connectors (DisplayPort (DP), HDMI, etc.) on this motherboard are you using? Are there dongles involved (DP-to-HDMI, for example)?

...S

0 Kudos
phylax
Beginner
2,897 Views

Yes, I know, this monitor is old, about 12 years, but in best condition and working very well with latest graphic cards from AMD and NVIDIA, also with DP to DVI-D adapter, when DVI-D Interface is missing. I'm using an DP to DVI-D active converter from BizLink supporting resolutions up to 2560x1600. 

With or without INF file, that makes no difference, the native resolution of the monitor is not detected and accepted in both cases by the INTEL driver.  Please keep in mind, that the monitor can be operated with its native resolution, when the INTEL driver is disabled.

So it seems to me, that the INTEL driver rejects the EDID data for whatever reason, in contrast to the Windows built-in driver, that is working without problems. However it lacks the GPU acceleration...

 

I'm using an ASRock motherboard PG-ITX/TB4, the monitor is attached to the DP via BizLink active PD to DVI-D converter.

Best regards

0 Kudos
Jean_Intel
Employee
2,866 Views

Hello phylax,

 

Thank you for posting on the Intel️® communities. We understand that you are unable to set the native resolution.

 

To have a better understanding of your issue, please provide me with the following:

 

  • Install the latest Graphics driver for your device. We recommend updating the graphics driver using the suggested Original Equipment Manufacturer Driver if one is available. The latest version available by Phantom Gaming for your motherboard is 31.0.101.3302.
  • Install the latest BIOS for your computer. The latest BIOS version available is 5.02.
    • Check with your computer manufacturer for the latest system BIOS and video BIOS with added support for the larger display mode.
  • Disconnect any video adapters/converters/docking stations and use a straight connection instead.
    • Some 3rd party components may prevent or alter the capability of the Intel Graphics to read the display's Extended Display Identification Data (EDID) data.
  • Test with a different display cable (HDMI, DisplayPort, etc)
  • Some displays will require an update to their firmware. Consult with your display manufacturer for instructions on how to update it.

 

Best regards,

Jean O. 

Intel Customer Support Technician


0 Kudos
phylax
Beginner
2,834 Views
Hello Jean,
Thank you for the suggestions to solve the problem. Before turning to this site to find help with this problem,
I already did the actions you suggested.
1. After a fresh install of Win11, installed ASRock OEM Driver: Resolution is 1280x800. 2. Installation BIOS version 4.03 and 5.02 : Resolution 1280x800. 3. A direct connection between mainboard graphics interface and monitor is not possible because
the HP monitor only has DVI-D interfaces and the mainboard only has display port and HDMI.
Therefore, the not really cheap DP to DVI-D adapter from BizLink was used. This configuration works perfectly
at 2560x1600 with graphics cards from big players like AMD and NVIDIA, but not with INTEL UHD770.
As explained in my earlier posts, this configuration also works in my system with a resolution of 2560x1600
if you switch off the INTEL driver in the hardware manager.
From this it can be concluded quite clearly that neither the HP LP3065 monitor with the adapter from BizLink
nor other hardware components are responsible for the problem. It is therefore unrealistic to suspect
bugs in the monitor's firmware, since this device works perfectly with drivers from AMD, NVIDIA and even
with the driver from Microsoft as part of Windows 11.
The bug must therefore be found in the INTEL driver software.
This would be easy for INTEL to reproduce if you read the attached EDID data from the monitor into an
EDID simulator and then observe how the INTEL drivers react to it. Finally, I have to fear that INTEL is not willing to dig deeper into this matter, since there are probably
higher priority issues to solve.
Best regards phylax

0 Kudos
Jean_Intel
Employee
2,817 Views

Hello phylax,

 

Thanks for the information provided. We understand that as per the effort and findings you have concludded that there must be an issue within the Intel Driver.

 

We would like to further investigate this matter. To further research this matter, we would like to have more system information. Please provide us with the report using the Intel®️ System Support Utility (Intel®️ SSU):

  • Download the Intel SSU
  • Open the application and click "Scan" to see the system and device information. By default, Intel®️ SSU will take you to the "Summary View."
  • Click on the menu where it says: "Summary" to change it to "Detailed View."
  • To save your scan: click "Next"; then "Save."

 

Best regards,

Jean O.

Intel Customer Support Technician


0 Kudos
phylax
Beginner
2,811 Views

Hello Jean,

attached is now the result of the ssu app.

 

Best regards

phylax

0 Kudos
Jean_Intel
Employee
2,800 Views

Hello phylax

 

Thank you for the information provided. 

 

I will proceed to check the issue internally and post back soon with more details.

 

Best regards,

Jean O. 

Intel Customer Support Technician


0 Kudos
Jean_Intel
Employee
2,729 Views

Hello phylax,

 

We appreciate your patience.

 

After reviewing this internally we can confirm that the issue can be related to the adapter, we can not guarantee this will work as adapters can modify how this works. We recommend that you do straight connections or test a different monitor with the same capabilities regarding resolutions and straight connections, adapters convert the signal and this could affect how EDID is read.

 

You should contact OEM adapters for more information and support.

 

Best regards,

Jean O. 

Intel Customer Support Technician

 

0 Kudos
Jean_Intel
Employee
2,703 Views

Hello phylax,

 

We hope you are doing fine.

 

We have not heard back from you. So we will close this thread. If you need any additional information, submit a new question, as this thread will no longer be monitored.

 

Best regards.

Jean O. 

Intel Customer Support Technician.


0 Kudos
freeseek
Beginner
1,864 Views

This might not be related but I have the same issue with the HP LP3065 combined with a Bizlink adapter but on Linux rather than on Windows. The problem was introduced in the Linux kernel on September 17th 2020 when the Linux i915 Intel driver was updated by Ville Syrjälä <ville.syrjala@linux.intel.com> as with the update the driver becomes unable to understand that the Bizlink adapter supports frequencies higher than 165khz, which is the frequency corresponding to a single-link DVI adapter. I overcome this issue with a small Linux kernel module that uses Kernel probes to hook itself into the return path of the drm_dp_downstream_max_tmds_clock() function included in the drm_dp_helper.c file and making the function return 300000 instead of 165000. With this expedient I am able to use the HP LP3065 2560x1600 resolution with the Bizlink adapter and the Intel Comet Lake UHD graphic controller. Whether this is the same issue as the Windows driver I do not know but at least on Linux Intel has refused to fix this issue. My understanding is that Intel does not care to support dual-link DVI adapters anymore.

0 Kudos
Reply