Bug 18443 - [845] can't back machine from suspend mode
Summary: [845] can't back machine from suspend mode
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Jesse Barnes
QA Contact: Xorg Project Team
URL: http://bugs.debian.org/cgi-bin/bugrep...
Keywords: NEEDINFO
Depends on: 12059
  Show dependency treegraph
Reported: 2008-11-08 09:45 UTC by pashaa
Modified: 2010-04-06 11:22 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Description pashaa 2008-11-08 09:45:38 UTC
+++ This bug was initially created as a clone of Bug #12059 +++

Alexander Vodomerov reported this bug on the Debian BTS yesterday. He has a notebook with
  82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device rev 3
The Intel driver (2.0, 2.1 and 2.1.1) can't find its LVDS (while i810 1.7 worked fine).

The log with 2.1.1 and a regular xorg.conf with ModeDebug is available at http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=32;filename=Xorg.0.log;att=1;bug=438650

There's nothing about LVDS in the log apart from:
(II) intel(0):  ADPA: 0x00000c00 (disabled, pipe A, -hsync, -vsync)
(II) intel(0):  LVDS: 0x00043011 (disabled, pipe A, 18 bit, 1 channel)
(II) intel(0):  DVOA: 0x00000000 (disabled, pipe A, no stall, -hsync, -vsync)

ch7xxx, ivch, sil164 and tfp410 all fail. Maybe it's a ch7017? The code for this chipset seems to be disabled because untested from what I see in the log...

Comment 1 pashaa 2008-11-08 10:00:10 UTC
After resolved bug 12059, my video successefully started, but i still have 3 problem.
1. I can't back machine from suspend mode (i tested various method). System need reboot, without any error in xorg.0.log.old
2. After boot, xorg start, but sometimes backlights not start (x system start good). After ctrl+alt+backspace backlight is start without any error in xorg.0.log.
3. After monitor go to save energy, backlight is off, and need x system restart.
Comment 2 pashaa 2008-11-08 10:04:44 UTC
With old i810 driver x system and suspend work properly. Is need intel driver  hack in other side for support ch7017?
Comment 3 Jesse Barnes 2008-12-18 13:32:09 UTC
Marking this as an enhancement request since we don't fully support this hardware yet.  Sounds like we need i2c based backlight control for your machine, and proper suspend/resume support for DVO attached encoders.
Comment 4 pashaa 2008-12-18 20:56:24 UTC
Become outdated driver i810 and old xorg 6.x - 7.0 completely supported my hardware. Was not what problems neither with suspend - resume, nor with backlights.
Comment 5 Eric Anholt 2009-07-15 16:17:08 UTC
Do you also have this problem with KMS enabled in 2.6.31-rc2?  There have been suspend/resume fixes to KMS recently, and KMS should support suspend/resume for you in a way that X never could.
Comment 6 pashaa 2009-07-16 22:17:22 UTC
I tryed KMS, no succsefull. Not go to sleep. Freese with black screen and no suspend. More speed work h264 video play. All console black and flashed vertical white line in left screen since kernel start.
Comment 7 pashaa 2009-07-16 22:20:43 UTC
X server work normal in KMS.
Comment 8 Jesse Barnes 2009-10-05 13:28:08 UTC
Lots more 8xx fixes have landed, is this still an issue for you?
Comment 9 pashaa 2009-10-06 09:20:00 UTC
No. Still not resolved, but i not try last developed hacks. I use stable xf86-driver-intel-2.4.3, while have not reason for install experimental driver. Added new problem. Not work KDE since 4.1 version. X start ok, but not work plasma.
Comment 10 Jesse Barnes 2009-10-06 09:38:54 UTC
Can you try the latest experimental versions?  Please file separate bugs for any other issues you find too, this one is just for suspend/resume.
Comment 11 pashaa 2009-10-27 12:07:40 UTC
Tested latest git xf86-video-intel. Bug keep alive.
Comment 12 Jesse Barnes 2010-02-05 14:59:50 UTC
Does this happen with current 2.6.33-rc kernels?
Comment 13 Jesse Barnes 2010-04-06 11:22:07 UTC
I guess this machine died or something.

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.