LinHES Forums • View topic - Jealous of those who have 1080i working

Board index KnoppMyth DTV

All times are UTC - 6 hours

Jealous of those who have 1080i working - I'm strug-a-ling

Page 1 of 2

[ 19 posts ]

Go to page 1, 2 Next

Print view

Previous topic Next topic

Author

Message

mihanson

Post subject: Jealous of those who have 1080i working - I'm strug-a-ling

Posted: Fri Dec 09, 2005 2:19 am

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

First, the set up:

Knoppmyth R5A26
HD-3000
Pentium 4 630 3.0 GHz (w/HT enabled; SpeedStep set to Maximum)
FX 5200 128 MB Nvidia card using DVI out to a Westinghouse LVM-37w1 LCD Flat Pannel capable of 1080i, 720p, 480p and 480i according to the manual
...
(the rest is in my signature below.)

I'm using my OTA antenna and tuned to the local PBS affiliate, KCET here in Los Angeles. I'm pretty sure they're broadcasting in 1080i. I've tried many different 1080i modelines, including custom made lines I created with http://xtiming.sourceforge.net. Many are validated in my XFree86.0.log, but none have worked. I've tried this with the 8174 Nvidia drivers as well as the old 6629 drivers. XvMC on and off, different deinterlacing methods (Bob, Linear Blend, OFF, et al). Everytime I get a picture with tearing, stuttering (especially on pans across the screen) and horizontal lines throughout the picture that I can't find the words to describe. The only headway I can make is if I use xrandr to change my screen to 1280x720. Then, and only then, does the tearing, stuttering and the horizontal lines go away, BUT the picture quality is definately not as sharp as HD should be and it appears as if I zoomed in, cutting off all kinds of picture information, especially on the right and the bottom. When I run top, I can see that my CPU is running at about 80% without XvMC and about 30% with XvMC enabled. My memory is nearly all used up (512MB), so that may be part of the problem, but I don't want to throw more money at this box if that will not solve the problem.

I'm beginning to feel the pressure from my wife to get this thing going. It's been two weeks. My wife asked me today why I'm doing "everything" the hard way. She wants to see a return on the investment of this shiney new HDTV. When mama's not happy, nobody's happy. :wink:

Found these lines in my mythbackend.log:

Code:

2005-12-08 23:02:42.782 Changing from WatchingLiveTV to None
2005-12-08 23:02:42.978 Closing DVB recorder
2005-12-08 23:02:43.094 MainServer::HandleAnnounce Playback
2005-12-08 23:02:43.099 adding: mythbox as a client (events: 0)
2005-12-08 23:02:43.126 MainServer::HandleAnnounce Playback
2005-12-08 23:02:43.131 adding: mythbox as a client (events: 0)
2005-12-08 23:02:43.142 adding: mythbox as a remote ringbuffer
2005-12-08 23:02:43.166 Changing from None to WatchingLiveTV
2005-12-08 23:02:43.267 Can't enable VBI recording
vbi: Invalid argument
2005-12-08 23:02:50.715 ret_pid(0) child(6715) status(0x0)
2005-12-08 23:02:51.725 ret_pid(0) child(6715) status(0x0)
2005-12-08 23:02:52.734 ret_pid(0) child(6715) status(0x0)
2005-12-08 23:02:53.743 ret_pid(6715) child(6715) status(0x0)
2005-12-08 23:02:53.747 External Tuning program exited with no error
2005-12-08 23:03:16.593 ret_pid(0) child(6727) status(0x0)
2005-12-08 23:03:17.606 ret_pid(0) child(6727) status(0x0)
2005-12-08 23:03:18.616 ret_pid(0) child(6727) status(0x0)
2005-12-08 23:03:19.625 ret_pid(6727) child(6727) status(0x0)
2005-12-08 23:03:19.629 External Tuning program exited with no error

I'm not ure what the VBI error is...

Below is the relevant output of my XFree86.0.log and the relevant parts of my XF86Config-4 file.

Code:

