S3 SuperSavage IX/C - Revision history

Bugmenot2: changed category

2021-01-22T13:01:24Z

changed category

2006-08-22T20:45:34Z

‎Direct Rendering (a.k.a accelerated OpenGL)

2006-06-26T08:14:47Z

‎Direct Rendering (a.k.a accelerated OpenGL)

2006-06-26T08:08:35Z

‎Linux kernel Framebuffer driver

2006-06-22T19:54:49Z

DRI and OpenGL information

2006-05-18T12:46:55Z

‎Linux kernel Framebuffer driver

2006-01-06T13:22:36Z

‎External VGA port

2005-12-01T02:10:16Z

make the comment less personal

2005-11-30T21:49:32Z

‎Linux kernel Framebuffer driver

2005-11-05T04:52:30Z

‎ThinkPad's this chip may be found in

@@ Line 21: / Line 21: @@
 === Direct Rendering (a.k.a accelerated OpenGL) ===
 Works without any external drivers with Xorg7. After hibernate (suspend to disk) DRI will not work correctly. glxgears runs fine but playing games will hardlock. Workaround to prevent this is rebooting X. After suspend to RAM it works somehow but rebooting X is recommended.
 Kernel modules: drm, savage

@@ Line 20: / Line 20: @@
 === Direct Rendering (a.k.a accelerated OpenGL) ===
-Works without any external drivers with Xorg7.
+Works without any external drivers with Xorg7. After hibernate (suspend to disk) DRI will not work correctly. glxgears runs fine but playing games will hardlock. Workaround to prevent this is rebooting X. After suspend to RAM it works somehow but rebooting X is recommended.
 Kernel modules: drm, savage

@@ Line 42: / Line 42: @@
 Suspend-to-RAM however does not work properly if the framebuffer is enabled. Suspending with X running is fine, so long as the framebuffer is disabled and X is using its own savage driver. With vesafb the screen is frozen on resume (but the system is still running fine behind it). With savagefb it won't even try to wake up.
 [http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] allows the use of a modular framebuffer, which might fix this- if you can find a way of removing the framebuffer module once inserted.
 === ThinkPads this chip may be found in ===

@@ Line 18: / Line 18: @@
 === Linux X.Org driver ===
 This chip is supported by the '[[savage]]' driver as part of the X.Org distribution
 ==== ThinkPad LCD ====

@@ Line 23: / Line 23: @@
 ==== External VGA port ====
-Works without trouble, even as Dualhead with xinerama. For swtching on/off use s3switch (also works for TVout).
+Works without trouble, even as Dualhead with xinerama. For swtching on/off use [[s3switch]] (also works for TVout).
 ==== SVideo port ====

@@ Line 31: / Line 31: @@
 This chip will work with either the 'vesa' or 'savagefb' driver as part of any recent 2.4 or 2.6 kernel.
-***fix needed***
+Suspend-to-RAM however does not work properly if the framebuffer is enabled. Suspending with X running is fine, so long as the framebuffer is disabled and X is using its own savage driver. With vesafb the screen is frozen on resume (but the system is still running fine behind it). With savagefb it won't even try to wake up.
-Suspend-to-RAM does not work if the framebuffer is enabled. Suspending with X running is fine, so long as the framebuffer is disabled and X is using its own savage driver. With vesafb the screen is frozen on resume (but the system is still running fine behind it). With savagefb it won't even try to wake up! Tried everything!
+[http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] allows the use of a modular framebuffer, which might fix this.
 === ThinkPads this chip may be found in ===