Bug 18210

Summary: [945GC] TV output on intel GMA scrambled - resolution not detected correctly?
Product: xorg Reporter: Matt <matthew>
Component: Driver/intelAssignee: Gordon Jin <gordon.jin>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium    
Version: 7.2 (2007.02)   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg-log as generated by X -configure
none
xorg.conf -really as generated by X -configure
none
output of: /usr/bin/xrandr -q 2>&1 >> /var/log/xrandr.log
none
lspci -vv
none
dmesg on this machine none

Description Matt 2008-10-24 12:19:50 UTC
Created attachment 19850 [details]
xorg-log as generated by X -configure

I purchased the BLKD945GCLF2 945GC ATOM330 motherboard for use as a mythtv box, so TV-out is the most critical function.

Unfortunately it is unable to display via S-Video no matter what settings I have tried.  1280x1024 gets the picture the closest to being readable on the TV but it is still flipping too fast to get a fix on.

I have unmasked the latest Xorg available on Gentoo so I am not filing a report on terribly outdated software, here are the packages installed:

xf86-input-keyboard-1.3.1  xf86-video-intel-2.4.2-r3
xf86-input-mouse-1.3.0     xf86-video-vesa-2.0.0
x11-drm-20080710  xorg-server-1.5.2  xorg-x11-7.2

I will follow this message with attachments of hopefully all relevant files.
Comment 1 Matt 2008-10-24 12:20:46 UTC
Created attachment 19851 [details]
xorg.conf -really as generated by X -configure
Comment 2 Matt 2008-10-24 12:21:53 UTC
Created attachment 19852 [details]
output of:  /usr/bin/xrandr -q 2>&1 >> /var/log/xrandr.log
Comment 3 Matt 2008-10-24 12:24:20 UTC
Probably unimportant but there are also MTRR warnings.

dmesg says:  
mtrr: no MTRR for 40000000,8000000 found
mtrr: no MTRR for 40000000,8000000 found

startx shows:


(==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 24 14:23:27 2008
(==) Using config file: "/etc/X11/xorg.conf"
(EE) intel(0): First SDVOB output reported failure to sync
FATAL: Module i915 not found.
(EE) [drm] drmOpen failed.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
output modeline:
input modeline:
Could not init font path element /usr/share/fonts/TTF/, removing from list!
Could not init font path element /usr/share/fonts/OTF, removing from list!
xinit:  No such file or directory (errno 2):  Cannot register with ConsoleKit: org.freedesktop.CkConnector.Error: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

--------------- and on ctrl+c -----------------

^C
waiting for X server to shut down X connection to :0.0 broken (explicit kill or server shutdown).
xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
login:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
(EE) intel(0): First SDVOB output reported failure to sync
error setting MTRR (base = 0x40000000, size = 0x08000000, type = 1) Invalid argument (22)
Comment 4 Matt 2008-10-24 12:25:09 UTC
Created attachment 19853 [details]
lspci -vv
Comment 5 Matt 2008-10-24 12:27:32 UTC
Created attachment 19854 [details]
dmesg on this machine

Let me know if you need any more info and thanks a million.  My wife is not happy that I "killed" the mythtv with this upgrade!
Comment 6 Matt 2008-10-24 12:32:15 UTC
Oh, you probably will want to know that it is a non-HD NTSC TV that I'm trying to get to work.  The system displays the BIOS screen and bootup messages just fine, it is only when it goes to X that it screws up the display, and the display remains in the fast-flip mode after X is shut down as well so it is left in an unusable state.
Comment 7 Gordon Jin 2008-10-25 20:40:37 UTC
Zhenyu is working on SDVO TV out support.

*** 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.