(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): Option "NoLogo" "1"
(**) NVIDIA(0): Option "HWcursor" "1"
(**) NVIDIA(0): Option "NvAGP" "3"
(**) NVIDIA(0): Option "ConnectedMonitor" "DFP"
(**) NVIDIA(0): Option "TVStandard" "HD1080i"
(**) NVIDIA(0): Option "RenderAccel" "1"
(**) NVIDIA(0): Enabling experimental RENDER acceleration
(**) NVIDIA(0): ConnectedMonitor string: "DFP"
(**) NVIDIA(0): TV Standard string: "HD1080i"
(--) NVIDIA(0): Linear framebuffer at 0xC8000000
(--) NVIDIA(0): MMIO registers at 0xDA000000
(II) NVIDIA(0): NVIDIA GPU detected as: GeForce FX 5200
(--) NVIDIA(0): VideoBIOS: 04.34.20.87.00
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): VideoRAM: 131072 kBytes
(II) NVIDIA(0): Using ConnectedMonitor string "DFP-0"
(--) NVIDIA(0): DFP-0: maximum pixel clock: 135 MHz
(--) NVIDIA(0): DFP-0: Internal Single Link TMDS
(II) NVIDIA(0): Frequency information for DFP-0:
(II) NVIDIA(0):   HorizSync   : 30.000-80.000 kHz
(II) NVIDIA(0):   VertRefresh : 50.000-75.000 Hz
(II) NVIDIA(0):      (HorizSync from EDID)
(II) NVIDIA(0):      (VertRefresh from EDID)
(II) NVIDIA(0): Adding EDID-provided mode "1920x1080" for DFP-0.
(II) NVIDIA(0): Monitor0: Using hsync range of 30.00-80.00 kHz
(II) NVIDIA(0): Monitor0: Using vrefresh range of 50.00-75.00 Hz
(II) NVIDIA(0): Clock range:  12.00 to 135.00 MHz
(II) NVIDIA(0): Not using default mode "640x350" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x175" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x400" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x200" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "720x400" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "360x200" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x240" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "800x600" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "400x300" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "512x384" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "512x384" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using mode "1920x1080" (bad mode clock/interlace/doublescan)
(WW) NVIDIA(0): Not using mode "800x600" (height 1200 is larger than
(WW) NVIDIA(0):      EDID-specified maximum 1080)
(WW) NVIDIA(0): Not using mode "1152x768":
(WW) NVIDIA(0):   horizontal sync start (1178) not a multiple of 8
(WW) NVIDIA(0): Not using mode "576x384":
(WW) NVIDIA(0):   horizontal sync start (589) not a multiple of 8
(**) NVIDIA(0): Validated modes for display device DFP-0:
(**) NVIDIA(0):      Mode "1920x1080@60i": 77.6 MHz, 34.2 kHz, 60.2 Hz (I)
(**) NVIDIA(0):      Mode "ATSC-1080-60i": 74.2 MHz, 33.8 kHz, 60.0 Hz (I)
(**) NVIDIA(0):      Mode "1920x1080@59i": 77.5 MHz, 34.1 kHz, 60.1 Hz (I)
(**) NVIDIA(0):      Mode "ATSC-1080-59.94i": 74.2 MHz, 33.7 kHz, 59.9 Hz (I)
(**) NVIDIA(0):      Mode "1080i STD": 74.2 MHz, 33.7 kHz, 59.9 Hz (I)
(**) NVIDIA(0):      Mode "1280x720@60": 73.8 MHz, 45.4 kHz, 60.0 Hz
(**) NVIDIA(0):      Mode "ATSC-720-60p": 74.2 MHz, 45.0 kHz, 60.0 Hz
(**) NVIDIA(0):      Mode "ATSC-720-71.93p": 88.9 MHz, 53.9 kHz, 71.9 Hz
(**) NVIDIA(0):      Mode "ATSC-720-72p": 89.0 MHz, 54.0 kHz, 72.0 Hz
(**) NVIDIA(0):      Mode "1280x720@59": 73.7 MHz, 45.4 kHz, 59.9 Hz
(**) NVIDIA(0):      Mode "ATSC-720-59.94p": 74.1 MHz, 45.0 kHz, 59.9 Hz
(**) NVIDIA(0):      Mode "640x480@60": 24.1 MHz, 30.4 kHz, 60.3 Hz
(**) NVIDIA(0):      Default mode "1400x1050": 122.0 MHz, 64.9 kHz, 60.0 Hz
(**) NVIDIA(0):      Default mode "1280x1024": 135.0 MHz, 80.0 kHz, 75.0 Hz
(**) NVIDIA(0):      Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(**) NVIDIA(0):      Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
(**) NVIDIA(0):      Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
(**) NVIDIA(0):      Default mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz
(**) NVIDIA(0):      Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(**) NVIDIA(0):      Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(**) NVIDIA(0):      Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(**) NVIDIA(0):      Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(**) NVIDIA(0):      Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(**) NVIDIA(0):      Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(**) NVIDIA(0):      Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(**) NVIDIA(0):      Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D)
(**) NVIDIA(0):      Default mode "640x512": 67.5 MHz, 80.0 kHz, 75.0 Hz (D)
(**) NVIDIA(0):      Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D)
(**) NVIDIA(0):      Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(**) NVIDIA(0):      Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(**) NVIDIA(0):      Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(**) NVIDIA(0):      Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D)
(**) NVIDIA(0):      Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D)
(**) NVIDIA(0):      Default mode "512x384": 39.4 MHz, 60.1 kHz, 75.1 Hz (D)
(**) NVIDIA(0):      Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D)
(**) NVIDIA(0):      Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
(**) NVIDIA(0):      Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D)
(**) NVIDIA(0):      Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D)
(**) NVIDIA(0):      Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D)
(**) NVIDIA(0):      Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
(**) NVIDIA(0):      Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
(**) NVIDIA(0):      Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D)
(**) NVIDIA(0):      Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D)
(**) NVIDIA(0):      Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
(--) NVIDIA(0): DPI set to (59, 59); computed from "UseEdidDpi" X config option

