ysxshweetyrxxliyysxsliststuxonicenet send tuxoniceusers mailing list submissions enpsfhxzstvnzliststuxonicenet subscribe unsubscribe via world wide web visit httpliststuxonicenetmailmanlistinfotuxoniceusers via email send message subject body help ysxshweetyrxxliyysxsliststuxonicenet reach person managing list ixmmppemuqpyfbotixliststuxonicenet replying please edit subject line specific contents tuxoniceusers digest todays topics 1 difference s4 s5 jeremy maitinshepard 2 difference s4 s5 nigel cunningham 3 difference s4 s5 nigel cunningham 4 find size wrote data florian strunk 5 find size wrote data nigel cunningham 6 tuxonicedevel 30rc5 released nigel cunningham 7 tuxonicedevel 30rc5 released nigel cunningham 8 find size wrote data nigel cunningham 9 find size wrote data florian strunk mxwlcmuedu sat apr 26 154924 2008 message 1 date sun 24 feb 2008 131926 0500 jeremy maitinshepard subject tuxoniceusers difference s4 s5 zixdtcx9umyfrliststuxonicenet messageid 87y79ausi9fsfjbmsathcx contenttype textplain david abrahams writes sat feb 23 2008 nigel cunningham wrote hi david abrahams wrote documentation find difference s4 s5 s4 image ram written disk course thats toi difference powerdownmethod 4 powerdownmethod 5 used toi mean even set 5 still ram image disk right s4 s5 acpi states reflected 4 5 powerdown method value acpi state s4 state bios knows image disk postresume acpi _wak iirc methods run might make things work otherwise wouldnt properly work postresume acpi state s5 simple power far acpi bios concerned youre resuming acpi _wak methods run purely dependent upon tuxonice os driver suspend resume routines right thing course still include acpi extent normal thing ought use powerdownmethod 4 historically though hasnt always worked people seem work ok although seems though mightve achieved success sooner known s4 worth trying since supposed make things work properly shouldnt docs howtos default suspend2conf updated use s4 default tell people try s5 doesnt work theory believe one reason s4 useful namely system supports certain wakeup devices s4 supported s5 youd like use practice though current linux hibernate implementations tuxonice swsusp neither hibernate resume paths exactly acpi spec envisions point view devices furthermore many devices bios implementations may even exactly spec result different steps done s4 used rather plain powerdown sometimes help note specifically thinking resume kernel typically initializes acpi prior loading saved image saved image attempts reinitialize acpi also devices repeatedly placed taken low power states suitable s3 process entering hibernation resume hibernation resume driver function called current interfaces thing available may know appropriate thing since also used resume devices s3 jeremy maitinshepard nlnprnigelsuspend2net sat apr 26 154924 2008 message 2 date mon 25 feb 2008 075745 1100 nigel cunningham subject tuxoniceusers difference s4 s5 tuxonice users list cc zixdtcx9umyfrliststuxonicenet messageid 47c1da499060503nigelsuspend2net contenttype textplain charsetiso88591 formatflowed hi jeremy maitinshepard wrote david abrahams writes sat feb 23 2008 nigel cunningham wrote hi david abrahams wrote documentation find difference s4 s5 s4 image ram written disk course thats toi difference powerdownmethod 4 powerdownmethod 5 used toi mean even set 5 still ram image disk right s4 s5 acpi states reflected 4 5 powerdown method value acpi state s4 state bios knows image disk postresume acpi _wak iirc methods run might make things work otherwise wouldnt properly work postresume acpi state s5 simple power far acpi bios concerned youre resuming acpi _wak methods run purely dependent upon tuxonice os driver suspend resume routines right thing course still include acpi extent normal thing ought use powerdownmethod 4 historically though hasnt always worked people seem work ok although seems though mightve achieved success sooner known s4 worth trying since supposed make things work properly shouldnt docs howtos default suspend2conf updated use s4 default tell people try s5 doesnt work theory believe one reason s4 useful namely system supports certain wakeup devices s4 supported s5 youd like use practice though current linux hibernate implementations tuxonice swsusp neither hibernate resume paths exactly acpi spec envisions point view devices furthermore many devices bios implementations may even exactly spec result different steps done s4 used rather plain powerdown sometimes help note specifically thinking resume kernel typically initializes acpi prior loading saved image saved image attempts reinitialize acpi also devices repeatedly placed taken low power states suitable s3 process entering hibernation resume hibernation resume driver function called current interfaces thing available may know appropriate thing since also used resume devices s3 yeah changing 2625 regards nigel thu 07 aug 2008 233216 0000 tuxoniceusers digest vol 36 issue 31