samsung 215TW monitor and DVI resolution - Hardware

This is a discussion on samsung 215TW monitor and DVI resolution - Hardware ; I have been avoiding this problem for some time, not really wanting t get involved. Re Mandriva 2007.1 I have a Samsung monitor 215TW which does not run at native resolution (1680x1050) with the DVI input. It gets only to ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: samsung 215TW monitor and DVI resolution

  1. samsung 215TW monitor and DVI resolution

    I have been avoiding this problem for some time, not really wanting t get
    involved.

    Re Mandriva 2007.1

    I have a Samsung monitor 215TW which does not run at native resolution
    (1680x1050) with the DVI input. It gets only to 1280x1024.

    The analog input is OK it runs full resolution

    I have both inputs, DVI and Analog, connected to the monitor to facilitate
    switching. Whether or not DVI works at all is variable and depends on
    xorg.config at boot. But the maximum resolution is always 1280x1024

    My graphics card is quite old now, a nvidia FX5200, which may prove to be the
    problem.

    Nvidia driver 100.14.11

    Logs and files to follow

    Xorg.0.log

    Some trimming here, not sure what to keep.

    X Window System Version 7.2.0
    Release Date: 22 January 2007
    X Protocol Version 11, Revision 0, Release 7.2
    Build Operating System: UNKNOWN
    Current Operating System: Linux unimatrix.localdomain.invalid 2.6.17-13mdv #1
    SMP Fri Mar 23 19:03:31 UTC 2007 i686
    Build Date: 26 March 2007

    (==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 6 10:10:51 2007
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "layout1"

    (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): Using HW cursor
    (**) NVIDIA(0): Enabling RENDER acceleration
    (==) NVIDIA(0): Video key set to default value of 0x101fe
    (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
    (II) NVIDIA(0): enabled.
    (II) NVIDIA(0): NVIDIA GPU GeForce FX 5200 (NV34) at PCI:1:0:0 (GPU-0)
    (--) NVIDIA(0): Memory: 131072 kBytes
    (II) NVIDIA(0): GPU Architecture: 0x30
    (II) NVIDIA(0): GPU Implementation: 0x34
    (II) NVIDIA(0): GPU Revision: 0xb1
    (II) NVIDIA(0): GPU RAM Type: DDR1
    (--) NVIDIA(0): VideoBIOS: 04.34.20.56.00
    (--) NVIDIA(0): Found 2 CRTCs on board
    (II) NVIDIA(0): Supported display device(s): CRT-0, CRT-1, DFP-0, TV-0
    (II) NVIDIA(0): Bus detected as AGP
    (II) NVIDIA(0): Detected AGP rate: 8X
    (--) NVIDIA(0): Interlaced video modes are supported on this GPU
    (II) NVIDIA(0):
    (II) NVIDIA(0): Mode timing constraints for : GeForce FX 5200
    (II) NVIDIA(0): Maximum mode timing values :
    (II) NVIDIA(0): Horizontal Visible Width : 8192
    (II) NVIDIA(0): Horizontal Blank Start : 8192
    (II) NVIDIA(0): Horizontal Blank Width : 4096
    (II) NVIDIA(0): Horizontal Sync Start : 8184
    (II) NVIDIA(0): Horizontal Sync Width : 504
    (II) NVIDIA(0): Horizontal Total Width : 8224
    (II) NVIDIA(0): Vertical Visible Height : 8192
    (II) NVIDIA(0): Vertical Blank Start : 8192
    (II) NVIDIA(0): Vertical Blank Width : 256
    (II) NVIDIA(0): Veritcal Sync Start : 8191
    (II) NVIDIA(0): Vertical Sync Width : 15
    (II) NVIDIA(0): Vertical Total Height : 8193
    (II) NVIDIA(0):
    (II) NVIDIA(0): Minimum mode timing values :
    (II) NVIDIA(0): Horizontal Total Width : 40
    (II) NVIDIA(0): Vertical Total Height : 2
    (II) NVIDIA(0):
    (II) NVIDIA(0): Mode timing alignment :
    (II) NVIDIA(0): Horizontal Visible Width : multiples of 8
    (II) NVIDIA(0): Horizontal Blank Start : multiples of 8
    (II) NVIDIA(0): Horizontal Blank Width : multiples of 8
    (II) NVIDIA(0): Horizontal Sync Start : multiples of 8
    (II) NVIDIA(0): Horizontal Sync Width : multiples of 8
    (II) NVIDIA(0): Horizontal Total Width : multiples of 8
    (II) NVIDIA(0):
    (--) NVIDIA(0): Connected display device(s) on GeForce FX 5200 at PCI:1:0:0:
    (--) NVIDIA(0): Samsung SyncMaster (CRT-0)
    (--) NVIDIA(0): Samsung SyncMaster (DFP-0)
    (--) NVIDIA(0): Samsung SyncMaster (CRT-0): 350.0 MHz maximum pixel clock
    (--) NVIDIA(0):
    (--) NVIDIA(0): --- EDID for Samsung SyncMaster (CRT-0) ---
    (--) NVIDIA(0): EDID Version : 1.3
    (--) NVIDIA(0): Manufacturer : SAM
    (--) NVIDIA(0): Monitor Name : Samsung SyncMaster
    (--) NVIDIA(0): Product ID : 531
    (--) NVIDIA(0): 32-bit Serial Number : 1146106417
    (--) NVIDIA(0): Serial Number String : HVZP500294
    (--) NVIDIA(0): Manufacture Date : 2007, week 20
    (--) NVIDIA(0): DPMS Capabilities : Active Off
    (--) NVIDIA(0): Prefer first detailed timing : Yes
    (--) NVIDIA(0): Supports GTF : No
    (--) NVIDIA(0): Maximum Image Size : 450mm x 280mm
    (--) NVIDIA(0): Valid HSync Range : 30.0 kHz - 81.0 kHz
    (--) NVIDIA(0): Valid VRefresh Range : 56 Hz - 75 Hz
    (--) NVIDIA(0): EDID maximum pixel clock : 170.0 MHz

    (--) NVIDIA(0):
    (--) NVIDIA(0): Detailed Timings:
    (--) NVIDIA(0): 1680 x 1050 @ 60 Hz
    (--) NVIDIA(0): Pixel Clock : 146.25 MHz
    (--) NVIDIA(0): HRes, HSyncStart : 1680, 1784
    (--) NVIDIA(0): HSyncEnd, HTotal : 1960, 2240
    (--) NVIDIA(0): VRes, VSyncStart : 1050, 1053
    (--) NVIDIA(0): VSyncEnd, VTotal : 1059, 1089
    (--) NVIDIA(0): H/V Polarity : -/+
    (--) NVIDIA(0):
    (--) NVIDIA(0):
    (--) NVIDIA(0): Raw EDID bytes:
    (--) NVIDIA(0):
    (--) NVIDIA(0): 00 ff ff ff ff ff ff 00 4c 2d 13 02 31 32 50 44
    (--) NVIDIA(0): 14 11 01 03 0e 2d 1c 78 2a ee 95 a3 54 4c 99 26
    (--) NVIDIA(0): 0f 50 54 bf ef 80 b3 00 81 80 81 40 71 4f 01 01
    (--) NVIDIA(0): 01 01 01 01 01 01 21 39 90 30 62 1a 27 40 68 b0
    (--) NVIDIA(0): 36 00 98 32 11 00 00 1c 00 00 00 fd 00 38 4b 1e
    (--) NVIDIA(0): 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53
    (--) NVIDIA(0): 79 6e 63 4d 61 73 74 65 72 0a 20 20 00 00 00 ff
    (--) NVIDIA(0): 00 48 56 5a 50 35 30 30 32 39 34 0a 20 20 00 9c
    (--) NVIDIA(0):
    (--) NVIDIA(0): --- End of EDID for Samsung SyncMaster (CRT-0) ---
    (--) NVIDIA(0):
    (--) NVIDIA(0): Samsung SyncMaster (DFP-0): 135.0 MHz maximum pixel clock
    (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Single Link TMDS
    (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Native FlatPanel Scaling is
    (--) NVIDIA(0): supported
    (--) NVIDIA(0): Samsung SyncMaster (DFP-0): DFP modes are limited to 60 Hz
    (--) NVIDIA(0): refresh rate
    (--) NVIDIA(0):
    (--) NVIDIA(0): --- EDID for Samsung SyncMaster (DFP-0) ---
    (--) NVIDIA(0): EDID Version : 1.3
    (--) NVIDIA(0): Manufacturer : SAM
    (--) NVIDIA(0): Monitor Name : Samsung SyncMaster
    (--) NVIDIA(0): Product ID : 532
    (--) NVIDIA(0): 32-bit Serial Number : 1146106417
    (--) NVIDIA(0): Serial Number String : HVZP500294
    (--) NVIDIA(0): Manufacture Date : 2007, week 20
    (--) NVIDIA(0): DPMS Capabilities : Active Off
    (--) NVIDIA(0): Prefer first detailed timing : Yes
    (--) NVIDIA(0): Supports GTF : No
    (--) NVIDIA(0): Maximum Image Size : 450mm x 280mm
    (--) NVIDIA(0): Valid HSync Range : 30.0 kHz - 81.0 kHz
    (--) NVIDIA(0): Valid VRefresh Range : 56 Hz - 75 Hz
    (--) NVIDIA(0): EDID maximum pixel clock : 170.0 MHz
    (--) NVIDIA(0):

    (--) NVIDIA(0):
    (--) NVIDIA(0): Detailed Timings:
    (--) NVIDIA(0): 1680 x 1050 @ 60 Hz
    (--) NVIDIA(0): Pixel Clock : 146.25 MHz
    (--) NVIDIA(0): HRes, HSyncStart : 1680, 1784
    (--) NVIDIA(0): HSyncEnd, HTotal : 1960, 2240
    (--) NVIDIA(0): VRes, VSyncStart : 1050, 1053
    (--) NVIDIA(0): VSyncEnd, VTotal : 1059, 1089
    (--) NVIDIA(0): H/V Polarity : -/+
    (--) NVIDIA(0):
    (--) NVIDIA(0):
    (--) NVIDIA(0): Raw EDID bytes:
    (--) NVIDIA(0):
    (--) NVIDIA(0): 00 ff ff ff ff ff ff 00 4c 2d 14 02 31 32 50 44
    (--) NVIDIA(0): 14 11 01 03 80 2d 1c 78 2a ee 95 a3 54 4c 99 26
    (--) NVIDIA(0): 0f 50 54 bf ef 80 b3 00 81 80 81 40 71 4f 01 01
    (--) NVIDIA(0): 01 01 01 01 01 01 21 39 90 30 62 1a 27 40 68 b0
    (--) NVIDIA(0): 36 00 98 32 11 00 00 1c 00 00 00 fd 00 38 4b 1e
    (--) NVIDIA(0): 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53
    (--) NVIDIA(0): 79 6e 63 4d 61 73 74 65 72 0a 20 20 00 00 00 ff
    (--) NVIDIA(0): 00 48 56 5a 50 35 30 30 32 39 34 0a 20 20 00 29
    (--) NVIDIA(0):
    (--) NVIDIA(0): --- End of EDID for Samsung SyncMaster (DFP-0) ---
    (--) NVIDIA(0):
    (II) NVIDIA(0): Frequency information for Samsung SyncMaster (CRT-0):
    (II) NVIDIA(0): HorizSync : 30.000-81.000 kHz
    (II) NVIDIA(0): VertRefresh : 56.000-75.000 Hz
    (II) NVIDIA(0): (HorizSync from EDID)
    (II) NVIDIA(0): (VertRefresh from EDID)
    (II) NVIDIA(0):
    (II) NVIDIA(0): --- Building ModePool for Samsung SyncMaster (CRT-0) ---
    (II) NVIDIA(0): Validating Mode "1680x1050":
    (II) NVIDIA(0): 1680 x 1050 @ 60 Hz
    (II) NVIDIA(0): Mode Source: EDID
    (II) NVIDIA(0): Pixel Clock : 146.25 MHz
    (II) NVIDIA(0): HRes, HSyncStart : 1680, 1784
    (II) NVIDIA(0): HSyncEnd, HTotal : 1960, 2240
    (II) NVIDIA(0): VRes, VSyncStart : 1050, 1053
    (II) NVIDIA(0): VSyncEnd, VTotal : 1059, 1089
    (II) NVIDIA(0): H/V Polarity : -/+
    (II) NVIDIA(0): Mode is valid.
    (II) NVIDIA(0):


    (II) NVIDIA(0):
    (II) NVIDIA(0): Computing DPI using physical size from Samsung SyncMaster
    (II) NVIDIA(0): (CRT-0)'s EDID and first mode to be programmed on Samsung
    (II) NVIDIA(0): SyncMaster (CRT-0):
    (II) NVIDIA(0): width : 1680 pixels 450 mm (DPI: 94)
    (II) NVIDIA(0): height : 1050 pixels 280 mm (DPI: 95)
    (--) NVIDIA(0): DPI set to (94, 95); computed from "UseEdidDpi" X config
    (--) NVIDIA(0): option
    (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC? No, I don't.


    I notice that the two EDID data blocks differ in the last byte, is this
    important.

    xorg.conf with some trimming

    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder3) Wed Jun 13 18:39:30
    PDT 2007

    # File generated by XFdrake (rev 142098)
    # ************************************************** ********************
    # Refer to the xorg.conf man page for details about the format of
    # this file.
    # ************************************************** ********************



    Section "Monitor"

    # Monitor preferred modeline (60.0 Hz vsync, 65.3 kHz hsync, ratio 16/10)
    Identifier "monitor1"
    VendorName "Plug'n Play"
    ModelName "SyncMaster"
    HorizSync 30.0 - 81.0
    VertRefresh 56.0 - 75.0
    ModeLine "1680x1050" 146.2 1680 1784 1960 2240 1050 1053 1059 1089
    +hsync -vsync

    EndSection

    Section "Device"
    Identifier "device1"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "NVIDIA GeForce FX - GeForce 7950"
    EndSection

    Section "Screen"
    Identifier "screen1"
    Device "device1"
    Monitor "monitor1"
    DefaultDepth 24
    Option "DPMS"
    SubSection "Display"
    Depth 8
    Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
    EndSubSection
    SubSection "Display"
    Depth 15
    Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
    EndSubSection
    SubSection "Display"
    Depth 16
    Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
    EndSubSection
    SubSection "Display"
    Depth 24
    Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
    EndSubSection
    EndSection

    Section "Extensions"
    Option "Composite"
    EndSection


    Basically I would like to use the DVI input. But do I have a problem with
    configuration or monitor or graphics card.



    --
    faeychild

  2. Re: samsung 215TW monitor and DVI resolution

    faeychild wrote:

    [1680x1050 not working with DVI ...]
    > (--) NVIDIA(0):
    > (--) NVIDIA(0): Detailed Timings:
    > (--) NVIDIA(0): 1680 x 1050 @ 60 Hz
    > (--) NVIDIA(0): Pixel Clock : 146.25 MHz
    > (--) NVIDIA(0): HRes, HSyncStart : 1680, 1784
    > (--) NVIDIA(0): HSyncEnd, HTotal : 1960, 2240
    > (--) NVIDIA(0): VRes, VSyncStart : 1050, 1053
    > (--) NVIDIA(0): VSyncEnd, VTotal : 1059, 1089
    > (--) NVIDIA(0): H/V Polarity : -/+
    > (--) NVIDIA(0):

    [...]
    > (--) NVIDIA(0): Samsung SyncMaster (DFP-0): 135.0 MHz maximum pixel clock
    > (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Single Link TMDS
    > (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Native FlatPanel Scaling is
    > (--) NVIDIA(0): supported
    > (--) NVIDIA(0): Samsung SyncMaster (DFP-0): DFP modes are limited to 60 Hz
    > (--) NVIDIA(0): refresh rate

    [...]
    I think the problem is, that you are trying to use a timing with 146.25 MHz
    pixel clock on a DVI link with 135.0 MHz maximum pixel clock.

  3. Re: samsung 215TW monitor and DVI resolution

    Markus Kossmann wrote:

    > faeychild wrote:
    >
    > [1680x1050 not working with DVI ...]
    >> (--) NVIDIA(0):
    >> (--) NVIDIA(0): Detailed Timings:
    >> (--) NVIDIA(0): 1680 x 1050 @ 60 Hz
    >> (--) NVIDIA(0): Pixel Clock : 146.25 MHz
    >> (--) NVIDIA(0): HRes, HSyncStart : 1680, 1784
    >> (--) NVIDIA(0): HSyncEnd, HTotal : 1960, 2240
    >> (--) NVIDIA(0): VRes, VSyncStart : 1050, 1053
    >> (--) NVIDIA(0): VSyncEnd, VTotal : 1059, 1089
    >> (--) NVIDIA(0): H/V Polarity : -/+
    >> (--) NVIDIA(0):

    > [...]
    >> (--) NVIDIA(0): Samsung SyncMaster (DFP-0): 135.0 MHz maximum pixel clock
    >> (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Single Link TMDS
    >> (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Native FlatPanel Scaling is
    >> (--) NVIDIA(0): supported
    >> (--) NVIDIA(0): Samsung SyncMaster (DFP-0): DFP modes are limited to 60 Hz
    >> (--) NVIDIA(0): refresh rate

    > [...]
    > I think the problem is, that you are trying to use a timing with 146.25 MHz
    > pixel clock on a DVI link with 135.0 MHz maximum pixel clock.


    The native refresh rate, analog and dvi, is 1680x1050 at 60 hz

    According to the manual specs..

    General
    Model Name SyncMaster 215TW
    LCD Panel
    Size 21" Wide Diagonal (54 cm)
    Display area 518.4 mm (H) x 324.0 mm (V)
    Pixel Pitch 0.270 mm (H) x 0.270 mm (V)
    Synchronization
    Horizontal 30 ~ 81 kHz
    Vertical 56 ~ 75 Hz
    Display Color
    16.7M Colors (8bit)
    Resolution
    Optimum resolution WSXGA 1680 x 1050 @ 60 Hz (Analog/Digital)
    Maximum resolution WSXGA 1680 x 1050 @ 60 Hz (Analog/Digital)
    Input Signal,Terminated
    RGB Analog, Compliant Digital RGB
    0.7 Vp-p 5%,TTL level (V high ? 2.0V, V low ? 0.8V)


    So how can I achieve this claimed resolution if the link bandwidth is limited.
    I assume it's possible or Samsung would be in conflict.

    --
    faeychild

  4. Re: samsung 215TW monitor and DVI resolution

    faeychild writes:
    >Markus Kossmann wrote:
    >
    >> faeychild wrote:
    >>
    >> [1680x1050 not working with DVI ...]
    >>> (--) NVIDIA(0):
    >>> (--) NVIDIA(0): Detailed Timings:
    >>> (--) NVIDIA(0): 1680 x 1050 @ 60 Hz
    >>> (--) NVIDIA(0): Pixel Clock : 146.25 MHz
    >>> (--) NVIDIA(0): HRes, HSyncStart : 1680, 1784
    >>> (--) NVIDIA(0): HSyncEnd, HTotal : 1960, 2240
    >>> (--) NVIDIA(0): VRes, VSyncStart : 1050, 1053
    >>> (--) NVIDIA(0): VSyncEnd, VTotal : 1059, 1089
    >>> (--) NVIDIA(0): H/V Polarity : -/+
    >>> (--) NVIDIA(0):

    >> [...]
    >>> (--) NVIDIA(0): Samsung SyncMaster (DFP-0): 135.0 MHz maximum pixel clock
    >>> (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Single Link TMDS
    >>> (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Native FlatPanel Scaling is
    >>> (--) NVIDIA(0): supported
    >>> (--) NVIDIA(0): Samsung SyncMaster (DFP-0): DFP modes are limited to 60 Hz
    >>> (--) NVIDIA(0): refresh rate

    >> [...]
    >> I think the problem is, that you are trying to use a timing with 146.25 MHz
    >> pixel clock on a DVI link with 135.0 MHz maximum pixel clock.

    ....
    >So how can I achieve this claimed resolution if the link bandwidth is limited.
    >I assume it's possible or Samsung would be in conflict.


    My guess is that the Windows drivers ignore that bandwidth limit; I am
    not sure where the limit is coming from, but it is probably just a
    programming error in that place. I know the Matrox G450 has a 122MHz
    (or so) DVI-D bandwidth limit, but I would not expect it from a Gforce
    5200. Even the old and low-end Radeon 7000 does not have such a
    limit.

    I don't know how you can convince X to go beyond this limit, but one
    option you have is to use a mode that does not exceed this limit, by
    reducing the blanking intervals (which can be very short on a flat
    panel, because they are not needed to change magnetisation), and/or by
    reducing the vsync frequency.

    E.g., you could try a mode like

    ModeLine "1680x1050" 135 1680 1784 1960 2208 1050 1053 1059 1089 +hsync -vsync

    which has a 135MHz dot clock and 56.1 Hz vertical refresh.

    Yes, I have done such things successfully, although with a different
    monitor, graphics card, and mode:
    , see the G450
    stuff.

    - anton
    --
    M. Anton Ertl Some things have to be seen to be believed
    anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
    http://www.complang.tuwien.ac.at/anton/home.html

  5. Re: samsung 215TW monitor and DVI resolution

    Anton Ertl wrote:


    >
    > E.g., you could try a mode like
    >
    > ModeLine "1680x1050" 135 1680 1784 1960 2208 1050 1053 1059 1089 +hsync
    > -vsync
    >
    > which has a 135MHz dot clock and 56.1 Hz vertical refresh.
    >

    I ran the modified xorg.conf

    Section "Monitor"

    # Monitor preferred modeline (60.0 Hz vsync, 65.3 kHz hsync, ratio 16/10)
    Identifier "monitor1"
    VendorName "Plug'n Play"
    ModelName "SyncMaster"
    HorizSync 30.0 - 81.0
    VertRefresh 56.0 - 75.0
    ModeLine "1680x1050_test" 135 1680 1784 1960 2208 1050 1053 1059 1089
    +hsync -vsync
    EndSection

    Section "Device"
    Identifier "device1"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "NVIDIA GeForce FX - GeForce 7950"
    EndSection

    Section "Screen"
    Identifier "screen1"
    Device "device1"
    Monitor "monitor1"
    DefaultDepth 24
    Option "DPMS"
    SubSection "Display"
    Depth 24
    Modes "1680x1050_test"
    EndSubSection
    EndSection

    Section "Extensions"
    Option "Composite"
    EndSection

    The DVI failed and the analog display was over scanned horizontally and
    vertically.

    I assume that it is OK to run both DVI and Analog connectors concurrently

    --
    faeychild

+ Reply to Thread