Now the XF86Config-4...

Code:

Section "Monitor"
        Identifier   "Monitor0"
        VendorName      "Westinghouse"
        ModelName       "LVM-37w1"
        HorizSync 30 - 80 # EDID-detected
        VertRefresh 50 - 75 # EDID-detected
        Option "ConnectedMonitor" "DFP"
        Option "TVStandard" "HD1080i"
#       Option "TVOverScan" "0.9"
        Option "NoLogo" "1"
        Option "RenderAccel" "1"
   Option "HWCursor" "1"
   Option "NvAGP" "3"
# The following POWERSTRIP modeline is taken from a post at http://mysettopbox.tv/phpBB2/viewtopic.php?t=6134
   Modeline "1080i STD" 74.184 1920 1960 2008 2200 1080 1084 1094 1124 +hsync -vsync interlace
# The following modelines are taken from http://www.linuxis.us/linux/media/howto/linux-htpc/video_card_configuration.html
#   # DTV Standard Modes
   Modeline "ATSC-1080-60i" 74.25 1920 1960 2016 2200 1080 1082 1088 1125 Interlace
   Modeline "ATSC-1080-59.94i" 74.176 1920 1960 2016 2200 1080 1082 1088 1125 Interlace
   #DTV-PCTweakedModes
   Modeline "ATSC-720-59.94p" 74.086 1280 1320 1376 1648 720 722 728 750
   Modeline "ATSC-720-60p" 74.16 1280 1320 1376 1648 720 722 728 750
   Modeline "ATSC-720-71.93p" 88.903 1280 1320 1376 1648 720 722 728 750
   Modeline "ATSC-720-72p" 88.992 1280 1320 1376 1648 720 722 728 750

# The modelines calculated from http://xtiming.sourceforge.net. Dot clock freq. = 140 MHz max.
# See also http://www.hdtvprimer.com/ISSUES/what_is_ATSC.html for screen resolution specs.

   Modeline "1920x1080@60i" 77.60 1920 1952 2240 2272 1080 1104 1110 1135 interlace # hfreq: 34.15 MHz
   Modeline "1920x1080@59i" 77.51 1920 1952 2240 2272 1080 1104 1110 1135 interlace # hfreq: 34.11
   Modeline "1280x720@60" 73.78 1280 1312 1592 1624 720 735 742 757 # hfreq: 45.43 MHz; 720p
   Modeline "1280x720@59" 73.69 1280 1312 1592 1624 720 735 742 757 # hfreq: 45.37 MHz; 720p
   Modeline "640x480@60" 24.11 640 672 760 792 480 490 495 505 # hfreq: 30.43; 480p 4:3

EndSection

Section "Device"
        Identifier  "Card0"
        Driver      "nvidia"
        VendorName  "Asus"
        BoardName   "V9520-X"
   # Dot clock max = 140 MHz; DDC-probed

        # The following line is auto-generated by KNOPPIX mkxf86config
        # BusID      "PCI:1:0:0"
EndSection

Section "Screen" 
   Identifier "Screen0" 
   Device "Card0" 
   Monitor "Monitor0" 
   DefaultColorDepth 24 
      SubSection "Display" 
      Depth 24 
      Modes
         "1920x1080@60i" "ATSC-1080-60i" "1920x1080@59i" "ATSC-1080-59.94i" "1080i STD" "1280x720@60" "ATSC-720-60p" "ATSC-720-71.93p" "ATSC-720-72p" "1280x720@59" "ATSC-720-59.94p" "640x480@60"
      EndSubSection 
