Difference between revisions of "S3 SuperSavage IX/C"
(→External VGA port) |
(→Linux kernel Framebuffer driver) |
||
| Line 32: | Line 32: | ||
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 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. | + | [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 === | === ThinkPads this chip may be found in === | ||
Revision as of 13:46, 18 May 2006
S3 SuperSavage IX/CThis is a S3 video adapter Features
|
Linux X.Org driver
This chip is supported by the 'savage' driver as part of the X.Org distribution
ThinkPad LCD
Display on the internal LCD works as long as you set the monitor settings correct.
External VGA port
Works without trouble, even as Dualhead with xinerama. For swtching on/off use s3switch (also works for TVout).
SVideo port
works.
Linux kernel Framebuffer driver
This chip will work with either the 'vesa' or 'savagefb' driver as part of any recent 2.4 or 2.6 kernel.
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. 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.
