Date: Thu, 28 Jun 2007 21:29:00 -0500 From: Karl Denninger <karl@denninger.net> To: freebsd-x11@freebsd.org Subject: Widescreen problems.... Message-ID: <46846E6C.4080301@denninger.net>
next in thread | raw e-mail | index | archive | help
Read the handbook, have a monitor that identifies as:
(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 146.2 MHz Image Size: 474 x 296 mm
(II) RADEON(0): h_active: 1680 h_sync: 1784 h_sync_end 1960
h_blank_end 2240 h
_border: 0
(II) RADEON(0): v_active: 1050 v_sync: 1053 v_sync_end 1059
v_blanking: 1089 v
_border: 0
(II) RADEON(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81
kHz, PixCl
ock max 170 MHz
(II) RADEON(0): Monitor name: SyncMaster
(II) RADEON(0): Serial No: HVFLB06818
So I added:
Section "Monitor"
DisplaySize 474 296 # mm
Identifier "Monitor0"
VendorName "SAM"
ModelName "SyncMaster"
Modeline "1680x1050" 146.2 1680 1784 1960 2240 1050 1053
1059 1089
### Comment all HorizSync and VertSync values to use DDC:
# HorizSync 30.0 - 81.0
HorizSync 65.0
VertRefresh 60
Option "DPMS"
EndSection
and.....
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
# Modes "1680x1050"
EndSubSection
EndSection
I get a startup screen that comes up with a clean "X" cursor, but
something's not right with the dot clock or similar, as the image is not
"locked".
If I remove the special config and just run on defaults, it comes up
even odder.
Ideas? Is the card in the machine unable to deal with this even though
it reports that its ok?
--
Karl Denninger (karl@denninger.net)
http://www.denninger.net
%SPAMBLOCK-SYS: Matched [@freebsd.org+], message ok
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46846E6C.4080301>