ibm-acpi.txt 29 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728
  1. IBM ThinkPad ACPI Extras Driver
  2. Version 0.12
  3. 17 August 2005
  4. Borislav Deianov <borislav@users.sf.net>
  5. http://ibm-acpi.sf.net/
  6. This is a Linux ACPI driver for the IBM ThinkPad laptops. It supports
  7. various features of these laptops which are accessible through the
  8. ACPI framework but not otherwise supported by the generic Linux ACPI
  9. drivers.
  10. Status
  11. ------
  12. The features currently supported are the following (see below for
  13. detailed description):
  14. - Fn key combinations
  15. - Bluetooth enable and disable
  16. - video output switching, expansion control
  17. - ThinkLight on and off
  18. - limited docking and undocking
  19. - UltraBay eject
  20. - CMOS control
  21. - LED control
  22. - ACPI sounds
  23. - temperature sensors
  24. - Experimental: embedded controller register dump
  25. - LCD brightness control
  26. - Volume control
  27. - Experimental: fan speed, fan enable/disable
  28. - Experimental: WAN enable and disable
  29. A compatibility table by model and feature is maintained on the web
  30. site, http://ibm-acpi.sf.net/. I appreciate any success or failure
  31. reports, especially if they add to or correct the compatibility table.
  32. Please include the following information in your report:
  33. - ThinkPad model name
  34. - a copy of your DSDT, from /proc/acpi/dsdt
  35. - which driver features work and which don't
  36. - the observed behavior of non-working features
  37. Any other comments or patches are also more than welcome.
  38. Installation
  39. ------------
  40. If you are compiling this driver as included in the Linux kernel
  41. sources, simply enable the CONFIG_ACPI_IBM option (Power Management /
  42. ACPI / IBM ThinkPad Laptop Extras).
  43. Features
  44. --------
  45. The driver creates the /proc/acpi/ibm directory. There is a file under
  46. that directory for each feature described below. Note that while the
  47. driver is still in the alpha stage, the exact proc file format and
  48. commands supported by the various features is guaranteed to change
  49. frequently.
  50. Driver version -- /proc/acpi/ibm/driver
  51. ---------------------------------------
  52. The driver name and version. No commands can be written to this file.
  53. Hot keys -- /proc/acpi/ibm/hotkey
  54. ---------------------------------
  55. Without this driver, only the Fn-F4 key (sleep button) generates an
  56. ACPI event. With the driver loaded, the hotkey feature enabled and the
  57. mask set (see below), the various hot keys generate ACPI events in the
  58. following format:
  59. ibm/hotkey HKEY 00000080 0000xxxx
  60. The last four digits vary depending on the key combination pressed.
  61. All labeled Fn-Fx key combinations generate distinct events. In
  62. addition, the lid microswitch and some docking station buttons may
  63. also generate such events.
  64. The following commands can be written to this file:
  65. echo enable > /proc/acpi/ibm/hotkey -- enable the hot keys feature
  66. echo disable > /proc/acpi/ibm/hotkey -- disable the hot keys feature
  67. echo 0xffff > /proc/acpi/ibm/hotkey -- enable all possible hot keys
  68. echo 0x0000 > /proc/acpi/ibm/hotkey -- disable all possible hot keys
  69. ... any other 4-hex-digit mask ...
  70. echo reset > /proc/acpi/ibm/hotkey -- restore the original mask
  71. The bit mask allows some control over which hot keys generate ACPI
  72. events. Not all bits in the mask can be modified. Not all bits that
  73. can be modified do anything. Not all hot keys can be individually
  74. controlled by the mask. Most recent ThinkPad models honor the
  75. following bits (assuming the hot keys feature has been enabled):
  76. key bit behavior when set behavior when unset
  77. Fn-F3 always generates ACPI event
  78. Fn-F4 always generates ACPI event
  79. Fn-F5 0010 generate ACPI event enable/disable Bluetooth
  80. Fn-F7 0040 generate ACPI event switch LCD and external display
  81. Fn-F8 0080 generate ACPI event expand screen or none
  82. Fn-F9 0100 generate ACPI event none
  83. Fn-F12 always generates ACPI event
  84. Some models do not support all of the above. For example, the T30 does
  85. not support Fn-F5 and Fn-F9. Other models do not support the mask at
  86. all. On those models, hot keys cannot be controlled individually.
  87. Note that enabling ACPI events for some keys prevents their default
  88. behavior. For example, if events for Fn-F5 are enabled, that key will
  89. no longer enable/disable Bluetooth by itself. This can still be done
  90. from an acpid handler for the ibm/hotkey event.
  91. Note also that not all Fn key combinations are supported through
  92. ACPI. For example, on the X40, the brightness, volume and "Access IBM"
  93. buttons do not generate ACPI events even with this driver. They *can*
  94. be used through the "ThinkPad Buttons" utility, see
  95. http://www.nongnu.org/tpb/
  96. Bluetooth -- /proc/acpi/ibm/bluetooth
  97. -------------------------------------
  98. This feature shows the presence and current state of a Bluetooth
  99. device. If Bluetooth is installed, the following commands can be used:
  100. echo enable > /proc/acpi/ibm/bluetooth
  101. echo disable > /proc/acpi/ibm/bluetooth
  102. Video output control -- /proc/acpi/ibm/video
  103. --------------------------------------------
  104. This feature allows control over the devices used for video output -
  105. LCD, CRT or DVI (if available). The following commands are available:
  106. echo lcd_enable > /proc/acpi/ibm/video
  107. echo lcd_disable > /proc/acpi/ibm/video
  108. echo crt_enable > /proc/acpi/ibm/video
  109. echo crt_disable > /proc/acpi/ibm/video
  110. echo dvi_enable > /proc/acpi/ibm/video
  111. echo dvi_disable > /proc/acpi/ibm/video
  112. echo auto_enable > /proc/acpi/ibm/video
  113. echo auto_disable > /proc/acpi/ibm/video
  114. echo expand_toggle > /proc/acpi/ibm/video
  115. echo video_switch > /proc/acpi/ibm/video
  116. Each video output device can be enabled or disabled individually.
  117. Reading /proc/acpi/ibm/video shows the status of each device.
  118. Automatic video switching can be enabled or disabled. When automatic
  119. video switching is enabled, certain events (e.g. opening the lid,
  120. docking or undocking) cause the video output device to change
  121. automatically. While this can be useful, it also causes flickering
  122. and, on the X40, video corruption. By disabling automatic switching,
  123. the flickering or video corruption can be avoided.
  124. The video_switch command cycles through the available video outputs
  125. (it simulates the behavior of Fn-F7).
  126. Video expansion can be toggled through this feature. This controls
  127. whether the display is expanded to fill the entire LCD screen when a
  128. mode with less than full resolution is used. Note that the current
  129. video expansion status cannot be determined through this feature.
  130. Note that on many models (particularly those using Radeon graphics
  131. chips) the X driver configures the video card in a way which prevents
  132. Fn-F7 from working. This also disables the video output switching
  133. features of this driver, as it uses the same ACPI methods as
  134. Fn-F7. Video switching on the console should still work.
  135. UPDATE: There's now a patch for the X.org Radeon driver which
  136. addresses this issue. Some people are reporting success with the patch
  137. while others are still having problems. For more information:
  138. https://bugs.freedesktop.org/show_bug.cgi?id=2000
  139. ThinkLight control -- /proc/acpi/ibm/light
  140. ------------------------------------------
  141. The current status of the ThinkLight can be found in this file. A few
  142. models which do not make the status available will show it as
  143. "unknown". The available commands are:
  144. echo on > /proc/acpi/ibm/light
  145. echo off > /proc/acpi/ibm/light
  146. Docking / undocking -- /proc/acpi/ibm/dock
  147. ------------------------------------------
  148. Docking and undocking (e.g. with the X4 UltraBase) requires some
  149. actions to be taken by the operating system to safely make or break
  150. the electrical connections with the dock.
  151. The docking feature of this driver generates the following ACPI events:
  152. ibm/dock GDCK 00000003 00000001 -- eject request
  153. ibm/dock GDCK 00000003 00000002 -- undocked
  154. ibm/dock GDCK 00000000 00000003 -- docked
  155. NOTE: These events will only be generated if the laptop was docked
  156. when originally booted. This is due to the current lack of support for
  157. hot plugging of devices in the Linux ACPI framework. If the laptop was
  158. booted while not in the dock, the following message is shown in the
  159. logs:
  160. Mar 17 01:42:34 aero kernel: ibm_acpi: dock device not present
  161. In this case, no dock-related events are generated but the dock and
  162. undock commands described below still work. They can be executed
  163. manually or triggered by Fn key combinations (see the example acpid
  164. configuration files included in the driver tarball package available
  165. on the web site).
  166. When the eject request button on the dock is pressed, the first event
  167. above is generated. The handler for this event should issue the
  168. following command:
  169. echo undock > /proc/acpi/ibm/dock
  170. After the LED on the dock goes off, it is safe to eject the laptop.
  171. Note: if you pressed this key by mistake, go ahead and eject the
  172. laptop, then dock it back in. Otherwise, the dock may not function as
  173. expected.
  174. When the laptop is docked, the third event above is generated. The
  175. handler for this event should issue the following command to fully
  176. enable the dock:
  177. echo dock > /proc/acpi/ibm/dock
  178. The contents of the /proc/acpi/ibm/dock file shows the current status
  179. of the dock, as provided by the ACPI framework.
  180. The docking support in this driver does not take care of enabling or
  181. disabling any other devices you may have attached to the dock. For
  182. example, a CD drive plugged into the UltraBase needs to be disabled or
  183. enabled separately. See the provided example acpid configuration files
  184. for how this can be accomplished.
  185. There is no support yet for PCI devices that may be attached to a
  186. docking station, e.g. in the ThinkPad Dock II. The driver currently
  187. does not recognize, enable or disable such devices. This means that
  188. the only docking stations currently supported are the X-series
  189. UltraBase docks and "dumb" port replicators like the Mini Dock (the
  190. latter don't need any ACPI support, actually).
  191. UltraBay eject -- /proc/acpi/ibm/bay
  192. ------------------------------------
  193. Inserting or ejecting an UltraBay device requires some actions to be
  194. taken by the operating system to safely make or break the electrical
  195. connections with the device.
  196. This feature generates the following ACPI events:
  197. ibm/bay MSTR 00000003 00000000 -- eject request
  198. ibm/bay MSTR 00000001 00000000 -- eject lever inserted
  199. NOTE: These events will only be generated if the UltraBay was present
  200. when the laptop was originally booted (on the X series, the UltraBay
  201. is in the dock, so it may not be present if the laptop was undocked).
  202. This is due to the current lack of support for hot plugging of devices
  203. in the Linux ACPI framework. If the laptop was booted without the
  204. UltraBay, the following message is shown in the logs:
  205. Mar 17 01:42:34 aero kernel: ibm_acpi: bay device not present
  206. In this case, no bay-related events are generated but the eject
  207. command described below still works. It can be executed manually or
  208. triggered by a hot key combination.
  209. Sliding the eject lever generates the first event shown above. The
  210. handler for this event should take whatever actions are necessary to
  211. shut down the device in the UltraBay (e.g. call idectl), then issue
  212. the following command:
  213. echo eject > /proc/acpi/ibm/bay
  214. After the LED on the UltraBay goes off, it is safe to pull out the
  215. device.
  216. When the eject lever is inserted, the second event above is
  217. generated. The handler for this event should take whatever actions are
  218. necessary to enable the UltraBay device (e.g. call idectl).
  219. The contents of the /proc/acpi/ibm/bay file shows the current status
  220. of the UltraBay, as provided by the ACPI framework.
  221. EXPERIMENTAL warm eject support on the 600e/x, A22p and A3x (To use
  222. this feature, you need to supply the experimental=1 parameter when
  223. loading the module):
  224. These models do not have a button near the UltraBay device to request
  225. a hot eject but rather require the laptop to be put to sleep
  226. (suspend-to-ram) before the bay device is ejected or inserted).
  227. The sequence of steps to eject the device is as follows:
  228. echo eject > /proc/acpi/ibm/bay
  229. put the ThinkPad to sleep
  230. remove the drive
  231. resume from sleep
  232. cat /proc/acpi/ibm/bay should show that the drive was removed
  233. On the A3x, both the UltraBay 2000 and UltraBay Plus devices are
  234. supported. Use "eject2" instead of "eject" for the second bay.
  235. Note: the UltraBay eject support on the 600e/x, A22p and A3x is
  236. EXPERIMENTAL and may not work as expected. USE WITH CAUTION!
  237. CMOS control -- /proc/acpi/ibm/cmos
  238. -----------------------------------
  239. This feature is used internally by the ACPI firmware to control the
  240. ThinkLight on most newer ThinkPad models. It may also control LCD
  241. brightness, sounds volume and more, but only on some models.
  242. The commands are non-negative integer numbers:
  243. echo 0 >/proc/acpi/ibm/cmos
  244. echo 1 >/proc/acpi/ibm/cmos
  245. echo 2 >/proc/acpi/ibm/cmos
  246. ...
  247. The range of valid numbers is 0 to 21, but not all have an effect and
  248. the behavior varies from model to model. Here is the behavior on the
  249. X40 (tpb is the ThinkPad Buttons utility):
  250. 0 - no effect but tpb reports "Volume down"
  251. 1 - no effect but tpb reports "Volume up"
  252. 2 - no effect but tpb reports "Mute on"
  253. 3 - simulate pressing the "Access IBM" button
  254. 4 - LCD brightness up
  255. 5 - LCD brightness down
  256. 11 - toggle screen expansion
  257. 12 - ThinkLight on
  258. 13 - ThinkLight off
  259. 14 - no effect but tpb reports ThinkLight status change
  260. LED control -- /proc/acpi/ibm/led
  261. ---------------------------------
  262. Some of the LED indicators can be controlled through this feature. The
  263. available commands are:
  264. echo '<led number> on' >/proc/acpi/ibm/led
  265. echo '<led number> off' >/proc/acpi/ibm/led
  266. echo '<led number> blink' >/proc/acpi/ibm/led
  267. The <led number> range is 0 to 7. The set of LEDs that can be
  268. controlled varies from model to model. Here is the mapping on the X40:
  269. 0 - power
  270. 1 - battery (orange)
  271. 2 - battery (green)
  272. 3 - UltraBase
  273. 4 - UltraBay
  274. 7 - standby
  275. All of the above can be turned on and off and can be made to blink.
  276. ACPI sounds -- /proc/acpi/ibm/beep
  277. ----------------------------------
  278. The BEEP method is used internally by the ACPI firmware to provide
  279. audible alerts in various situations. This feature allows the same
  280. sounds to be triggered manually.
  281. The commands are non-negative integer numbers:
  282. echo <number> >/proc/acpi/ibm/beep
  283. The valid <number> range is 0 to 17. Not all numbers trigger sounds
  284. and the sounds vary from model to model. Here is the behavior on the
  285. X40:
  286. 0 - stop a sound in progress (but use 17 to stop 16)
  287. 2 - two beeps, pause, third beep ("low battery")
  288. 3 - single beep
  289. 4 - high, followed by low-pitched beep ("unable")
  290. 5 - single beep
  291. 6 - very high, followed by high-pitched beep ("AC/DC")
  292. 7 - high-pitched beep
  293. 9 - three short beeps
  294. 10 - very long beep
  295. 12 - low-pitched beep
  296. 15 - three high-pitched beeps repeating constantly, stop with 0
  297. 16 - one medium-pitched beep repeating constantly, stop with 17
  298. 17 - stop 16
  299. Temperature sensors -- /proc/acpi/ibm/thermal
  300. ---------------------------------------------
  301. Most ThinkPads include six or more separate temperature sensors but
  302. only expose the CPU temperature through the standard ACPI methods.
  303. This feature shows readings from up to eight different sensors on older
  304. ThinkPads, and it has experimental support for up to sixteen different
  305. sensors on newer ThinkPads. Readings from sensors that are not available
  306. return -128.
  307. No commands can be written to this file.
  308. EXPERIMENTAL: The 16-sensors feature is marked EXPERIMENTAL because the
  309. implementation directly accesses hardware registers and may not work as
  310. expected. USE WITH CAUTION! To use this feature, you need to supply the
  311. experimental=1 parameter when loading the module. When EXPERIMENTAL
  312. mode is enabled, reading the first 8 sensors on newer ThinkPads will
  313. also use an new experimental thermal sensor access mode.
  314. For example, on the X40, a typical output may be:
  315. temperatures: 42 42 45 41 36 -128 33 -128
  316. EXPERIMENTAL: On the T43/p, a typical output may be:
  317. temperatures: 48 48 36 52 38 -128 31 -128 48 52 48 -128 -128 -128 -128 -128
  318. The mapping of thermal sensors to physical locations varies depending on
  319. system-board model (and thus, on ThinkPad model).
  320. http://thinkwiki.org/wiki/Thermal_Sensors is a public wiki page that
  321. tries to track down these locations for various models.
  322. Most (newer?) models seem to follow this pattern:
  323. 1: CPU
  324. 2: (depends on model)
  325. 3: (depends on model)
  326. 4: GPU
  327. 5: Main battery: main sensor
  328. 6: Bay battery: main sensor
  329. 7: Main battery: secondary sensor
  330. 8: Bay battery: secondary sensor
  331. 9-15: (depends on model)
  332. For the R51 (source: Thomas Gruber):
  333. 2: Mini-PCI
  334. 3: Internal HDD
  335. For the T43, T43/p (source: Shmidoax/Thinkwiki.org)
  336. http://thinkwiki.org/wiki/Thermal_Sensors#ThinkPad_T43.2C_T43p
  337. 2: System board, left side (near PCMCIA slot), reported as HDAPS temp
  338. 3: PCMCIA slot
  339. 9: MCH (northbridge) to DRAM Bus
  340. 10: ICH (southbridge), under Mini-PCI card, under touchpad
  341. 11: Power regulator, underside of system board, below F2 key
  342. The A31 has a very atypical layout for the thermal sensors
  343. (source: Milos Popovic, http://thinkwiki.org/wiki/Thermal_Sensors#ThinkPad_A31)
  344. 1: CPU
  345. 2: Main Battery: main sensor
  346. 3: Power Converter
  347. 4: Bay Battery: main sensor
  348. 5: MCH (northbridge)
  349. 6: PCMCIA/ambient
  350. 7: Main Battery: secondary sensor
  351. 8: Bay Battery: secondary sensor
  352. EXPERIMENTAL: Embedded controller register dump -- /proc/acpi/ibm/ecdump
  353. ------------------------------------------------------------------------
  354. This feature is marked EXPERIMENTAL because the implementation
  355. directly accesses hardware registers and may not work as expected. USE
  356. WITH CAUTION! To use this feature, you need to supply the
  357. experimental=1 parameter when loading the module.
  358. This feature dumps the values of 256 embedded controller
  359. registers. Values which have changed since the last time the registers
  360. were dumped are marked with a star:
  361. [root@x40 ibm-acpi]# cat /proc/acpi/ibm/ecdump
  362. EC +00 +01 +02 +03 +04 +05 +06 +07 +08 +09 +0a +0b +0c +0d +0e +0f
  363. EC 0x00: a7 47 87 01 fe 96 00 08 01 00 cb 00 00 00 40 00
  364. EC 0x10: 00 00 ff ff f4 3c 87 09 01 ff 42 01 ff ff 0d 00
  365. EC 0x20: 00 00 00 00 00 00 00 00 00 00 00 03 43 00 00 80
  366. EC 0x30: 01 07 1a 00 30 04 00 00 *85 00 00 10 00 50 00 00
  367. EC 0x40: 00 00 00 00 00 00 14 01 00 04 00 00 00 00 00 00
  368. EC 0x50: 00 c0 02 0d 00 01 01 02 02 03 03 03 03 *bc *02 *bc
  369. EC 0x60: *02 *bc *02 00 00 00 00 00 00 00 00 00 00 00 00 00
  370. EC 0x70: 00 00 00 00 00 12 30 40 *24 *26 *2c *27 *20 80 *1f 80
  371. EC 0x80: 00 00 00 06 *37 *0e 03 00 00 00 0e 07 00 00 00 00
  372. EC 0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  373. EC 0xa0: *ff 09 ff 09 ff ff *64 00 *00 *00 *a2 41 *ff *ff *e0 00
  374. EC 0xb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  375. EC 0xc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  376. EC 0xd0: 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  377. EC 0xe0: 00 00 00 00 00 00 00 00 11 20 49 04 24 06 55 03
  378. EC 0xf0: 31 55 48 54 35 38 57 57 08 2f 45 73 07 65 6c 1a
  379. This feature can be used to determine the register holding the fan
  380. speed on some models. To do that, do the following:
  381. - make sure the battery is fully charged
  382. - make sure the fan is running
  383. - run 'cat /proc/acpi/ibm/ecdump' several times, once per second or so
  384. The first step makes sure various charging-related values don't
  385. vary. The second ensures that the fan-related values do vary, since
  386. the fan speed fluctuates a bit. The third will (hopefully) mark the
  387. fan register with a star:
  388. [root@x40 ibm-acpi]# cat /proc/acpi/ibm/ecdump
  389. EC +00 +01 +02 +03 +04 +05 +06 +07 +08 +09 +0a +0b +0c +0d +0e +0f
  390. EC 0x00: a7 47 87 01 fe 96 00 08 01 00 cb 00 00 00 40 00
  391. EC 0x10: 00 00 ff ff f4 3c 87 09 01 ff 42 01 ff ff 0d 00
  392. EC 0x20: 00 00 00 00 00 00 00 00 00 00 00 03 43 00 00 80
  393. EC 0x30: 01 07 1a 00 30 04 00 00 85 00 00 10 00 50 00 00
  394. EC 0x40: 00 00 00 00 00 00 14 01 00 04 00 00 00 00 00 00
  395. EC 0x50: 00 c0 02 0d 00 01 01 02 02 03 03 03 03 bc 02 bc
  396. EC 0x60: 02 bc 02 00 00 00 00 00 00 00 00 00 00 00 00 00
  397. EC 0x70: 00 00 00 00 00 12 30 40 24 27 2c 27 21 80 1f 80
  398. EC 0x80: 00 00 00 06 *be 0d 03 00 00 00 0e 07 00 00 00 00
  399. EC 0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  400. EC 0xa0: ff 09 ff 09 ff ff 64 00 00 00 a2 41 ff ff e0 00
  401. EC 0xb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  402. EC 0xc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  403. EC 0xd0: 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  404. EC 0xe0: 00 00 00 00 00 00 00 00 11 20 49 04 24 06 55 03
  405. EC 0xf0: 31 55 48 54 35 38 57 57 08 2f 45 73 07 65 6c 1a
  406. Another set of values that varies often is the temperature
  407. readings. Since temperatures don't change vary fast, you can take
  408. several quick dumps to eliminate them.
  409. You can use a similar method to figure out the meaning of other
  410. embedded controller registers - e.g. make sure nothing else changes
  411. except the charging or discharging battery to determine which
  412. registers contain the current battery capacity, etc. If you experiment
  413. with this, do send me your results (including some complete dumps with
  414. a description of the conditions when they were taken.)
  415. LCD brightness control -- /proc/acpi/ibm/brightness
  416. ---------------------------------------------------
  417. This feature allows software control of the LCD brightness on ThinkPad
  418. models which don't have a hardware brightness slider. The available
  419. commands are:
  420. echo up >/proc/acpi/ibm/brightness
  421. echo down >/proc/acpi/ibm/brightness
  422. echo 'level <level>' >/proc/acpi/ibm/brightness
  423. The <level> number range is 0 to 7, although not all of them may be
  424. distinct. The current brightness level is shown in the file.
  425. Volume control -- /proc/acpi/ibm/volume
  426. ---------------------------------------
  427. This feature allows volume control on ThinkPad models which don't have
  428. a hardware volume knob. The available commands are:
  429. echo up >/proc/acpi/ibm/volume
  430. echo down >/proc/acpi/ibm/volume
  431. echo mute >/proc/acpi/ibm/volume
  432. echo 'level <level>' >/proc/acpi/ibm/volume
  433. The <level> number range is 0 to 15 although not all of them may be
  434. distinct. The unmute the volume after the mute command, use either the
  435. up or down command (the level command will not unmute the volume).
  436. The current volume level and mute state is shown in the file.
  437. EXPERIMENTAL: fan speed, fan enable/disable -- /proc/acpi/ibm/fan
  438. -----------------------------------------------------------------
  439. This feature is marked EXPERIMENTAL because the implementation
  440. directly accesses hardware registers and may not work as expected. USE
  441. WITH CAUTION! To use this feature, you need to supply the
  442. experimental=1 parameter when loading the module.
  443. This feature attempts to show the current fan speed, control mode and
  444. other fan data that might be available. The speed is read directly
  445. from the hardware registers of the embedded controller. This is known
  446. to work on later R, T and X series ThinkPads but may show a bogus
  447. value on other models.
  448. Most ThinkPad fans work in "levels". Level 0 stops the fan. The higher
  449. the level, the higher the fan speed, although adjacent levels often map
  450. to the same fan speed. 7 is the highest level, where the fan reaches
  451. the maximum recommended speed. Level "auto" means the EC changes the
  452. fan level according to some internal algorithm, usually based on
  453. readings from the thermal sensors. Level "disengaged" means the EC
  454. disables the speed-locked closed-loop fan control, and drives the fan as
  455. fast as it can go, which might exceed hardware limits, so use this level
  456. with caution.
  457. The fan usually ramps up or down slowly from one speed to another,
  458. and it is normal for the EC to take several seconds to react to fan
  459. commands.
  460. The fan may be enabled or disabled with the following commands:
  461. echo enable >/proc/acpi/ibm/fan
  462. echo disable >/proc/acpi/ibm/fan
  463. Placing a fan on level 0 is the same as disabling it. Enabling a fan
  464. will try to place it in a safe level if it is too slow or disabled.
  465. WARNING WARNING WARNING: do not leave the fan disabled unless you are
  466. monitoring all of the temperature sensor readings and you are ready to
  467. enable it if necessary to avoid overheating.
  468. An enabled fan in level "auto" may stop spinning if the EC decides the
  469. ThinkPad is cool enough and doesn't need the extra airflow. This is
  470. normal, and the EC will spin the fan up if the varios thermal readings
  471. rise too much.
  472. On the X40, this seems to depend on the CPU and HDD temperatures.
  473. Specifically, the fan is turned on when either the CPU temperature
  474. climbs to 56 degrees or the HDD temperature climbs to 46 degrees. The
  475. fan is turned off when the CPU temperature drops to 49 degrees and the
  476. HDD temperature drops to 41 degrees. These thresholds cannot
  477. currently be controlled.
  478. The fan level can be controlled with the command:
  479. echo 'level <level>' > /proc/acpi/ibm/thermal
  480. Where <level> is an integer from 0 to 7, or one of the words "auto"
  481. or "disengaged" (without the quotes). Not all ThinkPads support the
  482. "auto" and "disengaged" levels.
  483. On the X31 and X40 (and ONLY on those models), the fan speed can be
  484. controlled to a certain degree. Once the fan is running, it can be
  485. forced to run faster or slower with the following command:
  486. echo 'speed <speed>' > /proc/acpi/ibm/thermal
  487. The sustainable range of fan speeds on the X40 appears to be from
  488. about 3700 to about 7350. Values outside this range either do not have
  489. any effect or the fan speed eventually settles somewhere in that
  490. range. The fan cannot be stopped or started with this command.
  491. The ThinkPad's ACPI DSDT code will reprogram the fan on its own when
  492. certain conditions are met. It will override any fan programming done
  493. through ibm-acpi.
  494. EXPERIMENTAL: WAN -- /proc/acpi/ibm/wan
  495. ---------------------------------------
  496. This feature is marked EXPERIMENTAL because the implementation
  497. directly accesses hardware registers and may not work as expected. USE
  498. WITH CAUTION! To use this feature, you need to supply the
  499. experimental=1 parameter when loading the module.
  500. This feature shows the presence and current state of a WAN (Sierra
  501. Wireless EV-DO) device. If WAN is installed, the following commands can
  502. be used:
  503. echo enable > /proc/acpi/ibm/wan
  504. echo disable > /proc/acpi/ibm/wan
  505. It was tested on a Lenovo Thinkpad X60. It should probably work on other
  506. Thinkpad models which come with this module installed.
  507. Multiple Commands, Module Parameters
  508. ------------------------------------
  509. Multiple commands can be written to the proc files in one shot by
  510. separating them with commas, for example:
  511. echo enable,0xffff > /proc/acpi/ibm/hotkey
  512. echo lcd_disable,crt_enable > /proc/acpi/ibm/video
  513. Commands can also be specified when loading the ibm_acpi module, for
  514. example:
  515. modprobe ibm_acpi hotkey=enable,0xffff video=auto_disable
  516. The ibm-acpi kernel driver can be programmed to revert the fan level
  517. to a safe setting if userspace does not issue one of the fan commands:
  518. "enable", "disable", "level" or "watchdog" within a configurable
  519. ammount of time. To do this, use the "watchdog" command.
  520. echo 'watchdog <interval>' > /proc/acpi/ibm/fan
  521. Interval is the ammount of time in seconds to wait for one of the
  522. above mentioned fan commands before reseting the fan level to a safe
  523. one. If set to zero, the watchdog is disabled (default). When the
  524. watchdog timer runs out, it does the exact equivalent of the "enable"
  525. fan command.
  526. Note that the watchdog timer stops after it enables the fan. It will
  527. be rearmed again automatically (using the same interval) when one of
  528. the above mentioned fan commands is received. The fan watchdog is,
  529. therefore, not suitable to protect against fan mode changes made
  530. through means other than the "enable", "disable", and "level" fan
  531. commands.
  532. Example Configuration
  533. ---------------------
  534. The ACPI support in the kernel is intended to be used in conjunction
  535. with a user-space daemon, acpid. The configuration files for this
  536. daemon control what actions are taken in response to various ACPI
  537. events. An example set of configuration files are included in the
  538. config/ directory of the tarball package available on the web
  539. site. Note that these are provided for illustration purposes only and
  540. may need to be adapted to your particular setup.
  541. The following utility scripts are used by the example action
  542. scripts (included with ibm-acpi for completeness):
  543. /usr/local/sbin/idectl -- from the hdparm source distribution,
  544. see http://www.ibiblio.org/pub/Linux/system/hardware
  545. /usr/local/sbin/laptop_mode -- from the Linux kernel source
  546. distribution, see Documentation/laptop-mode.txt
  547. /sbin/service -- comes with Redhat/Fedora distributions
  548. /usr/sbin/hibernate -- from the Software Suspend 2 distribution,
  549. see http://softwaresuspend.berlios.de/
  550. Toan T Nguyen <ntt@physics.ucla.edu> notes that Suse uses the
  551. powersave program to suspend ('powersave --suspend-to-ram') or
  552. hibernate ('powersave --suspend-to-disk'). This means that the
  553. hibernate script is not needed on that distribution.
  554. Henrik Brix Andersen <brix@gentoo.org> has written a Gentoo ACPI event
  555. handler script for the X31. You can get the latest version from
  556. http://dev.gentoo.org/~brix/files/x31.sh
  557. David Schweikert <dws@ee.eth.ch> has written an alternative blank.sh
  558. script which works on Debian systems. This scripts has now been
  559. extended to also work on Fedora systems and included as the default
  560. blank.sh in the distribution.