Monitors

2 Iron

U2414H, will there be a firmware fix for DP issues?

* What specific Dell monitor? 6x U2414H REVA00
* What specific computer model, desktop/laptop? Lenovo i7 QuadCore
* What operating system? Windows 8.1
* What video card? Club 3D Radeon HD 7870 Eyefinity 6
* What video out ports are available on the video card? 6x Mini-DP
* What video out port are you using from the video card to what video in port on the monitor? 6x Mini-DP to DP (1.2 disabled)
* What cable are you using to attach the video card to the monitor? Dell supplied Mini-DP to DP cable that came with the monitors. Funny enough Dell shipped two different cables. 3x Amphenol and 3x BizLink. Both perform the same.
* Are you using the Dell supplied cable? Yes.

* Full description of the monitor issue?
I'm experiencing the unreliable DP connection that TFTCentral wrote about in their review of the monitor and which others reported in various postings. I have tried different video cards and different cables but the DP connection always behaves unreliable. There is a bunch of symptoms (link loss, DP communication errors) but the most prevalent and annoying issue is that  the monitor is not recognized correctly about half of the time. With 6 monitors there always is at least two that won't work at the start of the day (always different ones at random). They can show up as Generic Non-PnP Monitor with a resolution of 640x480 or as Generic PnP Monitors with a little higher resolution. Most of the time however they correctly show up as Dell U2414H(DisplayPort) monitors but the refresh rate maxes out at 30Hz interlaced instead of 60Hz. this means that the picture will have a lot of jitter and is unusuable. It will then take a lot of power-cycling and Detect-button hitting, until all 6 monitor are correctly recognized. Additionally once a day the graphics card driver will crash, which I would not normally fault the monitor for, but since it doesn't happen with other DP monitors and since TFTCentral mentioned a crashing driver in their review, I do in fact suspect the monitor is somehow not speaking the DP protocol right and confusing the driver. I tried 1.2 DP version enabled and disabled and it doesn't make a difference. At this point I'm fairly certain there is an issue with this particular models DP communication. What I want to know is:
- Did Dell manage to reproduce this behavior since it was first reported 3 months ago?
- Is Dell working on a firmware update to fix these issues?
- And most importantly: Will this future firmware update be field-up-gradable?

If the monitors are unable to get a firmware update that can be applied by us users I would like to know as I will have to return these monitors. As they are, they are basically unusable. I love everything else about the monitor though and will have to get new ones when a fixed version is available. Thanks for any information.

Replies (15)
2 Iron

For reference: here is what it looked like when the monitor is miss-detected and doesn't have all the refresh rates - causing the display to be unusable because at the wrong refresh rate it will jitter.

2 Iron

Even when the U2414H is successfully recognized there is weird stuff in the EDID. This is the list of supported resolutions the monitor reports (using EnTech Taiwan Software to read the EDID which are the same guys dell uses for their Dell Display Manager):

  • 720 x 400p at 70Hz - IBM VGA
  • 640 x 480p at 60Hz - IBM VGA
  • 640 x 480p at 75Hz - VESA
  • 800 x 600p at 60Hz - VESA
  • 800 x 600p at 75Hz - VESA
  • 1024 x 768p at 60Hz - VESA
  • 1024 x 768p at 75Hz - VESA
  • 1280 x 1024p at 75Hz - VESA
  • 1152 x 864p at 75Hz - VESA STD
  • 1280 x 1024p at 60Hz - VESA STD
  • 1600 x 900p at 60Hz - VESA STD
  • 1600 x 1200p at 60Hz - VESA STD
  • 1920 x 1080p at 60Hz - VESA STD

Why would 1600x1200 be reported by the monitor as a supported resolution when it clearly doesn't have the pixels available. This erodes my confidences in the current firmware of the controller board inside further. I'm still impressed by the monitors hardware though and really hope Dell looks into a firmware fix. I want this monitor to work.

Community Manager
Community Manager

burggraben,

Thanks for all the data. I have not heard any word on a firmware for this model. We have seen Forum and reviewer reports of the issue but not from Support (phone, email, chat). If it was a systemic issue, we would be getting thousands of calls about it. I wonder if there is a limit to how many monitors the video card can support in chain?

 



 

2 Iron

Hi Chris,

