[i945] [LPL] TV out stopped working in jaunty (okay in intrepid)

[dvdmeer]

After the update of 10 december xrandr isn't working properly (jaunty).
These are the updates I received:

libxrandr-dev (2:1.2.3-1) to 2:1.2.99.2-0ubuntu1
libxrandr2 (2:1.2.3-1) to 2:1.2.99.2-0ubuntu1

When I type xrandr and have my TV connected I do see this as being connected in the terminal.
But my TV doesn't show anything unfortunately. I tried this at two different TV's. Same thing. Previously I had no problems at all in jaunty.

So I started Intrepid, no problems here, I have a clone (or everything else I want) at my TV.

I'll attach xorg.0.log and the gdm log.

[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: Toshiba America Info Systems Device [1179:ff00]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
     Subsystem: Toshiba America Info Systems Device [1179:ff01]

[dvdmeer (dennis-dvdmeer)]

I just found out there is a bigger problem.

Xrandr only shows one resolution for my LVDS, 1280x800 (which is my normal resolution). It doesn't come with other resolutions as it should (e.g. 1024x768), like intrepid does.

So I checked System - Preferences - Screen resolution, same story, just one resolution available.

[dvdmeer (dennis-dvdmeer)]

I also changed the package hint to intel over libxrandr. I believe it has more to do with the recently updates of the intel driver.

[Bryce Harrington (bryce)]

[This is an automated message]

Hi dennis-dvdmeer,

Please attach the output of `lspci -vvnn` too.

[dvdmeer (dennis-dvdmeer)]

Bryce,

Here it is.

[Bryce Harrington (bryce)]

Interesting... Interestingly your system has one of the LPL brand LVDS display panels which is quirked in xserver. However I don't think the quirk is what is causing your issue (could be contributing to it though, not sure).

I also notice that there is an excessive amount of output in the log file repeating the note about the quirk. Perhaps that could be better surpressed.

Anyway, could you try following the directions on this page for enabling your TV, and let us know if it worked?
https://wiki.ubuntu.com/X/Config/SVideo

Also, for the Xorg.0.log posted above, was that with the TV connected?

[dvdmeer (dennis-dvdmeer)]

Hmm, that's very interesting..

I'm not sure anymore if the xorg log was with the TV connected, so when I'm home, I'll try it again and I'll attach both logs (with and without TV connected)..

I'll also look at that page from the link.

[dvdmeer (dennis-dvdmeer)]

I'll attach now the log of xorg while the tv was connected already (before boot).

In a moment I'll attacht the log while tv was not connected before boot.

[dvdmeer (dennis-dvdmeer)]

Here is the xorg log when the tv is not connected.

The information on https://wiki.ubuntu.com/X/Config/SVideo is for the radeon driver, not for intel.

For intel it is xrandr --output TV.

[dvdmeer (dennis-dvdmeer)]

And this is the output of xrandr --prop.

As notified in a previous message (2008-12-22), remarkable is that for my LVDS screen only the resolution 1280x800 available is. In intrepid I have more choices. Same story for the TV.

I hope it can be solved, if you need anymore information, just let me now ;)

[Alan Pope 🍺🐧🐱 🦄 (popey)]

I am also getting this issue (as per bug 317826) which I have discovered without having the laptop attached to any panels - just using the built in panel.

I did use it on a projector yesterday, and xrandr offered 1024x768 as a possible resolution for me on the external display - which I switched to and used successfully. I had the projector attached from boot up, and all output appeared on the projector, none on the panel. I was doing a presentation so didn't really have time to debug it.

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