<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.thinkwiki.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Joei</id>
	<title>ThinkWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.thinkwiki.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Joei"/>
	<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/wiki/Special:Contributions/Joei"/>
	<updated>2026-05-21T05:42:07Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.12</generator>
	<entry>
		<id>https://www.thinkwiki.org/w/index.php?title=Madwifi&amp;diff=44778</id>
		<title>Madwifi</title>
		<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/w/index.php?title=Madwifi&amp;diff=44778"/>
		<updated>2009-11-18T08:15:29Z</updated>

		<summary type="html">&lt;p&gt;Joei: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Madwifi''' (Multiband Atheros Driver for Wifi) is Linux driver for 802.11a/b/g universal NIC cards - Cardbus, PCI, or miniPCI - using Atheros chip sets.&lt;br /&gt;
&lt;br /&gt;
The following (incomplete) list of adapters sold by IBM use the Atheros chips:&lt;br /&gt;
* [[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]]&lt;br /&gt;
* [[IBM 11b/g Wireless LAN Mini PCI Adapter]]&lt;br /&gt;
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]&lt;br /&gt;
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]&lt;br /&gt;
* [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]&lt;br /&gt;
* IBM 802.11a Wireless LAN Cardbus Adapter&lt;br /&gt;
* IBM 11 a/b/g Wireless Cardbus Adapter&lt;br /&gt;
&lt;br /&gt;
* (11a/b/g/n) Atheros Communications, Inc. Unknown device 0024 (rev 01) (using SVN revision 2360+)&lt;br /&gt;
&lt;br /&gt;
== Packages ==&lt;br /&gt;
*Official {{Debian}} packages in the [http://packages.debian.org/src:madwifi non-free section]. See also the [http://alioth.debian.org/projects/pkg-madwifi/ Alioth project page] and the [http://madwifi-project.org/wiki/UserDocs/Distro/Debian Madwifi wiki].&lt;br /&gt;
*{{Debian}} Packages: http://www.marlow.dk/madwifi&lt;br /&gt;
*{{Debian}} Packages: http://www.users.tpg.com.au/sigm/debian/pkg-madwifi/&lt;br /&gt;
*{{Fedora}} Packages(1): http://rpm.livna.org&lt;br /&gt;
*{{Fedora}} Packages(2): http://www.atrpms.net/name/madwifi/&lt;br /&gt;
*{{Gentoo}} ebuild: {{cmduser|emerge net-wireless/madwifi-driver net-wireless/madwifi-tools}}&lt;br /&gt;
*{{SUSE}} Packages http://madwifi-project.org/wiki/UserDocs/Distro/SuSE&lt;br /&gt;
*{{Ubuntu}} Package: {{cmduser|sudo apt-get install linux-restricted-modules-`uname -r`}}&lt;br /&gt;
*[http://madwifi-project.org/wiki/UserDocs/GettingMadwifi MadWifi packages and source] for these and other distributions&lt;br /&gt;
&lt;br /&gt;
== Source ==&lt;br /&gt;
Detailed instructions can be found [http://madwifi-project.org/wiki/UserDocs/GettingMadwifi on the MadWiFi Wiki].&lt;br /&gt;
&lt;br /&gt;
* [http://snapshots.madwifi-project.org/ Daily Snapshots]&lt;br /&gt;
* checkout from svn:&lt;br /&gt;
:{{cmduser|svn checkout svn.madwifi-project.org/madwifi/trunk madwifi}}&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
*Make sure that you've got sysctl support and the net/radio enabled (wireless extensions) in your kernel. Install the driver with make &amp;amp; make install&lt;br /&gt;
* further more you like to install the wireless tools from [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless  tools]. Make sure the versions fit together by&lt;br /&gt;
:{{cmduser|iwconfig --version}}&lt;br /&gt;
&lt;br /&gt;
Setting up [[wpa_supplicant]] with wpa-psk.&lt;br /&gt;
&lt;br /&gt;
You can enable the wireless LAN status LED on your Thinkpad by following [http://madwifi-project.org/wiki/UserDocs/EnableLEDs these instructions] (tested on Thinkpad x60s).&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
Release 0.9.4[http://madwifi-project.org/wiki/Releases/0.9.4] available&lt;br /&gt;
&lt;br /&gt;
Release notes&lt;br /&gt;
    * fixes compilation for recently released kernel 2.6.24&lt;br /&gt;
    * introduces Minstrel rate control algorithm&lt;br /&gt;
    * introduces switch to turn ANI (Ambience Noise Immunity) off, which can help to improve performance (see also #705)&lt;br /&gt;
    * several bug fixes to improve stability&lt;br /&gt;
    * now defaults to radiotap headers in monitor mode&lt;br /&gt;
    * adds support for variable number of VAPs, tunable via module parameter&lt;br /&gt;
&lt;br /&gt;
== Free Software HAL ==&lt;br /&gt;
The old madwifi driver consisted of a BSD/GPL wrapper with an unmodifiable HAL (Hardware Abstraction Layer). This HAL was not binary firmware as with the Intel wireless chips, but a piece of code that needed to run in the Linux kernel.  It consisted of header files for which no permission to modify was granted, and pre-compiled object files.&lt;br /&gt;
The vendor's position was that the Linux community simply needs to accept this sourceless HAL, since in principle &lt;br /&gt;
the Atheros chip could be tuned to any frequency, and thus produce RF interference with systems operating in those frequencies.&lt;br /&gt;
&lt;br /&gt;
This binary HAL was unacceptable to the Linux kernel developers, and the Atheros driver in this state would never have become a part of the official kernel. Some OpenBSD developers, facing the same issue, clean-room reverse-engineered the binary HAL and had produced an open source driver ([[ath5k]]), which was subsequently picked up by the madwifi team as the future direction. At the same time the old madwifi driver was labeled 'legacy' to reinforce this point.&lt;br /&gt;
&lt;br /&gt;
In the meantime the ath5k driver has been merged into the linux kernel, and Atheros has come around and hired a linux kernel developer, released a second driver (ath9k) for newer wireless chips and has taken over maintenance of the ath5k driver.&lt;br /&gt;
&lt;br /&gt;
As of the latest distributions (Ubuntu 8.10 and Fedora 10) the atk5k driver is still flaky, but those problems seem to be resolved with the latest mainline kernel (2.6.29).&lt;br /&gt;
&lt;br /&gt;
{{NOTE|Atheros-Chip AR5211 still needs the MadWifi driver in Kernels &amp;gt;=2.6.29. Get the sources [[http://dimitar.me/wp-content/uploads/2009/10/madwifi-trunk-r4099-20090929.tar.gz here]] and build them (you will need your linux headers)}} &lt;br /&gt;
&lt;br /&gt;
== Problems on Fedora 9 ==&lt;br /&gt;
When installing madwifi 0.9.4 on my new machine (from source), ath_pci would load fine, apparently, but I could only see the wlan0 interface via iwconfig, and no attempt to create an ath0 interface or start it (via ifconfig) would work.  I finally found the problem ([http://forums.fedoraforum.org/forum/showthread.php?p=990516 described in this email trail]) which indicates the new ath5k module is the problem.  &lt;br /&gt;
&lt;br /&gt;
As directed, I fixed it by editing '''/etc/modprobe.d''' and creating a file called '''madwifi''' with the following in it:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
alias wlan0 ath_pci&lt;br /&gt;
blacklist ath5k&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Although this enables ath0, I have yet to get the wirelss to actually connect to anything.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://madwifi-project.org/ Official website]&lt;br /&gt;
&lt;br /&gt;
[[Category:Drivers]]&lt;/div&gt;</summary>
		<author><name>Joei</name></author>
		
	</entry>
	<entry>
		<id>https://www.thinkwiki.org/w/index.php?title=Category:Ubuntu_9.10&amp;diff=44777</id>
		<title>Category:Ubuntu 9.10</title>
		<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/w/index.php?title=Category:Ubuntu_9.10&amp;diff=44777"/>
		<updated>2009-11-18T07:19:47Z</updated>

		<summary type="html">&lt;p&gt;Joei: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Ubuntu 9.10, Karmic Koala, will be released in October 2009 with full ext4 support and grub2 as bootloader.&lt;br /&gt;
&lt;br /&gt;
[[Category:Ubuntu]]&lt;/div&gt;</summary>
		<author><name>Joei</name></author>
		
	</entry>
	<entry>
		<id>https://www.thinkwiki.org/w/index.php?title=User_talk:Tonko&amp;diff=44775</id>
		<title>User talk:Tonko</title>
		<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/w/index.php?title=User_talk:Tonko&amp;diff=44775"/>
		<updated>2009-11-18T00:31:46Z</updated>

		<summary type="html">&lt;p&gt;Joei: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hei, great work! If you have fitting pictures for the 755CD/CDV feel free to upload and change them. Concerning the 701 and 755 i'll check. Thx. [[User:Wyrfel|Wyrfel]] 10:20, 17 Mar 2005 (CET)&lt;br /&gt;
----&lt;br /&gt;
== Thinkpad ACPI ==&lt;br /&gt;
&lt;br /&gt;
Are you sure that thinkpad_acpi is removed from the kernel? it's still loaded in my 2.6.31-14 kernel...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== UltraBase ==&lt;br /&gt;
&lt;br /&gt;
Hi Tonko,&lt;br /&gt;
&lt;br /&gt;
You posted that the UltraBase has an UltraSlimBay. I don't think there IS such a thing as an UltraBase. Certainly all of the X series UltraBase (X2, X3 and X4) do NOT have an UltraSlimBay. They are already on the chart.&lt;br /&gt;
&lt;br /&gt;
Can you give a reference or part number to the UltraBase, please? [[User:Whizkid|Whizkid]] 14:22, 25 May 2005 (CEST)&lt;br /&gt;
&lt;br /&gt;
Hei Wizkid,&lt;br /&gt;
&lt;br /&gt;
(sorry for interfering ;-) ). The (original) UltraBase is the same kind of media slide but for the ThinkPad 570. That's why it didn't have an X, because the X originates from X series and the numbers with it to designate the generation of X series the according UltraBase fits. I owned one of these once, so believe me, they exist an they feature an UltraSlimBay. ;-)Wyrfel.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
We should create an [[UltraBase]] page, but I never had one, and am too busy right now to dig it up the details. Finding specs on these old options is getting difficult. Tonko&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
Just did that. I found some data in my old eBay announcement that i created when i sold the notebook. [[User:Wyrfel|Wyrfel]] 02:06, 26 May 2005 (CEST)&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Hei,&lt;br /&gt;
&lt;br /&gt;
as you have realized we sysoped you some days ago. We did this to give you the ability to delete and move pages etc. . If you would send [[User:akw|akw]] your email address, he will create a forward address for you on the thinkwiki domain.&lt;br /&gt;
&lt;br /&gt;
Thanks once more for all your great responsible work.&lt;br /&gt;
[[User:Wyrfel|Wyrfel]] 03:26, 17 Aug 2005 (CEST)&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rovclock ==&lt;br /&gt;
Hey, what's up with removing my info on lowest clockspeeds on the radeon 9500Pro? I'm sure people that find this wiki page might be interested at what speeds they can underclock their radeon in a desktop. maybe it's a media center that needs to be quiet and cool, maybe it's a desktop in a country that doesn't have enormous amounts of electricity at no charge like american's do. Either let people put all additional info on, or make the page read only.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
This is &amp;quot;ThinkWiki&amp;quot;, a Wiki for Linux on ThinkPads, not a Wiki for desktop machines&lt;br /&gt;
&lt;br /&gt;
--[[User:Tonko|Tonko]] 02:39, 3 Nov 2005 (CET)&lt;br /&gt;
&lt;br /&gt;
== Full Dock ==&lt;br /&gt;
&lt;br /&gt;
Hello,&lt;br /&gt;
&lt;br /&gt;
referring to the changes you made to the [[ThinkPad_Dock]] page.  I heard that the DVI pass-through works at least on the X3* models as well.  If you are not absolutely certain the models you listed are the only ones supporting DVI output through the dock I kindly request you to change the wording.&lt;br /&gt;
&lt;br /&gt;
--[[User:Rolf|Rolf]] 18:09, 13 Nov 2005 (CET)&lt;br /&gt;
----&lt;br /&gt;
Do you actually have evidence of that?&lt;br /&gt;
&lt;br /&gt;
The X30 most likely will not support DVI, as it has an Integrated graphics controller in the Intel Southbridge, the X31 and X32 have the ATI Radeon 7000 chip, and might perhaps be possible of DVI. But I have never seen anywhere stated that they can.&lt;br /&gt;
&lt;br /&gt;
So unless you can point to some IBM documentation that they can, or have personal experience with one of the X30 models that confirms that they can do DVI pass-through, I think we should leave it as is. I don't want someone to buy an X32 based on us saying it can do DVI pass-through when it cannot.&lt;br /&gt;
&lt;br /&gt;
--[[User:Tonko|Tonko]] 19:14, 13 Nov 2005 (CET)&lt;br /&gt;
&lt;br /&gt;
== Question about &amp;quot;nsc-ircc, Wrong chip version ff&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
Tonko,&lt;br /&gt;
&lt;br /&gt;
On the [[How to make use of IrDA]] page there is mention of a &amp;quot;Wrong chip version ff&amp;quot; error that is caused &amp;quot;if the FIR mode is not activated&amp;quot; when you attempt &amp;quot;to load the nsc-ircc module&amp;quot;. It is also briefly discussed on the associated talk page.&lt;br /&gt;
&lt;br /&gt;
I'm running Ubuntu Dapper Drake on a Z60m, and whenever I suspend to RAM, just before the screen goes dark, a console appears that shows this error several times (once per time I've suspended since last reboot). Corresponding entries also appear in my system log. So, I am experiencing this problem, but it isn't clear to me exactly how to fix it. I'm assuming I need to activate FIR mode before loading the nsc-ircc module, but I have no idea how to do this (or exactly what this means).&lt;br /&gt;
&lt;br /&gt;
Can you point me in the right direction?&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
&lt;br /&gt;
--[[User:Chiron|Chiron]] 18:41, 27 July 2006 (CEST)&lt;br /&gt;
&lt;br /&gt;
Chiron,&lt;br /&gt;
&lt;br /&gt;
Sorry for taking a while to respond. I have been away for a bit and started a new job and such...&lt;br /&gt;
&lt;br /&gt;
I do not have a 60 series machine, but it does sound like the chip is not getting initialized properly upon resume.&lt;br /&gt;
&lt;br /&gt;
You might be able to resolve this issue by simply upgrading to the latest 2.6 kernel from kernel.org, as that includes fixes for enabling the chip (without hacks), and also to re-activate the chip in FIR mode after a suspend.&lt;br /&gt;
&lt;br /&gt;
--[[User:Tonko|Tonko]] 14:16, 25 August 2006 (CEST)&lt;/div&gt;</summary>
		<author><name>Joei</name></author>
		
	</entry>
	<entry>
		<id>https://www.thinkwiki.org/w/index.php?title=Thinkpad-acpi&amp;diff=44774</id>
		<title>Thinkpad-acpi</title>
		<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/w/index.php?title=Thinkpad-acpi&amp;diff=44774"/>
		<updated>2009-11-18T00:24:38Z</updated>

		<summary type="html">&lt;p&gt;Joei: /* thinkpad-acpi - IBM ThinkPad ACPI Extras Driver */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| width=&amp;quot;100%&amp;quot;&lt;br /&gt;
|style=&amp;quot;vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;&amp;quot; | __TOC__&lt;br /&gt;
|style=&amp;quot;vertical-align:top&amp;quot; |&lt;br /&gt;
== thinkpad-acpi - IBM ThinkPad ACPI Extras Driver ==&lt;br /&gt;
This is a Linux ACPI driver for the IBM ThinkPad laptops written by Borislav Deianov, and currently maintained by [[User:hmh|Henrique de Moraes Holschuh]]. It was originally named ibm-acpi, but got renamed to thinkpad-acpi and is included with the Linux kernel. It aims to support various features of these laptops which are accessible through the ACPI framework but not otherwise supported by the generic Linux ACPI drivers. As a kernel module, ibm-acpi works as a bridge to deliver information about certain hardware events like key presses or control the state of certain hardware features by software.&lt;br /&gt;
&lt;br /&gt;
{{WARN|As of kernel 2.6.27 the thinkpad-acpi bay and dock drivers should no longer be used. Instead use the standard ACPI bay and dock drivers. As of kernel 2.6.31 the thinkpad-acpi bay and dock drivers have been removed completely.&lt;br /&gt;
Refer to [http://sourceforge.net/projects/ibm-acpi/files/thinkpad-acpi/0.23-20091010/thinkpad-acpi-0.23-20091010_v2.6.31.3.patch.gz/download IBM-ACPI Sourceforge Page] for more information.}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Thinkpad-specific ACPI driver==&lt;br /&gt;
This is a Linux ACPI driver for the IBM ThinkPad laptops written by Borislav Deianov and Henrique de Moraes Holschuh. The driver replaces ibm-acpi in Linux mainline as of 2.6.22 (March 2007). To confuse matters further, it appears that there was also an older (now abandoned) driver of the same name written by Erik Rigtorp which never made it into the mainline kernel. The current thinkpad-acpi contains essentially the same functionality as ibm-acpi with some added features. Among which are registering of acpi events to the &amp;quot;thinkvantage&amp;quot; and volume/mute buttons which could previously only be accessed through the use of the [[tpb]] utility.&lt;br /&gt;
&lt;br /&gt;
==Hotkeys==&lt;br /&gt;
To view which hotkeys are active you can use &amp;quot;acpi_listen&amp;quot;, but that is deprecated.  A better way is to use &amp;quot;lsinput&amp;quot; and &amp;quot;input-events&amp;quot; commands to look at the output of the thinkpad-acpi input device(s).&lt;br /&gt;
&lt;br /&gt;
One important difference from ibm-acpi for those who wish to enable all possible hot keys, is that thinkpad-acpi automatically enables them.  One should not need to do anything to get the best possible thinkpad-acpi configuration for his ThinkPad (as long as he is using the latest thinkpad-acpi).&lt;br /&gt;
&lt;br /&gt;
In particular, old documentation that tells you to &amp;quot;echo enable,0xffffffff &amp;gt;/proc/acpi/ibm/hotkey&amp;quot;, or to give thinkpad-acpi any hotkey= module parameters to enable hot keys by default, is likely incorrect.&lt;br /&gt;
&lt;br /&gt;
The thinkpad-acpi driver has detailed documentation, which is shipped inside the Linux kernel sources, as &amp;quot;Documentation/thinkpad-acpi.txt&amp;quot; or as &amp;quot;Documentation/laptops/thinkpad-acpi.txt&amp;quot;.  If you feel a need to change the hot key mask manually, it is probably best to look at that documentation first to understand the full side effects of any changes.&lt;br /&gt;
&lt;br /&gt;
==sysfs interface==&lt;br /&gt;
some of the ThinkPad specific settings can be viewed or altered in sysfs under {{path|/sys/devices/platform/thinkpad_acpi}} and {{path|/sys/devices/platform/thinkpad_hwmon}}&lt;br /&gt;
&lt;br /&gt;
====thinkpad_acpi====&lt;br /&gt;
{{path|/sys/devices/platform/thinkpad_acpi}} directory structure is as follows on a T60 with kernel 2.6.31&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
|-- bluetooth_enable&lt;br /&gt;
|-- cmos_command&lt;br /&gt;
|-- driver -&amp;gt; ../../../bus/platform/drivers/thinkpad_acpi&lt;br /&gt;
|-- hotkey_all_mask&lt;br /&gt;
|-- hotkey_bios_enabled&lt;br /&gt;
|-- hotkey_bios_mask&lt;br /&gt;
|-- hotkey_enable&lt;br /&gt;
|-- hotkey_mask&lt;br /&gt;
|-- hotkey_poll_freq&lt;br /&gt;
|-- hotkey_radio_sw&lt;br /&gt;
|-- hotkey_recommended_mask&lt;br /&gt;
|-- hotkey_report_mode&lt;br /&gt;
|-- hotkey_source_mask&lt;br /&gt;
|-- leds&lt;br /&gt;
|   |-- tpacpi::power&lt;br /&gt;
|   |   |-- brightness&lt;br /&gt;
|   |   |-- device -&amp;gt; ../../../thinkpad_acpi&lt;br /&gt;
|   |   |-- max_brightness&lt;br /&gt;
|   |   |-- power&lt;br /&gt;
|   |   |   `-- wakeup&lt;br /&gt;
|   |   |-- subsystem -&amp;gt; ../../../../../class/leds&lt;br /&gt;
|   |   |-- trigger&lt;br /&gt;
|   |   `-- uevent&lt;br /&gt;
|   |-- tpacpi::standby&lt;br /&gt;
|   |   |-- brightness&lt;br /&gt;
|   |   |-- device -&amp;gt; ../../../thinkpad_acpi&lt;br /&gt;
|   |   |-- max_brightness&lt;br /&gt;
|   |   |-- power&lt;br /&gt;
|   |   |   `-- wakeup&lt;br /&gt;
|   |   |-- subsystem -&amp;gt; ../../../../../class/leds&lt;br /&gt;
|   |   |-- trigger&lt;br /&gt;
|   |   `-- uevent&lt;br /&gt;
|   |-- tpacpi::thinklight&lt;br /&gt;
|   |   |-- brightness&lt;br /&gt;
|   |   |-- device -&amp;gt; ../../../thinkpad_acpi&lt;br /&gt;
|   |   |-- max_brightness&lt;br /&gt;
|   |   |-- power&lt;br /&gt;
|   |   |   `-- wakeup&lt;br /&gt;
|   |   |-- subsystem -&amp;gt; ../../../../../class/leds&lt;br /&gt;
|   |   |-- trigger&lt;br /&gt;
|   |   `-- uevent&lt;br /&gt;
|   `-- tpacpi::thinkvantage&lt;br /&gt;
|       |-- brightness&lt;br /&gt;
|       |-- device -&amp;gt; ../../../thinkpad_acpi&lt;br /&gt;
|       |-- max_brightness&lt;br /&gt;
|       |-- power&lt;br /&gt;
|       |   `-- wakeup&lt;br /&gt;
|       |-- subsystem -&amp;gt; ../../../../../class/leds&lt;br /&gt;
|       |-- trigger&lt;br /&gt;
|       `-- uevent&lt;br /&gt;
|-- modalias&lt;br /&gt;
|-- power&lt;br /&gt;
|   `-- wakeup&lt;br /&gt;
|-- rfkill&lt;br /&gt;
|   `-- rfkill0&lt;br /&gt;
|       |-- claim&lt;br /&gt;
|       |-- device -&amp;gt; ../../../thinkpad_acpi&lt;br /&gt;
|       |-- index&lt;br /&gt;
|       |-- name&lt;br /&gt;
|       |-- persistent&lt;br /&gt;
|       |-- power&lt;br /&gt;
|       |   `-- wakeup&lt;br /&gt;
|       |-- state&lt;br /&gt;
|       |-- subsystem -&amp;gt; ../../../../../class/rfkill&lt;br /&gt;
|       |-- type&lt;br /&gt;
|       `-- uevent&lt;br /&gt;
|-- subsystem -&amp;gt; ../../../bus/platform&lt;br /&gt;
|-- uevent&lt;br /&gt;
|-- wakeup_hotunplug_complete&lt;br /&gt;
`-- wakeup_reason&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====thinkpad_hwmon====&lt;br /&gt;
{{path|/sys/devices/platform/thinkpad_hwmon}} directory structure is as follows on a T60 with kernel 2.6.31&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
|-- driver -&amp;gt; ../../../bus/platform/drivers/thinkpad_hwmon&lt;br /&gt;
|-- fan1_input&lt;br /&gt;
|-- hwmon&lt;br /&gt;
|   `-- hwmon0&lt;br /&gt;
|       |-- device -&amp;gt; ../../../thinkpad_hwmon&lt;br /&gt;
|       |-- power&lt;br /&gt;
|       |   `-- wakeup&lt;br /&gt;
|       |-- subsystem -&amp;gt; ../../../../../class/hwmon&lt;br /&gt;
|       `-- uevent&lt;br /&gt;
|-- modalias&lt;br /&gt;
|-- name&lt;br /&gt;
|-- power&lt;br /&gt;
|   `-- wakeup&lt;br /&gt;
|-- pwm1&lt;br /&gt;
|-- pwm1_enable&lt;br /&gt;
|-- subsystem -&amp;gt; ../../../bus/platform&lt;br /&gt;
|-- temp10_input&lt;br /&gt;
|-- temp11_input&lt;br /&gt;
|-- temp12_input&lt;br /&gt;
|-- temp13_input&lt;br /&gt;
|-- temp14_input&lt;br /&gt;
|-- temp15_input&lt;br /&gt;
|-- temp16_input&lt;br /&gt;
|-- temp1_input&lt;br /&gt;
|-- temp2_input&lt;br /&gt;
|-- temp3_input&lt;br /&gt;
|-- temp4_input&lt;br /&gt;
|-- temp5_input&lt;br /&gt;
|-- temp6_input&lt;br /&gt;
|-- temp7_input&lt;br /&gt;
|-- temp8_input&lt;br /&gt;
|-- temp9_input&lt;br /&gt;
`-- uevent&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==proc interface==&lt;br /&gt;
some legacy interfaces can also be found under {{path|/proc/acpi/ibm}} these interfaces should be considered deprecated. Please use sysfs instead.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
|-- beep&lt;br /&gt;
|-- bluetooth&lt;br /&gt;
|-- cmos&lt;br /&gt;
|-- driver&lt;br /&gt;
|-- fan&lt;br /&gt;
|-- hotkey&lt;br /&gt;
|-- led&lt;br /&gt;
|-- light&lt;br /&gt;
|-- thermal&lt;br /&gt;
|-- video&lt;br /&gt;
`-- volume&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Development==&lt;br /&gt;
To help with development and maintenance of the thinkpad-acpi driver, please add your model to the [[List of DMI IDs]].&lt;br /&gt;
&lt;br /&gt;
==Further documentation==&lt;br /&gt;
More comprehensive documentation can be found in the kernel source tree under &amp;lt;tt&amp;gt;Documentation/thinkpad-acpi.txt&amp;lt;/tt&amp;gt; or &amp;lt;tt&amp;gt;Documentation/laptops/thinkpad-acpi.txt&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== External links related to thinkpad-acpi ===&lt;br /&gt;
* [http://ibm-acpi.sf.net ibm-acpi/thinkpad-acpi main page in Sourceforge]&lt;br /&gt;
* [http://acpi.sourceforge.net Linux ACPI main page in Sourceforge], includes DSDT repository&lt;br /&gt;
* [http://www.kernel.org kernel.org main archives]&lt;br /&gt;
* [http://repo.or.cz/w/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git thinkpad-acpi development git tree]&lt;br /&gt;
&lt;br /&gt;
[[Category:Drivers]]&lt;br /&gt;
&lt;br /&gt;
=== Supported ThinkPads ===&lt;br /&gt;
* {{770X}} , {{770Z}}&lt;br /&gt;
* {{A Series}}&lt;br /&gt;
* {{G Series}}&lt;br /&gt;
* {{R Series}}&lt;br /&gt;
* {{T Series}}&lt;br /&gt;
* {{W Series}}&lt;br /&gt;
* {{X Series}}&lt;br /&gt;
* {{Z Series}}&lt;br /&gt;
* {{TransNote}}&lt;/div&gt;</summary>
		<author><name>Joei</name></author>
		
	</entry>
</feed>