nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   1080i (http://www.nvnews.net/vbulletin/showthread.php?t=69255)

reub2000 04-28-06 07:30 AM

1080i
 
I have my 1080i TV hooked up to my mytv box using a hdmi-dvi cable connected to the GeForce 6600. However the video card refuses to work in 1080i. Apparently the TV is sending an EDID signal telling the video card it can't handle 1080i. However disabling EDID mode validation makes it so that no mode is getting validated at all.

Here are the modelines that I found on the gentoo wiki that I'm using:
Code:

      ModeLine        "720p" 73.825 1280 1320 1368 1640 720 722 724 751 +hsync +vsync
      ModeLine "1080i" 74.52 1920 1952 2016 2208 1080 1084 1096 1126 -hsync -vsync interlace

Here is the relevant part of the log file with EDID modes disabled:
Code:

(II) NVIDIA(0): NVIDIA GPU GeForce 6600 at PCI:1:0:0
(--) NVIDIA(0): VideoRAM: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 05.43.02.60.df
(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 6600 at PCI:1:0:0:
(--) NVIDIA(0):    TSB TSB-H84s (DFP-0)
(--) NVIDIA(0): TSB TSB-H84s (DFP-0): 155 MHz maximum pixel clock
(--) NVIDIA(0): TSB TSB-H84s (DFP-0): Internal Single Link TMDS
(II) NVIDIA(0): Mode Validation Overrides for TSB TSB-H84s (DFP-0):
(II) NVIDIA(0):    NoEdidModes
(WW) NVIDIA(0): Mode "720p" is too large for TSB TSB-H84s (DFP-0);
(WW) NVIDIA(0):    discarding.
(WW) NVIDIA(0): Mode "1080i" is too large for TSB TSB-H84s (DFP-0);
(WW) NVIDIA(0):    discarding.
(WW) NVIDIA(0): Mode "640x480" is too large for TSB TSB-H84s (DFP-0);
(WW) NVIDIA(0):    discarding.
(WW) NVIDIA(0): Mode "320x240" is too large for TSB TSB-H84s (DFP-0);
(WW) NVIDIA(0):    discarding.
(WW) NVIDIA(0): Mode "800x600" is too large for TSB TSB-H84s (DFP-0);
(WW) NVIDIA(0):    discarding.
(WW) NVIDIA(0): Mode "400x300" is too large for TSB TSB-H84s (DFP-0);
(WW) NVIDIA(0):    discarding.
(WW) NVIDIA(0): Mode "640x480" is too large for TSB TSB-H84s (DFP-0);
(WW) NVIDIA(0):    discarding.
(WW) NVIDIA(0): Mode "800x600" is too large for TSB TSB-H84s (DFP-0);
(WW) NVIDIA(0):    discarding.
(II) NVIDIA(0): Assigned Display Device: DFP-0
(WW) NVIDIA(0): No valid modes for "1080i"; removing.
(WW) NVIDIA(0): No valid modes for "720p"; removing.
(WW) NVIDIA(0): No valid modes for "800x600"; removing.
(WW) NVIDIA(0): No valid modes for "640x480"; removing.
(WW) NVIDIA(0):
(WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
(WW) NVIDIA(0):    "nvidia-auto-select".
(WW) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):    "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 800 x 600

Relevant section of log with EDID enabled:
Code:

(II) NVIDIA(0): NVIDIA GPU GeForce 6600 at PCI:1:0:0
(--) NVIDIA(0): VideoRAM: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 05.43.02.60.df
(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 6600 at PCI:1:0:0:
(--) NVIDIA(0):    TSB TSB-H84s (DFP-0)
(--) NVIDIA(0): TSB TSB-H84s (DFP-0): 155 MHz maximum pixel clock
(--) NVIDIA(0): TSB TSB-H84s (DFP-0): Internal Single Link TMDS
(WW) NVIDIA(0): Mode "1080i" is too large for TSB TSB-H84s (DFP-0);
(WW) NVIDIA(0):    discarding.
(II) NVIDIA(0): Assigned Display Device: DFP-0
(WW) NVIDIA(0): No valid modes for "1080i"; removing.
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):    "720p"
(II) NVIDIA(0):    "800x600"
(II) NVIDIA(0):    "640x480"
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 720
(**) NVIDIA(0): DPI set to (50, 50); computed from "DisplaySize" Monitor section option
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
        [0] 0  0      0xcc000000 - 0xccffffff (0x1000000) MX[b]
        [1] 0  0      0xc0000000 - 0xc7ffffff (0x8000000) MX[b]
        [2] 0  0      0xc8000000 - 0xcbffffff (0x4000000) MX[b]
        [3] -1  0      0xffe00000 - 0xffffffff (0x200000) MX[b](B)
        [4] -1  0      0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
        [5] -1  0      0x000f0000 - 0x000fffff (0x10000) MX[b]
        [6] -1  0      0x000c0000 - 0x000effff (0x30000) MX[b]
        [7] -1  0      0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [8] -1  0      0xd8000000 - 0xd8000fff (0x1000) MX[b]
        [9] -1  0      0xd8001000 - 0xd8001fff (0x1000) MX[b]
        [10] -1 0      0xd8002000 - 0xd8002fff (0x1000) MX[b]
        [11] -1 0      0xd8003000 - 0xd8003fff (0x1000) MX[b]
        [12] -1 0      0xd8005000 - 0xd80050ff (0x100) MX[b]
        [13] -1 0      0xd8004000 - 0xd8004fff (0x1000) MX[b]
        [14] -1 0      0xd4000000 - 0xd7ffffff (0x4000000) MX[b](B)
        [15] -1 0      0xd0000000 - 0xd3ffffff (0x4000000) MX[b](B)
        [16] -1 0      0xcc000000 - 0xccffffff (0x1000000) MX[b](B)
        [17] -1 0      0xc0000000 - 0xc7ffffff (0x8000000) MX[b](B)
        [18] -1 0      0xc8000000 - 0xcbffffff (0x4000000) MX[b](B)
        [19] 0  0      0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
        [20] 0  0      0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
        [21] 0  0      0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
        [22] -1 0      0x0000ffff - 0x0000ffff (0x1) IX[b]
        [23] -1 0      0x00000000 - 0x000000ff (0x100) IX[b]
        [24] -1 0      0x0000b000 - 0x0000b007 (0x8) IX[b]
        [25] -1 0      0x0000c400 - 0x0000c40f (0x10) IX[b]
        [26] -1 0      0x00000b60 - 0x00000b63 (0x4) IX[b]
        [27] -1 0      0x00000960 - 0x00000967 (0x8) IX[b]
        [28] -1 0      0x00000be0 - 0x00000be3 (0x4) IX[b]
        [29] -1 0      0x000009e0 - 0x000009e7 (0x8) IX[b]
        [30] -1 0      0x0000d800 - 0x0000d80f (0x10) IX[b]
        [31] -1 0      0x00000b70 - 0x00000b73 (0x4) IX[b]
        [32] -1 0      0x00000970 - 0x00000977 (0x8) IX[b]
        [33] -1 0      0x00000bf0 - 0x00000bf3 (0x4) IX[b]
        [34] -1 0      0x000009f0 - 0x000009f7 (0x8) IX[b]
        [35] -1 0      0x0000f000 - 0x0000f00f (0x10) IX[b]
        [36] -1 0      0x0000e000 - 0x0000e0ff (0x100) IX[b]
        [37] -1 0      0x0000dc00 - 0x0000dcff (0x100) IX[b]
        [38] -1 0      0x00004c40 - 0x00004c7f (0x40) IX[b]
        [39] -1 0      0x00004c00 - 0x00004c3f (0x40) IX[b]
        [40] -1 0      0x0000e400 - 0x0000e41f (0x20) IX[b]
        [41] 0  0      0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
        [42] 0  0      0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) NVIDIA(0): Setting mode "720p"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled


pe1chl 04-28-06 10:55 AM

Re: 1080i
 
Are you sure the TV can handle 1080i over DVI?

asdere 04-28-06 11:10 AM

Re: 1080i
 
Try using -logverbose 6 to find out why the 1080i is being rejected.
As a quick guess, you probably need :
Option "ModeValidation" ""NoVertRefreshCheck"

reub2000 04-28-06 03:22 PM

Re: 1080i
 
Quote:

Originally Posted by pe1chl
Are you sure the TV can handle 1080i over DVI?

It's a toshiba 46h84. It upscales everything to either 1080i or 540p.

From amazon.com:
" The set's HDMI (High-Definition Multimedia Interface) input allows a direct digital connection with a DTV set-top box or receiver. HDMI is a lossless, uncompressed, all-digital audio/video interface to link any audio/video source (such as a set-top box, DVD player, or AV receiver) with your TV or monitor. HDMI supports standard-definition (SD), enhanced definition (ED), or high-definition (HD) video, plus multi-channel digital audio--all using a single cable. It transmits all ATSC HDTV standards and supports up to 8-channel digital audio, with bandwidth to spare to accommodate future enhancements and requirements."

Kevin-B 04-28-06 03:40 PM

Re: 1080i
 
1 Attachment(s)
Quote:

Originally Posted by reub2000
I have my 1080i TV hooked up to my mytv box using a hdmi-dvi cable connected to the GeForce 6600. However the video card refuses to work in 1080i. Apparently the TV is sending an EDID signal telling the video card it can't handle 1080i. However disabling EDID mode validation makes it so that no mode is getting validated at all.

I have the same problem with my GeForce 6600 connected to a Sharp AQUOS LCD TV set running the NVidia 1.0.8756 driver. The Sharp AQUOS is capable of both 1080i and 720p. I was able to work around the problem noted by the original poster by setting NoVertRefreshCheck, but I'm running into a problem with the bounding box calculation for a 1080i mode defined in the configuration file. (I'll explain later why I want to do this.) Below, I've reproduced snippets of the log file and my configuration file to show where the problem lies. I've also attached a .zip file with the full /etc/X11/xorg.conf and /var/log/Xorg.0.log.

