Difference between revisions of "S3 SuperSavage IX/C"

From ThinkWiki
Jump to: navigation, search
(External VGA port)
(changed category)
 
(11 intermediate revisions by 6 users not shown)
Line 17: Line 17:
  
 
=== Linux X.Org driver ===
 
=== Linux X.Org driver ===
This chip is supported by the 'savage' driver as part of the X.Org distribution
+
This chip is supported by the '[[savage]]' driver as part of the X.Org distribution
 +
 
 +
=== 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.
 +
 
 +
Note: I upgraded BIOS to latest version (1.18) but still no luck. OpenGL (DRI?) hardlocks after hibernate.
 +
 
 +
Kernel modules: drm, savage
 +
 
 +
xorg.conf: load glx and dri modules
 +
 
 +
glxgears gives around ~500 fps.
  
 
==== ThinkPad LCD ====
 
==== ThinkPad LCD ====
Line 23: Line 34:
  
 
==== External VGA port ====
 
==== 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 ====
 
==== SVideo port ====
??
+
works.
 +
 
 
=== 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.
  
=== ThinkPad's this chip may be found in ===
+
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.
 +
 
 +
With kernel 2.6.17.1 savagefb works fine after resuming from suspend or hibernate. You might need to change your virtual terminal once to get it back to life.
 +
 
 +
=== ThinkPads this chip may be found in ===
 
* {{T23}}
 
* {{T23}}
  
[[Category:Components]]
+
[[Category:Video Controllers]]

Latest revision as of 14:01, 22 January 2021

S3 SuperSavage IX/C

This is a S3 video adapter
S3 is now owned by Via Technologies

Features

  • Chipset: S3
  • PCI ID: 5333:8c2e
  • AGP 4X
  • 16MB SDRAM video memory

Linux X.Org driver

This chip is supported by the 'savage' driver as part of the X.Org distribution

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.

Note: I upgraded BIOS to latest version (1.18) but still no luck. OpenGL (DRI?) hardlocks after hibernate.

Kernel modules: drm, savage

xorg.conf: load glx and dri modules

glxgears gives around ~500 fps.

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.

With kernel 2.6.17.1 savagefb works fine after resuming from suspend or hibernate. You might need to change your virtual terminal once to get it back to life.

ThinkPads this chip may be found in