path: root/doc/gettext/ru/power-management-guide.xml.po

msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2010-10-21 23:56+0600\n"
"PO-Revision-Date: 2010-10-21 23:46+0600\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):6
msgid "Power Management Guide"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):8
msgid "Author"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):9
msgid "earthwings@gentoo.org"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):9
msgid "Dennis Nienhüser"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):11
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):14
msgid "Editor"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):12
msgid "chriswhite@gentoo.org"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):12
msgid "Chris White"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):15
msgid "nightmorph"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(abstract):18
msgid ""
"Power Management is the key to extend battery run time on mobile systems "
"like laptops. This guide assists you setting it up on your laptop."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(version):27
msgid "1.47"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(date):28
msgid "2010-07-18"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):31
msgid "Introduction"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):35
msgid ""
"Capacity and lifetime of laptop batteries have improved much in the last "
"years. Nevertheless modern processors consume much more energy than older "
"ones and each laptop generation introduces more devices hungry for energy. "
"That's why Power Management is more important than ever. Increasing battery "
"run time doesn't necessarily mean buying another battery. Much can be "
"achieved applying intelligent Power Management policies."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):47
msgid "A Quick Overview"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):50
msgid ""
"Please notice that this guide describes Power Management for <e>laptops</e>. "
"While some sections might also suite for <e>servers</e>, others do not and "
"may even cause harm. Please do not apply anything from this guide to a "
"server unless you really know what you are doing."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):57
msgid ""
"As this guide has become rather long, here's a short overview helping you to "
"find your way through it."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):62
msgid ""
"The <uri link=\"#doc_chap2\">Prerequisites</uri> chapter talks about some "
"requirements that should be met before any of the following device "
"individual sections will work. This includes BIOS settings, kernel "
"configuration and some simplifications in user land. The following three "
"chapters focus on devices that typically consume most energy - processor, "
"display and hard drive. Each can be configured seperately. <uri link="
"\"#doc_chap3\">CPU Power Management</uri> shows how to adjust the "
"processor's frequency to save a maximum of energy without losing too much "
"performance. A few different tricks prevent your hard drive from working "
"unnecessarily often in <uri link=\"#doc_chap5\">Disk Power Management</uri> "
"(decreasing noise level as a nice side effect). Some notes on graphics "
"cards, Wireless LAN and USB finish the device section in <uri link="
"\"#doc_chap6\">Power Management For Other Devices</uri> while another "
"chapter is dedicated to the (rather experimental) <uri link="
"\"#doc_chap7\">sleep states</uri>. Last not least <uri link="
"\"#doc_chap8\">Troubleshooting</uri> lists common pitfalls."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):83
msgid "Power Budget For Each Component"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:link):87
msgid "/images/energy-budget.png"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:short):87
msgid "Which component consumes how much energy?"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:caption):87
msgid "Power budget for each component"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):89
msgid ""
"Nearly every component can operate in different states - off, sleep, idle, "
"active to name a few - consuming a different amount of energy. Major parts "
"are consumed by the LCD display, CPU, chipset and hard drives. Often one is "
"able to activate OS-independent Power Management in the BIOS, but an "
"intelligent setup in the operating system adapting to different situations "
"can achieve much more."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):102
msgid "Prerequisites"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):106
msgid ""
"Before discussing the details of making individual devices Power Management "
"aware, make sure certain requirements are met. After controlling BIOS "
"settings, some kernel options want to be enabled - these are in short ACPI, "
"sleep states and CPU frequency scaling. As power saving most of the time "
"comes along with performance loss or increased latency, it should only be "
"enabled when running on batteries. That's where a new runlevel <e>battery</"
"e> comes in handy."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):118
msgid "The BIOS Part"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):121
msgid ""
"First have a look into your BIOS Power Management settings. The best way is "
"to combine BIOS and operating system policies, but for the moment it's "
"better to disable most of the BIOS part. This makes sure it doesn't "
"interfere with your policies. Don't forget to re-check BIOS settings after "
"you configured everything else."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):132
msgid "Setting USE Flags"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):135
msgid ""
"Please check that the <c>acpi</c> USE flag is set in <path>/etc/make.conf</"
"path>. Other USE flags that might be interesting for your system are <c>apm</"
"c>, <c>lm_sensors</c>, <c>nforce2</c>, <c>nvidia</c>, <c>pmu</c>. See <path>/"
"usr/portage/profiles/use*.desc</path> for details. If you forgot to set one "
"of these flags, you can recompile affected packages using the <c>--newuse</"
"c> flag in <c>emerge</c>, see <c>man emerge</c>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):147
msgid "Configuring The Kernel"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):150
msgid ""
"ACPI (Advanced Configuration and Power Interface) support in the kernel is "
"still work in progress. Using a recent kernel will make sure you'll get the "
"most out of it."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):156
msgid ""
"There are different kernel sources in Portage. I'd recommend using <c>gentoo-"
"sources</c> or <c>tuxonice-sources</c>. The latter contains patches for "
"TuxOnIce, see the chapter about <uri link=\"#doc_chap7\">sleep states</uri> "
"for more details. When configuring the kernel, activate at least these "
"options:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):163
msgid "Minimum kernel setup for Power Management (Kernel 2.6)"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):163
#, no-wrap
msgid ""
"\n"
"Power management and ACPI options ---&gt;\n"
"[*] Power Management support\n"
"  [ ] Software Suspend\n"
"\n"
"  ACPI( Advanced Configuration and Power Interface ) Support ---&gt;\n"
"    [ ]   Deprecated /proc/acpi/ files\n"
"    [*]   AC Adapter\n"
"    [*]   Battery\n"
"    &lt;M&gt;   Button\n"
"    &lt;M&gt;   Video\n"
"    [ ]   Generic Hotkey\n"
"    &lt;M&gt;   Fan\n"
"    &lt;M&gt;   Processor\n"
"    &lt;M&gt;     Thermal Zone\n"
"    &lt; &gt;   ASUS/Medion Laptop Extras\n"
"    &lt; &gt;   IBM ThinkPad Laptop Extras\n"
"    &lt; &gt;   Toshiba Laptop Extras\n"
"    (0)   Disable ACPI for systems before Jan 1st this year\n"
"    [ ]   Debug Statements\n"
"    [*]   Power Management Timer Support\n"
"    &lt; &gt;   ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)\n"
"\n"
"  CPU Frequency Scaling ---&gt;\n"
"    [*] CPU Frequency scaling\n"
"    [ ]   Enable CPUfreq debugging\n"
"    &lt; &gt;   CPU frequency translation statistics\n"
"    [ ]     CPU frequency translation statistics details\n"
"          Default CPUFreq governor (userspace)\n"
"    &lt;*&gt;   'performance' governor\n"
"    &lt;*&gt;   'powersave' governor\n"
"    &lt;*&gt;   'ondemand' cpufreq policy governor\n"
"    &lt;*&gt;   'conservative' cpufreq governor\n"
"    &lt;*&gt;   CPU frequency table helpers\n"
"    &lt;M&gt; ACPI Processor P-States driver\n"
"    &lt;*&gt; <i>CPUFreq driver for your processor</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):201
msgid ""
"Decide yourself whether you want to enable Software Suspend, and Sleep "
"States (see below). If you own an ASUS, Medion, IBM Thinkpad or Toshiba "
"laptop, enable the appropriate section."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):207
msgid ""
"The kernel has to know how to enable CPU frequency scaling on your "
"processor. As each type of CPU has a different interface, you've got to "
"choose the right driver for your processor. Be careful here - enabling "
"<c>Intel Pentium 4 clock modulation</c> on a Pentium M system will lead to "
"strange results for example. Consult the kernel documentation if you're "
"unsure which one to take."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):215
msgid ""
"Compile your kernel, make sure the right modules get loaded at startup and "
"boot into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</"
"c> to get the acpi daemon. This one informs you about events like switching "
"from AC to battery or closing the lid. Make sure the modules are loaded if "
"you didn't compile them into the kernel and start acpid by executing <c>/etc/"
"init.d/acpid start</c>. Run <c>rc-update add acpid default</c> to load it on "
"startup. You'll soon see how to use it."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):225
msgid "Installing acpid"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):225
#, no-wrap
msgid ""
"\n"
"# <i>emerge sys-power/acpid</i>\n"
"# <i>/etc/init.d/acpid start</i>\n"
"# <i>rc-update add acpid default</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):234
msgid "Creating A \"battery\" Runlevel"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):237
msgid ""
"The default policy will be to enable Power Management only when needed - "
"running on batteries. To make the switch between AC and battery convenient, "
"create a runlevel <c>battery</c> that holds all the scripts starting and "
"stopping Power Management."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):244
msgid ""
"You can safely skip this section if you don't like the idea of having "
"another runlevel. However, skipping this step will make the rest a bit "
"trickier to set up. The next sections assume a runlevel <c>battery</c> "
"exists."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):250
msgid "Creating a battery runlevel"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):250
#, no-wrap
msgid ""
"\n"
"# <i>cd /etc/runlevels</i>\n"
"# <i>cp -a default battery</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):255
msgid ""
"Finished. Your new runlevel <c>battery</c> contains everything like "
"<c>default</c>, but there is no automatic switch between both yet. Time to "
"change it."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):264
msgid "Reacting On ACPI Events"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):267
msgid ""
"Typical ACPI events are closing the lid, changing the power source or "
"pressing the sleep button. An important event is changing the power source, "
"which should cause a runlevel switch. A small script will take care of it."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):273
msgid ""
"First you need a script which changes the runlevel to <c>default</c> "
"respectively <c>battery</c> depending on the power source. The script uses "
"the <c>on_ac_power</c> command from <c>sys-power/pm-utils</c> - make sure "
"the package is installed on your system."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):280
msgid "Installing pm-utils"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):280
#, no-wrap
msgid ""
"\n"
"# <i>emerge pm-utils</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):284
msgid ""
"You are now able to determine the power source by executing <c>on_ac_power "
"&amp;&amp; echo AC available || echo Running on batteries</c> in a shell. "
"The script below is responsible for changing runlevels. Save it as <path>/"
"etc/acpi/actions/pmg_switch_runlevel.sh</path>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):291
msgid "/etc/acpi/actions/pmg_switch_runlevel.sh"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):291
#, no-wrap
msgid ""
"\n"
"#!/bin/bash\n"
"\n"
"<comment># BEGIN configuration</comment>\n"
"RUNLEVEL_AC=\"default\"\n"
"RUNLEVEL_BATTERY=\"battery\"\n"
"<comment># END configuration</comment>\n"
"\n"
"\n"
"if [ ! -d \"/etc/runlevels/${RUNLEVEL_AC}\" ]\n"
"then\n"
"    logger \"${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting.\"\n"
"    exit 1\n"
"fi\n"
"\n"
"if [ ! -d \"/etc/runlevels/${RUNLEVEL_BATTERY}\" ]\n"
"then\n"
"    logger \"${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting.\"\n"
"    exit 1\n"
"fi\n"
"\n"
"if on_ac_power\n"
"then\n"
"    if [[ \"$(&lt;/var/lib/init.d/softlevel)\" != \"${RUNLEVEL_AC}\" ]]\n"
"    then\n"
"        logger \"Switching to ${RUNLEVEL_AC} runlevel\"\n"
"         /sbin/rc ${RUNLEVEL_AC}\n"
"    fi\n"
"elif [[ \"$(&lt;/var/lib/init.d/softlevel)\" != \"${RUNLEVEL_BATTERY}\" ]]\n"
"then\n"
"    logger \"Switching to ${RUNLEVEL_BATTERY} runlevel\"\n"
"    /sbin/rc ${RUNLEVEL_BATTERY}\n"
"fi\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):326
msgid ""
"Dont forget to run <c>chmod +x /etc/acpi/actions/pmg_switch_runlevel.sh</c> "
"to make the script executable. The last thing that needs to be done is "
"calling the script whenever the power source changes. That's done by "
"catching ACPI events with the help of <c>acpid</c>. First you need to know "
"which events are generated when the power source changes. The events are "
"called <c>ac_adapter</c> and <c>battery</c> on most laptops, but it might be "
"different on yours."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):336
msgid "Determining ACPI events for changing the power source"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):336
#, no-wrap
msgid ""
"\n"
"# <i>tail -f /var/log/messages | grep \"ACPI event\"</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):340
msgid ""
"Run the command above and pull the power cable. You should see something "
"like this:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):345
msgid "Sample output for power source changes"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):345
#, no-wrap
msgid ""
"\n"
"[Tue Sep 20 17:39:06 2005] ACPI event \"ac_adapter AC 00000080 00000000\"\n"
"[Tue Sep 20 17:39:06 2005] ACPI event \"battery BAT0 00000080 00000001\"\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):350
msgid ""
"The interesting part is the quoted string after <c>ACPI event</c>. It will "
"be matched by the event line in the files you are going to create below. "
"Don't worry if your system generates multiple events or always the same. As "
"long as any event is generated, runlevel changing will work."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):357
msgid "/etc/acpi/events/pmg_ac_adapter"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):357
#, no-wrap
msgid ""
"\n"
"<comment># replace \"ac_adapter\" below with the event generated on your laptop</comment>\n"
"<comment># For example, ac_adapter.* will match ac_adapter AC 00000080 00000000</comment>\n"
"event=ac_adapter.*\n"
"action=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):364
msgid "/etc/acpi/events/pmg_battery"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):364
#, no-wrap
msgid ""
"\n"
"<comment># replace \"battery\" below with the event generated on your laptop</comment>\n"
"<comment># For example, battery.* will match battery BAT0 00000080 00000001</comment>\n"
"event=battery.*\n"
"action=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):371
msgid "Finally acpid has to be restarted to recognize the changes."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):375
msgid "Finishing runlevel switching with acpid"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):375
#, no-wrap
msgid ""
"\n"
"# <i>/etc/init.d/acpid restart</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):379
msgid ""
"Give it a try: Plug AC in and out and watch syslog for the \"Switching to AC "
"mode\" or \"Switching to battery mode\" messages. See the <uri link="
"\"#doc_chap8\">Troubleshooting section</uri> if the script is not able to "
"detect the power source correctly."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):386
msgid ""
"Due to the nature of the event mechanism, your laptop will boot into "
"runlevel <c>default</c> regardless of the AC/battery state. This is fine "
"when running from AC, but we'd like to boot into the battery runlevel "
"otherwise. One solution would be to add another entry to the boot loader "
"with the parameter <c>softlevel=battery</c>, but it's likely to forget "
"choosing it. A better way is faking an ACPI event in the end of the boot "
"process and letting <path>pmg_switch_runlevel.sh</path> script decide "
"whether a runlevel change is necessary. Open <path>/etc/conf.d/local.start</"
"path> in your favourite editor and add these lines:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):398
msgid "Runlevel adjustment at boot time by editing local.start"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):398
#, no-wrap
msgid ""
"\n"
"<comment># Fake acpi event to switch runlevel if running on batteries</comment>\n"
"/etc/acpi/actions/pmg_switch_runlevel.sh \"battery/battery\"\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):403
msgid ""
"Prepared like this you can activate Power Management policies for individual "
"devices."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):413
msgid "CPU Power Management"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):417
msgid ""
"Mobile processors can operate at different frequencies. Some allow changing "
"voltage as well. Most of the time your CPU doesn't need to run at full speed "
"and scaling it down will save much energy - often without any performance "
"decrease."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):427
msgid "Some Technical Terms"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):430
msgid ""
"CPU frequency scaling brings up some technical terms that might be unknown "
"to you. Here's a quick introduction."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):435
msgid ""
"First of all, the kernel has to be able to change the processor's frequency. "
"The <b>CPUfreq processor driver</b> knows the commands to do it on your CPU. "
"Thus it's important to choose the right one in your kernel. You should "
"already have done it above. Once the kernel knows how to change frequencies, "
"it has to know which frequency it should set. This is done according to the "
"<b>policy</b> which consists of a <b>CPUfreq policy</b> and a <b>governor</"
"b>. A CPUfreq policy are just two numbers which define a range the frequency "
"has to stay between - minimal and maximal frequency. The governor now "
"decides which of the available frequencies in between minimal and maximal "
"frequency to choose. For example, the <b>powersave governor</b> always "
"chooses the lowest frequency available, the <b>performance governor</b> the "
"highest one. The <b>userspace governor</b> makes no decision but chooses "
"whatever the user (or a program in userspace) wants - which means it reads "
"the frequency from <path>/sys/devices/system/cpu/cpu0/cpufreq/"
"scaling_setspeed</path>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):452
msgid ""
"This doesn't sound like dynamic frequency changes yet and in fact it isn't. "
"Dynamics however can be accomplished with various approaches. For example, "
"the <b>ondemand governor</b> makes its decisions depending on the current "
"CPU load. The same is done by various userland tools like <c>cpudyn</c>, "
"<c>cpufreqd</c>, <c>powernowd</c> and many more. ACPI events can be used to "
"enable or disable dynamic frequency changes depending on power source."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):464
msgid "Setting The Frequency"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):467
msgid ""
"Decreasing CPU speed and voltage has two advantages: On the one hand less "
"energy is consumed, on the other hand there is thermal improvement as your "
"system doesn't get as hot as running on full speed. The main disadvantage is "
"obviously the loss of performance. Decreasing processor speed is a trade off "
"between performance loss and energy saving."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):475
msgid ""
"Not every laptop supports frequency scaling. If unsure, have a look at the "
"list of supported processors in the <uri link="
"\"#doc_chap8\">Troubleshooting</uri> section to verify yours is supported."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):481
msgid ""
"It's time to test whether CPU frequency changing works. Let's install "
"another tool: <c>sys-power/cpufrequtils</c>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):486
msgid "Checking CPU frequency"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):486
#, no-wrap
msgid ""
"\n"
"# <i>emerge cpufrequtils</i>\n"
"# <i>cpufreq-info</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):491
msgid "Here is an example output:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):495
msgid "Sample output from cpufreq-info"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):495
#, no-wrap
msgid ""
"\n"
"cpufrequtils 0.3: cpufreq-info (C) Dominik Brodowski 2004\n"
"Report errors and bugs to linux@brodo.de, please.\n"
"analyzing CPU 0:\n"
"  driver: centrino\n"
"  CPUs which need to switch frequency at the same time: 0\n"
"  hardware limits: 600 MHz - 1.40 GHz\n"
"  available frequency steps: 600 MHz, 800 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz\n"
"  available cpufreq governors: conservative, ondemand, powersave, userspace, performance\n"
"  current policy: frequency should be within 924 MHz and 1.40 GHz.\n"
"    The governor \"performance\" may decide which speed to use\n"
"    within this range.\n"
"  current CPU frequency is 1.40 GHz.\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):510
msgid ""
"Now play around with <c>cpufreq-set</c> to make sure frequency switching "
"works. Run <c>cpufreq-set -g ondemand</c> for example to activate the "
"ondemand governor and verify the change with <c>cpufreq-info</c>. If it "
"doesn't work as expected, you might find help in the <uri link="
"\"#doc_chap8\">Troubleshooting section</uri> in the end of this guide."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):518
msgid ""
"<c>cpufrequtils</c> can operate in an automatic mode (when you use the "
"<b>ondemand</b> governor), you can also switch to the <b>userspace</b> "
"governor if you want to manually set a specific speed. You can also "
"statically set your CPU to its highest or lowest frequency by using the "
"<b>performance</b> and <b>powersave</b> governors, respectively."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):526
msgid "Changing CPU speeds"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):526
#, no-wrap
msgid ""
"\n"
"<comment>(Set the highest available frequency)</comment>\n"
"# <i>cpufreq-set -g performance</i>\n"
"<comment>(Set the lowest available frequency)</comment>\n"
"# <i>cpufreq-set -g powersave</i>\n"
"<comment>(Set a specific frequency)</comment>\n"
"# <i>cpufreq-set -g userspace</i>\n"
"# <i>cpufreq-set -f 2.00ghz</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):539
msgid "Other CPU Speed Utilities"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):542
msgid ""
"While <c>cpufrequtils</c> may be the best all-around program, there are some "
"other choices available in Portage. The following table gives a quick "
"overview of available CPU speed utilities. It's roughly separated in three "
"categories <b>kernel</b> for approaches that only need kernel support, "
"<b>daemon</b> for programs that run in the background and <b>graphical</b> "
"for programs that provide a GUI for easy configuration and changes."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):553
msgid "Name"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):554
msgid "Category"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):555
msgid "Switch decision"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):556
msgid "Kernel governors"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):557
msgid "Further governors"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):558
msgid "Comments"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):561
msgid "'ondemand' governor"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):562
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):576
msgid "Kernel"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):563
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):577
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):592
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):618
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):642
msgid "CPU load"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):564
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):565
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):578
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):579
msgid "N.A."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):566
msgid ""
"Chooses maximal frequency on CPU load and slowly steps down when the CPU is "
"idle. Further tuning through files in <path>/sys/devices/system/cpu/cpu0/"
"cpufreq/ondemand/</path>. Still requires userland tools (programs, scripts) "
"if governor switching or similar is desired."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):575
msgid "'conservative' governor"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):580
msgid ""
"Unlike the ondemand governor, conversative doesn't jump to maximum frequency "
"when CPU load is high, but increases the frequency step by step. Further "
"tuning through files in <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/"
"</path>. Still requires userland tools (programs, scripts) if governor "
"switching or similar is desired."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):590
msgid "http://mnm.uib.es/~gallir/cpudyn/"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):590
msgid "cpudyn"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):591
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):602
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):617
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):630
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):641
msgid "Daemon"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):593
msgid "Performance, powersave"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):594
msgid "Dynamic"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):595
msgid ""
"Also supports disk standby - notice however that <e>laptop mode</e> in most "
"cases will do a better job."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):601
msgid "http://sourceforge.net/projects/cpufreqd/"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):601
msgid "cpufreqd"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):603
msgid "Battery state, CPU load, temperature, running programs and more"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):604
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):666
msgid "All available"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):605
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):619
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):632
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):643
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):654
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):655
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):656
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):667
msgid "None"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):606
msgid ""
"Sophisticated (but somewhat complicated) setup. Extendible through plugins "
"like sensor monitoring (lm_sensors) or coordinating some NVidia based "
"graphics card memory and core. Cpufreqd is SMP aware and can optionally be "
"controlled manually at runtime."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):615
msgid "http://www.deater.net/john/powernowd.html"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):615
msgid "powernowd"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):620
msgid "Passive, sine, aggressive"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):621
msgid "Supports SMP."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):628
msgid "http://projects.simpledesigns.com.pl/project/ncpufreqd/"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):628
msgid "ncpufreqd"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):631
msgid "Temperature"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):633
msgid "Powersave, performance"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):634
msgid ""
"Toggles the used governor between performance and powersave depending on "
"system temperature. Very useful on laptops with notorious heat problems."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):640
msgid "http://www.goop.org/~jeremy/speedfreq/"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):640
msgid "speedfreq"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):644
msgid "Dynamic, powersave, performance, fixed speed"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):645
msgid ""
"Easy to configure with a nice client/server interface. Requires a 2.6 "
"kernel. Unmaintained, broken and thus removed from Portage. Please switch to "
"cpufreqd if you're still using it."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):652
msgid "http://cpuspeedy.sourceforge.net/"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):652
msgid "gtk-cpuspeedy"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):653
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):664
msgid "Graphical"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):657
msgid ""
"Gnome application, a graphical tool to set CPU frequency manually. It does "
"not offer any automation."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):663
msgid "klaptopdaemon"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):665
msgid "Battery state"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):668
msgid "KDE only, 'ondemand' governor required for dynamic frequency scaling."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):674
msgid ""
"While adjusting the frequency to the current load looks simple at a first "
"glance, it's not such a trivial task. A bad algorithm can cause switching "
"between two frequencies all the time or wasting energy when setting "
"frequency to an unnecessary high level."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):681
msgid "Which one to choose? If you have no idea about it, try <c>cpufreqd</c>:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):685
msgid "Installing cpufreqd"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):685
#, no-wrap
msgid ""
"\n"
"# <i>emerge cpufreqd</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):689
msgid ""
"<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</"
"path>. The default one that ships with cpufreqd may look a bit confusing. I "
"recommend replacing it with the one from former Gentoo developer Henrik Brix "
"Andersen (see below). Please notice that you need cpufreqd-2.0.0 or later. "
"Earlier versions have a different syntax for the config file."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):697
msgid "/etc/cpufreqd.conf (cpufreqd-2.0.0 and later)"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):697
#, no-wrap
msgid ""
"\n"
"[General]\n"
"pidfile=/var/run/cpufreqd.pid\n"
"poll_interval=3\n"
"enable_plugins=acpi_ac, acpi_battery\n"
"enable_remote=1\n"
"remote_group=wheel\n"
"verbosity=5\n"
"[/General]\n"
"\n"
"[Profile]\n"
"name=ondemand\n"
"minfreq=0%\n"
"maxfreq=100%\n"
"policy=ondemand\n"
"[/Profile]\n"
"\n"
"[Profile]\n"
"name=conservative\n"
"minfreq=0%\n"
"maxfreq=100%\n"
"policy=conservative\n"
"[/Profile]\n"
"\n"
"[Profile]\n"
"name=powersave\n"
"minfreq=0%\n"
"maxfreq=100%\n"
"policy=powersave\n"
"[/Profile]\n"
"\n"
"[Profile]\n"
"name=performance\n"
"minfreq=0%\n"
"maxfreq=100%\n"
"policy=performance\n"
"[/Profile]\n"
"\n"
"[Rule]\n"
"name=battery\n"
"ac=off\n"
"profile=conservative\n"
"[/Rule]\n"
"\n"
"[Rule]\n"
"name=battery_low\n"
"ac=off\n"
"battery_interval=0-10\n"
"profile=powersave\n"
"[/Rule]\n"
"\n"
"[Rule]\n"
"name=ac\n"
"ac=on\n"
"profile=ondemand\n"
"[/Rule]\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):755
msgid ""
"Now you can start the cpufreqd daemon. Add it to the <c>default</c> and "
"<c>battery</c> runlevel as well."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):760
msgid "Starting cpufreqd"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):760
#, no-wrap
msgid ""
"\n"
"# <i>rc-update add cpufreqd default battery</i>\n"
"# <i>/etc/init.d/cpufreqd start</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):765
msgid ""
"Sometimes it can be desirable to select another policy than the daemon "
"chooses, for example when battery power is low, but you know that AC will be "
"available soon. In that case you can turn on cpufreqd's manual mode with "
"<c>cpufreqd-set manual</c> and select one of your configured policies (as "
"listed by <c>cpufreqd-get</c>). You can leave manual mode by executing "
"<c>cpufreqd-set dynamic</c>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):774
msgid ""
"Do not run more than one of the above programs at the same time. It may "
"cause confusion like switching between two frequencies all the time."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):782
msgid "Verifying the result"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):785
msgid ""
"The last thing to check is that your new policies do a good job. An easy way "
"to do so is monitoring CPU speed while working with your laptop:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):790
msgid "Monitoring CPU speed"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):790
#, no-wrap
msgid ""
"\n"
"# <i>watch grep \\\"cpu MHz\\\" /proc/cpuinfo</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):794
msgid ""
"If <path>/proc/cpuinfo</path> doesn't get updated (see <uri link="
"\"#doc_chap8\">Troubleshooting</uri>), monitor the CPU frequency with <c>sys-"
"apps/x86info</c>:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):800
msgid "Alternative CPU speed monitoring"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):800
#, no-wrap
msgid ""
"\n"
"# <i>watch x86info -mhz</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):804
msgid ""
"Depending on your setup, CPU speed should increase on heavy load, decrease "
"on no activity or just stay at the same level. When using <c>cpufreqd</c> "
"and verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get "
"additional information about what's happening reported to <c>syslog</c>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):816
msgid "LCD Power Management"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):820
msgid ""
"As you can see in <uri link=\"#doc_chap1_fig1\">figure 1.1</uri>, the LCD "
"display consumes the biggest part of energy (might not be the case for non-"
"mobile CPU's). Thus it's quite important not only to shut the display off "
"when not needed, but also to reduce it's backlight if possible. Most laptops "
"offer the possibility to control the backlight dimming."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):831
msgid "Standby settings"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):834
msgid ""
"The first thing to check is the standby/suspend/off timings of the display. "
"As this depends heavily on your windowmanager, I'll let you figure it out "
"yourself. Just two common places: Blanking the terminal can be done with "
"<c>setterm -blank &lt;number-of-minutesM&gt;</c>, <c>setterm -powersave on</"
"c> and <c>setterm -powerdown &lt;number-of-minutesM&gt;</c>. For X.org, "
"modify <path>/etc/X11/xorg.conf</path> similar to this:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):843
msgid "LCD suspend settings in X.org"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):843
#, no-wrap
msgid ""
"\n"
"Section \"ServerFlags\"\n"
"  Option  \"blank time\"  \"5\"  <comment># Blank the screen after 5 minutes (Fake)</comment>\n"
"  Option  \"standby time\"  \"10\"  <comment># Turn off screen after 10 minutes (DPMS)</comment>\n"
"  Option  \"suspend time\"  \"20\"  <comment># Full suspend after 20 minutes</comment>\n"
"  Option  \"off time\"  \"30\"  <comment># Turn off after half an hour</comment>\n"
"  [...]\n"
"EndSection\n"
"\n"
"[...]\n"
"\n"
"Section \"Monitor\"\n"
"  Identifier  [...]\n"
"  Option  \"DPMS\"\n"
"  [...]\n"
"EndSection\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):864
msgid "Backlight dimming"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):867
msgid ""
"Probably more important is the backlight dimming. If you have access to the "
"dimming settings via a tool, write a small script that dims the backlight in "
"battery mode and place it in your <c>battery</c> runlevel. The following "
"script should work on most IBM Thinkpads and Toshiba laptops. You've got to "
"enable the appropriate option in your kernel (IBM Thinkpads only). For "
"Toshiba laptops, install <c>sys-power/acpitool</c> and skip configuration of "
"<c>thinkpad_acpi</c> (formerly called <c>ibm_acpi</c>) as described below."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):877
msgid ""
"Support for setting brightness is marked experimental in thinkpad_acpi. It "
"accesses hardware directly and may cause severe harm to your system. Please "
"read the <uri link=\"http://ibm-acpi.sourceforge.net/\">thinkpad_acpi "
"website</uri>"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):884
msgid ""
"To be able to set the brightness level, the thinkpad_acpi module has to be "
"loaded with the experimental parameter."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):889
msgid "automatically loading the thinkpad_acpi module"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):889
#, no-wrap
msgid ""
"\n"
"<comment>(Please read the warnings above before doing this!)</comment>\n"
"# <i>echo \"options thinkpad_acpi experimental=1\" &gt;&gt; /etc/modprobe.d/thinkpad_acpi</i>\n"
"# <i>update-modules</i>\n"
"# <i>echo thinkpad_acpi &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
"# <i>modprobe thinkpad_acpi</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):897
msgid ""
"This should work without error messages and a file <path>/proc/acpi/ibm/"
"brightness</path> should be created after loading the module. An init script "
"will take care of choosing the brightness according to the power source."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):904
msgid "/etc/conf.d/lcd-brightness"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):904
#, no-wrap
msgid ""
"\n"
"<comment># See /proc/acpi/ibm/brightness for available values</comment>\n"
"<comment># Please read /usr/src/linux/Documentation/thinkpad-acpi.txt</comment>\n"
"\n"
"<comment># brightness level in ac mode. Default is 7.</comment>\n"
"BRIGHTNESS_AC=7\n"
"\n"
"<comment># brightness level in battery mode. Default is 4.</comment>\n"
"BRIGHTNESS_BATTERY=4\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):915
msgid "/etc/init.d/lcd-brightness"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):915
#, no-wrap
msgid ""
"\n"
"#!/sbin/runscript\n"
"\n"
"set_brightness() {\n"
"    if on_ac_power\n"
"    then\n"
"        LEVEL=${BRIGHTNESS_AC:-7}\n"
"    else\n"
"        LEVEL=${BRIGHTNESS_BATTERY:-4}\n"
"    fi\n"
"\n"
"    if [ -f /proc/acpi/ibm/brightness ]\n"
"    then\n"
"        ebegin \"Setting LCD brightness\"\n"
"        echo \"level ${LEVEL}\" &gt; /proc/acpi/ibm/brightness\n"
"        eend $?\n"
"    elif [[ -e /usr/bin/acpitool &amp;&amp; -n $(acpitool -T | grep \"LCD brightness\") ]]\n"
"    then\n"
"        ebegin \"Setting LCD brightness\"\n"
"        acpitool -l $LEVEL &gt;/dev/null || ewarn \"Unable to set lcd brightness\"\n"
"        eend $?\n"
"    else\n"
"        ewarn \"Setting LCD brightness is not supported.\"\n"
"        ewarn \"For IBM Thinkpads, check that thinkpad_acpi is loaded into the kernel\"\n"
"        ewarn \"For Toshiba laptops, you've got to install sys-power/acpitool\"\n"
"    fi\n"
"}\n"
"\n"
"start() {\n"
"    set_brightness\n"
"}\n"
"\n"
"stop () {\n"
"    set_brightness\n"
"}\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):952
msgid ""
"When done, make sure brightness is adjusted automatically by adding it to "
"the battery runlevel."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):957
msgid "Enabling automatic brightness adjustment"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):957
#, no-wrap
msgid ""
"\n"
"# <i>chmod +x /etc/init.d/lcd-brightness</i>\n"
"# <i>rc-update add lcd-brightness battery</i>\n"
"# <i>rc</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):968
msgid "Disk Power Management"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):972
msgid ""
"Hard disks consume less energy in sleep mode. Therefore it makes sense to "
"activate power saving features whenever the hard disk is not used for a "
"certain amount of time. I'll show you two alternative possibilities to do "
"it. First, laptop-mode will save most energy due to several measures which "
"prevent or at least delay write accesses. The drawback is that due to the "
"delayed write accesses a power outage or kernel crash will be more dangerous "
"for data loss. If you don't like this, you have to make sure that there are "
"no processes which write to your hard disk frequently. Afterwards you can "
"enable power saving features of your hard disk with <c>hdparm</c> as the "
"second alternative."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):987
msgid "Increasing idle time - laptop-mode"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):990
msgid ""
"Recent 2.6 kernels include the so-called <c>laptop-mode</c>. When activated, "
"dirty buffers are written to disk on read calls or after 10 minutes (instead "
"of 30 seconds). This minimizes the time the hard disk needs to be spun up."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):996
msgid "Automated start of laptop-mode"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):996
#, no-wrap
msgid ""
"\n"
"# <i>emerge laptop-mode-tools</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1000
msgid ""
"<c>laptop-mode-tools</c> has its configuration file in <path>/etc/laptop-"
"mode/laptop-mode.conf</path>. Adjust it the way you like it, it's well "
"commented. Run <c>rc-update add laptop_mode battery</c> to start it "
"automatically."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1007
msgid ""
"Recent versions (1.11 and later) of laptop-mode-tools include a new tool "
"<c>lm-profiler</c>. It will monitor your system's disk usage and running "
"network services and suggests to disable unneeded ones. You can either "
"disable them through laptop-mode-tools builtin runlevel support (which will "
"be reverted by Gentoo's <c>/sbin/rc</c>) or use your <c>default</c>/"
"<c>battery</c> runlevels (recommended)."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1016
msgid "Sample output from running lm-profiler"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1016
#, no-wrap
msgid ""
"\n"
"# <i>lm-profiler</i>\n"
"Profiling session started.\n"
"Time remaining: 600 seconds\n"
"[4296896.602000] amarokapp\n"
"Time remaining: 599 seconds\n"
"[4296897.714000] sort\n"
"[4296897.970000] mv\n"
"Time remaining: 598 seconds\n"
"Time remaining: 597 seconds\n"
"[4296900.482000] reiserfs/0\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1029
msgid ""
"After profiling your system for ten minutes, lm-profiler will present a list "
"of services which might have caused disk accesses during that time."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1034
msgid "lm-profiler suggests to disable some services"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1034
#, no-wrap
msgid ""
"\n"
"Program:     \"atd\"\n"
"Reason:      standard recommendation (program may not be running)\n"
"Init script: /etc/init.d/atd (GUESSED)\n"
"\n"
"Do you want to disable this service in battery mode? [y/N]: <i>n</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1042
msgid ""
"To disable atd as suggested in the example above, you would run <c>rc-update "
"del atd battery</c>. Be careful not to disable services that are needed for "
"your system to run properly - <c>lm-profiler</c> is likely to generate some "
"false positives. Do not disable a service if you are unsure whether it's "
"needed."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1053
msgid "Limiting Write Accesses"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1056
msgid ""
"If you don't want to use laptop-mode, you must take special care to disable "
"services that write to your disk frequently - <c>syslogd</c> is a good "
"candidate, for example. You probably don't want to shut it down completely, "
"but it's possible to modify the config file so that \"unnecessary\" things "
"don't get logged and thus don't create disk traffic. <c>Cups</c> writes to "
"disk periodically, so consider shutting it down and only enable it manually "
"when needed."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1066
msgid "Disabling cups in battery mode"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1066
#, no-wrap
msgid ""
"\n"
"# <i>rc-update del cupsd battery</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1070
msgid ""
"You can also use <c>lm-profiler</c> from laptop-mode-tools (see above) to "
"find services to disable. Once you eliminated all of them, go on with "
"configuring hdparm."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1079
msgid "hdparm"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1082
msgid ""
"The second possibility is using <c>hdparm</c>. Skip this if you are using "
"laptop-mode. Otherwise, edit <path>/etc/conf.d/hdparm</path> and add the "
"following values to your drive entries. This example assumes your hard drive "
"is called <b>hda</b>:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1089
msgid "Using /etc/conf.d/hdparm for disk standby"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1089
#, no-wrap
msgid ""
"\n"
"hda_args=\"-q -S12\"\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1093
msgid ""
"This will activate power management for your hard drive. If you ever want to "
"deactivate power management, you can edit <path>/etc/conf.d/hdparm</path> "
"and change the values to <c>-q -S0</c>, or just run <c>hdparm -q -S0 /dev/"
"hda</c>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1099
msgid ""
"See <c>man hdparm</c> for the options. Though you can always start "
"<c>hdparm</c> manually when you are on battery power by running <c>/etc/init."
"d/hdparm start</c>, it's much easier to automate its startup and shutdown. "
"To do so, add <c>hdparm</c> to the battery runlevel so that it will "
"automatically enable power management."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1107
msgid "Automate disk standby settings"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1107
#, no-wrap
msgid ""
"\n"
"# <i>rc-update add hdparm battery</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(impo):1111
msgid ""
"Be careful with sleep/spin down settings of your hard drive. Setting it to "
"small values might wear out your drive and lose warranty."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1119
msgid "Other tricks"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1122
msgid ""
"Another possibility is to deactivate swap in battery mode. Before writing a "
"swapon/swapoff switcher, make sure there is enough RAM and swap isn't used "
"heavily, otherwise you'll be in big problems."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1128
msgid ""
"If you don't want to use laptop-mode, it's still possible to minimize disk "
"access by mounting certain directories as <c>tmpfs</c> - write accesses are "
"not stored on a disk, but in main memory and get lost with unmounting. Often "
"it's useful to mount <path>/tmp</path> like this - you don't have to pay "
"special attention as it gets cleared on every reboot regardless whether it "
"was mounted on disk or in RAM. Just make sure you have enough RAM and no "
"program (like a download client or compress utility) needs extraordinary "
"much space in <path>/tmp</path>. To activate this, enable tmpfs support in "
"your kernel and add a line to <path>/etc/fstab</path> like this:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1140
msgid "Editing /etc/fstab to make /tmp even more volatile"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1140
#, no-wrap
msgid ""
"\n"
"none  /tmp  tmpfs  size=32m  0 0\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1144
msgid ""
"Pay attention to the size parameter and modify it for your system. If you're "
"unsure, don't try this at all, it can become a performance bottleneck "
"easily. In case you want to mount <path>/var/log</path> like this, make sure "
"to merge the log files to disk before unmounting. They are essential. Don't "
"attempt to mount <path>/var/tmp</path> like this. Portage uses it for "
"compiling..."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1157
msgid "Power Management For Other Devices"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1159
msgid "Graphics Cards"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1162
msgid ""
"In case you own an ATI graphics card supporting PowerPlay (dynamic clock "
"scaling for the graphics processing unit GPU), you can activate this feature "
"in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) the "
"<c>DynamicClocks</c> option in the Device section. Please notice that this "
"feature will lead to crashes on some systems."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1170
msgid "Enabling ATI PowerPlay support in X.org"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1170
#, no-wrap
msgid ""
"\n"
"Section \"Device\"\n"
"[...]\n"
"Option      \"DynamicClocks\" \"on\"\n"
"EndSection\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1180
msgid "Wireless Power Management"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1183
msgid ""
"Wireless LAN cards consume quite a bit of energy. Put them in Power "
"Management mode just like your hard drives."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1188
msgid ""
"This script assumes your wireless interface is called <c>wlan0</c>; replace "
"this with the actual name of your interface."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1193
msgid ""
"Add the following option to <path>/etc/conf.d/net</path> to automatically "
"enable power management for your wireless card:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1198
msgid "Automated WLAN Power Management"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1198
#, no-wrap
msgid ""
"\n"
"iwconfig_wlan0=\"power on\"\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1202
msgid ""
"See <c>man iwconfig</c> for details and more options like the period between "
"wakeups or timeout settings. If your driver and access point support "
"changing the beacon time, this is a good starting point to save even more "
"energy."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1211
msgid "USB Power Management"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1214
msgid ""
"There are two problems with USB devices regarding energy consumption: First, "
"devices like USB mice, digital cameras or USB sticks consume energy while "
"plugged in. You cannot avoid this (nevertheless remove them in case they're "
"not needed). Second, when there are USB devices plugged in, the USB host "
"controller periodically accesses the bus which in turn prevents the CPU from "
"going into sleep mode. The kernel offers an experimental option to enable "
"suspension of USB devices through driver calls or one of the <path>power/"
"state</path> files in <path>/sys</path>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1225
msgid "Enabling USB suspend support in the kernel"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1225
#, no-wrap
msgid ""
"\n"
"Device Drivers\n"
"  USB support\n"
"    [*]   Support for Host-side USB\n"
"      [*]   USB suspend/resume (EXPERIMENTAL)\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1237
msgid "Sleep States: sleep, standby, and suspend to disk"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1241
msgid "ACPI defines different sleep states. The more important ones are"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1246
msgid "S1 aka Standby"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1247
msgid "S3 aka Suspend to RAM aka Sleep"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1248
msgid "S4 aka Suspend to Disk aka Hibernate"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1251
msgid ""
"They can be called whenever the system is not in use, but a shutdown is not "
"wanted due to the long boot time."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1259
msgid "Sleep (S3)"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1262
msgid ""
"The ACPI support for these sleep states is marked experimental for good "
"reason. APM sleep states seem to be more stable, however you can't use APM "
"and ACPI together."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1268
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1362
msgid "Kernel configuration for the various suspend types"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1268
#, no-wrap
msgid ""
"\n"
"  Power Management Options ---&gt;\n"
"    [*]  Power Management support\n"
"    [*]  Suspend to RAM and standby \n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1274
msgid ""
"Once your kernel is properly configured, you can use the <c>hibernate-"
"script</c> to activate suspend or sleep mode. Let's install that first."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1280
msgid "Installing the hibernate-script"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1280
#, no-wrap
msgid ""
"\n"
"# <i>emerge hibernate-script</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1284
msgid ""
"Some configuration has to be done in <path>/etc/hibernate</path>. The "
"default package introduces a few configuration files for each sleep state. "
"Options that are common to all suspend methods are placed in <path>common."
"conf</path>; make sure this file is properly set up for your system."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1291
msgid ""
"To configure sleep, edit <path>sysfs-ram.conf</path> in <path>/etc/"
"hibernate</path>. <c>UseSysfsPowerState mem</c> is already setup correctly, "
"but if you need to make further changes to this particular sleep state (or "
"any other sleep state) you should add them to <path>/etc/hibernate/hibernate."
"conf</path>. The comments and option names will guide you. If you use nfs or "
"samba shares over the network, make sure to shutdown the appropriate init "
"scripts to avoid timeouts."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1301
msgid ""
"For more information on setting up sleep states, read <c>man hibernate.conf</"
"c>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1306
msgid ""
"Ready? Now is the last chance to backup any data you want to keep after "
"executing the next command. Notice that you probably have to hit a special "
"key like <c>Fn</c> to resume from sleep."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1312
msgid "Calling sleep"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1312
#, no-wrap
msgid ""
"\n"
"# <i>hibernate-ram</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1316
msgid ""
"If you're still reading, it seems to work. You can also setup standby (S1) "
"in a similar way by editing <path>sysfs-ram.conf</path> and changing "
"\"UseSysfsPowerState mem\" to \"UseSysfsPowerState standby\". S3 and S4 are "
"the more interesting sleep states due to greater energy savings however."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1326
msgid "Hibernate (S4)"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1329
msgid ""
"This section introduces hibernation, where a snapshot of the running system "
"is written to disk before powering off. On resume, the snapshot is loaded "
"and you can go on working at exactly the point you called hibernate before."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1335
msgid ""
"Don't exchange non hot-pluggable hardware when suspended. Don't attempt to "
"load a snapshot with a different kernel image than the one it was created "
"with. Shutdown any NFS or samba server/client before hibernating."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1341
msgid ""
"There are two different implementations for S4. The original one is swsusp, "
"then there is the newer tuxonice (formerly suspend2) with a nicer interface "
"(including fbsplash support). A <uri link=\"http://tuxonice.net/features."
"html#compare\">feature comparison</uri> is available at the <uri link="
"\"http://www.tuxonice.net\">tuxonice homepage</uri>. There used to be "
"Suspend-to-Disk (pmdisk), a fork of swsusp, but it has been merged back."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1351
msgid ""
"TuxOnIce is not included in the mainline kernel yet, therefore you either "
"have to patch your kernel sources with the patches provided by <uri link="
"\"http://www.tuxonice.net\">tuxonice.net</uri> or use <c>sys-kernel/tuxonice-"
"sources</c>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1358
msgid "The kernel part for both swusp and TuxOnIce is as follows:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1362
#, no-wrap
msgid ""
"\n"
"Power Management support ---&gt;\n"
"  <comment>(hibernate with swsusp)</comment>\n"
"  [*] Hibernation (aka 'suspend to disk')\n"
"      <comment>(replace /dev/SWAP with your swap partition)</comment>\n"
"      (/dev/SWAP)      Default resume partition\n"
"\n"
"  <comment>(hibernate with TuxOnIce)</comment>\n"
"  Enhanced Hibernation (TuxOnIce)\n"
"    --- Image Storage (you need at least one allocator)\n"
"    [*]    File Allocator\n"
"    [*]    Swap Allocator\n"
"    ---   General Options\n"
"    [*]    Compression support\n"
"    [ ]     Allow Keep Image Mode\n"
"    [*]     Replace swsusp by default\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1380
msgid ""
"The configuration for swsusp is rather easy. If you didn't store the "
"location of your swap partition in the kernel config, you can also pass it "
"as a parameter with the <c>resume=/dev/SWAP</c> directive. If booting is not "
"possible due to a broken image, use the <c>noresume</c> kernel parameter. "
"The <c>hibernate-cleanup</c> init script invalidates swsusp images during "
"the boot process."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1389
msgid "Invalidating swsusp images during the boot process"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1389
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1431
#, no-wrap
msgid ""
"\n"
"# <i>rc-update add hibernate-cleanup boot</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1393
msgid ""
"To activate hibernate with swsusp, use the hibernate script and set "
"<c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/sysfs-disk</path>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1398
msgid ""
"Backup your data before doing this. Run <c>sync</c> before executing one of "
"the commands to have cached data written to disk. First try it outside of X, "
"then with X running, but not logged in."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1404
msgid ""
"If you experience kernel panics due to uhci or similar, try to compile USB "
"support as module and unload the modules before sending your laptop to sleep "
"mode. There are configuration options for this in <path>common.conf</path>"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1410
msgid "Hibernating with swsusp"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1410
#, no-wrap
msgid ""
"\n"
"# <i>nano -w /etc/hibernate/common.conf</i>\n"
"<comment>(Make sure you have a backup of your data)</comment>\n"
"# <i>hibernate</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1416
msgid ""
"The following section discusses the setup of TuxOnIce including fbsplash "
"support for a nice graphical progress bar during suspend and resume."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1421
msgid ""
"The first part of the configuration is similar to the configuration of "
"swsusp. In case you didn't store the location of your swap partition in the "
"kernel config, you have to pass it as a kernel parameter with the "
"<c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a "
"broken image, append the <c>noresume</c> parameter. Additionally, the "
"<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the "
"boot process."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1431
msgid "Invalidating TuxOnIce images during the boot process"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1435
msgid ""
"Now edit <path>/etc/hibernate/tuxonice.conf</path>, enable the <c>TuxOnIce</"
"c> options you need. Do not enable the <c>fbsplash</c> options in <c>common."
"conf</c> just yet."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1441
msgid "Hibernating with TuxOnIce"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1441
#, no-wrap
msgid ""
"\n"
"# <i>nano -w /etc/hibernate/tuxonice.conf</i>\n"
"<comment>(Make sure you have a backup of your data)</comment>\n"
"# <i>hibernate</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1447
msgid ""
"Please configure <c>fbsplash</c> now if you didn't do already. To enable "
"fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c> "
"package is needed. Additionally, you've got to enable the <c>fbsplash</c> "
"USE flag."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1453
msgid "Installing tuxonice-userui"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1453
#, no-wrap
msgid ""
"\n"
"# <i>echo \"sys-apps/tuxonice-userui fbsplash\" &gt;&gt; /etc/portage/package.use</i>\n"
"<comment>(It may be marked ~arch, so first it must be keyworded)</comment>\n"
"# <i>echo \"sys-apps/tuxonice-userui\" &gt;&gt; /etc/portage/package.keywords</i>\n"
"# <i>emerge tuxonice-userui</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1460
msgid ""
"The ebuild tells you to make a symlink to the theme you want to use. For "
"example, to use the <c>livecd-2005.1</c> theme, run the following command:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1465
msgid "Using the livecd-2005.1 theme during hibernation"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1465
#, no-wrap
msgid ""
"\n"
"# <i>ln -sfn /etc/splash/livecd-2005.1 /etc/splash/tuxonice</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1469
msgid ""
"If you don't want a black screen in the first part of the resume process, "
"you have to add the <c>tuxoniceui_fbsplash</c> tool to your initrd image. "
"Assuming you created the initrd image with <c>splash_geninitramfs</c> and "
"saved it as <path>/boot/fbsplash-emergence-1024x768</path>, here's how to do "
"that."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1476
msgid "Adding tuxoniceui_fbsplash to an initrd image"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1476
#, no-wrap
msgid ""
"\n"
"# <i>mount /boot</i>\n"
"# <i>mkdir ~/initrd.d</i>\n"
"# <i>cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>\n"
"# <i>cd ~/initrd.d</i>\n"
"# <i>gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>\n"
"# <i>rm fbsplash-emergence-1024x768</i>\n"
"# <i>cp /usr/sbin/tuxoniceui_fbsplash sbin/</i>\n"
"# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 &gt; /boot/fbsplash-tuxonice-emergence-1024x768</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1487
msgid ""
"Afterwards adjust <path>grub.conf</path> (or <path>lilo.conf</path>) so that "
"your TuxOnIce kernel uses <path>/boot/fbsplash-tuxonice-emergence-1024x768</"
"path> as initrd image. You can now test a dry run to see if everything is "
"setup correctly."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1494
msgid "Test run for fbsplash hibernation"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1494
#, no-wrap
msgid ""
"\n"
"# <i>tuxoniceui_fbsplash -t</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1498
msgid ""
"Afterwards open <path>/etc/hibernate/common.conf</path> and activate the "
"fbsplash options. Execute <c>hibernate</c> and enjoy."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1508
msgid "Troubleshooting"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1512
msgid ""
"<e>Q:</e> I'm trying to change the CPU frequency, but <path>/sys/devices/"
"system/cpu/cpu0/cpufreq/scaling_governor</path> does not exist."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1518
msgid ""
"<e>A:</e> Make sure your processor supports CPU frequency scaling and you "
"chose the right CPUFreq driver for your processor. Here is a list of "
"processors that are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-"
"SA1100, ARM-SA1110, AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile "
"K6-3+, AMD mobile Duron, AMD mobile Athlon, AMD Opteron, AMD Athlon 64, "
"Cyrix Media GXm, Intel mobile PIII and Intel mobile PIII-M on certain "
"chipsets, Intel Pentium 4, Intel Xeon, Intel Pentium M (Centrino), National "
"Semiconductors Geode GX, Transmeta Crusoe, VIA Cyrix 3 / C3, UltraSPARC-III, "
"SuperH SH-3, SH-4, several \"PowerBook\" and \"iBook2\" and various "
"processors on some ACPI 2.0-compatible systems (only if \"ACPI Processor "
"Performance States\" are available to the ACPI/BIOS interface)."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1531
msgid ""
"<e>Q:</e> My laptop supports frequency scaling, but <path>/sys/devices/"
"system/cpu/cpu0/cpufreq/</path> is empty."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1536
msgid ""
"<e>A:</e> Look for ACPI related error messages with <c>dmesg | grep ACPI</"
"c>. Try to update the BIOS, especially if a broken DSDT is reported. You can "
"also try to fix it yourself (which is beyond the scope of this guide)."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1542
msgid ""
"<e>Q:</e> My laptop supports frequency scaling, but according to <path>/proc/"
"cpuinfo</path> the speed never changes."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1547
msgid ""
"<e>A:</e> Probably you have activated symmetric multiprocessing support "
"(CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older "
"kernels had a bug causing this. In that case, run <c>emerge x86info</c>, "
"update your kernel as asked and check the current frequency with <c>x86info -"
"mhz</c>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1554
msgid ""
"<e>Q:</e> I can change the CPU frequency, but the range is not as wide as in "
"another OS."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1559
msgid ""
"<e>A:</e> You can combine frequency scaling with ACPI throttling to get a "
"lower minimum frequency. Notice that throttling doesn't save much energy and "
"is mainly used for thermal management (keeping your laptop cool and quiet). "
"You can read the current throttling state with <c>cat /proc/acpi/processor/"
"CPU/throttling</c> and change it with <c>echo -n \"0:x\" &gt; /proc/acpi/"
"processor/CPU/limit</c>, where x is one of the Tx states listed in <path>/"
"proc/acpi/processor/CPU/throttling</path>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1569
msgid ""
"<e>Q:</e> When configuring the kernel, powersave, performance and userspace "
"governors show up, but that ondemand thing is missing. Where do I get it?"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1574
msgid ""
"<e>A:</e> The ondemand governor is only included in recent kernel sources. "
"Try updating them."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1579
msgid "<e>Q:</e> Battery life time seems to be worse than before."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1583
msgid ""
"<e>A:</e> Check your BIOS settings. Maybe you forgot to re-enable some of "
"the settings."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1588
msgid ""
"<e>Q:</e> My battery is charged, but KDE reports there would be 0% left and "
"immediately shuts down."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1593
msgid ""
"<e>A:</e> Check that battery support is compiled into your kernel. If you "
"use it as a module, make sure the module is loaded."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1598
msgid ""
"<e>Q:</e> My system logger reports things like \"logger: ACPI group "
"battery / action battery is not defined\"."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1603
msgid ""
"<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path> "
"script that is shipped with acpid. You can safely ignore it. If you like to "
"get rid of it, you can comment the appropriate line in <path>/etc/acpi/"
"default.sh</path> as shown below:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1610
msgid "Disabling warnings about unknown acpi events"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1610
#, no-wrap
msgid ""
"\n"
"        *)      # logger \"ACPI action $action is not defined\"\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1614
msgid "<e>Q:</e> I have a Dell Inspiron 51XX and I don't get any ACPI events."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1618
msgid ""
"<e>A:</e> This seems to be a kernel bug. Read on <uri link=\"http://bugme."
"osdl.org/show_bug.cgi?id=1752\">here</uri>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1623
msgid ""
"<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</"
"path> and now X.org crashes / the screen stays black / my laptop doesn't "
"shutdown properly."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1629
msgid ""
"<e>A:</e> This happens on some systems. You have to disable "
"<c>DynamicClocks</c>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1634
msgid ""
"<e>Q:</e> I want to use TuxOnIce, but it tells me my swap partition is too "
"small. Resizing is not an option."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1639
msgid ""
"<e>A:</e> If there is enough free space on your system, you can use the "
"filewriter instead of the swapwriter. The <c>hibernate-script</c> supports "
"it as well. More information can be found in <path>/usr/src/linux/"
"Documentation/power/tuxonice.txt</path>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1646
msgid ""
"<e>Q:</e> I just bought a brand new battery, but it only lasts for some "
"minutes! What am I doing wrong?"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1651
msgid ""
"<e>A:</e> First follow your manufacturer's advice on how to charge the "
"battery correctly."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1656
msgid "<e>Q:</e> The above didn't help. What should I do then?"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1660
msgid ""
"<e>A:</e> Some batteries sold as \"new\" are in fact old ones. Try the "
"following:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1664
msgid "Querying battery state"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1664
#, no-wrap
msgid ""
"\n"
"$ <i>grep capacity /proc/acpi/battery/BAT0/info</i>\n"
"design capacity:     47520 mWh\n"
"last full capacity:  41830 mWh\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1670
msgid ""
"If the \"last full capacity\" differs significantly from the design "
"capacity, your battery is probably broken. Try to claim your warranty."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1675
msgid "<e>Q:</e> My problem is not listed above. Where should I go next?"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1679
msgid ""
"<e>A:</e> Don't fear to contact me, <mail link=\"earthwings@gentoo.org"
"\">Dennis Nienhüser</mail>, directly. The <uri link=\"http://forums.gentoo."
"org\">Gentoo Forums</uri> are a good place to get help as well. If you "
"prefer IRC, try the <c>#gentoo-laptop</c><uri link=\"irc://irc.gentoo.org"
"\">channel</uri>."
msgstr ""

#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(None):0
msgid "translator-credits"
msgstr ""