Here is a somewhat snipped copy of EDID report from /var/log/Xorg.0.log:
Code:

(--) NVIDIA(0): --- EDID for Sharp HDMI (DFP-0) ---
(--) NVIDIA(0): EDID Version                : 1.3
(--) NVIDIA(0): Manufacturer                : SHP
(--) NVIDIA(0): Monitor Name                : Sharp HDMI
(--) NVIDIA(0): Product ID                  : 4032
(--) NVIDIA(0): 32-bit Serial Number        : 16843009
(--) NVIDIA(0): Serial Number String        :
(--) NVIDIA(0): Manufacture Date            : 2005, week 0
(--) NVIDIA(0): DPMS Capabilities            : Active Off
(--) NVIDIA(0): Prefer first detailed timing : Yes
(--) NVIDIA(0): Supports GTF                : No
(--) NVIDIA(0): Maximum Image Size          : 820mm x 460mm
(--) NVIDIA(0): Valid HSync Range            : 15kHz - 46kHz
(--) NVIDIA(0): Valid VRefresh Range        : 59Hz - 61Hz
(--) NVIDIA(0):
(--) NVIDIA(0): Detailed Timings:
(--) NVIDIA(0):  1920 x 1080 @ 60Hz
(--) NVIDIA(0):    Pixel Clock      : 74.25 MHz
(--) NVIDIA(0):    HRes, HSyncStart : 1920, 2008
(--) NVIDIA(0):    HSyncEnd, HTotal : 2052, 2200
(--) NVIDIA(0):    VRes, VSyncStart : 540, 542
(--) NVIDIA(0):    VSyncEnd, VTotal : 547, 562
(--) NVIDIA(0):    H/V Polarity    : +/+
(--) NVIDIA(0):    Extra            : Interlaced
(--) NVIDIA(0):  720  x 480  @ 60Hz
(--) NVIDIA(0):    Pixel Clock      : 27.00 MHz
(--) NVIDIA(0):    HRes, HSyncStart : 720, 736
(--) NVIDIA(0):    HSyncEnd, HTotal : 798, 858
(--) NVIDIA(0):    VRes, VSyncStart : 480, 489
(--) NVIDIA(0):    VSyncEnd, VTotal : 495, 525
(--) NVIDIA(0):    H/V Polarity    : -/-
(--) NVIDIA(0):  1280 x 720  @ 60Hz
(--) NVIDIA(0):    Pixel Clock      : 74.25 MHz
(--) NVIDIA(0):    HRes, HSyncStart : 1280, 1390
(--) NVIDIA(0):    HSyncEnd, HTotal : 1430, 1650
(--) NVIDIA(0):    VRes, VSyncStart : 720, 725
(--) NVIDIA(0):    VSyncEnd, VTotal : 730, 750
(--) NVIDIA(0):    H/V Polarity    : +/+
(--) NVIDIA(0):  1440 x 480  @ 60Hz
(--) NVIDIA(0):    Pixel Clock      : 27.00 MHz
(--) NVIDIA(0):    HRes, HSyncStart : 1440, 1478
(--) NVIDIA(0):    HSyncEnd, HTotal : 1602, 1716
(--) NVIDIA(0):    VRes, VSyncStart : 240, 244
(--) NVIDIA(0):    VSyncEnd, VTotal : 247, 262
(--) NVIDIA(0):    H/V Polarity    : -/-
(--) NVIDIA(0):    Extra            : Interlaced
(--) NVIDIA(0):
(--) NVIDIA(0): CEA-861B Timings:
(--) NVIDIA(0):  1920 x 1080 @ 60Hz
(--) NVIDIA(0):    Pixel Clock      : 74.18 MHz
(--) NVIDIA(0):    HRes, HSyncStart : 1920, 2008
(--) NVIDIA(0):    HSyncEnd, HTotal : 2052, 2200
(--) NVIDIA(0):    VRes, VSyncStart : 540, 542
(--) NVIDIA(0):    VSyncEnd, VTotal : 547, 562
(--) NVIDIA(0):    H/V Polarity    : +/+
(--) NVIDIA(0):    Extra            : Interlaced
(--) NVIDIA(0):    CEA Format      : 5

