[Openchrome-users] problem with Syncmaster wide monitor

Jelle de Jong jelledejong
Thu Sep 27 13:40:34 PDT 2007


Hello ALex,

I believe this will help you, I have a 940BW:

execute the following command:
gtf 1680 1050 60 -x

result: (remove the _60 part)
Modeline "1680x1050"  147.14  1680 1784 1968 2256  1050 1051 1054 1087
-HSync +Vsync

Use the result in your monitor section: (change it with your modline)

Section "Monitor"
        Identifier              "Generic Monitor"
        Option                  "DPMS"
        Modeline                "1440x900"  106.47  1440 1520 1672 1904
 900 901 904 932  -HSync +Vsync
        #gtf 1440 900 60 -x
        #DisplaySize            381 238
        #1024/96*25.4 and 768/96*25.4 =
        DisplaySize             270.93 195.2
        HorizSync               28-81
        VertRefresh             56-75
EndSection

Some extra commands that can help you solve problems:
xdpyinfo | grep resolution
xrdb -q | grep Xft
sudo xresprobe via
sudo ddcprobe
gtf 1440 900 60 -x
sudo ddcprobe | egrep '^[cd]*timing:' | sed -e 's/^[cd]*timing:
\([^x]*\)x\([^ @$]*\).*$/\1x\2/;'
grep -i dpi  /var/log/Xorg.0.log


I hope it works, i will wait for some feedback :-D

Best regards,

Jelle

