Description of problem:
Will attach tarball with suspend scripts that users on the console may invoke to
begin with. Should be good to include thus far; things we might want to improve
1) autodetecting radeons and using radeontool (pjones, any ideas?)
2) handling non-NM networking
The attached tarballs contains
-rw-r--r-- root/root 1182 2005-04-21 14:45:09 etc/pm-suspend.conf
lrwxrwxrwx root/root 0 2005-04-21 14:48:23 usr/bin/pm-suspend ->
-rwxr-xr-x root/root 3530 2005-04-21 14:59:21 usr/sbin/pm-suspend
-rw-r--r-- root/root 0 2005-04-21 14:55:29
Created attachment 113486 [details]
tarball with files
*** Bug 143397 has been marked as a duplicate of this bug. ***
Another (perhaps more complicated) solution is available in the suspend2
Which can suspend using suspend2, suspend1, S3 (suspend to ram), etc.
It also can use radeontool, vbetool, start a dummy X server after resume, change
to a text console, unload/reload modules, up/down interfaces, etc.
So it looks like pjones got the whitelist in the kernel so userspace don't have
to do tricks that the drivers should (however something needs to load radeonfb
With that in mind, can we go ahead and add the pm-suspend stuff? We need this to
include goodness like gnome-power-manager... I'm sure we want to change things
in pm-suspend before FC5 (perhaps just make it call a suspend2 scripts, who
knows) but we need to start somewhere.
A variant added in 0.02-1. Significant lack of configuration, *intentionally*. :)