The "ModePool" (from the same file) looks reasonable. (The actual reported ModePool is much larger; I've trimmed away the modes that I don't care about.)

Code:

(II) NVIDIA(0): Mode Validation Overrides for Sharp HDMI (DFP-0):
(II) NVIDIA(0):    AllowInterlacedModes
(II) NVIDIA(0):    NoVertRefreshCheck
(II) NVIDIA(0): Frequency information for Sharp HDMI (DFP-0):
(II) NVIDIA(0):  HorizSync  : 15.000-46.000 kHz
(II) NVIDIA(0):  VertRefresh : 59.000-61.000 Hz
(II) NVIDIA(0):    (HorizSync from EDID)
(II) NVIDIA(0):    (VertRefresh from EDID)
(II) NVIDIA(0):
(II) NVIDIA(0): --- Building ModePool for Sharp HDMI (DFP-0) ---
(II) NVIDIA(0):  Validating Mode "1920x1080":
(II) NVIDIA(0):    1920 x 540 @ 60Hz
(II) NVIDIA(0):    Mode Source: EDID
(II) NVIDIA(0):      Pixel Clock      : 74.25 MHz
(II) NVIDIA(0):      HRes, HSyncStart : 1920, 2008
(II) NVIDIA(0):      HSyncEnd, HTotal : 2052, 2200
(II) NVIDIA(0):      VRes, VSyncStart :  540,  542
(II) NVIDIA(0):      VSyncEnd, VTotal :  547,  562
(II) NVIDIA(0):      H/V Polarity    : +/+
(II) NVIDIA(0):      Extra            : Interlaced
(II) NVIDIA(0):    Mode is valid.
(II) NVIDIA(0):
(II) NVIDIA(0):  Validating Mode "1280x720":
(II) NVIDIA(0):    1280 x 720 @ 60Hz
(II) NVIDIA(0):    Mode Source: EDID
(II) NVIDIA(0):      Pixel Clock      : 74.25 MHz
(II) NVIDIA(0):      HRes, HSyncStart : 1280, 1390
(II) NVIDIA(0):      HSyncEnd, HTotal : 1430, 1650
(II) NVIDIA(0):      VRes, VSyncStart :  720,  725
(II) NVIDIA(0):      VSyncEnd, VTotal :  730,  750
(II) NVIDIA(0):      H/V Polarity    : +/+
(II) NVIDIA(0):    Mode is valid.
(II) NVIDIA(0):
(II) NVIDIA(0):  Validating Mode "1920x1080":
(II) NVIDIA(0):    1920 x 540 @ 60Hz
(II) NVIDIA(0):    Mode Source: EDID
(II) NVIDIA(0):      Pixel Clock      : 74.18 MHz
(II) NVIDIA(0):      HRes, HSyncStart : 1920, 2008
(II) NVIDIA(0):      HSyncEnd, HTotal : 2052, 2200
(II) NVIDIA(0):      VRes, VSyncStart :  540,  542
(II) NVIDIA(0):      VSyncEnd, VTotal :  547,  562
(II) NVIDIA(0):      H/V Polarity    : +/+
(II) NVIDIA(0):      Extra            : Interlaced
(II) NVIDIA(0):    Mode is valid.
(II) NVIDIA(0):
(II) NVIDIA(0):  Validating Mode "1920x1080_kev":
(II) NVIDIA(0):    1920 x 540 @ 60Hz
(II) NVIDIA(0):    Mode Source: X Server
(II) NVIDIA(0):      Pixel Clock      : 74.20 MHz
(II) NVIDIA(0):      HRes, HSyncStart : 1920, 2008
(II) NVIDIA(0):      HSyncEnd, HTotal : 2052, 2200
(II) NVIDIA(0):      VRes, VSyncStart :  540,  542
(II) NVIDIA(0):      VSyncEnd, VTotal :  547,  562
(II) NVIDIA(0):      H/V Polarity    : +/+
(II) NVIDIA(0):      Extra            : Interlaced
(II) NVIDIA(0):    Mode is valid.
(II) NVIDIA(0):
(II) NVIDIA(0):  Validating Mode "1224x688":
(II) NVIDIA(0):    1224 x 688 @ 60Hz
(II) NVIDIA(0):    Mode Source: X Server
(II) NVIDIA(0):      Pixel Clock      : 74.20 MHz
(II) NVIDIA(0):      HRes, HSyncStart : 1224, 1356
(II) NVIDIA(0):      HSyncEnd, HTotal : 1396, 1648
(II) NVIDIA(0):      VRes, VSyncStart :  688,  709
(II) NVIDIA(0):      VSyncEnd, VTotal :  714,  750
(II) NVIDIA(0):      H/V Polarity    : -/-
(II) NVIDIA(0):    Mode is valid.

