Difference between revisions of "S3 SuperSavage IX/C"
m (→ThinkPad's this chip may be found in) |
(→Linux kernel Framebuffer driver) |
||
| Line 30: | Line 30: | ||
=== Linux kernel Framebuffer driver === | === 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. | 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 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! | ||
| + | vesafb-tng allows the use of a modular framebuffer, which will probably fix this, but how do you unload a framebuffer module? Is it possible to detach the VC from it and reattach it when the module is loaded on resume? | ||
=== ThinkPads this chip may be found in === | === ThinkPads this chip may be found in === | ||
Revision as of 22:49, 30 November 2005
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.
- fix needed***
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! vesafb-tng allows the use of a modular framebuffer, which will probably fix this, but how do you unload a framebuffer module? Is it possible to detach the VC from it and reattach it when the module is loaded on resume?
