[i945] Regression: HDMI not working in Intrepid (945GM)

[Paul McEnery]

Binary package hint: xserver-xorg-video-intel

I have a mythtv frontend system installed on a Jetway J9F2-Extreme motherboard which features an onboard HDMI port:

http://www.jetway.com.tw/jetway/system/productshow.asp?id=404&proname=J9F2-Extreme

I usually use the system with a distribution called minimyth, but have run the system with Mythbuntu Hardy heron as well. I recently tried updating to the latest version of Minimyth which when booted simply produced "No Signal" on the HDMI connected TV. I thought this was just an issue with Minimyth and decided to install Intrepid. I saw the same result! I know for a fact that the HDMI port was working under Hardy Heron, but somewhere between Hardy and Intrepid, HDMI no longer works.

Here are a few observations....

Under Hardy, I saw the following in my Xorg.0.log:

(II) intel(0): Output VGA disconnected
(II) intel(0): Output LVDS connected
(II) intel(0): Output TMDS-1 disconnected
(II) intel(0): Output TMDS-2 connected
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(II) intel(0): Output TV disconnected

Under Intrepid, I see the following output in the Xorg.0.log:

(II) intel(0): Output VGA disconnected
(II) intel(0): Output LVDS connected
(II) intel(0): Output TMDS-1 disconnected
(II) intel(0): Output TV disconnected

It appears to no longer detect the TMDS-2 output which (I think) is the HDMI output.

P.S. I have installed and tried the latest PPA Intel drivers which fail in the same way.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: xserver-xorg-video-intel 2:2.5.1-1ubuntu5~intrepid
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.27-9-generic (buildd@rothera) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Nov 20 21:57:00 UTC 2008

SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.27-9-generic i686
UnreportableReason: This is not a genuine Ubuntu package
xkbcomp:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
     Subsystem: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
     Subsystem: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2]

[Geir Ove Myhr (gomyhr)]

Does it help if you ignore LVDS and/or TV-out? https://wiki.ubuntu.com/X/Quirks

[Paul McEnery (pmcenery)]

No. I tried both the LVDS- and TV-out quirk fixes with no success. The problem appears to be the missing TMDS-2 output. When I disable the LVDS output, X fails to start altogether with "No Screens". The TMDS-1 output is the DVI port which seems to work when the TV is connected.

I have now reverted to runing Hardy which works over HDMI with both the "i810" and "intel" drivers...

[Bryce Harrington (bryce)]

[This is an automatic notification.]

A new major version of the -intel driver is now available in Karmic.

This version includes a major reworking of the acceleration
architecture, which resolves a huge number of issues. We do not know
whether it resolves the issue you reported.

Would you mind testing Karmic Alpha-2 and seeing if it is still a
problem? CD ISO images are available here:

  http://cdimages.ubuntu.com/releases/karmic/

If the issue can still be reproduced on karmic, please report here with
your findings, and attach a fresh Xorg.0.log from your test, and we will
be able to forward the bug upstream.

Otherwise, if the bug no longer exists in Karmic, let us know that as
well.

In the off chance you encounter different bugs while attempting to test
Karmic, please report those as new bug reports.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.