My mainboard is an ASUS P4B-M 1.5 GB mem
I am only interested in suspend to RAM cause hibernate etc just takes to long (and is as fast as a normal shutdown/reboot)
To answer your question Jeremy
—-cat /sys/power/state
standby mem disk
--cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PCI0 S4 *disabled no-bus:pci0000:00
PCI1 S4 *disabled pci:0000:00:01.0
PCI2 S4 *disabled pci:0000:00:1e.0
USB0 S1 *enabled pci:0000:00:1f.2
USB1 S1 *enabled pci:0000:00:1f.4
I know the system can suspend and resume via several options because previously I had WinXP running on it. Suspended fine, came back to life after hitting the keyboard, or even when another client browsed for a share. The only downside was that the fans (processor and case) kept running.
With all the same bios settings I installed TKL, added pm-utils and hit pm-suspend in a console.
System goes beautifully in suspend mode. Even the fans stop running. Yooohooo!!
BUT, hitting the keyboard does nothing, sending a magic package (ethtool eth0 has pug for Wake-on) does not wake her up, just hitting the powerbutton makes the princess come alive.
I did not bother creating a script to add the keyboard and mouse to the /proc/acpi/wakeup folder, the system will be somewhere down in a dark closet where hardly anyone can touch it, and only with calamities someone will physically attend a console.
The server will be ’serving’ my father in law’s small insurance office (3 computers).
So what would be your ideas how to tackle this problem?
PS, just found out something 'funny' If I do a shutdown -h now. And send a magic package from some client. The computer comes back to life. But this actually takes to long (the booting I mean, and also the shutting down)
Power management
My mainboard is an ASUS P4B-M 1.5 GB mem
I am only interested in suspend to RAM cause hibernate etc just takes to long (and is as fast as a normal shutdown/reboot)
To answer your question Jeremy
—-cat /sys/power/state
standby mem disk
--cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PCI0 S4 *disabled no-bus:pci0000:00
PCI1 S4 *disabled pci:0000:00:01.0
PCI2 S4 *disabled pci:0000:00:1e.0
USB0 S1 *enabled pci:0000:00:1f.2
USB1 S1 *enabled pci:0000:00:1f.4
/sys/class/net/eth0/device/power/wakeup
says disabled
I know the system can suspend and resume via several options because previously I had WinXP running on it. Suspended fine, came back to life after hitting the keyboard, or even when another client browsed for a share. The only downside was that the fans (processor and case) kept running.
With all the same bios settings I installed TKL, added pm-utils and hit pm-suspend in a console.
System goes beautifully in suspend mode. Even the fans stop running. Yooohooo!!
BUT, hitting the keyboard does nothing, sending a magic package (ethtool eth0 has pug for Wake-on) does not wake her up, just hitting the powerbutton makes the princess come alive.
I did not bother creating a script to add the keyboard and mouse to the /proc/acpi/wakeup folder, the system will be somewhere down in a dark closet where hardly anyone can touch it, and only with calamities someone will physically attend a console.
The server will be ’serving’ my father in law’s small insurance office (3 computers).
So what would be your ideas how to tackle this problem?
PS, just found out something 'funny' If I do a shutdown -h now. And send a magic package from some client. The computer comes back to life. But this actually takes to long (the booting I mean, and also the shutting down)