From: Arlen Christian Mart Cuss <celtic@sairyx.org>
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 20:01:24 +1100 [thread overview]
Message-ID: <43CB60E4.1060305@sairyx.org> (raw)
In-Reply-To: <200601160946.51765.lkml@kcore.org>
Check out /proc/acpi - you should find a few things that you can tinker
with, including one for your screen; often called `lcd'. If you "echo 1
> lcd" in the right directory, it should switch it on. "echo 0 > lcd"
switches it off. Whatever is managing your power that turns it off,
isn't turning it back on. Look into these. It's not likely to be the
console/X driver's fault.
- Arlen.
Jan De Luyck wrote:
>(I have no idea who the maintainer for this is, I was unable to find any entry
>in the MAINTAINERS file.. if i overlooked it, feel free to correct me)
>
>Hello list,
>
>
>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?
>
>Thanks,
>
>Jan
>
>
next prev parent reply other threads:[~2006-01-16 9:01 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 [this message]
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
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=43CB60E4.1060305@sairyx.org \
--to=celtic@sairyx.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.