If you haven't already got a kernel with ACPI support, you have to enable it in
the kernel setup and then recompile the new kernel. You'll find the
ACPI-options under <menuchoice><guimenu>General Setup</guimenu><guimenu>Power Management Setup</guimenu><guimenuitem>ACPI</guimenuitem></menuchoice>. You must have at least the following options: <guimenuitem>ACPI Bus Manager</guimenuitem>, <guimenuitem>System</guimenuitem> and <guimenuitem>Processor.</guimenuitem>
Or for the new 2.4.22 Kernel: <menuchoice><guimenu>General Setup</guimenu><guimenu>ACPI Support</guimenu></menuchoice>. You must have at least the following option: <guimenuitem>Processor</guimenuitem>.
<para>2.6.x Kernel: <menuchoice><guimenu>Powermanagment options</guimenu><guimenu>ACPI</guimenu></menuchoice>. You must have at least the option <guimenuitem>Processor</guimenuitem> enabled. You shouldn't enable Thermal Zone !!
To use the command-line hack you normaly have to enable ACPI in the kernel, otherwise it is mentioned. No reboot is needed to enable the Powersaving. You could enable/disbale it from the command line with this commands:
Kernel Patch for 2.6.5</ulink> which supports all Via Chipsets up to the KT600 (thx to Sebastian Droege for porting it to 2.6.5 and adding the other Chipsets)</para>
Reboot, and at the kernel boot-prompt, enter the statement <userinput> amd_disconnect=yes </userinput>. This is because there are known bugs within the Athlon processor, which could cause problems on several boards. You should test the patch, and if it works, you can append the statement <userinput> amd_disconnect=yes </userinput> to the file <filename>/etc/lilo.conf</filename>.
</para>
</step>
</procedure>
</sect2>
<sect2id="lvcool">
<title>The LVCool Solution</title>
<para>
<emphasis>LVCool</emphasis> is a small port of the Windows programm
<ulinkurl="http://vcool.occludo.net/">
VCool</ulink>. It only supports the KT133/133A and KX133 chipset and
Ok ... you use one of the described powersaving possibilitys and you want to verify, whether
it works. Here are two ways to check it:
</para>
<para>
If you have temperature controlled Fan on your CPU-Heatsink, you could check for the noise level of the Fan to see whether it works or not. After a few idle minutes you give the CPU somthing to do.
<procedure>
<title>I normaly do it like this:</title>
<step>
get superuser (root)
</step>
<step>
<command>cd /usr/src/linux</command>
</step>
<step>
and give the computer something to do: <command>while true; do make clean; make bzImage; done</command>
</step>
</procedure>
After about 20 or 30 seconds you should notice that the noise of the fan is getting louder while the fan is getting faster. Don't forget to end the while-loop after some time ( a few minutes) with STRG-C.
The same procedure as above works also with a monitoring program for the cpu-temperature (like <ulinkurl="http://secure.netroedge.com/~lm78/">lm-sensors</ulink>, <ulinkurl="http://www.nt.phys.kyushu-u.ac.jp/shimizu/download/download.html">xmbmon</ulink> and <ulinkurl="http://perso.wanadoo.es/com.ea/rtsensors/">rtsensors</ulink>).
<para>There are two known bugs in the Athlon/Duron processor. This is number
11 and number 14 in the <citetitle>AMD Athlon Processor Revision Guide</citetitle>. It looks like the Athlon XP is significantly less often affected by these bugs. So if you have an Athlon XP you are on the lucky side (like me).</para>
<para>There could be following problems (caused by the bugs):
<itemizedlist>
<listitem>
<para>skips during sound playback</para>
</listitem>
<listitem>
<para>skips and slowdown during video playback</para>
</listitem>
<listitem>
<para>slowdown of the ultra-DMA harddisk transfers</para>
<para>Sometimes a BIOS-update will help (it exists as a workaround for
bug 11, which could be done by the BIOS). But as far as I know there are
only a few boards out there which have this workaround in the BIOS.</para>
<para>For the Asus A7V133-C, it is known that the BIOS-option <option>PCI master read caching</option> will solve most problems when it is enabled. So look
at your BIOS to see whether it has such functionality.</para>
<para>It is also known that on some boards, the BIOS option <option>Delayed Transaction</option> solves some of the problems. You may want to give this option a try too.</para>
<para>WARNING: On boards with KT133A, this could enable the famous VIA-Southbridge bug!</para>
<para>From a Newsnet post, regarding Asus A7V:
<itemizedlist>
<listitem>
<para>without delayed transaction: sound-skips and TV-skips</para>
</listitem>
<listitem>
<para>with delayed transaction: no sound skips and only slight TV problems</para>
</listitem>
<listitem>
<para>with delayed transcation and master read caching: nearly no TV problems and no sound skips at all</para>
</listitem>
</itemizedlist>
</para>
<para>There are other causes for problems:
<itemizedlist>
<listitem>
<para>the PSU is not strong enough to handle the fluctuations in the power consumption of the processor/motherboard</para>
</listitem>
<listitem>
<para>some motherboard voltage-regulators could have the same problems like the PSU ;)</para>
<para>The working of this Fix was confirmed by two People, so it looks like it works, but it may not work for everyone. Please feel free to submit further experiances!</para>
<para>Lets go: It looks like at least the sound skips are cureable by maximizing the pci latency timer of the device.</para>
<para>First you have to find the "pci-address" of your Soundcard. This could be done with <command>lspci</command>. You have to look for something like "Multimedia audio controller" or "AudioPCI". Take the "pci-address" of the device (looks like shomething like that: 01:06.0 -> it stands for: bus:slot.function) and maximize the latency timer for it. This is done by setpci:</para>
<para>For additional Information on the Latency Timer you could look <ulinkurl="http://www-106.ibm.com/developerworks/linux/library/l-hw2.html">here.</ulink></para>
<para>Maybe this works also for other Problems like USB-Problems and Harddisk-Transfer-Slowdowns, but this hasn't been tested for now. Feel free to test it (but don't blame me, if it doesn't work or makes everything worse) and report whether it works. The Problem is, that i have none of this Problems and so can't test this by myself.</para>
<para>If it works, you have to perform this setpci command at every startup/reboot of the Computer. So it would be wise to put it in one of the init-scripts (after the driver module is loaded!).</para>
<title>Another Fix for sound skips and other problems (on some Via-Chipsets)</title>
<para>Thank you to Wijatmoko Prayitno for submitting this!</para>
<para>The working of this Fix was confirmed only for KT/KM333 and KT/KM400 Chipsets. It may also work for other Via-Chipsets. Please report if it works on other Via-Chipsets !</para>
<para>This is quite easy and works like the Commandline-Hack for enabling the Powersaving:</para>
<variablelist>
<varlistentry>
<term>Soundfix on KT/KM333 and KT/KM400 Chipsets:</term>
<para>If it works, you have to perform this setpci command at every startup/reboot of the Computer. So it would be wise to put it in one of the init-scripts (after the driver module is loaded!).</para>