Of particular interest (to me anyway) are the modes 1920x1080_kev and 1224x688. 1920x1080_kev is 1080i mode which is nearly identical to the ones from the EDID, but for some reasons the size of the Bounding Box is computed incorrectly. I'll have more to say about this later. My intent was to start out with a working 1080i modeline that I define myself and then tweak it to remove the overscan. An example of this is the 1224x688 mode that I created. This started out as a 720p mode. I adjusted some of the parameters to fix the overscan problem on my TV. My hope is that by using a tweaked 1080i mode, I might end up with a mode that's closer to the native resolution of my TV (1366x768). (I'm guessing that when I'm finally able to do this, I'll end up with something along the lines of 1834x1032. Not exactly what I was hoping for, but I'd like to try it anyway...)

Now, back to my findings...

As I said earlier, the inital ModePool report looks good. But later on, there's a more abbreviated report which doesn't look so good:

Code:

(II) NVIDIA(0): --- Modes in ModePool for Sharp HDMI (DFP-0) ---
(II) NVIDIA(0): "nvidia-auto-select"  : 1920 x 1080 @ 120.1 Hz Interlaced  (from: EDID)
(II) NVIDIA(0): "1920x1080"            : 1920 x 1080 @ 120.1 Hz Interlaced  (from: EDID)
(II) NVIDIA(0): "1920x1080_120i"      : 1920 x 1080 @ 120.1 Hz Interlaced  (from: EDID)
(II) NVIDIA(0): "1920x1080_120i_0"    : 1920 x 1080 @ 120.0 Hz Interlaced  (from: EDID)
<snip>
(II) NVIDIA(0): "1280x720"            : 1280 x  720 @  60.0 Hz  (from: EDID)
(II) NVIDIA(0): "1280x720_60"          : 1280 x  720 @  60.0 Hz  (from: EDID)
(II) NVIDIA(0): "1280x720_60_0"        : 1280 x  720 @  59.9 Hz  (from: EDID)
(II) NVIDIA(0): "1280x720_60_1"        : 1280 x  720 @  60.0 Hz  (from: X Server)
(II) NVIDIA(0): "1224x688"            : 1224 x  688 @  60.0 Hz  (from: X Server)
(II) NVIDIA(0): "1224x688_60"          : 1224 x  688 @  60.0 Hz  (from: X Server)
<snip snip>

