Difference between revisions of "S3 Savage IX8"
(→Linux X.Org driver) |
(Cleanup and Information about 3D acceleration) |
||
| Line 19: | Line 19: | ||
=== 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. |
==== ThinkPad LCD ==== | ==== ThinkPad LCD ==== | ||
| Line 31: | Line 31: | ||
=== 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. |
| + | === Tips === | ||
| + | ==== Console Resolution Tip ==== | ||
To get nice 1400x1050 (some models have such displays) resolution in console try adding: <tt>vga=0x33c video=vesa:ywrap,mtrr</tt> to your kernel parameters (in your bootloader config). | To get nice 1400x1050 (some models have such displays) resolution in console try adding: <tt>vga=0x33c video=vesa:ywrap,mtrr</tt> to your kernel parameters (in your bootloader config). | ||
| − | === Dual Monitor | + | ==== Dual Monitor Tip ==== |
| − | |||
The chip supports using an external monitor plus the LCD as one big monitor. This can lead to a problem | The chip supports using an external monitor plus the LCD as one big monitor. This can lead to a problem | ||
if X is configured for this, but the external monitor has been detached. This creates a ghost monitor that you | if X is configured for this, but the external monitor has been detached. This creates a ghost monitor that you | ||
| Line 47: | Line 48: | ||
screen, even though you can't see it directly. | screen, even though you can't see it directly. | ||
| + | === Quirks === | ||
| + | ==== Power Management and savagefb ==== | ||
| + | The savagefb appears to interfere with acpi sleep. (tested on 2.6 kernels up to 2.6.12) There are also some display problems with savagefb including limiting boot text to a 800x600 window centered in a 1024x768 display and problems with libdirectfb. For those reasons, vesafb is recommended as the framebuffer driver. | ||
| + | |||
| + | ==== Video-related System Lockups ==== | ||
| + | Some quirks in the interactions between the OS and the Savage hardware can cause system lockups, especially due to high video load and 3D rendering operations. For a more complete description of this problem and the workarounds, see the [[Problem with video related system lockup]] page. | ||
| + | |||
| + | ==== The Black 'X' (old X pointer) Problem ==== | ||
| + | On some systems a black 'X' (which is actually the old default XFree86 pointer) appears frozen in the middle of the screen inside of X Windows. This problem can be remedied by setting | ||
| + | |||
| + | Option "SWCursor" "on" | ||
| + | |||
| + | in xorg.conf. Also see the [[Problem with black X]] page for more information. | ||
| + | |||
| + | ==== 3D Acceleration Quirks ==== | ||
| + | If 3D acceleration is not working on your system (after installing the DRM savage module), or 3D programs are exhibiting strange behavior, one of the following changes may fix the problem. First, most Savage chips do not have enough video memory to support 3D textures and acceleration with a frame buffer depth of 24 bits. Therefore, you may need to change "DefaultDepth 24" to "DefaultDepth 16" in the "Screen" section of xorg.conf (and of course provide the appropriate subsection for 16 bit depth if it is not present). Also, adding one of both of the following configuration options to the "Device" section of your xorg.conf may solve the video quirks (also explained in the [[Problem with video related system lockup|video related system lockup]] page) | ||
| + | |||
| + | Option "BusType" "PCI" | ||
| + | Option "DmaMode" "None" | ||
=== ThinkPads this chip may be found in === | === ThinkPads this chip may be found in === | ||
Revision as of 15:45, 9 March 2006
S3 Savage IX8 or IX8+This is a S3 video adapter The IX8 and IX8+ chips share the same PCI-ID 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 correctly.
External VGA port
Works. Fn-F7 switches between LCD and CRT. To use both, use s3switch (on some models you need to run "s3switch lcd crt tv" even if you want only CRT and LCD, otherwise the CRT display is corrupted). You can also use ibm-acpi to control video output by echoing commands to /proc/acpi/ibm/video.
SVideo port
Works. Use s3switch to change display output in software.
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.
Tips
Console Resolution Tip
To get nice 1400x1050 (some models have such displays) resolution in console try adding: vga=0x33c video=vesa:ywrap,mtrr to your kernel parameters (in your bootloader config).
Dual Monitor Tip
The chip supports using an external monitor plus the LCD as one big monitor. This can lead to a problem if X is configured for this, but the external monitor has been detached. This creates a ghost monitor that you cannot see, but can move the mouse onto and applications can open windows on.
Sometimes in this situation it's necessary to grab a window from the ghost monitor and drag it into view. This can be done by moving the mouse onto the ghost screen and then holding down the ALT key, which allows you to click-and-drag a window back into view. To see what is on the ghost monitor, a screen capture utility like Ksnapshot can help you. When it takes a screenshot of the entire screen, it will show the contents of the ghost screen, even though you can't see it directly.
Quirks
Power Management and savagefb
The savagefb appears to interfere with acpi sleep. (tested on 2.6 kernels up to 2.6.12) There are also some display problems with savagefb including limiting boot text to a 800x600 window centered in a 1024x768 display and problems with libdirectfb. For those reasons, vesafb is recommended as the framebuffer driver.
Some quirks in the interactions between the OS and the Savage hardware can cause system lockups, especially due to high video load and 3D rendering operations. For a more complete description of this problem and the workarounds, see the Problem with video related system lockup page.
The Black 'X' (old X pointer) Problem
On some systems a black 'X' (which is actually the old default XFree86 pointer) appears frozen in the middle of the screen inside of X Windows. This problem can be remedied by setting
Option "SWCursor" "on"
in xorg.conf. Also see the Problem with black X page for more information.
3D Acceleration Quirks
If 3D acceleration is not working on your system (after installing the DRM savage module), or 3D programs are exhibiting strange behavior, one of the following changes may fix the problem. First, most Savage chips do not have enough video memory to support 3D textures and acceleration with a frame buffer depth of 24 bits. Therefore, you may need to change "DefaultDepth 24" to "DefaultDepth 16" in the "Screen" section of xorg.conf (and of course provide the appropriate subsection for 16 bit depth if it is not present). Also, adding one of both of the following configuration options to the "Device" section of your xorg.conf may solve the video quirks (also explained in the video related system lockup page)
Option "BusType" "PCI" Option "DmaMode" "None"
