Bug 15268 - [830] Black screen with mouse pointer
Summary: [830] Black screen with mouse pointer
Status: RESOLVED FIXED
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: https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-30 06:41 UTC by Shaun Crampton
Modified: 2008-09-20 14:56 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments
My Xorg.0.log covering the time of the issue. (37.26 KB, text/plain)
2008-04-01 10:12 UTC, Shaun Crampton
no flags Details
My xorg.conf (unmodified Ubuntu Hardy beta) (1.42 KB, text/plain)
2008-04-01 10:27 UTC, Shaun Crampton
no flags Details
Fixup ordering and wait for vblank (15.13 KB, patch)
2008-05-07 15:27 UTC, Jesse Barnes
no flags Details | Splinter Review
X.org.log with modedebug enabled (68.65 KB, text/plain)
2008-06-30 11:35 UTC, Shaun Crampton
no flags Details

Description Shaun Crampton 2008-03-30 06:41:12 UTC
I have a Toshiba 3000-X4 laptop with i830 graphics card.  If I leave my laptop for 10 minutes with no mouse activity then the screen goes blank.  If I then move the mouse, the mouse pointer appears and responds to movement but the rest of the screen remains blank.  If I VT switch (or ssh in and temporarily start a second X server and then kill it), the desktop is restored.

I have this problem in Ubuntu Gutsy and Hardy Beta as well as recent Git snapshots provided by the Ubuntu maintainers for me to test.  The Ubuntu bug report is referenced in the URL field.

Specifically, I've tried git revisions r79a5585d and rac763634 with no luck as well as the current Hardy version and "2:2.1.1-0ubuntu9" (and previous versions) from Ubuntu Gutsy (I can't try versions in between due to another bug).
Comment 1 Gordon Jin 2008-04-01 00:00:19 UTC
Please attach your xorg.conf and Xorg.0.log here, prefereably with more info according to http://www.intellinuxgraphics.org/how_to_report_bug.html

Does this also happen with vesa driver?
Comment 2 Shaun Crampton 2008-04-01 10:12:44 UTC
Created attachment 15607 [details]
My Xorg.0.log covering the time of the issue.
Comment 3 Shaun Crampton 2008-04-01 10:27:49 UTC
Created attachment 15608 [details]
My xorg.conf (unmodified Ubuntu Hardy beta)
Comment 4 Shaun Crampton 2008-04-01 10:37:33 UTC
System Environment:

lspci -nn:
00:00.0 Host bridge [0600]: Intel Corporation 82830 830 Chipset Host Bridge [8086:3575] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation 82830 CGC [Chipset Graphics Controller] [8086:3577] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation 82830 CGC [Chipset Graphics Controller] [8086:3577]

uname -m:
i686

Package versions:
Long standing problem experienced in Ubuntu Gutsy and Hardy and git revisions detailed in previous post.

uname -r:
2.6.24-12-generic

Machine model:
Toshiba Satellite 3000-X4

Reproduction steps:
In previous post. 100% reproducible.

VESA Driver:
VESA driver (and i810) is broken on this machine (black screen).  I haven't got around to filing those bug reports yet.
Comment 5 Shaun Crampton 2008-04-11 14:16:06 UTC
I thinks that's everything that applies from the page you referenced.  Is there any more info that I can supply?
Comment 6 Gordon Jin 2008-04-12 19:27:30 UTC
Jesse/Eric/Keith, are you able to reproduce this on 830m?
Comment 7 Shaun Crampton 2008-04-27 05:53:21 UTC
This is still a problem in Ubuntu Hardy Final with the following version:

$apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.2.1-1ubuntu12
  Candidate: 2:2.2.1-1ubuntu12
  Version table:
 *** 2:2.2.1-1ubuntu12 0
        500 http://archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status
Comment 8 Jesse Barnes 2008-05-07 15:26:35 UTC
I don't have an 830 to reproduce this problem with.  But I'll attach a patch I've been working on to fix some mode register programming problems...
Comment 9 Jesse Barnes 2008-05-07 15:27:40 UTC
Created attachment 16417 [details] [review]
Fixup ordering and wait for vblank

