dCore Import Debian Packages to Mountable SCE extensions > dCore X86
suspend-to-ram (STR) in dCore-5.13.11.06
netnomad:
hi friends,
did you succeed with suspend-to-ram?
after the resume i get a black screen and the system seems to be frozen:
no effect for key strokes like shift, num-lock.
this behavior or problem is often reported in the web community, especially with my i915-intel-card :(
one major problem seems to be that for /sys/power/state even root has no permission and some commands think that it doesn't exist (the file is there but with the editor of midnight-commander strange characters are in line2).
i tried pm-utils, uswswap and acpid with s2ram with different options...
and added the boot-code acpi_sleep=s3_bios.
do you think that the kernel has all needed options or do i need more modules loaded?
i know that it's a common problem, but i'm curious whether you succeeded.
thank you for your replies.
tinypoodle:
What about
--- Code: ---cat /sys/power/state
--- End code ---
netnomad:
hi tinypoodle,
that's what i get:
tc@box:~$ cat /sys/power/state
mem disk
tinypoodle:
This means basically your system has capabilities to suspend to RAM and/or disk; my guess is that it might not be the best idea then to use mc to peek at /sys files.
Generally speaking, behaviour of suspend depends to a big degree on hardware and BIOS; and probabilities of success are higher with STD compared to STR.
netnomad:
--- Quote ---This means basically your system has capabilities to suspend to RAM and/or disk; my guess is that it might not be the best idea then to use mc to peek at /sys files.
--- End quote ---
yes, you're right that mc is not the best tool.
usually
tc@box:~$ echo mem >/sys/power/state
bash: /sys/power/state: Permission denied
should work.
--- Quote ---Generally speaking, behaviour of suspend depends to a big degree on hardware and BIOS; and probabilities of success are higher with STD compared to STR.
--- End quote ---
with microcore 4.7.7 and xvesa i have no problem at all to suspend-to-ram.
i'm not sure whether xorg or the newer kernel causes this problem.
Navigation
[0] Message Index
[#] Next page
Go to full version