2006-01-16 08:47:18

by Jan De Luyck

[permalink] [raw]
Subject: [2.6.15] screen remains blank after LID switch use

(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
--
This is NOT a repeat.


2006-01-16 09:01:34

by Yuki Cuss

[permalink] [raw]
Subject: Re: [2.6.15] screen remains blank after LID switch use

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
>
>

2006-01-16 09:05:41

by Matthew Garrett

[permalink] [raw]
Subject: Re: [2.6.15] screen remains blank after LID switch use

Jan De Luyck <[email protected]> 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.

It's a bug in Dell's BIOS. It seems to be present in all their current
machines that use Intel graphics, and it also happens in Windows if you
boot in safe mode. I'm trying to work this through with Dell, but it's
taking a long time and I'm ridiculously busy with real life right now.

--
Matthew Garrett | [email protected]

2006-01-16 09:29:47

by Jan De Luyck

[permalink] [raw]
Subject: Re: [2.6.15] screen remains blank after LID switch use

On Monday 16 January 2006 10:01, Arlen Christian Mart Cuss wrote:
> 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.

Okay, thanks for that information. After some further googling I came up with
this:

# echo 0x80000001 > /proc/acpi/video/VID/LCD/state

and the screen comes back to life. Thanks!

Jan

--
To err is human, to forgive is against company policy.

2006-01-16 11:02:33

by Paul Dickson

[permalink] [raw]
Subject: Re: [2.6.15] screen remains blank after LID switch use

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

2006-01-16 19:19:26

by Dmitry Torokhov

[permalink] [raw]
Subject: Re: [2.6.15] screen remains blank after LID switch use

On Monday 16 January 2006 04:05, Matthew Garrett wrote:
> Jan De Luyck <[email protected]> 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.
>
> It's a bug in Dell's BIOS. It seems to be present in all their current
> machines that use Intel graphics, and it also happens in Windows if you
> boot in safe mode. I'm trying to work this through with Dell, but it's
> taking a long time and I'm ridiculously busy with real life right now.
>

Not only Intel. I've learned to never close lid of my Inspiron 8100
(with nvidia chip) ;)

--
Dmitry

2006-01-16 23:23:30

by Matthew Garrett

[permalink] [raw]
Subject: Re: [2.6.15] screen remains blank after LID switch use

On Mon, Jan 16, 2006 at 02:19:19PM -0500, Dmitry Torokhov wrote:

> Not only Intel. I've learned to never close lid of my Inspiron 8100
> (with nvidia chip) ;)

Joy. The ATI ones seem ok.

--
Matthew Garrett | [email protected]