dCore Import Debian Packages to Mountable SCE extensions > dCore X86

suspend-to-ram (STR) in dCore-5.13.11.06

<< < (3/4) > >>

netnomad:

--- Quote from: tinypoodle on November 12, 2013, 07:28:05 PM ---"leave xorg" is ambiguous, do you mean you just switched to a VT or you killed the Xorg PID?

--- End quote ---
hi tinypoodle,

i did "Exit to prompt" with "TC Exit options", so i probably killed xorg pid.

netnomad:

--- Quote from: Jason W on November 12, 2013, 11:17:20 PM ---I just now seen the same behavior in TC 5.x suspend to disk with Xvesa as well as dCore with a newer kernel suspend to RAM. Maybe the newer kernel, maybe not at this point.

--- End quote ---
hi jason w,

with 4.7.7 and some native debian-configurations i succeeded with a script like this:

#!/bin/sh

vt='/usr/bin/fgconsole'
sudo rmmod oss_ich
sudo rmmod oss_usb
sudo rmmod oss_hdaudio
sudo rmmod osscore
sudo s2ram --force --vbe_save
/usr/bin/chvt $vt
sleep 1
sudo modprobe osscore
sudo modprobe oss_hdaudio
sudo modprobe oss_usb
sudo modprobe oss_ich

the black-display-problem could be prevented with the change of the virtual terminal...
... the other lines are just for the sound modules

tinypoodle:
Eh, not exactly same subtlety of methods...
Please try with s2ram with same parameters then, and stop OSS4 first, IIRC with Core you should first execute the script to stop OSS4 rather than directly rmmod'ing the modules.
I suggest you try manually issuing one command after the other and not using scripting until you got it to work.

netnomad:
hi tinypoodle,

i don´t use this script for testing in dCore,
i use it only in microcore 4.7.7 and it works properly on my and many different further hardware-environments.

in my testing with dCore i just try single commands in xterm (or after "Exit to prompt" with "TC Exit options") like

s2ram
s2ram -f
s2ram -f -p -m

but it´s always the same result :(

what do you think about this approach?
https://ubuntuforums.org/showthread.php?t=1978290

tinypoodle:
I wouldn't know about that link, but if it works for you with 4.7.7 you should first try the exact same steps, and preferably test with regular Core 5.x as Jason W suggested in Reply #6 for a diagnostic conclusion.

Navigation

[0] Message Index

[#] Next page

[*] Previous page