Bug 18541

Summary: [945GC] TV-1 output produces bad NTSC signal
Product: xorg Reporter: Todd Brunhoff <toddb>
Component: Driver/intelAssignee: Gordon Jin <gordon.jin>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg.conf
none
X boot Log with ModeDebug on none

Description Todd Brunhoff 2008-11-15 02:05:29 UTC 
Created attachment 20316 [details]
xorg.conf

I've built a new box running Mythdora 5.0 on Intel Atom 330 motherboard (Intel D945GCLF2). This has a VGA output (which works fine) and an S-video connector.  The output signal produced by any of the probed modes is not close enough to produce a stable signal. Those modes are listed below:
"640x480"
"1280x1024@60.00"
"1360x768"
"1360x768"
"1280x800"
"1152x864"
"1280x768"
"1280x720"
"1024x768"
"1024x768@60.00"
"920x766@60.00"
"832x624@60.00"
"800x600"
"800x600@60.00"
"720x576@60.00"
"704x576@60.00"
"720x540@60.00"
"720x480@60.00"

The "640x480" seems like it ought to work, but is jammed up along the left edge. It appears as if both vert and horiz refresh rates are too high.

I have compiled installed the intel driver from source (xf86-video-intel-2.5.0) which seems to work well enough. I have studied all of the xorg.conf bug reports that utilize TV-1 output, looking for hints, but 

I'm certain that this is a simple problem, and I appologize for the inconvenience, but I have run out of options. Please help. xorg.conf and log attached.
Comment 1 Todd Brunhoff 2008-11-15 02:12:58 UTC 
Created attachment 20317 [details]
X boot Log with ModeDebug on
Comment 2 Todd Brunhoff 2008-11-15 02:15:35 UTC 
I want to be clear that the only issue is the signal on the s-video connector when connected to a television.
Comment 3 Gordon Jin 2008-11-15 03:28:46 UTC 
Zhenyu is working on SDVO TV-out on D945GCLF2. It's in progress and expected to work in upcoming 2.6 release.

*** This bug has been marked as a duplicate of bug 17776 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.