Intel Arc A380 Unable to recognize the resolution, color depth, refresh rate of the monitor

[wy3]

Unable to recognize the resolution, color depth, refresh rate of the monitor, so that the screen is explicitly overclocked after connection.I connect this card to my TV during a meeting at work and the TV goes black and never shows.This happens not only with TVs but also with monitors, some of which, even though they can display, cannot adjust the refresh rate or color depth.This has never been the case with NVIDIA's graphics cards.For example, if the monitor is a 6bit+FRC configuration, it can be recognized.I can choose my own 6bit color depth to avoid the FRC splash screen.If my monitor supports 10bit, I can choose 10bit color depth myself.I hope that the independent graphics card can accurately recognize the resolution, color depth, and refresh rate of the monitor. Even if it cannot recognize them, it should provide as many options as possible and adopt a conservative strategy to ensure that the connection can be made explicit!!!

[MUC · Accepted solution]

I use an Intel Arc A380 myself and have no problems with it. I don't fully understand your concern either. For a diagnosis, please provide additional data about the devices:

Please run the Intel System Support Utility for Windows and perform a scan for all options. Attach the output file here.

Please also create a Report for Intel Graphics Drivers and attach the file here.

[wy3]

For example, when connecting to a high refresh rate TV, it cannot accurately recognize the refresh rate of the TV, the TV has an explicit overclocking error, and the same applies when connecting to a monitor.There is also a color depth issue. My monitor is a native 10 bit device, but it does not support HDR. Can I only run in 8-bit mode?These issues have never appeared on Nvidia graphics cards before!!!The A380 cannot even be displayed when connected to a monitor.I hope engineers can adopt a conservative strategy. Since it is not possible to identify the optimal settings for the display, it is better to use a setting that most displays support to ensure display first, and then suggest the optimal setting. If the optimal setting is too old to display, it can automatically time out and return to the conservative setting.

[wy3]

Actually, AMD's graphics cards had the same problem 16 years ago, but AMD has been improving. I hope Intel's graphics cards can surpass these companies!

[MUC]

The HDMI port on the Arc A380 is HDMI 2.0b = 4K @ 60 Hz. This is compatible with any TV using Transition-Minimized Differential Signaling (TMDS). I have never seen an "overclocking error" on a TV. We will help you, but we need to understand what you mean. Please make a video or a picture of it and please tell us the device specifications.

The display compatibility strategy you are talking about is not guaranteed by Intel but by the interface specification (DisplayPort / HDMI). It follows exactly the logic that if in doubt, a display is always shown and further improvement can be made manually if necessary. Resolution and refresh rate are changed via the Windows display settings. You can set the color depth and color model and other details in the Intel Graphics Command Center, just like you do with Nvidia in the "Nvidia Control Panel" and with AMD in the "Radeon Settings" or the "AMD Software: Adrenalin Edition".

Please update the driver for your Arc A380.

[wy3]

DDC is a data channel used by PC hosts to access display memory to obtain EDID (Extended Display Identification Data) format data from EEPROM (Electrically Erasable Programmable Read Only Memory) in the display, in order to determine display attribute information (such as resolution, aspect ratio, etc.) of the display.It is a standard for communication between a monitor and a computer graphics card, allowing the graphics card to read the monitor's capabilities, such as supported resolutions and refresh rates, in order to correctly configure display settings.The most direct application of DDC is to provide plug and play functionality for displays. When the monitor is connected to the host, the host can automatically read the EDID information of the monitor through the DDC channel, thereby automatically setting appropriate display parameters without the need for manual adjustment by the user.

The DDC standard is issued and continuously improved by organizations such as VESA (Video Electronics Standards Association). The main DDC standards currently include:

DDC1: The original DDC standard mainly specifies the data transmission format.
DDC2B: A bidirectional data exchange channel that enables the host to read extended display information from the monitor.
DDC2B+: Allow bidirectional code exchange between the host and the display, and the host can issue display control commands to the display.
DDC2AB: Further enhances the host's control capability over the display, allowing for remote bidirectional data exchange.

My 10 bit TV doesn't display directly when plugged in;When using different graphics cards, the same HDMI cable, and monitor, both AMD and Intel graphics cards will report overclocking errors after plugging in the monitor because they have issues with their strategy for handling EDID (Extended Display Identification Data). Additionally, Intel graphics cards do not support 6-bit screens as well as AMD, and many old enterprise configured monitors are 6bit. Using FRC can cause screen flickering, and customers may question the quality of the graphics card;

[MUC]

Yes, I know about the DDC. You can create a Report for Intel Graphics Drivers and extract the raw EDID that the graphics driver receives. You can parse it with suitable decoding tools. When analyzing problems, however, correct reception via the DDC does not necessarily mean that the video connection will be established accordingly. Unsuitable and too long (or even too short!) cables can disrupt the transmission. The DDC is just a simple data channel, but TMDS or Fixed Rate Link (FRL) transmission are a bit more complicated and are confirmed in development with eye diagram measurement and the HDMI Compliance Test Specification is processed. The latter is a requirement of the interface standard and does not arise from the volition of individual manufacturers. In principle, there can of course still be errors in the EDID compliance, the signal processing of the sink or the graphics driver. I certainly don't want to claim that I already know everything, but I have no reason to assume that Intel has a systematic problem with interface compliance. It is very difficult to identify the "culprit" in individual cases. There are also cases where errors and inaccuracies between source and sink cancel each other out and a signal is created that shouldn't actually exist.

I can't say anything about 6-bit display devices because I've never tested anything like that myself. But I've done a lot of testing in home cinemas using TVs and projectors. The Intel Arc A380 can operate at 4K @ 120 Hz and 8K @ 60 Hz if you cabling it accordingly.

Please read on here.

[wy3]

All of my monitors are devices from before 2008; But they are still functioning normally;May cause compatibility issues; @MUCI really appreciateyoursupport. It helps me feel better;I hope engineers can support old devices in the future;

[MUC]

We had a classic compatibility issue here.