video.txt 8.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186
  1. Video issues with S3 resume
  2. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  3. 2003-2006, Pavel Machek
  4. During S3 resume, hardware needs to be reinitialized. For most
  5. devices, this is easy, and kernel driver knows how to do
  6. it. Unfortunately there's one exception: video card. Those are usually
  7. initialized by BIOS, and kernel does not have enough information to
  8. boot video card. (Kernel usually does not even contain video card
  9. driver -- vesafb and vgacon are widely used).
  10. This is not problem for swsusp, because during swsusp resume, BIOS is
  11. run normally so video card is normally initialized. It should not be
  12. problem for S1 standby, because hardware should retain its state over
  13. that.
  14. We either have to run video BIOS during early resume, or interpret it
  15. using vbetool later, or maybe nothing is necessary on particular
  16. system because video state is preserved. Unfortunately different
  17. methods work on different systems, and no known method suits all of
  18. them.
  19. Userland application called s2ram has been developed; it contains long
  20. whitelist of systems, and automatically selects working method for a
  21. given system. It can be downloaded from CVS at
  22. www.sf.net/projects/suspend . If you get a system that is not in the
  23. whitelist, please try to find a working solution, and submit whitelist
  24. entry so that work does not need to be repeated.
  25. Currently, VBE_SAVE method (6 below) works on most
  26. systems. Unfortunately, vbetool only runs after userland is resumed,
  27. so it makes debugging of early resume problems
  28. hard/impossible. Methods that do not rely on userland are preferable.
  29. Details
  30. ~~~~~~~
  31. There are a few types of systems where video works after S3 resume:
  32. (1) systems where video state is preserved over S3.
  33. (2) systems where it is possible to call the video BIOS during S3
  34. resume. Unfortunately, it is not correct to call the video BIOS at
  35. that point, but it happens to work on some machines. Use
  36. acpi_sleep=s3_bios.
  37. (3) systems that initialize video card into vga text mode and where
  38. the BIOS works well enough to be able to set video mode. Use
  39. acpi_sleep=s3_mode on these.
  40. (4) on some systems s3_bios kicks video into text mode, and
  41. acpi_sleep=s3_bios,s3_mode is needed.
  42. (5) radeon systems, where X can soft-boot your video card. You'll need
  43. a new enough X, and a plain text console (no vesafb or radeonfb). See
  44. http://www.doesi.gmxhome.de/linux/tm800s3/s3.html for more information.
  45. Alternatively, you should use vbetool (6) instead.
  46. (6) other radeon systems, where vbetool is enough to bring system back
  47. to life. It needs text console to be working. Do vbetool vbestate
  48. save > /tmp/delme; echo 3 > /proc/acpi/sleep; vbetool post; vbetool
  49. vbestate restore < /tmp/delme; setfont <whatever>, and your video
  50. should work.
  51. (7) on some systems, it is possible to boot most of kernel, and then
  52. POSTing bios works. Ole Rohne has patch to do just that at
  53. http://dev.gentoo.org/~marineam/patch-radeonfb-2.6.11-rc2-mm2.
  54. (8) on some systems, you can use the video_post utility and or
  55. do echo 3 > /sys/power/state && /usr/sbin/video_post - which will
  56. initialize the display in console mode. If you are in X, you can switch
  57. to a virtual terminal and back to X using CTRL+ALT+F1 - CTRL+ALT+F7 to get
  58. the display working in graphical mode again.
  59. Now, if you pass acpi_sleep=something, and it does not work with your
  60. bios, you'll get a hard crash during resume. Be careful. Also it is
  61. safest to do your experiments with plain old VGA console. The vesafb
  62. and radeonfb (etc) drivers have a tendency to crash the machine during
  63. resume.
  64. You may have a system where none of above works. At that point you
  65. either invent another ugly hack that works, or write proper driver for
  66. your video card (good luck getting docs :-(). Maybe suspending from X
  67. (proper X, knowing your hardware, not XF68_FBcon) might have better
  68. chance of working.
  69. Table of known working notebooks:
  70. Model hack (or "how to do it")
  71. ------------------------------------------------------------------------------
  72. Acer Aspire 1406LC ole's late BIOS init (7), turn off DRI
  73. Acer TM 230 s3_bios (2)
  74. Acer TM 242FX vbetool (6)
  75. Acer TM C110 video_post (8)
  76. Acer TM C300 vga=normal (only suspend on console, not in X), vbetool (6) or video_post (8)
  77. Acer TM 4052LCi s3_bios (2)
  78. Acer TM 636Lci s3_bios,s3_mode (4)
  79. Acer TM 650 (Radeon M7) vga=normal plus boot-radeon (5) gets text console back
  80. Acer TM 660 ??? (*)
  81. Acer TM 800 vga=normal, X patches, see webpage (5) or vbetool (6)
  82. Acer TM 803 vga=normal, X patches, see webpage (5) or vbetool (6)
  83. Acer TM 803LCi vga=normal, vbetool (6)
  84. Arima W730a vbetool needed (6)
  85. Asus L2400D s3_mode (3)(***) (S1 also works OK)
  86. Asus L3350M (SiS 740) (6)
  87. Asus L3800C (Radeon M7) s3_bios (2) (S1 also works OK)
  88. Asus M6887Ne vga=normal, s3_bios (2), use radeon driver instead of fglrx in x.org
  89. Athlon64 desktop prototype s3_bios (2)
  90. Compal CL-50 ??? (*)
  91. Compaq Armada E500 - P3-700 none (1) (S1 also works OK)
  92. Compaq Evo N620c vga=normal, s3_bios (2)
  93. Dell 600m, ATI R250 Lf none (1), but needs xorg-x11-6.8.1.902-1
  94. Dell D600, ATI RV250 vga=normal and X, or try vbestate (6)
  95. Dell D610 vga=normal and X (possibly vbestate (6) too, but not tested)
  96. Dell Inspiron 4000 ??? (*)
  97. Dell Inspiron 500m ??? (*)
  98. Dell Inspiron 510m ???
  99. Dell Inspiron 5150 vbetool needed (6)
  100. Dell Inspiron 600m ??? (*)
  101. Dell Inspiron 8200 ??? (*)
  102. Dell Inspiron 8500 ??? (*)
  103. Dell Inspiron 8600 ??? (*)
  104. eMachines athlon64 machines vbetool needed (6) (someone please get me model #s)
  105. HP NC6000 s3_bios, may not use radeonfb (2); or vbetool (6)
  106. HP NX7000 ??? (*)
  107. HP Pavilion ZD7000 vbetool post needed, need open-source nv driver for X
  108. HP Omnibook XE3 athlon version none (1)
  109. HP Omnibook XE3GC none (1), video is S3 Savage/IX-MV
  110. HP Omnibook XE3L-GF vbetool (6)
  111. HP Omnibook 5150 none (1), (S1 also works OK)
  112. IBM TP T20, model 2647-44G none (1), video is S3 Inc. 86C270-294 Savage/IX-MV, vesafb gets "interesting" but X work.
  113. IBM TP A31 / Type 2652-M5G s3_mode (3) [works ok with BIOS 1.04 2002-08-23, but not at all with BIOS 1.11 2004-11-05 :-(]
  114. IBM TP R32 / Type 2658-MMG none (1)
  115. IBM TP R40 2722B3G ??? (*)
  116. IBM TP R50p / Type 1832-22U s3_bios (2)
  117. IBM TP R51 none (1)
  118. IBM TP T30 236681A ??? (*)
  119. IBM TP T40 / Type 2373-MU4 none (1)
  120. IBM TP T40p none (1)
  121. IBM TP R40p s3_bios (2)
  122. IBM TP T41p s3_bios (2), switch to X after resume
  123. IBM TP T42 s3_bios (2)
  124. IBM ThinkPad T42p (2373-GTG) s3_bios (2)
  125. IBM TP X20 ??? (*)
  126. IBM TP X30 s3_bios, s3_mode (4)
  127. IBM TP X31 / Type 2672-XXH none (1), use radeontool (http://fdd.com/software/radeon/) to turn off backlight.
  128. IBM TP X32 none (1), but backlight is on and video is trashed after long suspend. s3_bios,s3_mode (4) works too. Perhaps that gets better results?
  129. IBM Thinkpad X40 Type 2371-7JG s3_bios,s3_mode (4)
  130. IBM TP 600e none(1), but a switch to console and back to X is needed
  131. Medion MD4220 ??? (*)
  132. Samsung P35 vbetool needed (6)
  133. Sharp PC-AR10 (ATI rage) none (1), backlight does not switch off
  134. Sony Vaio PCG-C1VRX/K s3_bios (2)
  135. Sony Vaio PCG-F403 ??? (*)
  136. Sony Vaio PCG-GRT995MP none (1), works with 'nv' X driver
  137. Sony Vaio PCG-GR7/K none (1), but needs radeonfb, use radeontool (http://fdd.com/software/radeon/) to turn off backlight.
  138. Sony Vaio PCG-N505SN ??? (*)
  139. Sony Vaio vgn-s260 X or boot-radeon can init it (5)
  140. Sony Vaio vgn-S580BH vga=normal, but suspend from X. Console will be blank unless you return to X.
  141. Sony Vaio vgn-FS115B s3_bios (2),s3_mode (4)
  142. Toshiba Libretto L5 none (1)
  143. Toshiba Libretto 100CT/110CT vbetool (6)
  144. Toshiba Portege 3020CT s3_mode (3)
  145. Toshiba Satellite 4030CDT s3_mode (3) (S1 also works OK)
  146. Toshiba Satellite 4080XCDT s3_mode (3) (S1 also works OK)
  147. Toshiba Satellite 4090XCDT ??? (*)
  148. Toshiba Satellite P10-554 s3_bios,s3_mode (4)(****)
  149. Toshiba M30 (2) xor X with nvidia driver using internal AGP
  150. Uniwill 244IIO ??? (*)
  151. Known working desktop systems
  152. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  153. Mainboard Graphics card hack (or "how to do it")
  154. ------------------------------------------------------------------------------
  155. Asus A7V8X nVidia RIVA TNT2 model 64 s3_bios,s3_mode (4)
  156. (*) from https://wiki.ubuntu.com/HoaryPMResults, not sure
  157. which options to use. If you know, please tell me.
  158. (***) To be tested with a newer kernel.
  159. (****) Not with SMP kernel, UP only.