(There are more modes than this listed, but I'm striving for brevity. :) )

For the 1920x1080 modes, note the refresh rate: 120 (or so) Hz. Not good. This is why these modes get tossed out if you don't have enable NoVertRefreshCheck set for the ModeValidation option.

Now we come to the problem of the bounding box for the mode (1920x1080_kev) that I created:

Code:

(II) NVIDIA(0): Assigned Display Device: DFP-0
(II) NVIDIA(0): Requested modes:
(II) NVIDIA(0):    "1920x1080"
(II) NVIDIA(0):    "1920x1080_kev"
(II) NVIDIA(0):    "1224x688"
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): MetaMode "1920x1080":
(II) NVIDIA(0):    Bounding Box: [0, 0, 1920, 1080]
(II) NVIDIA(0):    Sharp HDMI (DFP-0): "1920x1080"
(II) NVIDIA(0):        Size          : 1920 x 1080
(II) NVIDIA(0):        Offset        : +0 +0
(II) NVIDIA(0):        Panning Domain: @ 1920 x 1080
(II) NVIDIA(0):        Position      : [0, 0, 1920, 1080]
(II) NVIDIA(0): MetaMode "1920x1080_kev":
(II) NVIDIA(0):    Bounding Box: [0, 0, 1920, 540]
(II) NVIDIA(0):    Sharp HDMI (DFP-0): "1920x1080_kev"
(II) NVIDIA(0):        Size          : 1920 x 540
(II) NVIDIA(0):        Offset        : +0 +0
(II) NVIDIA(0):        Panning Domain: @ 1920 x 540
(II) NVIDIA(0):        Position      : [0, 0, 1920, 540]
(II) NVIDIA(0): MetaMode "1224x688":
(II) NVIDIA(0):    Bounding Box: [0, 0, 1224, 688]
(II) NVIDIA(0):    Sharp HDMI (DFP-0): "1224x688"
(II) NVIDIA(0):        Size          : 1224 x 688
(II) NVIDIA(0):        Offset        : +0 +0
(II) NVIDIA(0):        Panning Domain: @ 1224 x 688
(II) NVIDIA(0):        Position      : [0, 0, 1224, 688]
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
(II) NVIDIA(0): Computing DPI from Sharp HDMI (DFP-0)'s EDID
(II) NVIDIA(0):  width  : 1920 pixels  820  mm (DPI: 59)
(II) NVIDIA(0):  height : 1080 pixels  460  mm (DPI: 59)

