ThinkWiki - User contributions [en]

S3 Savage IX8

2009-02-24T19:51:51Z

Mcfrisk: /* Blank screen */ T20

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== S3 Savage IX8 or IX8+===
This is a S3 video adapter<br>
S3 is now owned by Via Technologies

The IX8 and IX8+ chips share the same PCI-ID

=== Features ===
* Chipset: S3
* PCI ID: 5333:8c12
* AGP 2X
* 8MB SGRAM video memory
</div>
|style="vertical-align:top" |
|}

=== 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. The driver does not appear
to support [[DPMS]] on the internal LCD, so it is necessary to make sure that horizontal sync and vertical refresh settings are included in the "Monitor" section of xorg.conf.

HorizSync 31.5 - 48.5
VertRefresh 50-70

==== External VGA port ====
Works. {{key|Fn}}-{{Key|F7}} switches between LCD and CRT. To use both, use [http://www.probo.com/timr/savage40.html 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 {{path|/proc/acpi/ibm/video}}.

==== SVideo port ====
Works. Use [http://www.probo.com/timr/savage40.html 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.

==== 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.<br />
The 800x600 boot-text problem can be resolved by altering the savagefb.c (pre-2.6.20) or savagefb_driver.c (2.6.20 and later) and then recompiling the Kernel or the respective module. To do that, open the savagefb_driver.c, for example under ''<Kernel Root>/drivers/video/savage'' in the 2.6.20 release. Now, locate the following function:
<pre>static struct fb_var_screeninfo __devinitdata savagefb_var800x600x8 = {
.accel_flags = FB_ACCELF_TEXT,
.xres = 800,
.yres = 600,
.xres_virtual = 800,
.yres_virtual = 600,
.bits_per_pixel = 8,
.pixclock = 25000,
.left_margin = 88,
.right_margin = 40,
.upper_margin = 23,
.lower_margin = 1,
.hsync_len = 128,
.vsync_len = 4,
.sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
.vmode = FB_VMODE_NONINTERLACED
};</pre>

Alter the lines ''.xres'', ''.yres'', ''.xres_virtual'' and ''.yres_virtual'' to reflect your chosen resolution. Recompile and reinstall the Kernel, reboot or reload the module and the savagefb should use the new resolution.

==== 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"

On Debian based systems you need the package '''libgl1-mesa-dri''' to enable 3d acceleration. Deborphan may decide it is just a futile library, but that is false.

==== Blank screen ====

Symptoms:

* X starts but nothing shows up on screen, hard drive led shows normal activity up to login
* /etc/init.d/xorg.conf does not exist, so X.org is using autoconfiguration which fails
* /var/log/Xorg.0.log does not show any relevant errors or warnings

This happened on a T20 running Debian Etch and Lenny.

Workaround is to add DmaType and BusType as "PCI" in /etc/X11/xorg.conf:

Section "Device"
Identifier "S3 Inc. 86C270-294 Savage/IX-MV"
Driver "savage"
BusID "PCI:1:0:0"
Option "DmaType" "PCI"
Option "BusType" "PCI"
EndSection

=== ThinkPads this chip may be found in ===
* {{A22e}}
* {{T20}}, {{T21}}, {{T22}}

[[Category:Components]]

S3 Savage IX8

2009-02-24T19:41:38Z

Mcfrisk: /* Blank screen */ no errors in log

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== S3 Savage IX8 or IX8+===
This is a S3 video adapter<br>
S3 is now owned by Via Technologies

The IX8 and IX8+ chips share the same PCI-ID

=== Features ===
* Chipset: S3
* PCI ID: 5333:8c12
* AGP 2X
* 8MB SGRAM video memory
</div>
|style="vertical-align:top" |
|}

=== 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. The driver does not appear
to support [[DPMS]] on the internal LCD, so it is necessary to make sure that horizontal sync and vertical refresh settings are included in the "Monitor" section of xorg.conf.

HorizSync 31.5 - 48.5
VertRefresh 50-70

==== External VGA port ====
Works. {{key|Fn}}-{{Key|F7}} switches between LCD and CRT. To use both, use [http://www.probo.com/timr/savage40.html 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 {{path|/proc/acpi/ibm/video}}.

==== SVideo port ====
Works. Use [http://www.probo.com/timr/savage40.html 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.

==== 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.<br />
The 800x600 boot-text problem can be resolved by altering the savagefb.c (pre-2.6.20) or savagefb_driver.c (2.6.20 and later) and then recompiling the Kernel or the respective module. To do that, open the savagefb_driver.c, for example under ''<Kernel Root>/drivers/video/savage'' in the 2.6.20 release. Now, locate the following function:
<pre>static struct fb_var_screeninfo __devinitdata savagefb_var800x600x8 = {
.accel_flags = FB_ACCELF_TEXT,
.xres = 800,
.yres = 600,
.xres_virtual = 800,
.yres_virtual = 600,
.bits_per_pixel = 8,
.pixclock = 25000,
.left_margin = 88,
.right_margin = 40,
.upper_margin = 23,
.lower_margin = 1,
.hsync_len = 128,
.vsync_len = 4,
.sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
.vmode = FB_VMODE_NONINTERLACED
};</pre>

Alter the lines ''.xres'', ''.yres'', ''.xres_virtual'' and ''.yres_virtual'' to reflect your chosen resolution. Recompile and reinstall the Kernel, reboot or reload the module and the savagefb should use the new resolution.

==== 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"

On Debian based systems you need the package '''libgl1-mesa-dri''' to enable 3d acceleration. Deborphan may decide it is just a futile library, but that is false.

==== Blank screen ====

Symptoms:

* X starts but nothing shows up on screen, hard drive led shows normal activity up to login
* /etc/init.d/xorg.conf does not exist, so X.org is using autoconfiguration which fails
* /var/log/Xorg.0.log does not show any relevant errors or warnings

This happens on Debian Etch and Lenny.

Workaround is to add DmaType and BusType as "PCI" in /etc/X11/xorg.conf:

Section "Device"
Identifier "S3 Inc. 86C270-294 Savage/IX-MV"
Driver "savage"
BusID "PCI:1:0:0"
Option "DmaType" "PCI"
Option "BusType" "PCI"
EndSection

=== ThinkPads this chip may be found in ===
* {{A22e}}
* {{T20}}, {{T21}}, {{T22}}

[[Category:Components]]

S3 Savage IX8

2009-02-24T19:33:47Z

Mcfrisk: /* Quirks */ blank screen

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== S3 Savage IX8 or IX8+===
This is a S3 video adapter<br>
S3 is now owned by Via Technologies

The IX8 and IX8+ chips share the same PCI-ID

=== Features ===
* Chipset: S3
* PCI ID: 5333:8c12
* AGP 2X
* 8MB SGRAM video memory
</div>
|style="vertical-align:top" |
|}

=== 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. The driver does not appear
to support [[DPMS]] on the internal LCD, so it is necessary to make sure that horizontal sync and vertical refresh settings are included in the "Monitor" section of xorg.conf.

HorizSync 31.5 - 48.5
VertRefresh 50-70

==== External VGA port ====
Works. {{key|Fn}}-{{Key|F7}} switches between LCD and CRT. To use both, use [http://www.probo.com/timr/savage40.html 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 {{path|/proc/acpi/ibm/video}}.

==== SVideo port ====
Works. Use [http://www.probo.com/timr/savage40.html 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.

==== 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.<br />
The 800x600 boot-text problem can be resolved by altering the savagefb.c (pre-2.6.20) or savagefb_driver.c (2.6.20 and later) and then recompiling the Kernel or the respective module. To do that, open the savagefb_driver.c, for example under ''<Kernel Root>/drivers/video/savage'' in the 2.6.20 release. Now, locate the following function:
<pre>static struct fb_var_screeninfo __devinitdata savagefb_var800x600x8 = {
.accel_flags = FB_ACCELF_TEXT,
.xres = 800,
.yres = 600,
.xres_virtual = 800,
.yres_virtual = 600,
.bits_per_pixel = 8,
.pixclock = 25000,
.left_margin = 88,
.right_margin = 40,
.upper_margin = 23,
.lower_margin = 1,
.hsync_len = 128,
.vsync_len = 4,
.sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
.vmode = FB_VMODE_NONINTERLACED
};</pre>

Alter the lines ''.xres'', ''.yres'', ''.xres_virtual'' and ''.yres_virtual'' to reflect your chosen resolution. Recompile and reinstall the Kernel, reboot or reload the module and the savagefb should use the new resolution.

==== 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"

On Debian based systems you need the package '''libgl1-mesa-dri''' to enable 3d acceleration. Deborphan may decide it is just a futile library, but that is false.

==== Blank screen ====

Symptoms:

* X starts but nothing shows up on screen, hard drive led shows normal activity up to login
* /etc/init.d/xorg.conf does not exist, so X.org is using autoconfiguration which fails

This happens on Debian Etch and Lenny.

Workaround is to add DmaType and BusType as "PCI" in /etc/X11/xorg.conf:

Section "Device"
Identifier "S3 Inc. 86C270-294 Savage/IX-MV"
Driver "savage"
BusID "PCI:1:0:0"
Option "DmaType" "PCI"
Option "BusType" "PCI"
EndSection

=== ThinkPads this chip may be found in ===
* {{A22e}}
* {{T20}}, {{T21}}, {{T22}}

[[Category:Components]]

CS4239

2009-01-15T00:41:04Z

Mcfrisk: /* Linux ALSA driver */ note about debian etch kernels

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== CS4239 ===
This is a Cirrus Logic Audio controller

Note: This sound adapter is paired with a PCI [[CS4610]] audio controller.

=== Features ===
* Chipset: CS4239
* Interface: ISA 16bit
</div>
|style="vertical-align:top" |
|}

=== Linux OSS driver ===
This sound chip is supported by the cs4232 kernel module. Use the following options line when loading this module:

options cs4232 io=0x530 irq=5 dma=1 dma2=0

or try this from the Commandline:

''' modprobe cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=7 synthio=0x330 synthirq=7'''

''=> Dont forget to disable QUICKBOOT in the BIOS and dont INITIALIZE !''

=== Linux ALSA driver ===
This sound chip is supported by the snd-cs4236 kernel module. Use the following options line when loading this module:

options snd-cs4236 index=0 port=0x530 cport=0x538 isapnp=0 dma1=1 dma2=0 irq=5

On at least one 600E, the only options that would work definitively are:

options snd-cs4236 port=0x530 cport=0x538 isapnp=0 dma1=1 dma2=2 irq=5

One 600E running Debian Etch with vanilla 2.6.28 kernel failed to produce sound with snd-cs4236, but the sound works with driver snd-cs4232 loaded. Instructions for Ubuntu suggest to blacklist this driver which in this case was wrong. With standard Debian etch and etchnhalf kernels the snd-cs4236 did not work and snd-cs4232 got stuck on device initialisation or crashed the kernel. Working set of ALSA modules for this 600E on 2.6.28 is:

# lsmod|grep snd
snd_cs4232 11764 1
snd_opl3_lib 8928 1 snd_cs4232
snd_hwdep 6084 1 snd_opl3_lib
snd_wss_lib 22400 1 snd_cs4232
snd_pcm 60072 2 snd_wss_lib
snd_timer 16708 3 snd_opl3_lib,snd_wss_lib,snd_pcm
snd_page_alloc 8008 2 snd_wss_lib,snd_pcm
snd_mpu401_uart 5824 1 snd_cs4232
snd_rawmidi 17728 1 snd_mpu401_uart
snd_seq_device 6284 2 snd_opl3_lib,snd_rawmidi
snd 44580 10 snd_cs4232,snd_opl3_lib,snd_hwdep,snd_wss_lib,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 6016 1 snd

=== PnP issues ===
This chip is software configurable. In Thinkpads, the BIOS sets up the chip if fast boot is disabled. If fast boot is enabled, the chip is disabled until a PnP driver enables it. As both the OSS and the ALSA module do not support PnP discovering of this chips in a ThinkPad, a configuration script like [[Script for configuring the CS4239 sound chip in PnP mode|this one]] may be used. See also [[Problem with broken sound on some ThinkPads|this page]] for more information.

=== ThinkPads this chip may be found in ===
* {{600E}}
* {{770X}}, {{770Z}}

=== Mixer ===
I loaded the cs4242 module and on my Gnome Desktop (Ubuntu) and the sound work, but was too low when I play music and with the mixer of Gnome was not possible to modify the volume. I fixed the problem installing the mixer of KDE (kmix) and I use PCM to modify the volume.

[[Category:Components]]

CS4239

2009-01-14T23:06:46Z

Mcfrisk: /* Linux ALSA driver */ working alsa driver for 600E was snd_cs4232

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== CS4239 ===
This is a Cirrus Logic Audio controller

Note: This sound adapter is paired with a PCI [[CS4610]] audio controller.

=== Features ===
* Chipset: CS4239
* Interface: ISA 16bit
</div>
|style="vertical-align:top" |
|}

=== Linux OSS driver ===
This sound chip is supported by the cs4232 kernel module. Use the following options line when loading this module:

options cs4232 io=0x530 irq=5 dma=1 dma2=0

or try this from the Commandline:

''' modprobe cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=7 synthio=0x330 synthirq=7'''

''=> Dont forget to disable QUICKBOOT in the BIOS and dont INITIALIZE !''

=== Linux ALSA driver ===
This sound chip is supported by the snd-cs4236 kernel module. Use the following options line when loading this module:

options snd-cs4236 index=0 port=0x530 cport=0x538 isapnp=0 dma1=1 dma2=0 irq=5

On at least one 600E, the only options that would work definitively are:

options snd-cs4236 port=0x530 cport=0x538 isapnp=0 dma1=1 dma2=2 irq=5

One 600E running Debian Etch with vanilla 2.6.28 kernel failed to produce sound with snd-cs4236, but the sound works with driver snd-cs4232 loaded. Note that instructions for Ubuntu suggest to blacklist this driver which in this case was wrong. Working set of ALSA modules for this 600E is:

# lsmod|grep snd
snd_cs4232 11764 1
snd_opl3_lib 8928 1 snd_cs4232
snd_hwdep 6084 1 snd_opl3_lib
snd_wss_lib 22400 1 snd_cs4232
snd_pcm 60072 2 snd_wss_lib
snd_timer 16708 3 snd_opl3_lib,snd_wss_lib,snd_pcm
snd_page_alloc 8008 2 snd_wss_lib,snd_pcm
snd_mpu401_uart 5824 1 snd_cs4232
snd_rawmidi 17728 1 snd_mpu401_uart
snd_seq_device 6284 2 snd_opl3_lib,snd_rawmidi
snd 44580 10 snd_cs4232,snd_opl3_lib,snd_hwdep,snd_wss_lib,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 6016 1 snd

=== PnP issues ===
This chip is software configurable. In Thinkpads, the BIOS sets up the chip if fast boot is disabled. If fast boot is enabled, the chip is disabled until a PnP driver enables it. As both the OSS and the ALSA module do not support PnP discovering of this chips in a ThinkPad, a configuration script like [[Script for configuring the CS4239 sound chip in PnP mode|this one]] may be used. See also [[Problem with broken sound on some ThinkPads|this page]] for more information.

=== ThinkPads this chip may be found in ===
* {{600E}}
* {{770X}}, {{770Z}}

=== Mixer ===
I loaded the cs4242 module and on my Gnome Desktop (Ubuntu) and the sound work, but was too low when I play music and with the mixer of Gnome was not possible to modify the volume. I fixed the problem installing the mixer of KDE (kmix) and I use PCM to modify the volume.

[[Category:Components]]