diff --git a/LDP/howto/docbook/ACPI-HOWTO.xml b/LDP/howto/docbook/ACPI-HOWTO.xml index 26d71c47..0f1b9f37 100644 --- a/LDP/howto/docbook/ACPI-HOWTO.xml +++ b/LDP/howto/docbook/ACPI-HOWTO.xml @@ -31,7 +31,7 @@ custom kernels with Debian's kernel-package system ]> -
+
ACPI: Advanced Configuration and Power Interface @@ -87,10 +87,9 @@ custom kernels with Debian's kernel-package system 2003-06-12 - - + About this document When I first started the switch from APM to ACPI I didn't realize the kernel needed to be patched. My problem (insanely loud fan) was fixed just @@ -120,7 +119,7 @@ of doing things. There is also generic information in the - + About ACPI In the world of power management ACPI is relatively new to the game. @@ -174,7 +173,7 @@ url="http://tuxmobil.org/Mobile-Guide.db/mobile-guide-p2c1-hardware-in-detail.ht Mobile Guide. - + Why switch? Not all systems support both APM and ACPI. I switched because my system only supported ACPI. Pretty easy decision really. If you're switching @@ -190,7 +189,7 @@ the list if you've installed ACPI! They also have a list of machines that are not supported. - + DSDT: Differentiated System Description Table Thanks to Erich writing this section. @@ -210,7 +209,7 @@ This override is quite easy: instead of loading the DSDT table from bios, the kernel uses the compiled-in DSDT table. That's all. - + Installing from scratch ACPI is constantly being revised. It is currently not available in the 2.4.x series kernels but will be released into the @@ -286,7 +285,7 @@ with them. Please don't email me asking about them, ask maxx instead. - + Backups If you are already running a kernel that is the same version of the one you are about to patch I recommend creating a fresh @@ -304,7 +303,7 @@ directory for the newly patched kernel. Remember that backups are - + Required packages Since I was starting on a brand new machine, I'm pretty sure I have the full list of required packages to make this whole patch go smoothly. Here's @@ -320,7 +319,7 @@ the list all in one go: - + Download and patch Download a fresh kernel from www.kernel.org. You need to make sure you @@ -454,7 +453,7 @@ look for the absence of errors.) - + Configure the new kernel Now instead of using make menuconfig, I have a godsend of an option. Check this out: copy your current .config file into @@ -511,7 +510,7 @@ and make sure you have your APM (the old stuff) turned off. Under exit and save the new configuration - + Compile the new kernel If you have additional modules that are not part of the main source tree, you will need to add modules_image when you make your Debian @@ -552,7 +551,7 @@ still think it's a good way to do things. &kernel-compile; - + Install the new kernel I like to configure lilo on my own, but do whatever tickles your fancy. @@ -589,7 +588,7 @@ still think it's a good way to do things. &kernel-compile; - + Reboot and test At this point you should reboot your machine. When your system comes back up (assuming of course that everything went well and you still have a @@ -620,7 +619,7 @@ says that S3 is a supported state, but we already know it's not. It does give the correct version though, which is useful. - + Load related modules If you compiled ACPI support in as "M"odules you'll probably need to load the modules by hand. You'll need to hunt around a bit to see what @@ -689,7 +688,7 @@ file just create a new one and add each module name (remember, no dot-o) on a separate line. - + Switching from APM to ACPI Don't let apmd and acpid run at the same time unless you REALLY know what you're doing. Debian will not make sure only one is running @@ -714,11 +713,9 @@ two things: the line under Section "Monitor". - - - + Using ACPI There are a few different applications/daemons you will want to install on your system: acpid (the daemon that will control your hardware states), and acpi (the interface to monitor events and states) are the base install. The @@ -1057,7 +1054,7 @@ generally getting ACPI up and running. - + Thanks Much thanks goes out to the following: @@ -1102,7 +1099,7 @@ enthusiastic about learning DocBook There is very little difference between The Debian Way and the generic way. In fact it's probably only 10 or so lines of difference. - + Compile the kernel The normal way of compiling a kernel does not use make-kpkg. Instead, it uses the following steps: @@ -1133,7 +1130,7 @@ generic way. In fact it's probably only 10 or so lines of difference. - + Install the new kernel In The Debian Way, you create a deb file which contains information about where the kernel is (and makes the kernel and yada-yada). In the normal way, you put things where they need to be right away. You need to install your modules and then configure lilo to point to the new kernel and then run lilo. If you are not doing things The Debian Way your install will look like this: @@ -1175,7 +1172,7 @@ lilo. If you are not doing things The Debian Way your - + Software packages You can still use all of the software mentioned in this HOWTO even if you're not using Debian. Unfortunately it will take a little more effort on