Thanks for the interest in this issue, despite the fact that it is apparently not widespread. Maybe it only affects a specific production batch?

I have some more technical observations that might help narrow it down. I am using the PowerStrip utility from EnTech and it provides three options to read EDID data.

  • Read data directly from monitor
  • Read data from stored EDID
  • Read data from registry

It seem to me that the higher up in this list you can get data from, the better the data is. I made the following observation with my remaining 5 monitors (1 already sent back because of self-activating touch buttons). On none of them I can read the EDID from the monitor itself, even though DDC/CI is set to enabled in the OSD. I get this:

Then the tool automatically falls back to "Read data from stored EDID". Now there are two cases.

Case A: This happens on monitors that work as expected (full resolution and 60Hz). In this case PowerStrip manages to read the stored EDID (I don't know if that is previously read EDID from monitor or driver supplied EDID).

Case B: This happens on monitors which currently don't work as expected. In this case reading from stored EDID fails and I get this:

Then it falls back to "Reading from registry" which usually seem to contains a bunch of garbage that doesn't work for the monitor. On monitors where reading from "stored EDID" works, the data in the registry is fine too.

Chris, could you confirm for me whether the U2414H is supposed to support reading the EDID with a tool like EnTech Taiwan's PowerStrip utility? I already tried other EnTech Tools (MonInfo) but they don't manage to read from DDC either and just display the registry data.

If DDC doesn't work on my monitor it would explain why these display sometimes work for me (when Windows has either a stored EDID or the right data in registry) and sometime don't. It also explain why the monitors frequently show up as Non-PlugAndPlay monitor - because Windows relies on DDC to provide PnP functionality.

Has anybody else tested their U2414H with the PowerStrip utility and could confirm that "Read data directly from monitor" works for them?

2 Iron

This would also explain why Windows sometimes has a slightly different name for the monitor in the "Screen Resolution" configuration dialog. When it manages to read from stored EDID the monitor will the called "DELL U2414H", when it doesn't mange to do that it falls back to registry and the monitor will be called "Dell U2414H(DisplayPort)".  The monitors that have a registry configuration are the most likely to cause trouble.

3 Argentum

* What video card? Club 3D Radeon HD 7870 Eyefinity 6

* What video out ports are available on the video card? 6x Mini-DP

Has anybody else tested their U2414H with the PowerStrip utility and could confirm that "Read data directly from monitor" works for them?

FWIW, PowerStrip has not been updated in years, and would not support your new-ish HD7870 specifically or DisplayPort generally, so errors in reading the EDID directly would be expected and do not necessarily indicate an issue.

Doesn't mean you do *not* have a problem of this nature, just that, with DP, you can't use old I2C based software to diagnose it...

You don't say whether Dell Display Manager can communicate with the your U2414H? That would be more telling...

2 Iron

Thanks swamped207. You are correct of coarse and so was Chris from Dell which told me to use EnTech's softMCCS instead. I did and here are my findings. When the monitors work as they should then softMCCS confirms that they can talk to to it and that they speak DDC. Windows will recognize the U2414H as a U2414H and set the resolution and frequency right. Dell's Display Manager which speaks DDC/CI as works and lets me set the brightness in software. However when the monitor don't work as expected (which happens randomly after a restart, after sleep/hibernation or if a monitor gets added/removed) then none of the above work.

Dell's Display Manager and softMCCS won't see the monitor at all and Windows recognizes it as a Generic Non-PnP Monitor with all the wrong resolutions (NoN-PnP pointing to the fact that there is no DDC signal).

Here is an example of a computer with 3xU2414H monitor and one Lenovo display. Usually I'm testing with 5xU2414H without anything else, but I'm switching computer and graphics cards to isolate the issue, but it's the same everywhere.

In the picture below the Windows "Screen resolution" dialog recognizes two Dell (with different names, one taken from registry, the other from the stored EDID or driver) and the third Dell is a Generic Non-PnP. softMCCS doesn't see the Non-PnP at all.

When we look at the event log of the Non-PnP we see that it used to be recognized as U2414H, but when a reconfiguration event was triggered Windows uninstalled the Dell driver (Device deleted) and used the Non-PnP driver insteas (monitor.inf).

Currentely it looks to me like the monitor sometimes does talk DDC to the GPU and sometimes doesn't. When it does everything works fine, but when it doesn't then Windows doesn't know what to do.

2 Iron

I forgot to say that when softMCCS doesn't see the Non-PnP, it is switched on and actually displaying stuff at a 640x480 resolution. It's not that it's off or disconnected, softMCCS doesn't find the monitor while it is on and in use and should be talking DDC to softMCCS.

2 Iron

Just discovered the Dell Diagnostics Tool in DDM (Shift+Right Click) and it shows the same picture as painted above of the three monitors in the example above two are recognized according to DDM and one is a "Default_Monitor". When the device enumeration finishes DDM has this line to say:

21:27:39.500...Ending enumeration
21:27:39.566...New=DELA0A2000000030200 DELA0A2000000030300 Default_Monitor000000030400

There is also a bunch of errors:

21:27:40.230......Error: getting number of physical monitors (0x000005B5) = Invalid monitor handle

When things work it will simply enumerate the 3 (or 5 if all are attached) display with correct EDID and no errors. Other times "Default_Monitor" shows up. And sometimes I won't enumerate anything real just dump the Windows device enumeration which is a list of 25 or so monitors grouped under a bunch of devices names. Interestingly for each device name there is a monitor with the correct EDID and a bunch with a 0000 EDID. I guess these "Windows enumerations" are what Windows picks when the monitors don't enumerate correctly over DDC and if it picks one with a good EDID it works, if it picks one with a 0000 EDID I get a Non-PnP monitor. Example of just one device (there is several with several monitors each):

01:20:44.236...4.DeviceName = \\.\DISPLAY4
01:20:44.236.....DeviceFlags = 08080000
01:20:44.236.....DeviceString = AMD Radeon HD 7800 Series
01:20:44.236.....DeviceID = PCI\VEN_1002&DEV_6818&SUBSYS_23211787&REV_00
01:20:44.237.....DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Video\{BD5860EF-F299-4411-8B34-A11B48143DC1}\0001
01:20:44.242.....a.MonitorName = \\.\DISPLAY4\Monitor0
01:20:44.242.......MonitorFlags = 00000002
01:20:44.242.......MonitorString = Dell U2414H(DisplayPort)
01:20:44.242.......MonitorID = MONITOR\DELA0A2\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
01:20:44.242.......MonitorKey = \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
01:20:44.243.......Raw EDID = 00FFFFFFFFFFFF0010ACA2A04C3250342B170104A5351E783E7E75A755529C270F5054A54B00714F8180A9C0A940D1C0010101010101023A801871382D40582C45000F282100001E000000FF0039544734363341503450324C0A000000FC0044454C4C205532343134480A20000000FD00384C1E5311000A20202020202001ED
01:20:44.248.....b.MonitorName = \\.\DISPLAY4\Monitor1
01:20:44.248.......MonitorFlags = 00000002
01:20:44.248.......MonitorString = Dell U2414H(DisplayPort)
01:20:44.248.......MonitorID = MONITOR\Default_Monitor\{4d36e96e-e325-11ce-bfc1-08002be10318}\0002
01:20:44.248.......MonitorKey = \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0002
01:20:44.249.......Raw EDID = 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
01:20:44.254.....c.MonitorName = \\.\DISPLAY4\Monitor2
01:20:44.254.......MonitorFlags = 00000002
01:20:44.254.......MonitorString = Dell U2414H(DisplayPort)
01:20:44.254.......MonitorID = MONITOR\Default_Monitor\{4d36e96e-e325-11ce-bfc1-08002be10318}\0003
01:20:44.254.......MonitorKey = \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0003
01:20:44.254.......Raw EDID = 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
01:20:44.259.....d.MonitorName = \\.\DISPLAY4\Monitor3
01:20:44.260.......MonitorFlags = 00000002
01:20:44.260.......MonitorString = Dell U2414H(DisplayPort)
01:20:44.260.......MonitorID = MONITOR\Default_Monitor\{4d36e96e-e325-11ce-bfc1-08002be10318}\0007
01:20:44.260.......MonitorKey = \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0007
01:20:44.260.......Raw EDID = 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
01:20:44.265...5.DeviceName = \\.\DISPLAY5

Top Contributor
Latest Solutions