This patch *may* help...  Can you also reproduce your problem using 'xset dpms force off' or any other way?
Comment 10 Shaun Crampton 2008-05-08 10:21:43 UTC
I tried "xset dpms force off" but it did not repro. the bug.  Moving the mouse brought the screen back on.  I'll see if I can work out how to build a patched driver...
Comment 11 Jesse Barnes 2008-05-21 13:53:37 UTC
Shaun, any update?  If you need help with building, you could try contacting Ubuntu's X maintainer, Bryce Harrington, I think he's been working on making it easier to build & distribute patched driver packages.
Comment 12 Shaun Crampton 2008-05-26 02:54:39 UTC
Jesse,  sorry about that.  I think I missed your follow up in my email.  I tried to build your patch against the Ubuntu tree but the codebases were too divergent (and I don't have enough experience of the code to manually merge).  I've asked Bryce if he'd mind building the patch for me -- I'm just waiting on his response.
Comment 13 Shaun Crampton 2008-05-29 12:29:04 UTC
Bryce says it'll be a few days before he has time to build the patch against Hardy's driver.  I'll keep you posted.
Comment 14 Jesse Barnes 2008-06-06 13:18:20 UTC
you could also try the "ForceEnablePipeA" option, since this bug seems similar to some others where that works around the problem.
Comment 15 Shaun Crampton 2008-06-07 07:25:02 UTC
Jesse, that workaround seems to have done the trick.  Thanks a lot.
Comment 16 Jesse Barnes 2008-06-20 15:04:14 UTC
Can you attach a log file with the 'modedebug' option enabled?  Looks like LVDS is getting routed to pipe A, which would explain why the ForceEnablePipeA option is working for you...
Comment 17 Shaun Crampton 2008-06-30 11:35:44 UTC
Created attachment 17467 [details]
X.org.log with modedebug enabled
Comment 18 Shaun Crampton 2008-06-30 11:39:51 UTC
I've attached the X log with modedebug enabled.

I just noticed that when I turn on ForceEnablePipeA I can no longer use the VGA output from the laptop (although it works around the flat panel issue recorded here).  I simply get no output from the VGA port to my projector.  Is this expected as a consequence of the ForceEnable option or should I file another bug?
Comment 19 Jesse Barnes 2008-08-20 13:00:34 UTC
No, that's not expected, so it would be another bug.  Some of our code must have some "pipe b" assumptions that don't apply in your case since LVDS is attached by DVO.

It almost sounds like your BIOS is doing the screen blanking for you, maybe there's an option to disable it?

Gordon, do we have any i830 machines in QA?  We could probably reproduce this problem by hacking the driver to route things like the register dumps on Shaun's machine indicate; it would probably be easy to fix after doing that, but I don't have an i830...
Comment 20 Gordon Jin 2008-08-20 19:24:33 UTC
(In reply to comment #19)
> Gordon, do we have any i830 machines in QA?  
No. We've never had i830 in Shanghai.
Comment 21 Shaun Crampton 2008-09-20 03:37:03 UTC
I've been runnig with the Pipe-A workaround for a long time.  Just had to reinstall my laptop and the bug seems to have been fixed (I'm no longer running with the Pipe-A workaround but it doesn't repro).  Thanks!

xserver-xorg-video-intel:
  Installed: 2:2.2.1-1ubuntu13.7
  Candidate: 2:2.2.1-1ubuntu13.7
  Version table:
 *** 2:2.2.1-1ubuntu13.7 0
        500 http://ubuntu.virginmedia.com hardy-proposed/main Packages
        100 /var/lib/dpkg/status
     2:2.2.1-1ubuntu13.6 0
        500 http://ubuntu.virginmedia.com hardy-updates/main Packages
     2:2.2.1-1ubuntu12 0
        500 http://ubuntu.virginmedia.com hardy/main Packages
Comment 22 Jesse Barnes 2008-09-20 14:56:18 UTC
Ok, guess we can close this then, thanks for the update!


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.