LCD with DVI connection to 9500 pro

[Sam]

I have an Samsung SyncMaster 191T LCD panel connected to an ATI Radeon 9500
using a DVI connection. It works fine, except when I reboot the screen goes
blank and doesn't re-appear until the Windows XP loading screen appears.
Since I like to see what it's doing during a boot, I'd like to see the
whole process. I can see everything normally using a VGA connection... just
not using the DVI.

Is this normal, or do I have something set up incorrectly.

Sam

 

[Chimera]

I have an Samsung SyncMaster 191T LCD panel connected to an ATI Radeon 9500
using a DVI connection. It works fine, except when I reboot the screen goes
blank and doesn't re-appear until the Windows XP loading screen appears.
Since I like to see what it's doing during a boot, I'd like to see the
whole process. I can see everything normally using a VGA connection... just
not using the DVI.

Is this normal, or do I have something set up incorrectly.

Sam

Ive got an LCD, DVI & Radeon setup, and my only impression is that the LCDs
often take longer to sync up than a CRT, but mine still displays all the
POST information

 

[Sam]

Ive got an LCD, DVI & Radeon setup, and my only impression is that the LCDs
often take longer to sync up than a CRT, but mine still displays all the
POST information

I wonder if this is a motherboard / Bios issue. I have an Asus A7N8X
(nForce2) MB with the latest (1006) Bios installed. However, I can find no
options that deal with this. It's like it just takes a long time to synch
up and decide that it has a valid signal to display.

Sam

 

[Barry Watzman]

Some DVI monitors are not fully compatible with some video boards. And
I've seen it happen both ways -- it works only UNTIL Winodws comes up,
or it works only AFTER Windows comes up (your situation).

The issue, I believe, has to do with incompatible protocols for the DDC
(Display Data Channel) part of the DVI interface. In SOME versions of
the ATI drivers, the driver can be told to just ignore DDC entirely (and
I think that in other cases, it can be forced to do this with an
undocumented registry hack). However, this only fixed the opposite
situation from what you have. Your problem lies in the video card
firmware, which deals with the monitor prior to startup of the Windows
driver. I don't know a solution for that. It shouldn't be that way,
and it isn't (on many monitors), but it is on some of them. You might
talk to ATI or Samsung. The only other solution I've seen people use is
to connect both the analog and DVI cables.