Note that the bounding box for mode 1920x1080 was computed correctly, but that (IMO, anyway) the mode for 1920x1080_kev was not. For 1920x1080, the height (number of rows) is 1080 (which is correct). But for 1920x1080_kev, the height is calculated as 540, which is half of what it should be. I'm guessing that the bounding box calculation is unaware of the fact that this is an interlaced mode.

As you might expect, when I switch to 1920x1080_kev, everything looks twice as tall as it should be.

Additional Info:

Here's the relevant portions from /etc/X11/xorg.conf:

Code:

Section "Monitor"
    Identifier    "Monitor0"
    VendorName    "Sharp"
    ModelName      "DFP-0"
    HorizSync      15.0 - 46.0
    VertRefresh    59.0 - 61.0
    ModeLine      "1920x1080_kev" 74.2 1920 2008 2052 2200 540 542 547 562 +hsync +vsync interlace
    ModeLine      "1832x1032" 74.2 1832 2008 2052 2200 516 542 547 562 +hsync +vsync interlace
    ModeLine      "1224x688" 74.2 1224 1356 1396 1648 688 709 714 750 -hsync -vsync
    ModeLine      "1192x672" 74.2 1192 1336 1376 1648 672 677 682 750 -hsync -vsync
    Option        "dpms"
    Option        "ExactModeTimingsDVI" "true"
EndSection

Section "Device"
    Identifier    "Videocard0"
    Driver        "nvidia"
    VendorName    "Videocard vendor"
    BoardName      "NVIDIA GeForce 6600"
EndSection

