Dell Inspiron 6000 Close Lid, Can't Get Display Back
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Dell Inspiron 6000 Close Lid, Can't Get Display Back
I have a Dell Inspiron 6000 running Slackware 10.2, kernel 2.6.13. Closing the lid turns off the display and I cannot get it turned back on. The system contines running (I ssh into it from another server) but the only way to get the display back is to reboot the system.
Searching through similar problems in LQ has proved no help, including one suggestion to disable ACPI and enable APM instead (no joy there), and I've been unable to figure out any way in /etc/acpi or other places to get the thing to work. The only way seems to be power it down (or init 6 from an ssh login) and, well, that's not much of a solution.
I havent had 10.2 on my laptop yet, but ubuntu sleeps and wakes fine. If it works in ubuntu it should work in slack. If you need a config file let me know and I will post it.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
The odd thing is that I initially installed Slackware 10.2 with the 2.4.31 kernel on the thing and had no problem with opening and closing the lid and the display -- but it ran like a three-legged dog with a busted tail. Seems that 2.4.x isn't so good with laptops of this generation (and we all know laptops are weird). I rebuilt it completely with the 2.6.13 kernel (which vastly improves performance in every way) and this problem showed up. Other folk with the same laptop have reported the same problem.
So, if there is a configuration that might take care of the problem, yes, I'd appreciate seeing it and thanks.
Try googling for Slackware on the 700m -- chessgriffin.com I believe it was. It goes into detail (in the Speedstepping config) about the hibernation state. The info may be useful on the 6000
but it ran like a three-legged dog with a busted tail.
The reason for this is the 6000's have a sata controller. When you install 2.4 kernel you are running in a simulated IDE mode. You will notice your drives show up as /dev/hda.
If you build your kernel correctly when you finish 2.6 with sata support your drives are /dev/sda and are about a million times faster.
this might be a pain in the rear at this point, but you might want to use 2.4 kernel and before building your new 2.6 kernel, run make oldconfig. that should give you the settings in 2.4 into your 2.6, then change things as needed. Might help with the lid issue.
Let me know if you get this working. I can only use "other" distro's for so long, before I go back to slack. It would be nice to know its working.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
I figured out about the controller, but I also noted that 2.6.13 supports much, much more of this peculiar laptop (as are all laptops, peculiar) with the single exception of the lid close and waking the thing back up (I mentioned previously that the system keeps running -- I log in to it via ssh from another box). Things like ACPI work (it didn't), it's fast, etc.
I also noticed that the graphics chipset is Intel 915GM/GMS,910GML and that doesn't appear to be supported in the current release of X in Slackware 10.2. So, there's no convenient way to get the resolution up to 1280x800 and I have to live with big-gunky for a while (I'm working on this one, but...).
There's something about "resume=/dev/sdaN" mentioned here and there but I haven't quite gotten to trying it yet -- I think it goes in lilo.conf -- and that may just do it.
Bottom line? Other than this lid nonsense (and the screen resolution) so far I'm a happy camper with this thing with 2.6.13 and I'll fiddle with the kernel (I try to avoid compiling kernels if I can help it) and see what's up with that. I'm reasonably sure that there is a simple, elegant fix for this and that I just haven't tripped over it yet.
In inspiron 6000 (Slackware 10.2,kernel 2.6.13.3) when I close the lid - display is power off, when I open it display is not turned on. Then I do that: Ctrl+Alt+F(1-6) to activate some console - the tisplay is turned on )) - then Alt+F7 to go back to X sesion.
tronayne:
tell me more about your system;
Slackware 10.2 - OK
kernel 2.6 - (or 2.6...) - ???
KDE or GNOME you are runnig ???
your xorg.conf
your 'lsmod' output
your /etc/rc.d/rc.local (without your private lines)
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
DigiSmile:
OK, here goes -- and thanks for asking!
Slackware 10.2
Kernel 2.6.13
KDE 3.4.2 (GNOME is not installed)
My xorg.conf (the hardware is Intel 915GM/GMS/910GML but the drivers are not in this version of X-11 [X11.6.8.2], I canot get 1280x800 resolution either):
/etc/rc.d/rc.local:
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local setup commands in here:
#
# Start the NTP daemon
#
if [ -x /etc/rc.d/rc.ntpd ]
then
/etc/rc.d/rc.ntpd start
fi
#
# Start the VPN client
if [ -x /etc/rc.d/vpnclient_init ]
then
/etc/rc.d/vpnclient_init start
fi
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
)) - then Alt+F7 to go back to X sesion.