EndSection 

Section "DRI" 
   Mode 0666 
EndSection

And for good measure, the output of xrandr...

Code:

 SZ:    Pixels          Physical       Refresh
*0   1920 x 1080   ( 827mm x 465mm )  *60  
 1   1280 x 720    ( 827mm x 465mm )   60  
 2    640 x 480    ( 827mm x 465mm )   60   75   73  
 3   1400 x 1050   ( 827mm x 465mm )   60  
 4   1280 x 1024   ( 827mm x 465mm )   75   60  
 5   1280 x 960    ( 827mm x 465mm )   60  
 6   1152 x 864    ( 827mm x 465mm )   75  
 7   1024 x 768    ( 827mm x 465mm )   75   70   60  
 8    832 x 624    ( 827mm x 465mm )   75  
 9    800 x 600    ( 827mm x 465mm )   75   72   60   56  
 10   700 x 525    ( 827mm x 465mm )   60  
 11   640 x 512    ( 827mm x 465mm )   75   60  
 12   576 x 432    ( 827mm x 465mm )   75  
 13   512 x 384    ( 827mm x 465mm )   75   70   60  
 14   416 x 312    ( 827mm x 465mm )   75  
 15   400 x 300    ( 827mm x 465mm )   75   72   60   56  
 16   320 x 240    ( 827mm x 465mm )   75   73   60  
Current rotation - normal
Current reflection - none
Rotations possible - normal 
Reflections possible - none

Anything jump off the page to anyone?

_________________
Mike
My Hardware Profile

Top

Liv2Cod

Post subject:

Posted: Fri Dec 09, 2005 1:00 pm

Joined: Fri May 21, 2004 11:55 pm

Posts: 1206

Location: Silicon Valley, CA

Something seems wrong. I have pretty much the same setup, but my cpu is about 50% or less when doing software decoding on 1080i output. As a shot in the dark, have you tuned up your disk using hdparm -tT? Maybe your disk isn't properly using a DMA mode or something. From your description, it sure seems like there's something amiss with the bandwidth of the data stream.

The 6629 drivers give me correct 1080i through the VGA port. I couldn't use any later drivers because they wrap the image around the middle of the screen. This may not be the case for DVI, however.

_________________
Do you code to live, or live to code?
Search LinHES forum through Google

Top

nonpro

Post subject:

Posted: Fri Dec 09, 2005 3:25 pm

Joined: Wed Oct 12, 2005 10:29 am

Posts: 12

I have both CRT RPTV which supports 1080i and LCD flat panel which supports 720p. For 1080i, I couldn't get TV to accept it through DVI, but only through VGA and 9A60.

I also use VGA connection for the LCD flat panel, but without 9A60. Main reason was I could only get 1:1 pixel to pixel mapping through VGA, without annoying overscan. And long VGA cable is relatively cheaper too (I have 50FT). I did find tearing and stutter on drivers higher than 6629 in 720p mode. So now 6629 is the driver of choice in both machines.

I would suggest you try 1080p, no interlace, with 6629 driver. I guess that may fix your problem. If you don't like overscan, then use VGA connection.

Top

mihanson

Post subject:

Posted: Fri Dec 09, 2005 3:45 pm

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

I'm not at home at the moment, but I'll look into the hard drive tuning. I've never done that before, so maybe there's something to it.

I was able to playback and also watch live HDTV when I fed X my custom 720p modeline so long as I enable the extra audio buffering and XvMC under Utilities/Setup --> Setup --> TV Setup --> Playback. However, it's still not 1080i or 1080p which my monitor/tv is supposed to handle. If you follow the link in my first post to my monitor/tv and select the Specifications tab, it clearly states that 1080p as well as 1080i are supported...

<a few minutes pass>

I just had an epiphony... when I enter values for the modelines on http://xtiming.sourceforge.net, there are two Dot Clock Frequency fields on the initial screen. The first is for the MONITOR'S Dot Clock and the second is for the VIDEO CARD'S Dot Clock. This may be my problem. I was using the video card's Dot Clock in both fields. I'll check this out and report back.

_________________
Mike
My Hardware Profile

Top

mihanson

Post subject:

Posted: Sat Dec 10, 2005 7:40 pm

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