Section "Screen"
    Identifier    "Screen0"
    Device        "Videocard0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option        "ConnectedMonitor" "DFP"
    Option        "FlatPanelProperties" "native"
    Option        "ModeValidation" "AllowInterlacedModes, NoVertRefreshCheck"
    SubSection    "Display"
        Viewport    0 0
        Depth      16
        Modes      "800x600" "640x480"
    EndSubSection
    SubSection    "Display"
        Viewport    0 0
        Depth      24
        Modes      "1920x1080" "1920x1080_kev" "1224x688"
    EndSubSection
EndSection

Hopefully, this report will help the original poster work around the problem encountered. Hopefully, too it will help NVidia tech support pass along the relevant information to someone capable of fixing the bounding box problem.

pest_789 11-11-06 08:05 PM

Re: 1080i
 
1 Attachment(s)
Has anything been done about this problem? I've got exactly the same issue with 1080i over DVI with 9629

netllama 11-11-06 08:17 PM

Re: 1080i
 
Which 'same issue' are you having with 1080i? According to your bug report, X is running with your 1920x1080i modeline.

pest_789 11-12-06 01:09 AM

Re: 1080i
 
Yeah that modeline doesnt display - I'm talking about the EDID data coming up at 120Hz vertical refresh at 540 lines for a 1080i Tv that never in a million years would report a 120hz mode for what should be a 1080i 30hz mode. Your EDID reading has been broken for several versions and nothing has been done about it since april. I'll upload another bug report that shows the driver trying to give my tv a 120hz 1920x540 'interlaced' mode if you really need that to investigate a problem that's existed since at least april.

pest_789 11-12-06 01:23 AM

Re: 1080i
 
1 Attachment(s)
Here's another bug report showing things 'working' with a supposed 120hz 1920x540 interlaced mode which my tv and those of two other people supposedly asked for. Like the other guys, I get the top half of the screen showing at double height and flickering like it's really interlaced. Please realize that just because it SAYS it's working, doesn't mean the output is usable. At the same time, my other myth box connected to this tv with a component cable works just fine. It's only over DVI that your driver mis-interprets the EDID info and gives an incorrect picture.

That's what I meant by 'exactly the same issue'.

Why do you have such a bitchy attitude toward your loyal customers who just want the hardware they paid good money for to work? I've got this card, a 6600gt, and two 7950gs cards in constant use in my house and a 7800gt sitting in my garage in a box because I don't have a machine that needs a pci-e video card at the moment, but your crap attitude has got me wondering if there isn't a better game in town.

pest_789 11-13-06 01:57 PM

Re: 1080i
 
bump

asdere 11-13-06 04:28 PM

Re: 1080i
 
I have the same problem with the EDID based 1920x1080 interlaced mode that my TV reports. Basically, my guess is the driver doesn't calculate the 1080 when the TV responds with 1920x540 interlace. So, the resolution that the driver sets up is 540interlaced with a virtual desktop size of 1920x1080, which ends up showing the top portions to the TV at 270lines of resolution.

Using this modeline for my TV:
ModeLine "1080i3" 148.4 1920 2008 2052 2200 1080 1084 1094 1125 +hsync +vsync interlace

Gives me 1920x1080 interlaced output. Basically I doubled all the values for the vertical info from the EDID and also doubled the clock rate (from 74.18 rounded up). From the logs, this effectively gave me:
1920x1080 interlace at 60hz, which I think is correct for 1080i.

Beta driver 9742 is the first release that has enabled me to play videos via XV/XVMC over DVI without lockups on PCI-E or onboard 6150! So I'm super happy about that, although the jitter problems still persists for interlaced videos. The quick and dirty solution for me on the jitter/stuttering was just to deinterlace, which wasn't necessary with 8183. Searching and playing around, my guess is something got changed with vertical syncs after 8183... the jitters doesn't happen at the same spots everytime, sometimes it's smooth and othertimes stuttery, so perhaps a timing issue. With mythv, turning on opengl v-sync smoothed things out, but causes mythtv to crash after each video, so for now I'll stick with deinterlacing 1080i content for 1080i output (upgraded to FC6 so 8183 isn't a viable fallback anymore).
I figured perhaps it was a speed problem, but this happens with 6150 onboard, 6200 TC, 6600 and 7900GT. The jitters were there with VGA/Component output too, so not limited to just DVI.

pest_789 11-13-06 05:40 PM

Re: 1080i
 
AHA! Good thinking! I will give that modeline a try when I get home. Thanks!


All times are GMT -5. The time now is 05:54 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.