The output of 's2ram --test' is
Machine unknown
This machine can be identified by:
sys_vendor = "iQon.ie"
sys_product = "8S661GXMP"
sys_version = "rev 1.1"
bios_version = "F2"
The command 's2ram --force' gives the same behavior as above.
]]>'echo mem > /sys/power/state' also gave the same result.
Oddly though I have noticed, once the PC is suspended and all LEDs, fans etc are off. I can then switch it back on by pressing the Enter key on the keyboard, but after that the keyboard is unresponsive?
Hibernation doesn't work either, the machine fails to shutdown, it just displays a fast blinking cursor in the upper left corner. I did make sure to edit the Syslinux configuration to point to the correct swap-file etc.
]]>Have you tried using that "acpi_sleep=old_ordering"?
The result is still the same. I do however get a few extra messages when I run 'journalctl'
Nov 24 14:56:03 iqon su[360]: (to root) ash on /dev/pts/0
Nov 24 14:56:03 iqon su[360]: pam_unix(su:session): session opened for user root by ash(uid=1000)
Nov 24 14:56:13 iqon systemd[1]: Starting Sleep.
Nov 24 14:56:13 iqon systemd[1]: Reached target Sleep.
Nov 24 14:56:13 iqon systemd[1]: Starting Suspend...
Nov 24 14:56:13 iqon systemd-sleep[364]: Suspending system...
-- Reboot --
Nov 24 14:57:11 iqon systemd-journal[108]: Allowing runtime journal files to grow to 36.0M.
Nov 24 14:57:11 iqon kernel: Initializing cgroup subsys cpuset
Nov 24 14:57:11 iqon kernel: Initializing cgroup subsys cpu
Nov 24 14:57:11 iqon kernel: Linux version 3.6.6-1-ARCH (tobias@testing) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Nov 5 13:14:42 CET 2012
Does this extra line added to the bootloader require the 'acpi' package to be installed? I'm just grabbing at ideas now though.
Thank You for your help so far.
]]>Nov 24 10:14:15 iqon su[847]: (to root) ash on /dev/pts/0
Nov 24 10:14:15 iqon su[847]: pam_unix(su:session): session opened for user root by ash(uid=1000)
-- Reboot --
Nov 24 10:15:33 iqon systemd-journal[107]: Allowing runtime journal files to grow to 36.0M.
Nov 24 10:15:33 iqon kernel: Initializing cgroup subsys cpuset
Nov 24 10:15:33 iqon kernel: Initializing cgroup subsys cpu
Nov 24 10:15:33 iqon kernel: Linux version 3.6.6-1-ARCH (tobias@testing) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Nov 5 13:14:42 CET 2012
This is a snippet off my 'journalctl'. As you can see I switched to root at 10:14, and then entered 'systemctl suspend'. It shows no other messages until have to hit the physical reset button.
]]>Does the systemd journal tell you anything about why that fails?
That is a massive log.
I tried to filter it by typing running the command 'journalctl -u suspend' but it returned nothing.
I scanned though manually, I can clearly see when I have started and shutdown the machine, but nothing in between with regards to the failed resume. I will have a closer look a bit later on.
]]>How does suspending this way interact with systemd? Did you try suspending with systemd first and find that didn't work?
I first tryed 'systemctl suspend' and it didn't work.
I then started getting carried away with pm-utils etc, which didn't work either. I have since removed all those and i'm back to square one.
]]>The bootloader stuff is only relevant for suspend to disk/hibernate. Not for suspend to RAM/sleep.
What does
cat /sys/power/state
give? I think that may tell you what should work although I'm sure somebody will tell me if I'm wrong about that. For example, I get "mem disk".
I also get 'mem disk'.
If it makes a difference I know this machine in it's current configuration would suspend-to-RAM and also wake up succesfully with a previous install of Ubuntu 12.04LTS with the LXDE-Desktop installed.
If there is a command that allows me to post up the hardware info i will post it up but basically it is as follows. (It's all quite outdated hardware)
Pentium 4 3.2Ghz
Gigabyte Motherboard w/ SiS Graphics on-board
768MB RAM
80GB WD HDD