Well, my epiphony was wrong. It seems that no matter what figure I put in the Dot Clock frequency, I end up with the same modelines. No 1080i (or 1080p) modeline is agreeing with my system. I am able to get 720p working, but no 1080i/p. I even tried the 6629 nvidia drivers, but no luck. Does anyone who has the 1080i working with the nvidia drivers use the DVI output of their video card? I'd be interested in seeing your modelines if you do.

I tried the hdparm -tT /dev/sda and here's what I got:

Code:

/dev/sda:
 Timing cached reads:   2044 MB in  2.00 seconds = 1021.94 MB/sec
HDIO_DRIVE_CMD (NULL) (wait for flush complete) failed: Inappropriate ioctl for device
 Timing buffered disk reads:  176 MB in  3.00 seconds =  58.58 MB/sec
HDIO_DRIVE_CMD (NULL) (wait for flush complete) failed: Inappropriate ioctl for device

I'm using a 300GB SATA Seagate hard drive. Is there someother test for me to run with a serial drive? I'm also have an issue with my mythfrontend crashing, but I think that'd be better suited in a new post.

_________________
Mike
My Hardware Profile

Top

nonpro

Post subject:

Posted: Sat Dec 10, 2005 9:48 pm

Joined: Wed Oct 12, 2005 10:29 am

Posts: 12

Sure your 1080i was working. From your log file:

