[i965gm] Displaystate not remebered after suspend/resume (KMS)

[pittipatti]

In my Samsung Q45 with Intel GM965 graphics I encounter the following problem when using KMS:

After a suspend/resume cycle the internal LVDS always gets enabled, whether it was on before or not.

State before suspend/resume: LVDS: off / VGA: 1600x1200
State after resuming from suspend: LVDS: 1280x800 / VGA: 1600x1200

"xrandr --query" reports that the LVDS is off and it is not possible to turn it off by issuing "xrandr --output LVDS --off"

To finally turn the LVDS off it needs to be "enabled" it first by using "xrandr ... --auto".
Afterwards it is possible to really turn it off.

Expected behavior:
- LVDS stays off after resume when it was off before

Sidenote:
If the displays are configured the other way round (VGA off/LVDS on) a suspend/resume cycle does not enable the VGA output.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
     Subsystem: Samsung Electronics Co Ltd Device [144d:c510]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03)
     Subsystem: Samsung Electronics Co Ltd Device [144d:c510]

[F.-A. Bourbonnais (fbourbonnais)]

I'm also affected by this bug but I think that it can be a side effect of this one:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/432334

[F.-A. Bourbonnais (fbourbonnais)]

Sorry, wrong bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/417608

[pittipatti (pittipatti)]

The bug seems to be fixed in 2.6.33.

Using 2.6.33 rc6 I can't reproduce this behavior anymore.

[Vikram Dhillon (dhillon-v10)]

This issue was reported against karmic, so can you confirm if this issue exists with the most recent Lucid Lynx 10.04 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/lucid/ . Thanks in advance.

[pittipatti (pittipatti)]

This issue seems to be fixed in recent lucid versions.

[Geir Ove Myhr (gomyhr)]

This bug report has been inactive for quite some time and in the meantime Ubuntu has moved along. I hope the reported problem has been resolved in the current version of Ubuntu. If it has not and there are people willing to follow up with information collecting and testing, it is best to file a new bug report with the latest Ubuntu development version (10.04 still works, but soon 10.10 is better), using the ubuntu-bug command if possible. Feel free to mention the bug number of this bug.

We are sorry that we are not always have the capacity to look at all reported bugs in a timely manner. Occasionally we have to purge old bug reports where no progress has been made. Whether it is due to the reporter not being able to respond or lack of manpower on the Ubuntu side, the reality is that after a while the attached information is outdated and it is better to close this bug report. Sorry for the inconvenience this may cause.

Here are a few general tips that will make it easier for triagers and developers to process your bug:
* Read https://wiki.ubuntu.com/X/Reporting
* Browse https://wiki.ubuntu.com/X and see if there is some relevant information for you problem
* Respond quickly to questions from triagers
* Try changing things to see if the behaviour changes, e.g.
  * A new mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D (more information at https://wiki.ubuntu.com/KernelTeam/MainlineBuilds)
  * The xorg-edgers PPA: https://launchpad.net/~xorg-edgers/+archive/ppa
  * Various options in `/etc/X11/xorg.conf` (see `man intel`)
* Browse other bug reports to see if you find a similar one and provide the information that is being asked for there.