Results 1 to 8 of 8

Thread: No display on new 2048 * 1152 monitor

Hybrid View

  1. #1
    Join Date
    Nov 2007
    Posts
    117

    Default No display on new 2048 * 1152 monitor

    I bought a new Samsung 2343BWZ monitor; one of the new 16:9 form factor monitors with a native resolution of 2048 * 1152.

    I plugged it in and reboot my machine, and I get no display. What is the most likely cause?

    Sapphire 4670 card (RV730XT)
    Fedora 9
    kernel 2.6.27.21-78.2.41.fc9.x86_64
    xorg-x11-drv-ati-6.8.0-19.fc9.x86_64
    xorg-x11-drv-radeonhd-1.2.4-1.1.20081212git.fc9.x86_64
    xorg-x11-server-Xorg-1.5.2-6.fc9.x86_64
    xorg-x11-server-common-1.5.2-6.fc9.x86_64

    I tried the "radeon" driver, and I tried the "radeonhd" driver.
    I used a DVI-D single link cable.

    If I calculated properly, this should only take a single link DVI cable. Is that correct? cuz that's what ships with the monitor.

    Does either the radeon or radeonhd driver support this resolution? Would newer versions of the driver help?

    From Xorg.0.log:
    (II) RADEONHD(0): EDID data for SyncMaster
    (II) RADEONHD(0): Manufacturer: SAM Model: 41f Serial#: 1297691187
    (II) RADEONHD(0): Year: 2009 Week: 11
    (II) RADEONHD(0): EDID Version: 1.3
    (II) RADEONHD(0): Digital Display Input
    (II) RADEONHD(0): Max Image Size [cm]: horiz.: 51 vert.: 29
    (II) RADEONHD(0): Gamma: 2.20
    (II) RADEONHD(0): DPMS capabilities: Off
    (II) RADEONHD(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    (II) RADEONHD(0): First detailed timing is preferred mode
    (II) RADEONHD(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
    (II) RADEONHD(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
    (II) RADEONHD(0): Supported VESA Video Modes:
    (II) RADEONHD(0): 640x480@60Hz
    (II) RADEONHD(0): 800x600@56Hz
    (II) RADEONHD(0): 800x600@60Hz
    (II) RADEONHD(0): 1024x768@60Hz
    (II) RADEONHD(0): Manufacturer's mask: 0
    (II) RADEONHD(0): Supported Future Video Modes:
    (II) RADEONHD(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    (II) RADEONHD(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    (II) RADEONHD(0): #2: hsize: 1280 vsize 800 refresh: 60 vid: 129
    (II) RADEONHD(0): #3: hsize: 1440 vsize 900 refresh: 60 vid: 149
    (II) RADEONHD(0): #4: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    (II) RADEONHD(0): Supported additional Video Mode:
    (II) RADEONHD(0): clock: 156.8 MHz Image Size: 510 x 287 mm
    (II) RADEONHD(0): h_active: 2048 h_sync: 2096 h_sync_end 2128 h_blank_end 2208 h_border: 0
    (II) RADEONHD(0): v_active: 1152 v_sync: 1155 v_sync_end 1160 v_blanking: 1185 v_border: 0
    (II) RADEONHD(0): Ranges: V min: 56 V max: 60 Hz, H min: 30 H max: 81 kHz, PixClock max 160 MHz
    (II) RADEONHD(0): Monitor name: SyncMaster
    (II) RADEONHD(0): Serial No: H9NS301393
    (II) RADEONHD(0): EDID (in hex):
    (II) RADEONHD(0): 00ffffffffffff004c2d1f043332594d
    (II) RADEONHD(0): 0b13010380331d782aee91a3544c9926
    (II) RADEONHD(0): 0f50542308008180814081009500b300
    (II) RADEONHD(0): 0101010101013b3d00a0808021403020
    (II) RADEONHD(0): 3500fe1f1100001a000000fd00383c1e
    (II) RADEONHD(0): 5110000a202020202020000000fc0053
    (II) RADEONHD(0): 796e634d61737465720a2020000000ff
    (II) RADEONHD(0): 0048394e533330313339330a202000ee
    (II) RADEONHD(0): Calling DAC_LoadDetection
    (II) RADEONHD(0): DAC_LoadDetection Successful
    (II) RADEONHD(0): Output VGA_1 disconnected
    (II) RADEONHD(0): Output DVI-D_1 disconnected
    (II) RADEONHD(0): Output DVI-I_2/digital connected
    (II) RADEONHD(0): Output DVI-I_2/analog disconnected
    (II) RADEONHD(0): Using exact sizes for initial modes
    (II) RADEONHD(0): Output DVI-I_2/digital using initial mode 2048x1152
    (II) RADEONHD(0): RandR 1.2 support enabled
    (==) RADEONHD(0): RGB weight 888
    (==) RADEONHD(0): Default visual is TrueColor
    (==) RADEONHD(0): Using gamma correction (1.0, 1.0, 1.0)
    (II) RADEONHD(0): Using 2048x2048 Framebuffer with 2048 pitch
    (II) RADEONHD(0): FB: Allocated ScanoutBuffer at offset 0x00008000 (size = 0x01000000)
    (==) RADEONHD(0): DPI set to (96, 96)
    ...

    I don't see any "EE" lines that are relevant. What should I be looking for?

  2. #2
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,514

    Default

    According to the following I *think* you should be OK with single link, assuming I correctly remember that the limit is 165 MHz for single link.

    (II) RADEONHD(0): Supported additional Video Mode:
    (II) RADEONHD(0): clock: 156.8 MHz Image Size: 510 x 287 mm
    (II) RADEONHD(0): h_active: 2048 h_sync: 2096 h_sync_end 2128 h_blank_end 2208 h_border: 0
    (II) RADEONHD(0): v_active: 1152 v_sync: 1155 v_sync_end 1160 v_blanking: 1185 v_border: 0
    (II) RADEONHD(0): Ranges: V min: 56 V max: 60 Hz, H min: 30 H max: 81 kHz, PixClock max 160 MHz
    Can you pastebin the entire log ?

    I'm not sure that 1.2.4 completely supports the 4670 though, will check... EDIT - yeah, should be OK. I also checked the H and V frequencies and confirmed that they were in range as well. Might be something related to "TMDS Coherent Mode", I think radeonhd defaults to incoherent; if so then trying coherent would be a good next step (TMDS coherent mode refers to the detailed timing relationship between clock edges and data transitions, nothing to do with the developers state of mind ).

    The "radeon" driver you used (6.8.0) is much too old to support 4670; we're at 6.12.2 today.
    Last edited by bridgman; 04-22-2009 at 03:41 PM.

  3. #3
    Join Date
    Dec 2007
    Posts
    2,395

    Default

    You might also want to try xf86-video-ati from git. I just added support for fractional feedback dividers which should allows us to hit much closer to the target dot clock since 156.8 MHz can not be hit exactly with most common reference clocks.

  4. #4
    Join Date
    Nov 2007
    Posts
    117

    Default

    I don't seem to be allowed to make attachments, so I put the file on my web server here: Xorg.0.log.old

    I don't see any occurrence of either "TMDS" or "coherent" in the log file.

    Would I be able to try the git driver version on my current system, or would I need to update several other things as well, such as X server? I don't want to wander too far off the reservation.

    I am planning to update to Fedora 11 when it goes full release, should be about another month.

  5. #5
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,514

    Default

    You should be able to use the latest drivers on older X servers.

    Pastebin and nopaste are good for posting logs.

  6. #6
    Join Date
    Nov 2007
    Posts
    117

    Default

    OK, it's been pastebinned.

    m1de12abf

  7. #7
    Join Date
    Nov 2007
    Posts
    117

    Default

    It's working now.

    I tried adding an Option "coherent" line, but it seems to work with or without it.

    I had to hit the "source" button on the monitor to get it to pick up. Maybe because I turned on the monitor before the computer? I guess I didn't try hard enough the first time; I changed both the monitor and card at the same time.

    Thanks for your efforts.

  8. #8
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,514

    Default

    Most monitors let you cycle through inputs, and one of the options in the cycle is "auto" (which looks for an active input). If the monitor wasn't set to DVI or "auto" then I don't think power-up sequence would make a difference.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •