← Back to team overview

desktop-packages team mailing list archive

[Bug 706386] Re: Screen blanks on lid close, never unblank (reboot required)

 

elik, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/706386/comments/5
regarding you aren't using Ubuntu. For future reference you can manage
the status of your own bugs by clicking on the current status in the
yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: xorg (Ubuntu)
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/706386

Title:
  Screen blanks on lid close, never unblank (reboot required)

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: xserver-xorg-video-intel

  I'm not sure the bug is with xserver-xorg-video-intel, but I'll
  explain why it think it might be.

  I get this issue with the options Blank Screen for When laptop lid is
  closed in AC power in Power-Managent and with Do Nothing and Blank
  screen in Battery Power. Interestingly enough (I think, at least), if
  suspend is chosen, the laptop suspends correctly and brings back the
  screen correctly on resume.

  I tried alt-sys-req to reboot xserver and I tried going to a tty
  (ctrl-alt-f1), but it never brought the screen back on.

  The machine is not crashed and I can ssh to the machine. I used that
  to try a few interesting thing while the screen was blank.

  I found this thread (a bit old, but still):
  http://ubuntuforums.org/showthread.php?t=358432. I tried to "vbetools
  dpms on", but it didn't help.

  https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen has an
  interesting article on intel graphics which I followed. Even though it
  mentioned was marked as a solution for machine lock-up (my machine
  doesn't lock-up per se), I tried the ForcePipeA quirck
  (https://wiki.ubuntu.com/X/Quirks#Force Pipe A Quirk), but when I did,
  Xorg reported that the option did not exist.

  I had a whole bunch of errors in Xorg logs: (EE) FBDEV(0):
  FBIOPUTCMAP: Invalid argument. I looked it up and found no bug reports
  that pointed in the direction of the bug I'm having, so I decided to
  let it be.

  Finally, on one bug report, I found someone talking about installing
  the dbg version of the package, which I did. I played with
  "intel_reg_dumper" a little bit, wrote a bash script that track
  changes to the registers (probably not exactly the most effective
  option, but meh). Basically, what I did is that I ran
  "intel_reg_dumper" before and and after closing the lid (and causing
  the bug). I found somehting, but I don't know what it means...
  VGACNTRL would change from VGACNTRL: 0x22040000 (enabled) to VGACNTRL:
  0x80000000 (disabled). I couldn't find a tool to mess with that
  directly and confirm if it's part of the problem. Most likely it's the
  result of something not being done properly higher up the pipe... but
  I only know that much about the inner workings of linux (very
  limited).

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu5.1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  Architecture: i386
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1024x768
   edid-base64:
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  Date: Sat Jan 22 14:17:00 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: IBM 2887W5H
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic root=UUID=9e733a0c-b087-4f98-948b-0d11b228ba40 ro quiet splash
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-intel
  dmi.bios.date: 11/15/2005
  dmi.bios.vendor: IBM
  dmi.bios.version: 1VET67WW (1.25 )
  dmi.board.name: 2887W5H
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnIBM:bvr1VET67WW(1.25):bd11/15/2005:svnIBM:pn2887W5H:pvrThinkPadR51:rvnIBM:rn2887W5H:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2887W5H
  dmi.product.version: ThinkPad R51
  dmi.sys.vendor: IBM
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro:             Ubuntu
   codename:           maverick
   architecture:       i686
   kernel:             2.6.35-24-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/706386/+subscriptions