https://wiki.archlinux.org/api.php?action=feedcontributions&user=Techaddicted&feedformat=atomArchWiki - User contributions [en]2024-03-28T18:00:52ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Kernel&diff=278614Kernel2013-10-13T19:31:23Z<p>Techaddicted: /* AUR packages */</p>
<hr />
<div>[[Category:Kernel]]<br />
[[cs:Kernel Compilation]]<br />
[[es:Kernel Compilation]]<br />
[[it:Kernels]]<br />
[[ja:Kernels]]<br />
[[zh-CN:Kernels]]<br />
{{Article summary start}}<br />
{{Article summary text|This article discusses kernels in Arch, kernel patches and kernel compilation.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Kernel modules}}<br />
{{Article summary wiki|Kernel Panics}}<br />
{{Article summary wiki|Linux-ck}}<br />
{{Article summary wiki|sysctl}}<br />
{{Article summary end}}<br />
<br />
From [[Wikipedia:Kernel (computing)|Wikipedia]]:<br />
:''the kernel is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).''<br />
<br />
There are various alternative kernels available for Arch Linux in addition to the mainline Linux kernel. This article lists some of the options available in the repositories with a brief description of each. There is also a description of patches that can be applied to the system's kernel. The article ends with an overview of custom kernel compilation with links to various methods.<br />
<br />
==Precompiled kernels==<br />
===Official packages===<br />
;{{Pkg|linux}}<br />
:The Linux kernel and modules from the [core] repository. Vanilla kernel with [https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/linux two patches applied].<br />
<br />
;{{Pkg|linux-lts}}<br />
:Long term support (LTS) Linux kernel and modules from the [core] repository.<br />
<br />
===AUR packages===<br />
;{{AUR|linux-bfs}}<br />
:Linux kernel and modules with the [[Wikipedia:Brain_Fuck_Scheduler|Brain Fuck Scheduler]] (BFS) - created by Con Kolivas for desktop computers with fewer than 4096 cores, with BFQ I/O scheduler as optional.<br />
<br />
;{{AUR|linux-ck}}<br />
:Linux Kernel built with Con Kolivas' ck1 patchset.<br />
:Additional options which can be toggled on/off in the [[PKGBUILD]] include: BFQ scheduler, nconfig, localmodconfig and use running kernel's config.<br />
:These are patches designed to improve system responsiveness with specific emphasis on the desktop, but suitable to any workload. The ck patches include BFS.<br />
:For further information and installation instructions, please read the [[linux-ck]] main article.<br />
<br />
;{{AUR|linux-eee-ck}}<br />
:The Linux Kernel and modules for the Asus Eee PC 701, built with Con Kolivas' ck1 patchset.<br />
<br />
;{{AUR|linux-fbcondecor}}<br />
:The Linux Kernel and modules with [[Fbsplash|fbcondecor support]]. <br />
<br />
;{{AUR|linux-grsec}}<br />
:The Linux Kernel and modules with [[Grsecurity Patchset]] and PaX patches for increased security.<br />
<br />
;{{AUR|linux-mainline}}<br />
:The Mainline Linux Kernel and modules.<br />
<br />
;{{AUR|linux-pax}}<br />
:The Linux Kernel and modules with PaX patches for increased security.<br />
<br />
;{{AUR|linux-ice}}<br />
:The Linux Kernel and modules with gentoo-sources patchset and [[TuxOnIce]] support.<br />
<br />
;{{AUR|linux-lqx}}<br />
:[http://liquorix.net Liquorix] is a distro kernel replacement built using a Debian-targeted configuration and the ZEN kernel sources. Designed for desktop, multimedia, and gaming workloads, it is often used as a Debian Linux performance replacement kernel. Damentz, the maintainer of the Liquorix patchset, is a developer for the ZEN patchset as well.<br />
<br />
;{{AUR|linux-pf}}<br />
:Linux kernel and modules with the pf-kernel patch [-ck patchset (BFS included), TuxOnIce, BFQ] and aufs3.<br />
<br />
;{{AUR|linux-zen}}<br />
:The [http://zen-kernel.org ZEN Kernel] is a the result of a collaborative effort of kernel hackers to provide the best Linux kernel possible for every day systems. Builds of a ZEN kernel are available [https://bbs.archlinux.org/viewtopic.php?id=117157 in this repository].<br />
<br />
;{{AUR|kernel-netbook}}<br />
:Static kernel for netbooks with Intel Atom N270/N280/N450/N550 such as the Eee PC with the add-on of external firmware ({{AUR|broadcom-wl}}) and patchset (BFS + TuxOnIce + BFQ optional) - Only Intel GPU<br />
<br />
;{{AUR|linux-lts-tresor}}<br />
:The stable LTS Linux Kernel and modules with integrated [http://www1.informatik.uni-erlangen.de/tresor TRESOR]<br />
<br />
;{{AUR|linux-git}}<br />
:Linux kernel and modules built using sources from [http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git Linus Torvalds' git repository].<br />
<br />
==Patches and Patchsets==<br />
<br />
There are lots of reasons to patch your kernel, the major ones are for performance or support for non-mainline features such as reiser4 file system support. Other reasons might include fun and to see how it is done and what the improvements are.<br />
<br />
However, it is important to note that the best way to increase the speed of your system is to first tailor your kernel to your system, especially the architecture and processor type. For this reason using pre-packaged versions of custom kernels with generic architecture settings is not recommended or really worth it. A further benefit is that you can reduce the size of your kernel (and therefore build time) by not including support for things you do not have or use. For example, you might start with the stock kernel config when a new kernel version is released and remove support for things like bluetooth, video4linux, 1000Mbit ethernet, etc.; functionality you know you will not require for your specific machine. Although this page is not about customizing your kernel config, it is recommended as a first step--before moving on to using a patchset once you have grasped the fundamentals involved.<br />
<br />
===How to install===<br />
<br />
The installation process of custom kernel packages relies on the Arch Build System (ABS). If you haven't built any custom packages yet you may consult the following articles: [[Arch Build System]] and [[Creating Packages]].<br />
<br />
If you haven't actually patched or customized a kernel before it is not that hard and there are many PKGBUILDs on the forum for individual patchsets. However, you are advised to start from scratch with a bit of research on the benefits of each patchset, rather than just arbitrarily picking one. This way you'll learn much more about what you are doing rather than just choosing a kernel at startup and then be left wondering what it actually does.<br />
<br />
See [[#Compilation]].<br />
<br />
{{note|Don't forget to change the boot options in your bootloader, e.g. grub, to use the new kernel.}}<br />
<br />
===Major patchsets===<br />
<br />
First of all it is important to note that patchsets are developed by a variety of people. Some of these people are actually involved in the production of the linux kernel and others are hobbyists, which may reflect its level of reliability and stability.<br />
<br />
It is also worth noting that some patchsets are built on the back of other patchsets (which may or may not be reflected in the title of the patch). Patchsets (and kernel updates) can be released '''very''' frequently and often it is not worth keeping up with ALL of them so do not go crazy, unless you make it your hobby!<br />
<br />
You can search google for more sets - remember to use quotes {{ic|"-nitro"}} for example otherwise google will deliberately '''NOT''' show the results you want!<br />
<br />
{{note|This section is for '''information only''' - clearly no guarantees of stability or reliability are implied by inclusion on this page.}}<br />
<br />
====-ck====<br />
[[Linux-ck]] contains patches designed to improve system responsiveness with specific emphasis on the desktop, but suitable to any workload. The patches are created and maintained by Con Kolivas, his site is at http://users.on.net/~ckolivas/kernel/. Con maintains a full set but also provides the patches broken down so you can add only those you prefer.<br />
<br />
The -ck patches can be found at http://ck.kolivas.org/patches/3.0/<br />
<br />
====-rt====<br />
<br />
This patchset is maintained by a small group of core developers, led by Ingo Molnar. This patch allows nearly all of the kernel to be preempted, with the exception of a few very small regions of code ("raw_spinlock critical regions"). This is done by replacing most kernel spinlocks with mutexes that support priority inheritance, as well as moving all interrupt and software interrupts to kernel threads. <br />
<br />
It further incorporates high resolution timers - a patch set, which is independently maintained.<br />
<br />
[as said from the [http://rt.wiki.kernel.org/index.php/CONFIG_PREEMPT_RT_Patch Real-Time Linux Wiki]]<br />
<br />
patch at http://www.kernel.org/pub/linux/kernel/projects/rt/<br />
<br />
====-bld====<br />
{{Warning|This scheduler is in development.}}<br />
BLD is best described as a O(1) CPU picking technique. Which is done by reordering CPU runqueues based on runqueue loads. In other words, it keeps the scheduler aware of the load changes, which helps scheduler to keep runqueues in an order. This technique doesn't depend on scheduler ticks. The two most simple things in this technique are: load tracking and runqueue ordering; these are relatively simpler operations. Load tracking will be done whenever a load change happens on the system and based on this load change runqueue will be ordered. So, if we have an ordered runqueue from lowest to highest, then picking the less (or even busiest) runqueue is easy. Scheduler can pick the lowest runqueue without calculation and comparison at the time of placing a task in a runqueue. And while trying to distribute load at sched_exec and sched_fork our best choice is to pick the lowest busiest runqueue of the system. And in this way, system remains balanced without doing any load balancing. At the time of try_to_wake_up picking the idlest runqueue is topmost priority but it has been done as per domain basis to utilize CPU cache properly and it's an area where more concentration is requires.<br />
<br />
Google code Webpage: http://code.google.com/p/bld/<br />
<br />
====-grsecurity====<br />
<br />
[[Grsecurity]] is a security focused patchset. It adds numerous security related features such as Role-Based Access Control and utilizes features of the PaX project. It can be used on a desktop but a public server would receive the greatest benefit. Some applications are incompatible with the additional security measures implemented by this patchset. If this occurs, consider using a lower security level.<br />
<br />
The -grsecurity patches can be found at http://grsecurity.net<br />
<br />
====Tiny-Patches====<br />
The goal of [http://elinux.org/Linux_Tiny Linux Tiny] is to reduce its memory and disk footprint, as well as to add features to aid working on small systems. Target users are developers of embedded system and users of small or legacy machines such as 386s.<br />
<br />
Patch releases against the mainstream Linux kernel have been discontinued. The developers chose to focus on a few patches and spend their time trying to get them merged into the mainline kernel.<br />
<br />
====-pf====<br />
{{AUR|linux-pf}} is yet another Linux kernel fork which provides you with a handful of awesome features not merged into mainline. It is based on neither existing Linux fork nor patchset, although some unofficial ports may be used if required patches haven't been released officially.<br />
The most prominent patches of linux-pf are TuxOnIce, the CK patchset (most notably BFS), AUFS3, LinuxIMQ, l7 filter and BFQ.<br />
<br />
===Individual patches===<br />
<br />
These are patches which can be simply included in any build of a vanilla kernel or incorporated (probably with some major tweaking) into another patchset. I have included some common ones for starters.<br />
<br />
====Reiser4====<br />
<br />
[[Reiser4]]<br />
<br />
====Gensplash/fbsplash====<br />
[[Gensplash]] - http://dev.gentoo.org/~spock/projects/ {{linkrot|2013|05|20}}<br />
<br />
== Compilation ==<br />
Arch Linux provides for several methods of kernel compilation.<br />
<br />
=== Using the Arch Build System ===<br />
Using the [[Arch Build System]] takes advantage of the high quality of the existing {{Pkg|linux}} [[PKGBUILD]] and the benefits of [[Wikipedia:Package management system|package management]]. The PKGBUILD is structured so that you can stop the build after the source is downloaded and configure the kernel.<br />
<br />
See [[Kernels/Compilation/Arch Build System]].<br />
<br />
=== Traditional ===<br />
This involves manually downloading a source tarball, and compiling in your home directory as a normal user. Once configured, two installation methods are available; the traditional manual method, or with [[Makepkg]] + [[Pacman]].<br />
<br />
An advantage of learning the traditional method is that it is ''not'' distribution-specific. <br />
<br />
See [[Kernels/Compilation/Traditional]].<br />
<br />
===Proprietary NVIDIA driver===<br />
See [[NVIDIA#Alternate install: custom kernel]] for instructions on using the proprietary NVIDIA driver with a custom kernel.<br />
<br />
== See also ==<br />
*[http://www.kroah.com/lkn/ O'Reilly - Linux Kernel in a Nutshell] (free ebook)</div>Techaddictedhttps://wiki.archlinux.org/index.php?title=Laptop_Mode_Tools&diff=275038Laptop Mode Tools2013-09-11T13:47:22Z<p>Techaddicted: </p>
<hr />
<div>[[Category:Laptops]]<br />
[[Category:Power management]]<br />
[[de:Laptop Mode Tools]]<br />
[[fr:Laptop Mode Tools]]<br />
[[it:Laptop Mode Tools]]<br />
[[ru:Laptop Mode Tools]]<br />
[[zh-CN:Laptop Mode Tools]]<br />
{{Article summary start}}<br />
{{Article summary text|Overview of the Laptop Mode Tools power management suite for notebooks.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|acpid}}<br />
{{Article summary wiki|systemd}}<br />
{{Article summary wiki|cpufrequtils}}<br />
{{Article summary wiki|pm-utils}}<br />
{{Article summary wiki|Laptop}}<br />
{{Article summary wiki|Powertop}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary link|Laptop Mode Tools|http://samwel.tk/laptop_mode/}}<br />
{{Article summary link|Mailing List Archives|http://mailman.samwel.tk/pipermail/laptop-mode/ }}<br />
{{Article summary end}}<br />
<br />
''[http://samwel.tk/laptop_mode/ Laptop Mode Tools] is a laptop power saving package for Linux systems. It is the primary way to enable the Laptop Mode feature of the Linux kernel, which lets your hard drive spin down. In addition, it allows you to tweak a number of other power-related settings using a simple configuration file.''<br />
<br />
Combined with [[acpid]] and [[CPU Frequency Scaling|CPU frequency scaling]], LMT provides most users with a complete notebook power management suite.<br />
<br />
== Installation ==<br />
<br />
{{Pkg|laptop-mode-tools}} can be [[pacman|installed]] from the [[Official Repositories|official repositories]].<br />
<br />
== Configuration ==<br />
<br />
Enable the {{ic|laptop-mode}} service:<br />
<br />
# systemctl enable laptop-mode.service<br />
<br />
Configuration is handled through:<br />
<br />
* {{ic|/etc/laptop-mode/laptop-mode.conf}} - primary configuration file<br />
* {{ic|/etc/laptop-mode/conf.d/*}} - dozens of feature-specific "modules". <br />
<br />
Each module can be explicitly enabled/disabled by changing the {{ic|CONTROL_*}} value in the individual settings file found in {{ic|conf.d/*}}.<br />
<br />
If {{ic|ENABLE_AUTO_MODULES}} is set in {{ic|/etc/laptop-mode/laptop-mode.conf}}, LMT will automatically enable any modules where {{ic|CONTROL_*}} is set to {{ic|auto}}.<br />
<br />
If you want to check which modules are enabled, disabled or auto, run:<br />
<br />
$ grep -r '^\(CONTROL\&#124;ENABLE\)_' /etc/laptop-mode/conf.d<br />
<br />
{{Note|{{ic|auto-hibernate.conf}} and {{ic|battery-level-polling.conf}} are an exception and use an {{ic|ENABLE_*}} variable instead of {{ic|CONTROL_*}}.}}<br />
<br />
=== Hard disks ===<br />
<br />
For this you need to have hdparm and/or sdparm installed. See [[Hdparm]].<br />
<br />
Spinning down the hard drive through {{Ic|hdparm -S}} values saves power and makes everything a lot more quiet. By using the readahead function you can allow the drives to spin down more often even though you are using the computer. LMT can also establish {{Ic|hdparm -B}} values. The maximum hard drive power saving is 1 and the minimum is 254. Set this value to 254 when on AC and 1 when on battery. If you find that normal activity hangs often while waiting for the disk to spin up, it might be a good idea to set it to a higher value (eg. 128) which will make it spin down less often. {{Ic|hdparm -S}} and {{Ic|hdparm -B}} values are configured in {{ic|/etc/laptop-mode/laptop-mode.conf}}.<br />
<br />
{{expansion|reason=Please can someone add info on how to treat SSD disks with laptommode-tools? As, to my knowledge, readahead is useless for them (zero read time, just does wear out), and spin down most likely as well. }}<br />
<br />
With the CONTROL_MOUNT_OPTIONS variable (default on), laptop-mode-tools automatically remounts your partitions, appending 'commit=600,noatime' in the mount options. This keeps the journaling program jbd2 from accessing your disc every few seconds, instead the disc journal gets updated every 10 minutes (BEWARE: with this setting you could lose up to 10 minutes of work). Also be sure not to use the {{Ic|atime}} mount option, use {{Ic|noatime}} or {{Ic|relatime}} instead.<br />
<br />
{{Note|1=CONTROL_MOUNT_OPTIONS should not be turned on with nilfs2 partitions (see this thread on the forum https://bbs.archlinux.org/viewtopic.php?id=134656)}}<br />
<br />
=== CPU frequency ===<br />
<br />
For this you need to have a CPU frequency driver installed. See [[CPU Frequency Scaling]].<br />
<br />
# cpufreq.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
CONTROL_CPU_FREQUENCY=1<br />
BATT_CPU_MAXFREQ=fastest<br />
BATT_CPU_MINFREQ=slowest<br />
BATT_CPU_GOVERNOR=ondemand<br />
BATT_CPU_IGNORE_NICE_LOAD=1<br />
LM_AC_CPU_MAXFREQ=fastest<br />
LM_AC_CPU_MINFREQ=slowest<br />
LM_AC_CPU_GOVERNOR=ondemand<br />
LM_AC_CPU_IGNORE_NICE_LOAD=1<br />
NOLM_AC_CPU_MAXFREQ=fastest<br />
NOLM_AC_CPU_MINFREQ=slowest<br />
NOLM_AC_CPU_GOVERNOR=ondemand<br />
NOLM_AC_CPU_IGNORE_NICE_LOAD=0<br />
CONTROL_CPU_THROTTLING=0<br />
<br />
=== Device and bus ===<br />
<br />
==== Intel SATA ====<br />
<br />
* Enable the Intel SATA AHCI controller Aggressive Link Power Management feature to set the disk link into a very low power mode in the absence of disk IO.<br />
<br />
# intel-sata-powermgmt.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_INTEL_SATA_POWER=1<br />
BATT_ACTIVATE_SATA_POWER=1<br />
LM_AC_ACTIVATE_SATA_POWER=1<br />
NOLM_AC_ACTIVATE_SATA_POWER=0<br />
<br />
{{Note|Review the well-documented {{ic|/etc/laptop-mode/conf.d/intel-sata-powermgmt.conf}} file for additional configuration details.}}<br />
<br />
==== USB autosuspend ====<br />
<br />
# usb-autosuspend.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_USB_AUTOSUSPEND=1<br />
BATT_SUSPEND_USB=1<br />
LM_AC_SUSPEND_USB=1<br />
NOLM_AC_SUSPEND_USB=0<br />
AUTOSUSPEND_TIMEOUT=2<br />
<br />
{{Note|Review the well-documented {{ic|/etc/laptop-mode/conf.d/usb-autosuspend.conf}} file for additional configuration details. If you have an USB tool you always use (like an USB mouse), blacklisting them would stop them from suspending.}}<br />
<br />
=== Display and graphics ===<br />
<br />
==== LCD brightness ====<br />
<br />
* Available brightness values for certain laptops can be obtained by running following command:<br />
<br />
$ cat /proc/acpi/video/VID/LCD/brightness<br />
<br />
===== ThinkPad T40/T42 =====<br />
<br />
For [http://en.wikipedia.org/wiki/ThinkPad ThinkPad] T40/T42 notebooks, minimum and maximum brightness values can be obtained by running:<br />
<br />
$ cat /sys/class/backlight/acpi_video0/brightness<br />
$ cat /sys/class/backlight/acpi_video0/max_brightness<br />
<br />
# lcd-brightness.conf<br />
# ThinkPad T40/T42 Example<br />
#<br />
DEBUG=0<br />
CONTROL_BRIGHTNESS=1<br />
BATT_BRIGHTNESS_COMMAND="echo 0"<br />
LM_AC_BRIGHTNESS_COMMAND="echo 7"<br />
NOLM_AC_BRIGHTNESS_COMMAND="echo 7"<br />
BRIGHTNESS_OUTPUT="/sys/class/backlight/thinkpad_screen/brightness"<br />
<br />
===== ThinkPad T60 =====<br />
<br />
* For [http://en.wikipedia.org/wiki/ThinkPad ThinkPad] T60 notebooks, minimum and maximum brightness values can be obtained by running:<br />
<br />
$ cat /sys/class/backlight/thinkpad_screen/max_brightness<br />
$ cat /sys/class/backlight/thinkpad_screen/brightness<br />
<br />
# lcd-brightness.conf<br />
# ThinkPad T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_BRIGHTNESS=1<br />
BATT_BRIGHTNESS_COMMAND="echo 0"<br />
LM_AC_BRIGHTNESS_COMMAND="echo 7"<br />
NOLM_AC_BRIGHTNESS_COMMAND="echo 7"<br />
BRIGHTNESS_OUTPUT="/sys/class/backlight/acpi_video0/brightness"<br />
<br />
{{Note|Review the well-documented {{ic|/etc/laptop-mode/conf.d/lcd-brightness.conf}} file for additional configuration details.}}<br />
<br />
==== Terminal blanking ====<br />
<br />
# terminal-blanking.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_TERMINAL=1<br />
TERMINALS="/dev/tty1"<br />
BATT_TERMINAL_BLANK_MINUTES=1<br />
BATT_TERMINAL_POWERDOWN_MINUTES=2<br />
LM_AC_TERMINAL_BLANK_MINUTES=10<br />
LM_AC_TERMINAL_POWERDOWN_MINUTES=10<br />
NOLM_AC_TERMINAL_BLANK_MINUTES=10<br />
NOLM_AC_TERMINAL_POWERDOWN_MINUTES=10<br />
<br />
{{Note|Review the well-documented {{ic|/etc/laptop-mode/conf.d/terminal-blanking.conf}} file for additional configuration details.}}<br />
<br />
=== Networking ===<br />
<br />
==== Ethernet ====<br />
<br />
# ethernet.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_ETHERNET=1<br />
LM_AC_THROTTLE_ETHERNET=0<br />
NOLM_AC_THROTTLE_ETHERNET=0<br />
DISABLE_WAKEUP_ON_LAN=1<br />
DISABLE_ETHERNET_ON_BATTERY=1<br />
ETHERNET_DEVICES="eth0"<br />
<br />
==== Wireless LAN ====<br />
<br />
Wireless interface power management settings are hardware-dependent, and thus a bit trickier to configure. Depending on the wireless chipset, the settings are managed in one of the following three files:<br />
#{{ic|/etc/laptop-mode/conf.d/wireless-power.conf}} for a generic method of saving power (using "iwconfig wlan0 power on/off"). This applies to most chipsets (that is, anything but Intel chipsets listed below).<br />
#{{ic|/etc/laptop-mode/conf.d/wireless-ipw-power.conf}} for Intel chipsets driven by the old ipw driver. This apply to IPW3945, IPW2200 and IPW2100. It currently (as of LMT 1.55-1) uses iwpriv for IPW3945, and a combination of iwconfig and iwpriv settings for IPW2100 and IPW220. See {{ic|/usr/share/laptop-mode-tools/modules/wireless-ipw-power}} for details. (note that the ipw3945 is not used anymore, see below)<br />
#{{ic|/etc/laptop-mode/conf.d/wireless-iwl-power.conf}} for Intel chipsets driven by modules iwl4965, iwl3945 and iwlagn (this latter supports chipsets 4965, 5100, 5300, 5350, 5150, 1000, and 6000)<br />
Note that activating the three of them should not be much of a problem, since LMT detects the module used by the interface and acts accordingly.<br />
<br />
The supported modules for each configuration file, indicated above, are taken directly from LMT. However, this seems to be a bit out-of-date, since the current 2.6.34 kernel does not provide the ipw3945 and iwl4965 modules anymore (3945 chipset uses iwl3945 instead, and 4965 uses the generic module iwlagn). This is only brought here for information, as this does not (or should not) affect the way LMT works.<br />
<br />
There is a known issue with some chipsets running with the iwlagn module (namely, the 5300 chipset, and maybe others). On those chipsets, the following settings of {{ic|/etc/laptop-mode/conf.d/wireless-iwl-power.conf}}:<br />
<br />
IWL_AC_POWER<br />
IWL_BATT_POWER<br />
<br />
are ignored, because the {{ic|/sys/class/net/wlan*/device/power_level}} file does not exist. Instead, the standard method (with "iwconfig wlan0 power on/off") is automatically used.<br />
<br />
=== Audio ===<br />
<br />
==== AC97 ====<br />
<br />
# ac97-powersave.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_AC97_POWER=1<br />
<br />
==== Intel HDA ====<br />
<br />
# intel-hda-powersave.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_INTEL_HDA_POWER=1<br />
BATT_INTEL_HDA_POWERSAVE=1<br />
LM_AC_INTEL_HDA_POWERSAVE=1<br />
NOLM_AC_INTEL_HDA_POWERSAVE=0<br />
INTEL_HDA_DEVICE_TIMEOUT=10<br />
INTEL_HDA_DEVICE_CONTROLLER=0<br />
<br />
== Tips and tricks ==<br />
<br />
=== Aliases ===<br />
<br />
=== lm-profiler ===<br />
<br />
=== Disabling ===<br />
<br />
== Troubleshooting ==<br />
<br />
=== Laptop-mode-tools is not picking up events ===<br />
<br />
You need to install and enable [[acpid]]. Enable the {{Ic|acpid}} systemd service with:<br />
<br />
# systemctl enable acpid.service<br />
<br />
If that does not help, go through the laptop-mode configuration files and make sure that the service you want to enable is set to 1. Many services (including cpufreq control) are by default set to "auto", which may not enable them.<br />
<br />
I have experienced issues with bluetooth not working if i boot up with battery, and i fixed it with disabling runtime-pm.<br />
<br />
=== Laptop-mode-tools does not disable on AC ===<br />
<br />
It is possible if you have both laptop-mode-tools and pm-utils installed, they can conflict with each other, causing laptop-mode-tools to not properly set its state.<br />
<br />
This can be fixed by disabling scripts with duplicate functionality in pm-utils. The main cause of this particular issue is the laptop-mode script located in {{ic|/usr/lib/pm-utils/power.d}}. You can stop any unwanted hooks from running by creating a dummy file in {{ic|/etc/pm/power.d}} with the same name as the corresponding {{ic|/usr/lib/pm-utils/power.d}} hook. For example if you want to disable the laptop-mode hook:<br />
<br />
# touch /etc/pm/power.d/laptop-mode<br />
<br />
{{Note|Do not set the executable bit on that dummy-hook.}}<br />
<br />
Its recommended to disable any hook that has equivalent functionality in LMT.</div>Techaddicted