How to suspend Dell e6400 laptop?

[yr1945]

can't suspend my dell laptop e6400 on most new OS's...

usually I can just close the lid on all older OS's...

even tried adding acpitool coupled with pupshutdown apps... still won't suspend... any suggestions? Thank You.

[bigpup]

Have you tried Xenialpup 7.5 64 or 32 bit version?

If you are going to try and fix this.
Need to talk about one specific version of Puppy.

[yr1945]

yes, I have tried Xenialpup 7.5 32 bit version, as well as most other recent OS's... laptop will not suspend... Thank you.

[musher0]

Hello yr1945.

Here is one way to do it!!!

[Marv]

@musher0, I never considered Foucault suspension

[jafadmin]

First try something simple to test dpms:

Code: Select all

xset dpms force off

That should blank the screen and unblank when mouse or keyboard are used.
If that works, try:

Code: Select all

xset dpms force standby

all:

Code: Select all

xset dpms force [{standby|suspend|off|on}]

[Sailor Enceladus]

Did you try running?

Code: Select all

. /etc/acpi/actions/suspend.sh

Maybe running it from terminal will tell you what is wrong.

[ally]

I have xenial64 7.5 running on a lenovo x230 and suspend does not work

the above command gives

Code: Select all

rmmod: ERROR: Module ehci_hcd is builtin.

suspbase used to work on tahrpup on lenovo x201 but not on xenial

Code: Select all

#!/bin/sh
sleep 1
echo mem > /sys/power/state


:)

edit: closing the suspends but immediately restarts

edit: [code]xset dpms force standby

blanks screen then comes straight back[/code]

[wiak]

I have xenial64 7.5 running on a lenovo x230 and suspend does not work

the above command gives

Code: Select all

rmmod: ERROR: Module ehci_hcd is builtin.

suspbase used to work on tahrpup on lenovo x201 but not on xenial

Might be related to the bug I posted about on xenialdog thread concerning suspend with xenial in link below. I have not managed to resolve the problem on my system:

http://murga-linux.com/puppy/viewtopic. ... 395#981395

wiak

[yr1945]

I would like to Thank You for all the responses... nothing seems to work... still cannot suspend my laptop...

well, actually the suggestion from musher0 works (lol)

[matchpoint]

I clipped this from the Arch wiki. It may help those of you with enough experience.

[Marv]

I loved the pic from musher0. I think we've all had systems that needed that. I'm intrigued by hardware/system interactions though... I set up a pristine Grub4Dos boot of xenialpup64 7.5 on my Fujitsu S761 i5 based laptop (it does have docking capabilities). Once booted with the timezone and wifi set up, nothing added at all, I suspended from lid closure , suspended by running

Code: Select all

/etc/acpi/actions/suspend.sh

in terminal, and suspended by running

Code: Select all

echo -n mem > /sys/power/state

in terminal. All basically worked and would work well with a few tweaks to the stock suspend.sh file. Two questions if you don't mind. Is it a USB based boot and what does your system do exactly, particularly in response to the echo command in terminal?

Another question, what is the output of

Code: Select all

lspci | grep Network

run in terminal? May seem irrelevant but I had an intel 6205n (IIRC) wireless card that caused many interrupt and memory space conflicts with newer kernels and among other things resulted in odd shutdown behavior. Fortunately I had 3 other identical systems with a different wifi card that were ok. Replaced that card and all 4 are now truly identical and happy.

[yr1945]

output of,,, lspci | grep Network...

[Marv]

Thanks, That's not the card I had issues with. In fact, I'm using both the intel 5100 and 5300 on my core 2 duos with no issues, some running a xenialpup64 7.5 deriv. Still curious about what your system does when you run the echo -n mem ... command in terminal. No response at all? Lock up?

[ally]

both above commands sleep but restarts immediately

[yr1945]

the command... echo -n mem > /sys/power/state... makes my laptop go to sleep for just one second and then the screen immediately comes back on again...

[bigpup]

Are you booting and running Puppy from a USB drive.
USB Flash drive or hard drive?

I remember something about suspend made to not work if running from a USB drive.

This code is in suspend.sh

Code: Select all

# do not suspend if usb media mounted
USBS=$(probedisk2|grep '|usb' | cut -d'|' -f1 )
for USB in $USBS
do
mount | grep -q "^$USB" && rm -f "$LOCKFILE" && exit 0
done

[yr1945]

Thanks, but I boot from a CD.

[Marv]

Invoking suspend with the echo command bypasses that USB check. The 1 second delay 'seems' like something is sending an interrupt that the kernel interprets as a power button press. I don't have any hardware that behaves in this manner so it's a bit of a 'thought experiment' for me. Doing that echo command and then entering dmesg in terminal and then looking at the final lines of the output (after a line that contains "suspend entry" in my system) might shed some light on what the kernel is doing. I'll attach those lines from my system doing a normal suspend and wake as an example. When you're ready to call a halt say so, otherwise I'm still puzzled.

@ally Thanks for the check. I replied but must have just previewed and slept. How are you booting?

[ally]

@marv

Code: Select all

  kernel /xenial64_7.5/vmlinuz   psubdir=xenial64_7.5 pmedia=atahd pfix=fsck intel_pstate=disable acpi_osi="!Windows 2012"

grub4dos