I have exactly the same problem, but I have Asus P7H55D-M EVO motherboard and Zalman Trimon 22". DVI output worked just fine until the display driver was installed and machine rebooted. After that only analog provides picture. HDMI works for digital television also. However, as an interesting detail, installing a new driver immediately switches to DVI output and everything works fine until next reboot. Seems that there is a problem with Intel's display driver as the same problem plagues multiple motherboards. I have the latest BIOS & drivers (just checked).
Hello guys, it's been more than a month since I raised the question.
I have been in touch with Gigabyte and eventually, after much exchange of messages, they have concluded that it is a compatibility issue and recommended that I contact the monitor's manufacturer (Viewsonic) for help. On their part, it's a dead end issue.
Looks like I've got no choice but to change my LCD monitor or just stay with VGA.
It seems to be an Intel driver issue, but unfortunately everybody including our friends at Intel are pointing fingers at someone else. It's forced me not to increase the time the system go to sleep from 15 min to 4 hours, so I don't have to deal with this frequently and I just restart the system after the sleep. The other system I have connected to the same KVM switch is a Mac Mini and works like a charm!
The reason I'm here is the same as everyone else. I've just installed XP Home SP3 onto a new Gigabyte GA-H55M-UD2H motherboard. My Viewsonic VA-912b monitor is not being correctly detected when only the DVI input is connected, and the digital signal stops as XP starts properly loading but it's OK in Safe Mode. As with everyone else, it works OK when the VGA input is connected.
It's looking like all the companies involved will keep saying that it's someone else's problem, but I'll keep watching this board in case someone comes up with a solution. At least now I know it's not due to me misconfiguring something.
Hi Robert. Thanks for suggesting this possibility. I installed it and rebooted the system but in my case it didn't help at all so I did a system restore back to how it was. The analog video image on my Viewsonic VA912b monitor (1280x1024 native resolution) is virtually identical to the digital image (on a system which produces it) so it's not a major deal, just annoying that I can't use my DVI-capable monitor with my DVI-capable new motherboard.
I have the same issue with the GMA 500 drivers. I upgraded to the latest drivers late last year and now the only way I can get my computer to detect my external DVI monitor (connected to my HDMI port of my computer) is to unplug and plug in again the video cable. I have to do this a number of times sometimes. It worked fine on the older driver.
I have the exact same issue. Motherboard is a rev 3 Asus P8H67-M EVO with a Viewsonic VX2035wm.
The driver listed here did allow me to use my VGA input but I much prefer the performance of the DVI input on my viewsonic.
I hope Intel works on a solution so I can use my DVI instead of VGA.
Intel: Can we look forward toa fix in the near future?
Some posts suggest a failing monitor. If slow startup on cold mornings is observed failure can be expected with degradation of computer sleep capablities. Kits are available for some monitors to replace capacitors and tend to be top quality. The cost can be less than $40 including soldering and desoldering irons. A multimeter would be another $25. As with any power problem, safety and ventilation are concerns. Web sites vary in stressing this but latex gloves are never mentioned. Pressing the power button a minute with wall power disconnected will discharge most of the charge.
I may have more to say shortly but I can add that using a DVI-A adapter or any other could disrupt the logic of the monitor/system. No problems may be observable until usage without the adapter. At that point two monitors can behave differently and swaps add a variable. I get flak mentioning minor possibilites that can confuse the user and system. I have no love of service techs but they also can't see your system or read your mind. This may be an issue that Intel should address.
Regarding monitor repair I've found that while it was easy to repair a Viewsonic VP930b, other monitors appear to have no simple way of dismanteling for repair. This can solve some problems associated with monitor sleep and or computer sleep/hibernation. Some issues are probably due to drivers. If the input isn't what you expect about your problem, just ignore it, at your own risk.
I tried reseting my system, where the monitor would not sleep by itself, by moving a graphics card. The monitor would sleep but computer would not sleep. Reverting to onboard DG45ID graphics with DVI left me with monitor no sleep but OK computer/monitor sleep and hibernate. Reverted to VGA and all is OK. This system has too many software and hardware suspects so I will use as is for limited purposes. Having had an adapter that did not work, this adapter use is still suspect. I'm sure some think this is nonsense.
I hope my first post didn't squelch conversation. Has anyone had any success? The aging monitor aspect should only be relevant in some cases.
Same problem to me. Until they (I mean...INTEL) release new and working drivers I managed to use DVI output in this way:
Control panel -> System -> Device Manager -> Display Adapter -> Right Click on The Intel HD Graphics -> Uninstall Device (put a check on the option "Delete the driver software for this device")
Just repeat for your monitor driver:
Control panel -> System -> Device Manager -> Monitors -> Right Click -> Uninstall Device (put a check on the option "Delete the driver software for this device")
Now I work with a Standard Monitor and Standard VGA Adapter, but It works.... hope to solve it soon!
In my opinion I think is just a matter of compatibility with the specific monitor. I tried a friend DVI monitor and it worked...
DID ANYONE SOLVE IT IN OTHER WAYS?
I've temporarily swapped my old Viewsonic VA-912b monitor with a new Vivo one and it works OK on the DVI interface. Apparently the Viewsonic doesn't tell the Intel drivers what they want to hear but the Vivo does, and Intel isn't going to investigate it further. For now everything's OK in my setup but it doesn't fix the underlying problem.