Lawrenbce Suto wrote: > Thanks > > The monitor is an LCD connecting via a VGA cable and a VGA to DVI adapter. > Yes the EDID is not getting read: > > lsuto at opensolaris:~$ grep EDID /var/log/Xorg.0.log > (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-1 > (WW) NVIDIA(0): Unable to get display device CRT-1's EDID; cannot compute DPI > (WW) NVIDIA(0): from CRT-1's EDID. > Either the cable (which should be DVI-I) or the adapter is not passing through the two DDC lines. Using a VOM, test DVI pin 6 is routed to VGA pin 15 and DVI pin 7 is routed to VGA pin 12. Use these as visual references:
http://www.interfacebus.com/Design_Connector_Digital_Visual_Interface_DVI_Bus.html http://www.interfacebus.com/Design_VGA_PinOuts.html Out of curiousity, you are using the secondary output (CRT-1). What is connected to the primary output? > I tried the new frequency range you suggested, but I still get the same > resolution set with the monitor now running at 59.98HZ. > To find out why the 1680x1050 mode is not being validated, enable verbose debugging output: $ pfexec svccfg -s x11-server setprop options/server_args = 'astring: ("-logverbose" "6")' (I just reboot at this point, but there is probably a more clever way using the svcadm command to refresh or restart the correct service. I'm also told an alternate method is to directly edit /etc/X11/gdm/custom.conf or run gdmsetup, but I've not tried this method.) The file /var/log/Xorg.0.log will now be very large. Either extract the relevant sections for 1680x1050 to post to this list or send me the entire file via email.
