Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

InstallationGuide changed

Browse Source 
Updated workarounds for S3 resume problems
This commit is contained in:
Joanna Rutkowska 2010-07-06 12:30:16 +00:00
parent 0e48c30fac
commit 8f92714cb5
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
InstallationGuide.md
View File

@ -232,8 +232,7 @@ This should be appended the ```kernel``` line in ```grub.conf```. This will disa
1. If you have Intel HD graphics card on Core i5/i7 processor, do **not** enable desktop effects (or at least do not choose OpenGL engine). There is a known problem with those cards drivers that causes X to crash every few minutes, when OpenGL is used. This happens on standard Fedora installation, even without Xen and without Qubes. 1. If you have Intel HD graphics card on Core i5/i7 processor, do **not** enable desktop effects (or at least do not choose OpenGL engine). There is a known problem with those cards drivers that causes X to crash every few minutes, when OpenGL is used. This happens on standard Fedora installation, even without Xen and without Qubes.
1. The clock in AppVMs is not properly updated after resume from S3 sleep, if you don't use NTP in the VMs. 1. The clock in AppVMs is not properly updated after resume from S3 sleep. The temporary workaround is to use NTP for clock syncing in each AppVM.
1. Sometimes an AppVM might lock up after a resume from S3 sleep. 1. On processors with Hyper-Threading support, such as Intel Core i5/i7 (but not Core 2 Duo), the AppVM might lock up after a resume from S3 sleep. A temporary work around for this is to disable [HyperThreading?](/wiki/HyperThreading) in BIOS.
**Generally, please consider the suspend/resume to be highly experimental currently, and always save your work before suspending your system too S3 sleep'''**