From: Paul Dickson <dickson@permanentmail.com>
To: Jan De Luyck <lkml@kcore.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.15] screen remains blank after LID switch use
Date: Mon, 16 Jan 2006 04:02:28 -0700 [thread overview]
Message-ID: <20060116040228.13267e96.dickson@permanentmail.com> (raw)
In-Reply-To: <200601160946.51765.lkml@kcore.org>
On Mon, 16 Jan 2006 09:46:51 +0100, Jan De Luyck wrote:
> I've recently gotten an Dell D610 laptop from my company. After some digging I
> managed to get Linux running on it, with kernel 2.6.15 at this moment.
>
> There is something odd going on with the LID switch functionality tho:
> everytime the LID is closed, the screen goes off, as expected. Unfortunately,
> the screen does not come back alive afterwards, it remains blank.
>
> Starting X doesn't help, switching consoles doesn't help either. The problem
> is appareant both in X and the console.
>
> The laptop remains completely functional, except for the display.
>
> Currently I'm not using a fb console, and the X driver is the i810.
>
> Any ideas?
I hit this and manage to get myself out of it.
I run with many xterm windows open. After opening the lid in my Inspiron 6000, I switched to a workspace with an open xterm window and type the equivalent of:
xset dpms force suspend
(I usually use this command to blank the screen "right now".)
$ more ~/bin/blank
#! /bin/sh
sleep 2
xset dpms force suspend
Then when I move the mouse pointer or press a key, the screen turns back on.
-Paul
prev parent reply other threads:[~2006-01-16 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 8:46 [2.6.15] screen remains blank after LID switch use Jan De Luyck
2006-01-16 9:01 ` Arlen Christian Mart Cuss
2006-01-16 9:28 ` Jan De Luyck
2006-01-16 9:05 ` Matthew Garrett
2006-01-16 19:19 ` Dmitry Torokhov
2006-01-16 23:23 ` Matthew Garrett
2006-01-16 11:02 ` Paul Dickson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060116040228.13267e96.dickson@permanentmail.com \
--to=dickson@permanentmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@kcore.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox