| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | swsusp/S3 tricks | 
|  | 2 | ~~~~~~~~~~~~~~~~ | 
|  | 3 | Pavel Machek <pavel@suse.cz> | 
|  | 4 |  | 
|  | 5 | If you want to trick swsusp/S3 into working, you might want to try: | 
|  | 6 |  | 
|  | 7 | * go with minimal config, turn off drivers like USB, AGP you don't | 
|  | 8 | really need | 
|  | 9 |  | 
|  | 10 | * turn off APIC and preempt | 
|  | 11 |  | 
| Matt LaPlante | 53cb472 | 2006-10-03 22:55:17 +0200 | [diff] [blame] | 12 | * use ext2. At least it has working fsck. [If something seems to go | 
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 13 | wrong, force fsck when you have a chance] | 
|  | 14 |  | 
|  | 15 | * turn off modules | 
|  | 16 |  | 
|  | 17 | * use vga text console, shut down X. [If you really want X, you might | 
|  | 18 | want to try vesafb later] | 
|  | 19 |  | 
|  | 20 | * try running as few processes as possible, preferably go to single | 
|  | 21 | user mode. | 
|  | 22 |  | 
|  | 23 | * due to video issues, swsusp should be easier to get working than | 
|  | 24 | S3. Try that first. | 
|  | 25 |  | 
|  | 26 | When you make it work, try to find out what exactly was it that broke | 
|  | 27 | suspend, and preferably fix that. |