Skip to contentSkip to conversation

[2.6.15] screen remains blank after LID switch use

DISCUSSION Jan De Luyck 6 participants 7 messages Jan 16, 2006

lore
Share & tools
lore
#0 lore raw

(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

Signature · 1 line
This is NOT a repeat.
#1 lore raw

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.

Quoted 22 lines · Jan De Luyck

(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

#3 lore raw
In reply to Jan De Luyck
Quoted 2 lines · Jan De Luyck

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.

Signature · 1 line
Matthew Garrett | [email protected]
#2 lore raw
In reply to Arlen Christian Mart Cuss
Quoted 8 lines · Arlen Christian Mart Cuss

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

Quoted 1 line

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

Signature · 1 line
To err is human, to forgive is against company policy.
#6 lore raw
In reply to Jan De Luyck
Quoted 7 lines · Jan De Luyck

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.

Quoted 8 lines

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

#4 lore raw
In reply to Matthew Garrett
Quoted 10 lines · Matthew Garrett
Quoted 2 lines · Jan De Luyck

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

Signature · 1 line
Dmitry
#5 lore raw
Quoted 2 lines · Dmitry Torokhov

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

Joy. The ATI ones seem ok.

Signature · 1 line
Matthew Garrett | [email protected]