<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.thinkwiki.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Wonko</id>
	<title>ThinkWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.thinkwiki.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Wonko"/>
	<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/wiki/Special:Contributions/Wonko"/>
	<updated>2026-05-23T10:49:19Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.12</generator>
	<entry>
		<id>https://www.thinkwiki.org/w/index.php?title=Problem_with_broken_sound_on_some_ThinkPads&amp;diff=33845</id>
		<title>Problem with broken sound on some ThinkPads</title>
		<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/w/index.php?title=Problem_with_broken_sound_on_some_ThinkPads&amp;diff=33845"/>
		<updated>2007-10-12T17:52:37Z</updated>

		<summary type="html">&lt;p&gt;Wonko: /* Affected Models */ had same problem on my x60s&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Information about the phenomena of broken sound on some ThinkPad models.&lt;br /&gt;
&lt;br /&gt;
==Problem description==&lt;br /&gt;
There are two sound chips in these machines, a PCI based [[CS4610|Crystal SoundFusion 4610]], and an ISA based [[CS4239|Crystal SoundFusion 4239]].&lt;br /&gt;
&lt;br /&gt;
The Linux drivers for the CS4610 (both OSS and ALSA) expect to find it paired with an AC'97 codec chip, while instead the CS4610 is paired with the ISA CS4239. This was done, because at the time this allowed DOS games to output sound using SoundBlaster Pro emulation.&lt;br /&gt;
&lt;br /&gt;
To get sound under Linux you will have to use the OSS cs4232 or ALSA snd-cs4236 driver for the ISA soundchip instead.&lt;br /&gt;
&lt;br /&gt;
A good thread on the problem can be found in the [http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg01181.html alsa-devel mailing list]&lt;br /&gt;
&lt;br /&gt;
There is also a separate issue with recent ALSA builds and the Intel AD1981-1984 chip.  [[http://www.linuxquestions.org/questions/showthread.php?p=2879174]]  This causes problems starting with alsa shipped with kernel 2.6.22.  Workarounds include manually updating ALSA or using your distributions version rather than the kernel version.  Also see [[AD1984]] for patches.&lt;br /&gt;
&lt;br /&gt;
==Affected Models==&lt;br /&gt;
*ThinkPad {{600E}}&lt;br /&gt;
*ThinkPad {{770X}}, {{770Z}}&lt;br /&gt;
*Thinkpad {{T43p}}, {{T60}}, {{T61}}&lt;br /&gt;
*ThinkPad {{x60s}}&lt;br /&gt;
&lt;br /&gt;
==Solutions==&lt;br /&gt;
===Activating the devices===&lt;br /&gt;
First you must make sure that the sound devices are activated.&lt;br /&gt;
&lt;br /&gt;
Disable &amp;quot;Quick Boot&amp;quot; in your ThinkPad BIOS, otherwise the sound devices will not be activated by the BIOS.&lt;br /&gt;
To enter the BIOS, power cycle your ThinkPad and press F1 when the ThinkPad screen shows.&lt;br /&gt;
&lt;br /&gt;
You can also manually activate the sound card once booted:&lt;br /&gt;
* With apm and pnpbios, this is done with setpnp from the pcmcia package:&lt;br /&gt;
:{{cmdroot|setpnp 0x0e on}}&lt;br /&gt;
:{{cmdroot|setpnp 0x0f on}}&lt;br /&gt;
&lt;br /&gt;
* With acpi and pnpacpi, use these commands:&lt;br /&gt;
:{{cmdroot|echo 'activate' &amp;gt; /sys/devices/pnp0/00:05/resources}}&lt;br /&gt;
:{{cmdroot|echo 'activate' &amp;gt; /sys/devices/pnp0/00:06/resources}}&lt;br /&gt;
&lt;br /&gt;
It seems that with very new kernels and ACPI enabled, you will need to manually enable the device even if you have correctly disabled &amp;quot;Quick Boot&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
This only works with newer kernels that fully support pnpacpi, and provided that [http://bugzilla.kernel.org/show_bug.cgi?id=3912 this patch] has been applied (applied to Linus' tree in july 2005).&lt;br /&gt;
&lt;br /&gt;
It seems that the default dma numbers change when pnpacpi is used (to dma1=1 dma2=3, for instance).&lt;br /&gt;
&lt;br /&gt;
If you're using acpi and pnpacpi, you can see which resources the sound card is using like this:&lt;br /&gt;
:{{cmdroot|cat /sys/devices/pnp0/00:05/resources}}&lt;br /&gt;
:{{cmdroot|cat /sys/devices/pnp0/00:06/resources}}&lt;br /&gt;
&lt;br /&gt;
===Using ALSA===&lt;br /&gt;
Compile the sound driver as a module and load it after everything else.&lt;br /&gt;
You can add the following line to a boot script, ie. {{path|rc.local}} for that:&lt;br /&gt;
 /sbin/modprobe snd-cs4236 index=0 port=0x530 cport=0x538 irq=5 dma1=1 dma2=0 isapnp=0&lt;br /&gt;
&lt;br /&gt;
This is reported to work at least with kernel 2.6.9, 2.6.13 and 2.6.15.&lt;br /&gt;
&lt;br /&gt;
On the 770x using kernel 2.6.16/2.6.17 you may try this:&lt;br /&gt;
 /sbin/modprobe snd-cs4232 port=0x530 cport=0x120 irq=5 dma1=1 dma2=0 isapnp=0&lt;br /&gt;
&lt;br /&gt;
There is a [[Script for configuring the CS4239 sound chip in PnP mode|nice script]] which can do all this for you, including activation of the device and detecting the correct resource settings to use.&lt;br /&gt;
&lt;br /&gt;
===Using OSS===&lt;br /&gt;
Add the following lines to a boot script, ie. {{path|rc.local}}:&lt;br /&gt;
 modprobe sound&lt;br /&gt;
 insmod ad1848&lt;br /&gt;
 insmod uart401&lt;br /&gt;
 insmod cs4232 io=0x530 irq=5 dma=1 dma2=0 &lt;br /&gt;
&lt;br /&gt;
or try from commandline: &lt;br /&gt;
 &lt;br /&gt;
 modprobe cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=7 synthio=0x330 synthirq=7 (parameter not necessarily)&lt;br /&gt;
&lt;br /&gt;
In case an insmod or modprobe of cs4232 fails with the following error appearing at the console, via dmesg, or in {{path|/var/log/messages}}, double-check you have ''QUICKBOOT (in the BIOS) disabled''.&lt;br /&gt;
 modprobe: FATAL: Error inserting cs4232: No such device&lt;br /&gt;
&lt;br /&gt;
====Audio loops====&lt;br /&gt;
If your OSS module loads like it should, but audio loops or sounds choppy then reloading the module should help:&lt;br /&gt;
:{{cmdroot|rmmod cs4232 &amp;amp;&amp;amp; modprobe cs4232}}&lt;br /&gt;
&lt;br /&gt;
(For the modprobe command to work without IRQ/IO/DMA parameters, you'll probably want to add the correct parameters as an &amp;quot;options&amp;quot; clause in {{path|/etc/modprobe.conf}}).&lt;/div&gt;</summary>
		<author><name>Wonko</name></author>
		
	</entry>
	<entry>
		<id>https://www.thinkwiki.org/w/index.php?title=Recovering_without_Recovery_CDs&amp;diff=32788</id>
		<title>Recovering without Recovery CDs</title>
		<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/w/index.php?title=Recovering_without_Recovery_CDs&amp;diff=32788"/>
		<updated>2007-08-31T07:56:24Z</updated>

		<summary type="html">&lt;p&gt;Wonko: /* Windows XP */  bumped into some problems with the ahci-mode when installing a fresh windows xp&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Information about recovering the preloaded OS without any Recovery CD.&lt;br /&gt;
&lt;br /&gt;
==Coverage of this approach==&lt;br /&gt;
You can't download preinstalled commercial applications from the IBM website (only updates are provided). Commercial software known to be preinstalled is CD/DVD burning and DVD playback software and Norton AntiVirus. On the other hand, this approach doesn't restore the original setup, but gives you a system with the lates drivers and tools from IBM, that might work even better than the originally installed one.&lt;br /&gt;
&lt;br /&gt;
==preinstalled Windows versions and their keys==&lt;br /&gt;
===Windows 98===&lt;br /&gt;
{{Todo|Windows 98 specific stuff}}&lt;br /&gt;
&lt;br /&gt;
===Windows ME===&lt;br /&gt;
{{Todo|Windows ME specific stuff}}&lt;br /&gt;
&lt;br /&gt;
===Windows 2000===&lt;br /&gt;
{{Todo|Windows 2000 specific stuff}}&lt;br /&gt;
&lt;br /&gt;
===Windows XP===&lt;br /&gt;
Preinstalled Windows XP versions usually have an OEM key that does not work with a boxed Windows XP. You will have to use the key that comes with the box instead.&lt;br /&gt;
Note: The Windows XP install-cd doesn't include drivers for the AHCI-mode of the S-ATA drive. Therefore, on the models using this by default, you should set the SATA Controller Mode Option (in the BIOS setup) to &amp;quot;Compatibility&amp;quot; before installing windows, OR before beginning the install, download the &amp;quot;Intel Matrix Storage Manager Driver&amp;quot; from Lenovo's support-site, copy these to a diskette to install by pressing F6 during the driver-loading of the windows install process (see the readme for more info).&lt;br /&gt;
&lt;br /&gt;
==Downloading Drivers==&lt;br /&gt;
Get drivers by entering your model into the appropriate fields on IBMs [http://www.ibm.com/products/finder/us/en/finders?pg=ddfinder Downloads and drivers] page.&lt;br /&gt;
&lt;br /&gt;
==Installing Drivers==&lt;br /&gt;
The easiest way to install drivers after the system installation is through the Software Installer. It is available from the Lenovo support pages. To use it, you will need to connect your freshly setup ThinkPad to the internet.&lt;br /&gt;
&lt;br /&gt;
So you should care about having any means of a network driver at hand for the Windows system you are installing on the ThinkPad. So, connect a second machine to the net and download the Software Installer and a network driver for your particular network card. Network drivers are available from the Lenovo support pages as well.&lt;br /&gt;
&lt;br /&gt;
Once you installed the Software Installer, run it and follow the process. It might happen that the Software Installer doesn't install all drivers available for your ThinkPad model. To make sure you have everything check IBMs [http://www.ibm.com/products/finder/us/en/finders?pg=ddfinder Downloads and drivers] page for your model.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==External Sources==&lt;br /&gt;
*[http://www.ibm.com/products/finder/us/en/finders?pg=ddfinder IBM Downloads and drivers]&lt;br /&gt;
*[http://www-307.ibm.com/pc/support/site.wss/DRVR-MATRIX.html IBM Windows Driver Matrix]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Windows]]&lt;/div&gt;</summary>
		<author><name>Wonko</name></author>
		
	</entry>
</feed>