Linux-2.6.12-rc2
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
This commit is contained in:
27
Documentation/power/tricks.txt
Normal file
27
Documentation/power/tricks.txt
Normal file
@@ -0,0 +1,27 @@
|
||||
swsusp/S3 tricks
|
||||
~~~~~~~~~~~~~~~~
|
||||
Pavel Machek <pavel@suse.cz>
|
||||
|
||||
If you want to trick swsusp/S3 into working, you might want to try:
|
||||
|
||||
* go with minimal config, turn off drivers like USB, AGP you don't
|
||||
really need
|
||||
|
||||
* turn off APIC and preempt
|
||||
|
||||
* use ext2. At least it has working fsck. [If something seemes to go
|
||||
wrong, force fsck when you have a chance]
|
||||
|
||||
* turn off modules
|
||||
|
||||
* use vga text console, shut down X. [If you really want X, you might
|
||||
want to try vesafb later]
|
||||
|
||||
* try running as few processes as possible, preferably go to single
|
||||
user mode.
|
||||
|
||||
* due to video issues, swsusp should be easier to get working than
|
||||
S3. Try that first.
|
||||
|
||||
When you make it work, try to find out what exactly was it that broke
|
||||
suspend, and preferably fix that.
|
Reference in New Issue
Block a user