(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080

But there were too many 1080i modelines in your configure. I couldn't tell which one this was.

The easiest way to get a working modeline is to connect your monitor to a Windows PC and get it working at 1920x1080. Then using Powerstrip to generate a modeline from the setup.

Top

cesman

Post subject:

Posted: Mon Dec 12, 2005 8:35 pm

Joined: Fri Sep 19, 2003 7:05 pm

Posts: 5088

Location: Fontana, Ca

nonpro wrote:

The easiest way to get a working modeline is to connect your monitor to a Windows PC and get it working at 1920x1080. Then using Powerstrip to generate a modeline from the setup.

Or do a Google search...

_________________
cesman

When the source is open, the possibilities are endless!

Top

mihanson

Post subject:

Posted: Wed Dec 14, 2005 9:46 pm

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

I've tried dozens of different 1080i modelines that came up on Google. None seems to work.

It got to a point where now I'm documenting them all in my XF86Config-4 and placing them in a section that's commented out (#) with info on where I got them from. It helps me avoid repeating myself with bad modelines.

Re: Powerstrip
The only Windows computer I have is a laptop. (Why would anyone need Windows? :wink:

) Therefore, I can't test my video card with my HDTV.

Edited to remove questions about non-*nix software.

_________________
Mike
My Hardware Profile

Last edited by mihanson on Thu Dec 15, 2005 10:31 am, edited 1 time in total.

Top

cesman

Post subject:

Posted: Wed Dec 14, 2005 10:09 pm

Joined: Fri Sep 19, 2003 7:05 pm

Posts: 5088

Location: Fontana, Ca

If you want to learn more about Powerstrip, I suggest a search on Google (or the search engine of your choice). This isn't the place to discuss Windows software.

_________________
cesman

When the source is open, the possibilities are endless!

Top

Liv2Cod

Post subject:

Posted: Wed Dec 14, 2005 11:46 pm

Joined: Fri May 21, 2004 11:55 pm

Posts: 1206

Location: Silicon Valley, CA

Here's mine. May it give you 1080i pleasure.

Code:

Section "Monitor"
        Identifier      "Monitor0"
        Option  "DPMS"  "false"
        VendorName      "Pioneer"
        ModelName       "PRO-610HD"
        HorizSync 31.5 - 37.9
        VertRefresh 59 - 61
        ModeLine "ATSC-1080-59.94i" 74.176 1920 1960 2016 2200 1080 1082 1088 1125 Interlace

_________________
Do you code to live, or live to code?
Search LinHES forum through Google

Top

mihanson

Post subject:

Posted: Thu Dec 15, 2005 4:18 pm

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

So I just re-read this whole post and it seems that all the 1080i success stories are via the VGA output of an Nvidia card. Some run thru a VGA --> Component converter, but still the signal originates from the VGA port of your video card. Although I find this to be less than an ideal way to get 1080i output (VGA = analog signal, right?) when I have a HDTV/Monitor with two DVI inputs, it may be the only way to get a 1080i output with an Nvidia card. Also, if I remember correctly, if the broadcast flag gets implemented (boo!) it will force a degraded signal to any analog input on your TV. My TV supports the future "copy protection" (I forget the acronym). The good news is that the broadcast flag is not yet a done deal and it's worth a shot for me to try it.

Nvidia and 1080i via DVI = not functional. Nvidia and 1080i via VGA = possible with the correct drivers.

I probably should have paid more attention to this post, too.

Oye, vey! :roll:

_________________
Mike
My Hardware Profile

Top

mihanson

Post subject: NVIDIA FX5200 and Dot Clock Maximum of 135 kHz

Posted: Mon Jul 03, 2006 10:09 am

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

Just to update anyone whose interested... I never successfully got a 1080 modeline to work properly. I stopped looking for an answer some time ago, but only recently revisited the topic. I have been running a 720p modeline instead. I should be able to run my monitor's native EDID provided 1080 modeline via the "nvidia-auto-select" option with the 8762 driver. The modeline is:

ModeLine "1920x1080" 138.5 1920 1968 2000 2080 1080 1082 1087 1111 +hsync -vsync

After much googling yesterday, I found that the reason I cannot run a 1080 modeline over DVI is because there is an issue with the NVIDIA drivers incorrectly reading the maximum pixel clock (aka Dot Clock) as 135 kHz for the FX 5200. It in fact should be at least 140 kHz from what I've deduced in my own tests. The bug was introduced around the release of the 7xxx release of the NVIDIA drivers. This post at nvnews.net details the issue. Unfortunately, the bug is still present in the latest drivers, 8762, as of this writing.

So, if you're having trouble, don't worry, you're not alone. I have not rolled back to the 6629 driver yet, but I would think it should work, but keep in mind it does not support the "nvidia-auto-select" option. You'll need to pull your modeline info from your EDID by stopping gdm and starting x with

Code:

# startx -- -logverbose 6

and then check your XFree86.0.log for the numbers.

_________________
Mike
My Hardware Profile

Top

getnate

Post subject: Similar problem solved

Posted: Fri Jul 14, 2006 4:06 am

Joined: Wed Apr 26, 2006 10:47 am

Posts: 17

I have the LVM-37w3 and I was having the same problems. However I was trying to get 1080p working not 1080i. It seems in your last post that modeline is a 1080p modeline not 1080i.

To solve my problems I:
1. Had to update to the latest drivers because of the Dot-clock issues you mentioned.
2. Used the standard ATSC modelines found on the mythtv wiki
3. disable all forms of EDID detection
4. enable the 'use exact modeline timings' option for the nvidia drivers
5. Use DVI2 input on my montior. (the lvm-37w3 has 2 DVI ports, DVI1 had lots of sync problems, DVI2 works like a charm. This one took the longest to figure out)

-Nate

Top

mihanson

Post subject: Re: Similar problem solved

Posted: Fri Jul 21, 2006 2:48 pm

Joined: Sun Sep 25, 2005 3:50 pm

Posts: 1013

Location: Los Angeles

Thank you for the tips Nate. I have yet to try them out, but I will and I'll let everyone know about my success or failures! :lol:

_________________
Mike
My Hardware Profile

Top

TransAmGore

Post subject:

Posted: Wed Jul 26, 2006 11:01 am

Joined: Thu Jun 24, 2004 4:06 pm

Posts: 23

For the record, if your video card has only one DVI output (and the other is VGA), then you can't get 1080i through the DVI port. A single-link DVI output cannot display 1920x1080 resolution. I forget what the highest it can display is, but 720p is about the highest TV standard you'll be able to get. On the monitor I'm using right now, the best resolution I can get through DVI is 1400x1050, even though the monitor's native resolution is 1680x1050. The native resolution is just barely out of a single DVI link's range. If you want 1920x1080 output, you'll need to do it by using one of the following:

- VGA output
- Component (RGB) output
- A video card with 2 real DVI outputs (dual DVI link)

I have an MSI K8NGM2-FID motherboard with integrated video. It's an nvidia 430/6150 chipset, and it has VGA, DVI (single link) and component video output. I can get 1920x1080 without any problems through the component output, although I usually stick to my TV's native 720p anyways. Video performance is excellent, despite not having a separate video card. It looks beautiful on the 60" DLP TV in the living room.

I don't even use any custom modeline. Mind you, this is using Xorg 6.9 from SUSE 10.1. I don't know if XFree86 on KnoppMyth would make it so easy, but I don't see why not.

Frank

Top

Page 1 of 2

[ 19 posts ]

Go to page 1, 2 Next

Board index KnoppMyth DTV

All times are UTC - 6 hours

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum