Thanks, The Cvt program have this "-r" option that calculates data for LCD screens. The older Gtf program apperantly only works for CRT screens. The pixel clock value derived now actually corresponds with the info from Samsung.
$ ./cvt 2560 1600 60 -r -v 1: [V FIELD RATE RQD] : 60.000000 2: [H PIXELS RND] : 2560.000000 2.5: [ASPECT_RATIO] : 16:10 2.5: [V SYNC] : 6.000000 3: [LEFT MARGIN (PIXELS)] : 0.000000 3: [RIGHT MARGIN (PIXELS)] : 0.000000 4: [TOTAL ACTIVE PIXELS] : 2560.000000 5: [V LINES RND] : 1600.000000 6: [TOP MARGIN (LINES)] : 0.000000 6: [BOT MARGIN (LINES)] : 0.000000 7: [INTERLACE] : 0.000000 8: [H PERIOD EST] : 10.129167 9: [Actual VBI LINES] : 45.413410 9: [VBI LINES] : 46.000000 10: [Minimum VBI Lines] : 15.000000 10: [ACT VBI LINES] : 46.000000 11: [TOTAL V LINES] : 1646.000000 12: [TOTAL PIXELS] : 2720.000000 13: [Non-rounded PIXEL FREQ] : 268.627197 13: [ACT PIXEL FREQ] : 268.500000 14: [ACT H FREQ] : 98.713234 15: [ACT FIELD RATE] : 59.971588 16: [ACT FRAME RATE] : 59.971588 20: [H BACK PORCH] : 80.000000 21: [H SYNC RND] : 32.000000 22: [H FRONT PORCH] : 48.000000 23: [V FRONT PORCH] : 3.000000 # 2560x1600 @ 60.00 Hz Reduced Blank (CVT) # field rate 59.97 Hz; hsync: 98.71 kHz; pclk: 268.50 MHz Modeline "2560x1600_60.00_rb" 268.50 2560 2608 2640 2720 1600 1603 1609 1646 +HSync -Vsync Regards //Lars Stuart Kreitman wrote: > Ok, I understand your predicament a little better. > > > Firstly, try using "cvt", it uses the coordinated video timing > specificaton from VESA: > > # ./cvt 2560 1600 > # 2560x1600 59.99 Hz (CVT 4.10MA) hsync: 99.46 kHz; pclk: 348.50 MHz > Modeline "2560x1600_60.00" 348.50 2560 2760 3032 3504 1600 1603 > 1609 1658 -hsync +vsyn > > > Also need to add to the monitor section: > > option "Preferred Mode" "2560x1600_60.00 > > and skip the failing EDID probe with: > > option "NoDDC" "true" > > > It is the KVM unit that is blocking your system from > auto-configuring. If you can plug the monitor > directly into the system, you will see autoconfig working. While > you're there, dump the EDID data > (Some drivers, like the ATI, dump EDID into Xorg.0.log) > > A wealth of information on this: > > http://blogs.sun.com/moinakg/entry/grabbing_monitor_edid_data_on > > > Stuart > > > > > Lars Tunkrans wrote: >> Skk Wrote: >> >>> Lars: >>> You should not need to do this. The Xorg server will read the EDID data >>> >> >from the display >> >>> and autoconfigure it. If this is not working correctly, please submit >>> /var/log/Xorg.0.log >>> >> >> >> Yeah, it should should read the EDID data But the Samsung >> screen I have presently does'nt share its EDID data with solaris. >> Probably a bug in the screens microcode. Maybe its the KVM unit >> between the computer and the screen thats the cause. So I figured I >> needed to know if I had the correct values before buying a new screen. >> Anyway, Here is what happends when Xorg 7.02 tries to read my >> existing Samsung MP242 24" screen : >> >> Solaris Nevada version is Build 64a >> Nvidia Driver: >> >> NVDAgraphics NVIDIA Graphics System Software >> (i386) 1.0.9637,REV=2007.03.01.18.47 >> >> from /var/log/Xorg.0.log >> >> (II) Setting vga for screen 0. >> (++) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 >> (==) NVIDIA(0): RGB weight 888 >> (==) NVIDIA(0): Default visual is TrueColor >> (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) >> (**) NVIDIA(0): Enabling RENDER acceleration >> (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0 >> (II) NVIDIA(0): NVIDIA GPU GeForce 6500 at PCI:1:0:0 (GPU-0) >> (--) NVIDIA(0): Memory: 262144 kBytes >> (--) NVIDIA(0): VideoBIOS: 05.44.02.45.68 >> (II) NVIDIA(0): Detected PCI Express Link width: 16X >> (--) NVIDIA(0): Interlaced video modes are supported on this GPU >> (--) NVIDIA(0): Connected display device(s) on GeForce 6500 at >> PCI:1:0:0: >> (--) NVIDIA(0): CRT-0 >> (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock >> (II) NVIDIA(0): Assigned Display Device: CRT-0 >> (WW) NVIDIA(0): No valid modes for "1920x1200"; removing. >> (WW) NVIDIA(0): No valid modes for "1600x1200"; removing. >> (II) NVIDIA(0): Validated modes: >> (II) NVIDIA(0): "1280x1024" >> (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024 >> (WW) NVIDIA(0): Unable to get display device CRT-0's EDID; cannot >> compute DPI >> (WW) NVIDIA(0): from CRT-0's EDID. >> (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default >> >> And this is the correct behavior with the Modeline >> (II) Setting vga for screen 0. >> (++) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 >> (==) NVIDIA(0): RGB weight 888 >> (==) NVIDIA(0): Default visual is TrueColor >> (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) >> (**) NVIDIA(0): Enabling RENDER acceleration >> (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0 >> (II) NVIDIA(0): NVIDIA GPU GeForce 6500 at PCI:1:0:0 (GPU-0) >> (--) NVIDIA(0): Memory: 262144 kBytes >> (--) NVIDIA(0): VideoBIOS: 05.44.02.45.68 >> (II) NVIDIA(0): Detected PCI Express Link width: 16X >> (--) NVIDIA(0): Interlaced video modes are supported on this GPU >> (--) NVIDIA(0): Connected display device(s) on GeForce 6500 at >> PCI:1:0:0: >> (--) NVIDIA(0): CRT-0 >> (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock >> (II) NVIDIA(0): Assigned Display Device: CRT-0 >> (WW) NVIDIA(0): No valid modes for "1600x1200"; removing. >> (II) NVIDIA(0): Validated modes: >> (II) NVIDIA(0): "1920x1200" >> (II) NVIDIA(0): "1280x1024" >> (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200 >> (WW) NVIDIA(0): Unable to get display device CRT-0's EDID; cannot >> compute DPI >> (WW) NVIDIA(0): from CRT-0's EDID. >> (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default >> >> >> //Lars >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> desktop-discuss mailing list >> desktop-discuss at opensolaris.org >> >
