I may be wrong, but don't you need ACPI for various power-off states?

@mmmrr According to your check, only freeze (suspend-to-idle) is supported with your setup. Apparently this particular power state is always available. With my setup freeze, standby and mem is stipulated in /sys/power/state. This is as far as I can help you with this.

phoenix

from menu.lst:
title grub2title grub2
kernel /boot/grub/i386-pc/core.img rdrand=force

from grub.cfg
linux /bionic-rc-a2/vmlinuz pmedia=atahd pdrv=082A-1B73 psubdir=/bionic-rc-a2 pfix=fsck,fsckp TZ=CST6CDT,M3.2.0,M11.1.0 acpi=off

acpitool_0.5.1 shows 'already installed' by puppy package manager.

acpi* search in ppm shows ten or so other acpi packages.

on previous toshiba laptops over the years i remember having to
install acpitool_0.5.1 before sleep [suspend] would work.

mm

thanks amethyst

acpi=off

What happens if you make it acpi=on

amethyst

i suppose that the menu.lst entry
and the grub.cfg entry should be the same?
here goes.

mm

amethyst

changed menu.lst and grub.cfg to acpi=on,
rebooted.
entered 'echo mem > /sys/power/state' in terminal.
display went black.
power switch went from blue to pulsing orange.
waited a few moments.
pressed power switch, display returned, frozen.
held down power switch til shutdown, a moment.
waited a couple of minutes, restarted without issue.

mm

Once you get it to freeze again when resuming, please post the output of /var/log/previous.messages.

thanks phoenix,
i'll freeze shortly,
got a little tidying
to do first...i ran

"/var/log/previous.messages"

to see what response
before setting the freeze:

/var/l# /var/log/previous.messages

bash: /var/log/previous.messages: Permission denied

don't know where '/var/l#' comes from

later , mm

edit 1: after resuming from freeze

/var/log/previous.messages

bash: /var/log/previous.messages: Permission denied

mmmrr wrote: ↑Sun Nov 26, 2023 6:09 pm

amethyst

changed menu.lst and grub.cfg to acpi=on,
rebooted.
entered 'echo mem > /sys/power/state' in terminal.
display went black.
power switch went from blue to pulsing orange.
waited a few moments.
pressed power switch, display returned, frozen.
held down power switch til shutdown, a moment.
waited a couple of minutes, restarted without issue.

mm

On my laptop, I press the power button for about 3 seconds and then move the mouse slightly to get out of the sleep state. Works every time for me.

I meant to say, upload it. Alternatively open them with a text editor and paste giant walls of text. Or use a paste service.

amethyst, thanks. i'll try that.

hi phoenix, how upload? i copy/
pasted fron terminal. the forum
made giant text.. i will go to
/var/log/private.messages,
see if a texteditor opens it.

cheers..mm

okay phoenix
here comes giant wall of text after
restart after freeze.

i will be trying amethyst's method for awakening
computer: 3 sec hold on power button; slight
movement of mouse.

output text too big for posting:
"Your message contains 154361 characters.
The maximum number of allowed characters is 60000."

it looks like i have posted the output at:

https://pastes.io
title: -v-l-p.m
password: Password

cheers, mm

Have you tried modprobe toshiba_acpi? Also please re-enable acpi while you're at it.
Otherwise I cannot think of much. I would suggest trying a newer kernel and see if perhaps it is fixed there.

hi phoenix

i have been acpi=on for the last two weeks.
is that the same as re-enabling acpi?
i have just 'modprobe toshiba_acpi'
i have a plainer bionic32 on cd , boots, works.
i'll try installing it to a ext2 partition.
this pup i'm trying to suspend is installed
on vfat partition. a well experienced puppian
suggested that the vfat might be problem.
thanks, mm

the bionic32 on cd-rw which booted and ran
last week this would not this evening.
the boot process halted when the sfs file could
not be found. i was invited to enter 'debugsave' .

in due course i rebooted to the hard drive, looked
in the partition i'd saved the debug info to. lots of info,
non of it understandable by me.

i'll download a fresh bionic32, start over....mm

Filesystem type does not prohibit the ability to enter sleep. Remember, sleep saves in-memory contents of RAM, and makes the general assumption that whatever devices were connected will be connected when the machine wakes up.