Roitman wrote:
> John,
> 
> Thanks for your reply. I tried various DisplaySize values
> and it does not seem to affect much. Maybe the fonts
> take notice, but definitely not images.
> 
> I am pretty sure I am not using the modes that are standard
> for this monitor. I guess I end up in a weird "custom" mode
> instead of a proper 1.6 mode with square pixels. Here's the
> snippet from xorg.conf:
> ==============
> Section "Device"
> 	Identifier	"Generic Video Card"
> 	Driver		"via"
> 	BusID		"PCI:1:0:0"
> EndSection
> 
> Section "Monitor"
> 	Identifier	"Generic Monitor"
> 	Option		"DPMS"
> 	HorizSync	30.0 - 81.0
> 	VertRefresh	56.0 - 75.0
> 	DisplaySize	474 296
> EndSection
> 
> Section "Screen"
> 	Identifier	"Default Screen"
> 	Device		"Generic Video Card"
> 	Monitor		"Generic Monitor"
> 	DefaultDepth	24
> 	SubSection "Display"
> 		Depth		1
> 		Modes		"1680x1050" "1440x900" "1280x800"
> 	EndSubSection
> 	SubSection "Display"
> 		Depth		4
> 		Modes		"1680x1050" "1440x900" "1280x800"
> 	EndSubSection
> 	SubSection "Display"
> 		Depth		8
> 		Modes		"1680x1050" "1440x900" "1280x800"
> 	EndSubSection
> 	SubSection "Display"
> 		Depth		15
> 		Modes		"1680x1050" "1440x900" "1280x800"
> 	EndSubSection
> 	SubSection "Display"
> 		Depth		16
> 		Modes		"1680x1050" "1440x900" "1280x800"
> 	EndSubSection
> 	SubSection "Display"
> 		Depth		24
> 		Modes		"1680x1050" "1440x900" "1280x800"
> 	EndSubSection
> EndSection
> ==============
> 
> and then I get this in the Xorg.0.log (the full log attached as well)
> ==============
> (II) VIA(0): Supported Future Video Modes:
> (II) VIA(0): #0: hsize: 1680  vsize 1050  refresh: 60  vid: 179
> (II) VIA(0): #1: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
> (II) VIA(0): #2: hsize: 1280  vsize 960  refresh: 60  vid: 16513
> (II) VIA(0): #3: hsize: 1152  vsize 864  refresh: 75  vid: 20337
> (II) VIA(0): Supported additional Video Mode:
> (II) VIA(0): clock: 119.0 MHz   Image Size:  474 x 296 mm
> (II) VIA(0): h_active: 1680  h_sync: 1728  h_sync_end 1760 h_blank_end
> 1840 h_border: 0
> (II) VIA(0): v_active: 1050  v_sync: 1053  v_sync_end 1059 v_blanking:
> 1080 v_border: 0
> (II) VIA(0): Ranges: V min: 56  V max: 75 Hz, H min: 30  H max: 81 kHz,
> PixClock max 140 MHz
> ==============
> 
> Then:
> (--) VIA(0): Virtual size is 1680x1050 (pitch 1680)
> (**) VIA(0): *Driver mode "1680x1050": 119.0 MHz (scaled from 460.5
> MHz), 64.7 kHz, 59.9 Hz
> (II) VIA(0): Modeline "1680x1050"  119.00  1680 1728 1760 1840  1050
> 1053 1059 1080 -hsync +vsync
> 
> Then:
> (II) VIA(0): VIAScreenInit
> (II) VIA(0): VIAMapFB
> (--) VIA(0): mapping framebuffer @ 0xf0000000 with size 0x4000000
> (==) VIA(0): Write-combining range (0xf0000000,0x4000000)
> (--) VIA(0): Frame buffer start: 0xb3a8f000, free start: 0x6baa80 end:
> 0x4000000
> (II) VIA(0): VIAMapMMIO
> (--) VIA(0): mapping MMIO @ 0xfd000000 with size 0x9000
> (--) VIA(0): mapping BitBlt MMIO @ 0xfd200000 with size 0x10000
> (II) VIA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is
> 0x0000
> (II) VIA(0): VIASave
> (II) VIA(0): Primary
> (II) VIA(0): TVSave...
> (II) VIA(0): VIAWriteMode
> (II) VIA(0): ViaModePrimary
> (II) VIA(0): ViaModePrimaryVGA
> (II) VIA(0): ViaModePrimaryVGA: Setting up 1680x1050
> (II) VIA(0): CrtcHTotal: 0x730
> (II) VIA(0): CrtcHDisplay: 0x690
> (II) VIA(0): CrtcHBlankStart: 0x690
> (II) VIA(0): CrtcHBlankEnd: 0x730
> (II) VIA(0): CrtcHSyncStart: 0x6C0
> (II) VIA(0): CrtcHSyncEnd: 0x6E0
> (II) VIA(0): CrtcVTotal: 0x438
> (II) VIA(0): CrtcVDisplay: 0x41A
> (II) VIA(0): CrtcVSyncStart: 0x41D
> (II) VIA(0): CrtcVSyncEnd: 0x423
> (II) VIA(0): CrtcVBlankStart: 0x41A
> (II) VIA(0): CrtcVBlankEnd: 0x438
> (II) VIA(0): Offset: 0x348
> (II) VIA(0): Fetch Count: 0x348
> (II) VIA(0): ViaTVPower: Off.
> (II) VIA(0): ViaSetPrimaryFIFO
> (II) VIA(0): ViaSetPrimaryDotclock to 0x838802
> (II) VIA(0): ViaSetUseExternalClock
> (II) VIA(0): VIAAdjustFrame
> (II) VIA(0): VIAAdjustFrame
> (II) VIA(0): - Blanked
> 
> 
> So it seems all well, but it does not look right.
> I am fairly clueless about this details. IF anybody
> could point me to the right direction I'd be most grateful.
> 
> Thanks,
> Alex
> 
> 
> On Thu, 2007-09-27 at 17:12 +0100, John Robinson wrote:
>> On 27/09/2007 05:37, Alex Roitman wrote:
>>> Hello,
>>>
>>> I am having problems with setting up the Samsung Syncmaster 216BW
>>> monitor. I have an onboard UniChrome chip:
>>>     Chipset VM800/CN700/P4M800Pro found
>>>
>>> When the mode is of 1.6 aspect ratio, the image "does not fit" into
>>> the display. The height is fine, but I can see only about 2/3 widths
>>> of the desktop.
>>>
>>> When the mode is anything with 1.33 ratio, I can see the whole
>>> thing, but of course it is now squished and appears wrong.
>>>
>>> I googled a bit and found this:
>>>    http://visnup.com/2007/08/28/fedora-7-at-1680x1050/
>>>
>>> but it is for an Intel graphic chip. I wonder if anybody savvy
>>> in modelines, dotclocks and whatnot can direct me into something
>>> similar for the unichrome chip.
>> I'm not quite sure, but have you set DisplaySize to something that's 
>> 1.6:1? Like this perhaps:
>> Section "Monitor"
>> 	Identifier   "Monitor0"
>> 	ModelName    "Samsung SyncMaster 216BW"
>> 	DisplaySize  480 300
>> EndSection
>>
>> If you use a 1.6:1 mode, the apps that pay any attention will now know 
>> the pixels are square.
>>
>> Another trick: tell X your monitor's smaller than it really is, and 
>> things will be drawn bigger. Try:
>>          DisplaySize 336 210
>> The opposite also works:
>> 	DisplaySize 560 350
>> will draw things smaller.
>>
>> Cheers,
>>
>> John.





More information about the Openchrome-users mailing list