[g33] No DPMS on DVI port of ADD2 card

[Loïc Minier]

Hi,

I own an ADD2 card which is some kind of remote port for Intel graphics chipsets; it sits on the PCI-E bus; this is the one I bought:
http://www.materiel.net/ctl/Cartes_graphiques/25588-ADD2_DVI_D_OEM.html

It's connected to a LG monitor over DVI, and this setup works fine except for DPMS. The monitor is perfectly DPMS capable, I tested with DVI on another computer, and from Xorg.log it seems DPMS support is correctly detected:
(II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display

The monitor never goes to DPMS.

There are some weird (EE) lines in Xorg.log, so I'll attach it:
...
(II) intel(0): I2C device "SDVOB DDC Bus:ddc2" registered at address 0xA0.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
...

Bye,

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02)
     Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8276]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA])
     Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8276]

[Loïc Minier (lool)]

NB: I have a second monitor attached to the native VGA port; it's a iiyama ProLite E403S => PLE430 in the log; it's DMPS support is detected and working fine.

[Bryce Harrington (bryce)]

Thanks for attaching your Xorg.0.log. Can you also attach your xorg.conf and the output of lspci -vvnn?

I've posted a .deb of the latest intel driver git HEAD here if you would like to test it:
http://people.ubuntu.com/~bryce/Testing/intel/xserver-xorg-video-intel_2.1.1~git20071004-0ubuntu1_i386.deb

Since it's straight out of git, it may include new issues. Direct rendering often stops working, for instance. However it would be interesting to hear if it addresses this issue or not.

[Loïc Minier (lool)]

I'm afraid I run amd64 and I didn't find the .dsc in the same dir; I'll try building the driver out of git.

[Loïc Minier (lool)]

Today's git version of the driver worked on my box (but had a major display issue which seems related to the kernel fixes which broke G33 support yesterday; perhaps these kernel changes are required), but DPMS didn't work better.

The screen stops receiving any signal and becomes black, but instead of shutting down immediately like it when connected to e.g. a MacOSX laptop, it will display in loop "Check signal cable", and wont shut down. The other monitor conneted to the VGA port also displays this, but shuts down.

I don't know how the DVI port provided by the adapter is being used: perhaps it's used in DVI-A mode, or perhaps it's used in DVI-D mode but can't transmit DPMS?

I'm attaching my xorg.conf and will attach the Xorg.log from the git intel driver build.

[Bryce Harrington (bryce)]

Thanks for testing the upstream -intel. I'm hoping to roll out a new -intel for gutsy-updates at some point. If we can identify the specific patch that fixes your issue, that would make it easier to make the case for rolling out the update.

[Loïc Minier (lool)]

@Bryce: the new version did NOT fix the issue; I probably caused confusion when I claimed the git version "worked" on my box: it's because there is/was an issue with git versions of the driver with unpatched kernels or vice-versa.

The DPMS problem is still an issue for me unfortunately.

[Bryce Harrington (bryce)]

Hi Loic, is this issue still occurring on Intrepid? If so I'll forward this upstream.

[Loïc Minier (lool)]

I dist-upgraded to intrepid; I confirm the issue is still present.

[Rich Johnson (nixternal)]

This issue only occurs for me in Intrepid. In Hardy I had no problems with my dual monitor configuration, but Intrepid I get the following errors and the 2nd monitor constantly flashes on/off:

(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1680x1050"x0.0 132.00 1680 1728 1760 2000 1050 1053 1059 1100 -hsync -vsync (66.0 kHz)
(II) intel(0): EDID vendor "SEC", prod id 13136
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(II) intel(0): EDID vendor "DEL", prod id 16435
(II) intel(0): EDID vendor "SEC", prod id 13136

[Bryce Harrington (bryce)]

Heya loic,

I've forwarded this bug upstream at https://bugs.freedesktop.org/show_bug.cgi?id=18069. Please subscribe to this bug in case upstream wishes additional information or needs you to test something.

Note that 845 is a fairly old chipset and I'm not sure what amount of support we'll get from upstream, but it's worth a shot.

[Loïc Minier (lool)]

Bryce, not sure where you see "845" as a chipset; is this in the ADD2 card? What I have is a G33 chipset which is GMA 3100, don't think it's very old, and an ADD2/SVDO card, I don't think it has a graphics chip, does it?

[Loïc Minier (lool)]

Original link to selling website is dead now; this is the actual addon card:
http://www.sapphiretech.com/us/products/products_overview.php?gpid=165&pid=g&grp=9

[Bryce Harrington (bryce)]

[This is an automatic notice.]

We'd like to forward your bug upstream, however upstream requires
that you first test it against their newer driver code.

To save you the effort of building the driver from source, we've built
packages for the driver and its new dependencies.

So you have a couple options:

 1. Download and test .debs for intrepid, from:
     https://edge.launchpad.net/~intel-gfx-testing/+archive

 -or-

 2. Download and test the Jaunty alpha-2 (or newer) Live CD,
     (which includes a beta of the new xserver 1.6 as well).
     See http://cdimage.ubuntu.com/releases/9.04/ for ISOs

Thanks ahead of time! You can simply reply to this email to report your
findings.

P.S., if you wish to forward your bug upstream yourself, please follow
these directions to do so:
  http://intellinuxgraphics.org/how_to_report_bug.html

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

[Loïc Minier (lool)]

Please don't close the bug if it's already forwarded upstream?

[Jesse Barnes (jbarnes-virtuousgeek)]

Can someone confirm whether this still happens with KMS?

[Loïc Minier (lool)]

So it's likely that my card doesn't support DPMS.

[Loïc Minier (lool)]

Oh and I had confirmed upstream that the same happens with KMS