https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=84.191.139.74&feedformat=atomThinkWiki - User contributions [en]2024-03-28T12:37:49ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=ThinkPad_Button&diff=8242ThinkPad Button2005-07-20T09:36:33Z<p>84.191.139.74: </p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:Accessibm.png]]<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
The Access IBM Button is a button situated in the upper left corner of the keyboard on modern ThinkPads. It is intended to be a means of quick access to help and support. Technically it is nothing else than a button that can be configured to launch a certain piece of software.<br />
<br />
On earlier models this button is labelled "ThinkPad".<br />
</div><br />
|}<br />
__NOTOC__<br />
== Linux support ==<br />
Under Linux, the IBM ThinkPad(tm) special keys can be enabled using [[tpb]].<br />
<br />
I.e., to make pressing the Access IBM Button launch ntpctl, add the following line {{path|/etc/tpbrc}} file: <br />
THINKPAD /usr/bin/X11/xterm -T ntpctl -e ntpctl<br />
<br />
To make pressing the Access IBM Button launch the ThinkWiki homepage, add the following line: <br />
<nowiki>THINKPAD /usr/bin/firefox http://www.thinkwiki.org</nowiki><br />
<br />
See the [[tpb]] page and the [[How to get special keys to work | ThinkPad special keys HOWTO]] for more information.<br />
<br />
<br />
== {{Windows}} support (2000 or XP) ==<br />
If you want to customize the program that is launched when the Access IBM button is pressed while<br />
the machine is running Windows (2000 or XP) you can change the following registry entry:<br />
<br />
<code>HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TPHOTKEY\8001</code><br />
<br />
Here are the default values:<br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TPHOTKEY\8001]<br />
"File"="C:\\Program Files\\IBM\\Access IBM\\\\aibm.exe"<br />
"DispName"="Access IBM"<br />
<br />
== Related Links ==<br />
*[http://www.pc.ibm.com/us/think/thinkvantagetech/accessibm.html IBMs Access IBM ThinkVantage Technology page]<br />
*[http://www-3.ibm.com/pc/support/site.wss/AIBM-TOOLS.html Access IBM - Customization Guide]<br />
<br />
<br />
==Models featuring this Technology==<br />
*ThinkPad {{A Series}}<br />
*ThinkPad {{G Series}}<br />
*ThinkPad {{R Series}}<br />
*ThinkPad {{T Series}}<br />
*ThinkPad {{X Series}}<br />
<br />
<br />
[[Category:Glossary]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=IrDA&diff=8235IrDA2005-07-20T09:35:40Z<p>84.191.139.74: </p>
<hr />
<div>== ThinkPad IrDA configuration ==<br />
<br />
IrDA can be used to communicate using Infrared to other IrDA compliant devices, such as other Notebooks, PDA's and mobile phones.<br />
<br />
All IBM ThinkPads manufactured in the last years have integrated IrDA that can be used in one of two modes, SIR or FIR.<br />
Some very old ThinkPads only support SIR mode, or might not have IrDA support at all.<br />
<br />
The purpose of this document is to get the IrDA hardware in your ThinkPad operational, setting up communication to other devices is not covered. However, the external links section can prove useful for this.<br />
<br />
=== Serial IR (SIR) ===<br />
SIR is limited to serial datarates up to 115.2Kb/s<br />
<br />
==== Linux 2.4 kernel config ====<br />
Edit {{path|/etc/modules.conf}} and add the following lines<br />
alias tty-ldisc-11 irtty<br />
alias char-major-161 ircomm-tty<br />
<br />
=== Fast IR (FIR) ===<br />
FIR is the preferred mode of IrDA operation and operates at a bandwidth of 4 Mbps<br />
==== BIOS settings ====<br />
Main problem here is that the chips FIR mode needs to be activated. On A, G, R, T and X model ThinkPads, the easiest way to activate FIR mode is by entering BIOS setup during boot-up by pressing {{key|F1}} when prompted.<br />
Then, selecting 'Config' followed by 'Infrared' will allow you to control the IrDA operation. Here you will need to select the option to Enable the infra-red port. Be sure to save the changes, and then Exit.<br />
<br />
Note: Changing these BIOS settings do not affect Windows 2000 or XP operating systems, but may cause memory resource issues in older windows versions, or other legacy operating systems.<br />
==== PnP settings from Linux ====<br />
If changing the BIOS setting is not an option or if the settings cannot be altered, as on some older ThinkPads, the FIR mode can be activated by running Linux OS with one of the following:<br />
<br />
* setpnp as part of the old pcmcia-utils source package<br />
* tpctl, but only for some old ThinkPads<br />
<br />
setpnp requires a kernel with pnp-bios support compiled in, which the {{Redhat}} and {{Fedora}} kernels lack.<br />
==== ISA PnP patch ====<br />
2.6 kernel ISA PnP Patches exist for the nsc-ircc driver, that allow the loading of the driver without the BIOS, setpnp or tpctl hacks.<br><br />
You will still have to call setserial and set the dongle_id parameter, as shown below.<br />
<br />
* [http://steffenpingel.de/patches/nsc-ircc-pnp.diff 2.6.10 patch]<br />
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12-rc6.diff 2.6.12-rc6 patch] (applies cleanly on 2.6.12 as well)<br />
<br />
==== Linux 2.4 kernel config ====<br />
Edit {{path|/etc/modules.conf}} and add the following lines<br />
<br />
alias irda0 nsc-ircc<br />
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3<br />
pre-install nsc-ircc setserial /dev/ttyS1 uart none port 0 irq 0<br />
<br />
==== Linux 2.6 kernel config ====<br />
Edit {{path|/etc/modprobe.conf}} and add the following lines<br />
<br />
alias irda0 nsc-ircc<br />
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3<br />
install nsc-ircc /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install nsc-ircc<br />
<br />
=== Very Fast IR (VFIR) ===<br />
A newer VFIR standard exists, which supports speeds upto 16Mbps.<br><br />
However for the moment no ThinkPads support this.<br />
=== Known problems ===<br />
* If the FIR mode is not activated, attempts to load the nsc-ircc module will result in an error in syslog of "Wrong chip version ff".<br />
* after suspend the nsc-ircc module needs to be manually reloaded<br />
* Module reloading does not work for me after a suspend. The IrDA port has to be actived.<br />
rmmod nsc_ircc<br />
echo disable > /sys/devices/pnp0/00\:0d/resources<br />
echo activate > /sys/devices/pnp0/00\:0d/resources<br />
modprobe nsc_ircc<br />
<br />
=== Some other things you might want to do with IrDA ===<br />
<br />
* add fast PPP support:<br />
:{{cmdroot|modprobe irnet}}<br />
* if needed, limit further the size of the transmit window<br />
:{{cmdroot|echo 1 > /proc/sys/net/irda/max_tx_window}}<br />
<br />
== External links ==<br />
*[http://irda.sourceforge.net/ Linux-IrDA Project] (External)<br />
*[http://pcmcia-cs.sourceforge.net/ Linux PCMCIA Project] (External)<br />
*[http://tpctl.sourceforge.net/ tpctl homepage] (External)<br />
<br />
== Supported Models ==<br />
'''IrDA 1.0 (SIR - 115Kbps)'''<br />
* {{365C}}, {{365CD}}, {{365CS}}, {{365CSD}}, {{365E}}, {{365ED}}, {{365X}}, {{365XD}}<br />
* {{560}}<br />
* {{755CD}}, {{755CDV}}, {{755CE}}, {{755CSE}}, {{755CV}}, {{755CX}}<br />
* {{760C}}, {{760CD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760L}}, {{760LD}}, {{760XD}}, {{760XL}}<br />
* {{765D}}, {{765L}}<br />
* {{PC110}}<br />
'''IrDA 1.1 (FIR - 4Mbps)'''<br />
* {{240}}, {{240X}}<br />
* {{380}}, {{380D}}, {{380E}}, {{380ED}}, {{380XD}}, {{380Z}}<br />
* {{385D}}, {{385ED}}, {{385XD}}<br />
* {{390}}, {{390E}}, {{390X}}<br />
* {{560E}}, {{560X}}, {{560Z}}<br />
* {{570}}, {{570E}}<br />
* {{600}}, {{600E}}, {{600X}}<br />
* {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}<br />
* {{A Series}}<br />
* {{i1720}}, {{i1721}}<br />
* {{R Series}}<br />
* {{T Series}}<br />
* {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}} and {{X41T}}<br />
* {{TransNote}}<br />
<br />
[[Category:Drivers]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_get_special_keys_to_work&diff=6969How to get special keys to work2005-07-20T09:30:42Z<p>84.191.139.74: </p>
<hr />
<div>==Overview==<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
! key !! standard function !! tools supporting key{{footnote|1}} !! configurability !! remarks<br />
|-<br />
| {{key|Fn}} || - || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || on release without completed key combination<br />
|-<br />
| {{key|Fn}}{{key|F3}} || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||<br />
|-<br />
| {{key|Fn}}{{key|F4}} || suspend to ram || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||<br />
|-<br />
| {{key|Fn}}{{key|F5}} || switch bluetooth || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models starting from 2002<br />
|-<br />
| {{key|Fn}}{{key|F7}} || switch display || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions || <br />
|-<br />
| {{key|Fn}}{{key|F8}} || toggle display expansion || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions ||<br />
|-<br />
| {{key|Fn}}{{key|F9}} || eject from dock || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||<br />
|-<br />
| {{key|Fn}}{{key|F12}} || hibernate || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||<br />
|-<br />
| {{key|Fn}}{{key|Pos1}} || brightness up || [[#tpb configuration|tpb]] || additional actions ||<br />
|-<br />
| {{key|Fn}}{{key|End}} || brightness down || [[#tpb configuration|tpb]] || additional actions ||<br />
|-<br />
| {{key|Fn}}{{key|PageUp}} || toggle thinklight || [[#ibm-acpi events|ibm-acpi]], [[#tpb configuration|tpb]] || additional actions ||<br />
|-<br />
| {{key|Fn}}{{key|Space}} || toggle zoom || [[#tpb configuration|tpb]] || full ||<br />
|-<br />
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || help application || [[#tpb configuration|tpb]] || full ||<br />
|-<br />
| {{ibmkey|Home|#494949}} || open web browser || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards<br />
|-<br />
| {{ibmkey|Search|#494949}} || open search application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards<br />
|-<br />
| {{ibmkey|Mail|#494949}} || open mail application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards<br />
|-<br />
| {{ibmkey|Favorites|#494949}} || open favorites || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards<br />
|-<br />
| {{ibmkey|Reload|#494949}} || reload web page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards<br />
|-<br />
| {{ibmkey|Abort|#494949}} || abort loading page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards<br />
|-<br />
| {{ibmkey|Backward|#494949}} || previous page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and Thinkpads starting from 2002<br />
|-<br />
| {{ibmkey|Forward|#494949}} || next page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and Thinkpads starting from 2002<br />
|-<br />
| {{ibmkey|Volume up|#494949}} || volume up || [[#tpb configuration|tpb]] || additional actions ||<br />
|-<br />
| {{ibmkey|Volume down|#494949}} || volume down || [[#tpb configuration|tpb]] || additional actions ||<br />
|-<br />
| {{ibmkey|Volume mute|#494949}} || mute volume || [[#tpb configuration|tpb]] || additional actions ||<br />
|-<br />
| {{ibmkey|Power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press<br />
|-<br />
| Display lid || blank screen || [[#ibm-acpi events|ibm-acpi]] || full ||<br />
|-<br />
| Ultrabay lid || announce ultrabay change || [[#ibm-acpi events|ibm-acpi]] || full ||<br />
|-<br />
| Dock eject || eject from dock || [[#ibm-acpi events|ibm-acpi]] || full ||<br />
|}<br />
<br />
==Triggering key events==<br />
===ibm-acpi events===<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+ events triggered by [[ibm-acpi]] for {{path|/etc/acpi/events}} files<br />
! key !! event<br />
|-<br />
| {{key|Fn}}{{key|F3}} || ibm/hotkey HKEY 00000080 00001003<br />
|-<br />
| {{key|Fn}}{{key|F4}} || ibm/hotkey HKEY 00000080 00001004<br />
|-<br />
| {{key|Fn}}{{key|F5}} || ibm/hotkey HKEY 00000080 00001005<br />
|-<br />
| {{key|Fn}}{{key|F7}} || ibm/hotkey HKEY 00000080 00001007<br />
|-<br />
| {{key|Fn}}{{key|F8}} || ibm/hotkey HKEY 00000080 00001008<br />
|-<br />
| {{key|Fn}}{{key|F9}} || ibm/hotkey HKEY 00000080 00001009<br />
|-<br />
| {{key|Fn}}{{key|F12}} || ibm/hotkey HKEY 00000080 0000100c<br />
|-<br />
| {{ibmkey|Power|#494949}} || button/power PWRF 00000080 xxxxxxxx<br />
|-<br />
| Display lid || button/lid LID 00000080 xxxxxxxx<br />
|-<br />
| Ultrabay eject || ibm/bay MSTR 00000003 00000000<br />
|-<br />
| Ultrabay inserted || ibm/bay MSTR 00000001 00000000<br />
|-<br />
| Dock eject || ibm/dock GDCK 00000003 00000001<br />
|}<br />
<br />
===tpb configuration===<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+ configuration keywords for [[tpb]] (to put in {{path|/etc/tpbrc}})<br />
! key !! config keyword<br />
|-<br />
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || THINKPAD<br />
|-<br />
| {{ibmkey|Home|#494949}} || HOME<br />
|-<br />
| {{ibmkey|Search|#494949}} || SEARCH<br />
|-<br />
| {{ibmkey|Mail|#494949}} || MAIL<br />
|-<br />
| {{ibmkey|Favorites|#494949}} || FAVORITES<br />
|-<br />
| {{ibmkey|Reload|#494949}} || RELOAD<br />
|-<br />
| {{ibmkey|Abort|#494949}} || ABORT<br />
|-<br />
| {{ibmkey|Backward|#494949}} || BACKWARD<br />
|-<br />
| {{ibmkey|Forward|#494949}} || FORWARD<br />
|-<br />
| {{key|Fn}} || FN<br />
|-<br />
| {{key|Fn}}{{key|Space}} || CALLBACK (zoom on/off)<br />
|-<br />
| {{key|Fn}}{{key|PageUp}} || CALLBACK (thinklight on/off)<br />
|-<br />
| {{key|Fn}}{{key|F7}} || CALLBACK (display lcd/crt/both)<br />
|-<br />
| {{key|Fn}}{{key|F8}} || CALLBACK (expand on/off)<br />
|-<br />
| {{key|Fn}}{{key|Home}} || CALLBACK (brightness <percent>)<br />
|-<br />
| {{key|Fn}}{{key|End}} || CALLBACK (brightness <percent>)<br />
|-<br />
| {{ibmkey|Volume up|#494949}} || CALLBACK (volume <percent>)<br />
|-<br />
| {{ibmkey|Volume down|#494949}} || CALLBACK (volume <percent>)<br />
|-<br />
| {{ibmkey|Volume mute|#494949}} || CALLBACK (mute on/off)<br />
|}<br />
<br />
To all parameter keywords should be assigned the full path to the executables supposed to be started on key press.<br />
The exectable provided for the CALLBACK keyword should take the parameters given in parentheses and act according to them.<br />
If you want to use xmodmap for the HOME, SEARCH, MAIL, FAVORITES, RELOAD, ABORT, BACKWARD, FORWARD and FN keys you should<br />
provide a <tt>XEVENTS=off</tt> in your {{path|/etc/tpbrc}}.<br />
<br />
===xmodmap configuration===<br />
xmodmap enables you to edit the modifier map and keymap tables that are used to translate keycodes into keysyms.<br />
Understood? Well, basically it allows you to give the X server a dictionary for the translation of keycodes like "97" into more human readable synonyms like "Home". This way xmodmap allows you to make the special keys of your keyboard known to X applications.<br />
<br />
Usually you should write your keycode-keysym associations into the file {{path|~/.Xmodmap}}. This file is usually read by the X session startup scripts of your system, so that the mappings automatically get included everytime you run the X server.<br />
<br />
The {{path|~/.Xmodmap}} lines for our purpose are in the form of<br />
keycode <keycode> = <keysym><br />
<br />
The following table shows the keycodes generated by the Thinkpad special keys and sensible keysyms to assign them to.<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+ keycodes and recommended keysyms<br />
! key !! keycode !! keysym<br />
|-<br />
| {{ibmkey|Backward|#494949}} || 234 || XF86Back or F21<br />
|-<br />
| {{ibmkey|Forward|#494949}} || 233 || XF86Forward or F22<br />
|-<br />
| {{ibmkey|Home|#494949}} || 178 || XF86HomePage<br />
|-<br />
| {{ibmkey|Search|#494949}} || 229 || XF86Search<br />
|-<br />
| {{ibmkey|Mail|#494949}} || 236 || XF86Mail<br />
|-<br />
| {{ibmkey|Favorites|#494949}} || 230 || XF86AddFavorite or XF86Favorites<br />
|-<br />
| {{ibmkey|Reload|#494949}} || 231 || XF86Reload<br />
|-<br />
| {{ibmkey|Abort|#494949}} || 232 || XF86Stop<br />
|-<br />
| {{key|Fn}} || 227 || F35<br />
|}<br />
<br />
(In case you want to use the browser keys in Firefox, you will have to assign the F21 and F22 or similar keysyms to them.)<br />
<br />
Note: if you are running [[tpb]] you might need to add the line <tt>XEVENTS=off</tt> into your tpbrc to stop it from grabbing the key events and allow them to get through to X instead.<br />
<br />
==Example Applications==<br />
===Web Browsers===<br />
====Firefox====<br />
(First of all thanks go to Ryan Barrett for writing the little howto on his blog.)<br /><br />
To have firefox make use of the browser keys you need to modify one of its files.<br />
To do this you will first need to extract it from the {{path|browser.jar}} archive. Do...<br />
<br />
:{{cmdroot|cd <firefox-directory>/chrome}}<br /><br />
:{{cmdroot|unzip browser.jar}}<br />
<br />
The file of interest is {{path|content/browser/browser.xul}}. Edit it...<br />
:{{cmdroot|vi content/browser/browser.xul}}<br />
<br />
Look for the '''<keyset id="mainKeyset">''' section and add the following lines within...<br />
<key id="goBackTP" keycode="VK_F21" command="Browser:Back" /><br />
<key id="goForwardTP" keycode="VK_F22" command="Browser:Forward" /><br />
Now save the file and repackage the {{path|browser.jar}} archive...<br />
:{{cmdroot|zip -rD0 browser.jar content/browser/}}<br />
<br />
That's it.<br />
<br />
Another interesting Page on Firefox is http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ It uses different key mappings (F19 resp. F20) but a ready .xpi is provided which is pretty comfortable.<br />
<br />
====Firefox and KDE====<br />
KDE provides Khotkeys. Get into the KDE system controls (kcontrol) and just assign keyboard inputs "Alt+Left" and "Alt+Right" to the two browser keys. That way, you don't need to mess around with the firefox internals. Maybe, you'll need to set up {{path|~/.Xmodmap}} as described [[#xmodmap configuration|above]] in order to assign them the symbols XF86Back and XF86Forward.<br />
<br />
====Opera====<br />
However this isn't a simple configration file, you can set your browser manually.<br /><br />
Go to <i>Tool > Settings > Mouse and keyboard > Keyboard settings > Edit > Browser Window</i>. There add F21 - Back and F22 - Forward. Now you can surf using your TP keys ;-)<br />
<br />
===Window Managers===<br />
====fvwm====<br />
To get the Backwards and Forwards keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fvwmrc}}:<br />
Key XF86Back A A Scroll -100000 0<br />
Key XF86Forward A A Scroll +100000 0<br />
If you use multiple virtual desktops, you could instead use the keys to flip between them by using GotoDesk.<br />
<br />
====pekwm configuration====<br />
You can make the two browser keys switch workspaces in pekwm, by adding the following two lines to the {{path|~/.pekwm/keys}} file:<br />
KeyPress = "Mod1 XF86Back" { Actions = "GoToWorkspace prev" }<br />
KeyPress = "Mod1 XF86Forward" { Actions = "GoToWorkspace next" }<br />
<br />
====pwm====<br />
Another example how to use these two keys to switch between pwm tabs. These two lines should be added to {{path|~/.pwm/keys-default.conf}} or {{path|/etc/pwm/keys-default.conf}}:<br />
kbind "Back", "switch_rot", -1<br />
kbind "Forward", "switch_rot", 1<br />
<br />
===Other Uses===<br />
====Console tools configuraton====<br />
To make the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys useful in console, add this to your keymap ({{path|/etc/console/boottime.kmap.gz}} in {{Debian}}):<br />
keycode 158 = Decr_Console<br />
keycode 159 = Incr_Console<br />
<br />
==External Sources==<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51537 IBMs page on configuring the ThinkPad buttons (ThinkPad, Access IBM, Mail, Search, and Home buttons) under Linux]<br />
*[http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ Rob Mayoffs page on using IBM Keyboard Navigation Keys in Linux Mozilla and Firefox]<br />
*[http://snarfed.org/space/thinkpad+keys+in+firefox Ryan Barretts blog article about using the browser keys in Firefox]<br />
<br />
{{footnotes|<br />
#if there are more than one tool listed, one is sufficient<br />
}}</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_configure_powernowd&diff=15898How to configure powernowd2005-07-20T09:20:59Z<p>84.191.139.74: </p>
<hr />
<div>{{NOTE|See the [[How to make use of Dynamic Frequency Scaling|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}<br />
<br />
<br />
powernowd originally was only written for AMD CPUs which support PowerNow! technology, but it supports other CPUs as well.<br />
<br />
Make sure you have loaded the necessary kernel modules. (See [[How to make use of Dynamic Frequency Scaling]])<br />
<br />
Install "powernowd".<br />
<br />
On Debian you can do this with:<br />
:{{cmdroot|apt-get install powernowd}}<br />
<br />
Also, on Debian you may specify different options for powernowd in {{path|/etc/default/powernowd}}. This file will be loaded by the init script {{path|/etc/init.d/powernowd}}.</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_configure_powernowd&diff=6720How to configure powernowd2005-07-20T09:20:22Z<p>84.191.139.74: </p>
<hr />
<div>{{NOTE|See the [[How to make use of Dynamic Frequency Scaling|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}<br />
<br />
<br />
powernowd originally was only written for AMD CPUs which support PowerNow! technology, but it supports other CPUs as well.<br />
<br />
Make sure you have loaded the necessary kernel modules. (See [[How to make use of Dynamic Frequency Scaling]])<br />
<br />
Install "powernowd".<br />
<br />
On Debian you can do this with:<br />
:{{cmdroot|apt-get install powernowd}}<br />
<br />
Also, on Debian you may specify different options for powernowd in <tt>/etc/default/powernowd</tt>. This file will be loaded by the init script <tt>/etc/init.d/powernowd</tt>.</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_use_cpufrequtils&diff=16103How to use cpufrequtils2005-07-20T09:19:50Z<p>84.191.139.74: </p>
<hr />
<div>{{NOTE|See the [[How_to_make_use_of_Dynamic_Frequency_Scaling|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}<br />
<br />
<br />
This package mainly has 2 programs:<br />
:{{path|/usr/bin/cpufreq-info}}<br />
:{{path|/usr/bin/cpufreq-set}}<br />
<br />
cpufreq-info gives general device information:<br />
xaiki@gonzo:~$ cpufreq-info<br />
cpufrequtils 0.2: cpufreq-info (C) Dominik Brodowski 2004<br />
Report errors and bugs to linux@brodo.de, please.<br />
analyzing CPU 0:<br />
driver: speedstep-smi<br />
CPUs which need to switch frequency at the same time: 0<br />
hardware limits: 500 MHz - 700 MHz<br />
available frequency steps: 700 MHz, 500 MHz<br />
available cpufreq governors: userspace, performance<br />
current policy: frequency should be within 500 MHz and 700 MHz.<br />
The governor "userspace" may decide which speed to use<br />
within this range.<br />
current CPU frequency is 700 MHz.<br />
<br />
and cpufreq-set allows setting<br />
... Never got it working ...</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_configure_cpufreqd&diff=14762How to configure cpufreqd2005-07-20T09:19:12Z<p>84.191.139.74: </p>
<hr />
<div>{{NOTE|See the [[How_to_make_use_of_Dynamic_Frequency_Scaling|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}<br />
<br />
<br />
In Debian, all you have to do is:<br />
:{{cmdroot|apt-get install cpufreqd}}<br />
<br />
And in most cases it will work out of the box.<br />
<br />
This is the default Debian config, but works well out of the box:<br />
<br />
# this is a comment<br />
#<br />
# you need: 1 [General] section,<br />
# 1 or more [Profile] sections<br />
# 1 or more [Rule] sections<br />
#<br />
# a section ends at the first blank line<br />
#<br />
# [Rule] sample:<br />
# [Rule]<br />
# name=sample_rule<br />
# ac=on # (on/off)<br />
# battery_interval=0-10<br />
# cpu_interval=30-60<br />
# programs=xine,mplayer<br />
# profile=sample_profile<br />
#<br />
# [Profile] sample:<br />
# [Profile]<br />
# name=sample_profile<br />
# minfreq=10%<br />
# maxfreq=100%<br />
# policy=performance<br />
#<br />
# see CPUFREQD.CONF(5) manpage for a complete reference<br />
<br />
[General]<br />
pidfile=/var/run/cpufreqd.pid<br />
poll_interval=2<br />
pm_type=acpi #(acpi, apm or pmu)<br />
# Uncomment the following line to enable ACPI workaround (see cpufreqd.conf(5)) # acpi_workaround=1<br />
verbosity=4 #(if you want a minimal logging set to 5)<br />
<br />
[Profile]<br />
name=hi_boost<br />
minfreq=66%<br />
maxfreq=100%<br />
policy=performance<br />
<br />
[Profile]<br />
name=medium_boost<br />
minfreq=33%<br />
maxfreq=66%<br />
policy=performance<br />
<br />
[Profile]<br />
name=lo_boost<br />
minfreq=0%<br />
maxfreq=33%<br />
policy=performance<br />
<br />
[Profile]<br />
name=lo_power<br />
minfreq=0%<br />
maxfreq=33%<br />
policy=powersave<br />
<br />
# conservative mode when not AC<br />
[Rule]<br />
name=conservative<br />
ac=off # (on/off)<br />
battery_interval=0-100<br />
cpu_interval=0-40<br />
cpu_nice_scale=1.5<br />
delay_cycles=3<br />
profile=lo_boost<br />
<br />
# need some power<br />
[Rule]<br />
name=lo_cpu_boost<br />
ac=off # (on/off)<br />
battery_interval=0-100<br />
cpu_interval=30-80<br />
profile=medium_boost<br />
<br />
# need big power (not if battery very low)<br />
[Rule]<br />
name=hi_cpu_boost<br />
ac=off # (on/off)<br />
battery_interval=50-100<br />
cpu_interval=70-100<br />
profile=medium_boost<br />
<br />
# full power when AC<br />
[Rule]<br />
name=AC_on<br />
ac=on # (on/off)<br />
profile=hi_boost<br />
<br />
# full power when watching DVDs and not AC:<br />
# this is the last rule and takes less<br />
# precedence with respect to the others<br />
[Rule]<br />
name=dvd_watching<br />
ac=off # (on/off)<br />
battery_interval=0-100<br />
programs=xine,totem,vlc,avidemux<br />
cpu_interval=0-100<br />
profile=hi_boost</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_get_SpeedStep_working_on_P4-class-Celeron_based_ThinkPads&diff=9512How to get SpeedStep working on P4-class-Celeron based ThinkPads2005-07-20T09:18:40Z<p>84.191.139.74: </p>
<hr />
<div>==Introduction==<br />
If you have an P4-class Celeron based Thinkpad (like the {{R40e}} in my case) you can use the p4-Clockmod scaling option from 2.6 kernels to set cpu speed. Use any userspace daemon like powernowd or cpufreqd to get dynamic speedstepping to work.<br />
<br />
==Kernel config==<br />
CONFIG_CPU_FREQ=y<br />
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y<br />
CONFIG_CPU_FREQ_TABLE=y<br />
CONFIG_X86_P4_CLOCKMOD=y (for R40e, p4-class celeron, other tp's might need something different here)<br />
<br />
make sure to have the sys interface built within your kernel<br />
CONFIG_SYSFS=y<br />
<br />
==using the sysfs interface==<br />
use the sys-interface to discover and set available frequencies<br />
<br />
make sure to have sysfs mounted:<br />
add<br />
none /sys sysfs defaults 0 0<br />
to your /etc/fstab (if not already there)<br />
<br />
get available freqencies:<br />
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies}}<br />
275000 550000 825000 1100000 1375000 1650000 1925000 2200000<br />
<br />
set frequency:<br />
:{{cmdroot|echo 825000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}<br />
<br />
You can use powernowd (easier) or cpufreq (more settings) to have cpuspeed dynamically managed.<br />
<br />
==Powernowd==<br />
for powernowd use the sys interface to set the min and max speed:<br />
:{{cmdroot|echo 825000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq}}<br />
:{{cmdroot|echo 2200000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq}}<br />
:{{cmdroot|/etc/init.d/powernowd start}}<br />
<br />
On my {{R40e}} frequencies below 825000 make x almost unusable (mouse jumps around, until cpuspeed rises).<br />
<br />
==cpufreqd==<br />
TODO<br />
<br />
<br />
[[Category:R40e]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_get_SpeedStep_working_on_Coppermine-piix4-smi_based_ThinkPads&diff=10088How to get SpeedStep working on Coppermine-piix4-smi based ThinkPads2005-07-20T09:17:09Z<p>84.191.139.74: /* How to get it work */</p>
<hr />
<div>==Foreword==<br />
APPLYING THIS HOWTO MAY MAKE YOU DUMB, CRASH YOUR CPU, YOUR MOTHERBOARD, MAKE YOUR GIRLFRIEND LEAVE YOU, OR MAYBE WORSE, USE IT AT YOUR OWN RISKS, I'M NOTHING OF A KERNEL HACKER, NEITHER A SMART GUY, THIS IS HOW I TRYED TO GET IT WORK, AND TILL NOW IT IS WORKING, MY PROPOSITION ARE ALMOST GUARANTED TO BE DUMB.<br />
<br />
This HowTo is intended for people having trouble getting SpeedStep working via CpuFreq on their Coppermine CPU with a piix4 mainboard. <br />
Thinkpads known to have this configuration are the {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{T20}}, {{T21}}, {{T22}}, {{TransNote}} and possibly {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}} models.<br />
<br />
The issue is that these CPUs do not repport correctly that they are SpeedStep capable.<br />
<br />
This Document is under the GNU/GPL v2+ Licence.<br />
<br />
==My case==<br />
<!--<br />
==============================================================================<br />
(this part is intended for Google matching of people having the same logs ). <br />
==============================================================================<br />
--><br />
This is what i get:<br />
I have a x21 IBM ThinkPad, and when trying the SpeedStep implementation of 2.6 kernels i got:<br />
:{{cmd|sudo modprobe speedstep-smi}}<br />
:{{cmdresult|FATAL: Error inserting speedstep_smi (/lib/modules/2.6.10-rc1-mm4-xa1/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-smi.ko): No such device}}<br />
<br />
Rebooting with <tt>cpufreq.debug=7</tt> ( 1 is for core, 2 is for ??, and 4 is for drivers, 7 = 1 + 2 + 4 ) gave:<br />
:{{cmd|sudo modprobe speedstep-smi}}<br />
:{{cmdresult|FATAL: Error inserting speedstep_smi (/lib/modules/2.6.10-rc1-mm4-xa1/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-smi.ko): No such device}}<br />
:{{cmd|sudo tail /var/log/syslog}}<br />
:{{cmdresult|[...]}}<br />
:{{cmdresult|Nov 11 19:54:20 localhost kernel: speedstep-lib: x86: 6, model: 8}}<br />
:{{cmdresult|Nov 11 19:54:20 localhost kernel: speedstep-lib: Coppermine: MSR_IA32_EBL_CR_POWERON is 0x44080020, 0x0}}<br />
:{{cmdresult|Nov 11 19:54:20 localhost kernel: speedstep-lib: Coppermine: MSR_IA32_PLATFORM ID is 0x0, 0x540000}}<br />
:{{cmdresult|Nov 11 19:54:20 localhost kernel: speedstep-smi: No supported Intel CPU detected.}}<br />
<br />
==How to get it work==<br />
Note: to get this working on recent kernels you'll need:<br />
CONFIG_X86_SPEEDSTEP_RELAXED_CHECK = y<br />
Easy =) just disable the speedstep-lib checks<br />
:{{cmd|1=sudo modprobe speedstep-lib relaxed_check=1}}<br />
:{{cmd|sudo modprobe speedstep-smi}}<br />
Hurrah !!<br />
<br />
In Debian ( and probably with others, please confirm ), you can automate the module parmeters by creating a {{path|/etc/modprobe.d/speedstep-lib}} file with:<br />
options speedstep-lib relaxed_check=1<br />
<br />
And then, you may add these 2 lines to {{path|/etc/modules}}:<br />
speedstep-lib<br />
speedstep-smi<br />
<br />
==How to use it==<br />
[[How to make use of Dynamic Frequency Scaling]]<br />
<br />
==What's not working==<br />
The speeds shown may be erroneous, witch has dramatic consequances if you try to watch movies or applications that are (exact) time-depending (as the timer is all dizzy).</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_get_SpeedStep_working_on_Coppermine-piix4-smi_based_ThinkPads&diff=6715How to get SpeedStep working on Coppermine-piix4-smi based ThinkPads2005-07-20T09:14:35Z<p>84.191.139.74: </p>
<hr />
<div>==Foreword==<br />
APPLYING THIS HOWTO MAY MAKE YOU DUMB, CRASH YOUR CPU, YOUR MOTHERBOARD, MAKE YOUR GIRLFRIEND LEAVE YOU, OR MAYBE WORSE, USE IT AT YOUR OWN RISKS, I'M NOTHING OF A KERNEL HACKER, NEITHER A SMART GUY, THIS IS HOW I TRYED TO GET IT WORK, AND TILL NOW IT IS WORKING, MY PROPOSITION ARE ALMOST GUARANTED TO BE DUMB.<br />
<br />
This HowTo is intended for people having trouble getting SpeedStep working via CpuFreq on their Coppermine CPU with a piix4 mainboard. <br />
Thinkpads known to have this configuration are the {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{T20}}, {{T21}}, {{T22}}, {{TransNote}} and possibly {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}} models.<br />
<br />
The issue is that these CPUs do not repport correctly that they are SpeedStep capable.<br />
<br />
This Document is under the GNU/GPL v2+ Licence.<br />
<br />
==My case==<br />
<!--<br />
==============================================================================<br />
(this part is intended for Google matching of people having the same logs ). <br />
==============================================================================<br />
--><br />
This is what i get:<br />
I have a x21 IBM ThinkPad, and when trying the SpeedStep implementation of 2.6 kernels i got:<br />
:{{cmd|sudo modprobe speedstep-smi}}<br />
:{{cmdresult|FATAL: Error inserting speedstep_smi (/lib/modules/2.6.10-rc1-mm4-xa1/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-smi.ko): No such device}}<br />
<br />
Rebooting with <tt>cpufreq.debug=7</tt> ( 1 is for core, 2 is for ??, and 4 is for drivers, 7 = 1 + 2 + 4 ) gave:<br />
:{{cmd|sudo modprobe speedstep-smi}}<br />
:{{cmdresult|FATAL: Error inserting speedstep_smi (/lib/modules/2.6.10-rc1-mm4-xa1/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-smi.ko): No such device}}<br />
:{{cmd|sudo tail /var/log/syslog}}<br />
:{{cmdresult|[...]}}<br />
:{{cmdresult|Nov 11 19:54:20 localhost kernel: speedstep-lib: x86: 6, model: 8}}<br />
:{{cmdresult|Nov 11 19:54:20 localhost kernel: speedstep-lib: Coppermine: MSR_IA32_EBL_CR_POWERON is 0x44080020, 0x0}}<br />
:{{cmdresult|Nov 11 19:54:20 localhost kernel: speedstep-lib: Coppermine: MSR_IA32_PLATFORM ID is 0x0, 0x540000}}<br />
:{{cmdresult|Nov 11 19:54:20 localhost kernel: speedstep-smi: No supported Intel CPU detected.}}<br />
<br />
==How to get it work==<br />
Note: to get this working on recent kernels you'll need:<br />
CONFIG_X86_SPEEDSTEP_RELAXED_CHECK = y<br />
Easy =) just disable the speedstep-lib checks<br />
:{{cmd|sudo modprobe speedstep-lib relaxed_check=1}}<br />
:{{cmd|sudo modprobe speedstep-smi}}<br />
Hurrah !!<br />
<br />
In Debian ( and probably with others, please confirm ), you can automate the module parmeters by creating a {{path|/etc/modprobe.d/speedstep-lib}} file with:<br />
options speedstep-lib relaxed_check=1<br />
<br />
And then, you may add these 2 lines to {{path|/etc/modules}}:<br />
speedstep-lib<br />
speedstep-smi<br />
<br />
==How to use it==<br />
[[How to make use of Dynamic Frequency Scaling]]<br />
<br />
==What's not working==<br />
The speeds shown may be erroneous, witch has dramatic consequances if you try to watch movies or applications that are (exact) time-depending (as the timer is all dizzy).</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_configure_the_TrackPoint&diff=9352How to configure the TrackPoint2005-07-20T09:07:06Z<p>84.191.139.74: </p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |The [[Patch to enable advanced trackpoint configuration|kernel trackpoint driver]] is controlled by echoing values to special files. Common configuration options are outlined below.<br />
{{NOTE|<br />
Prior to kernel 2.6.11 these files were located in <tt>/proc/trackpoint</tt>.<br />
<br />
From 2.6.11 on this is no longer the case. Instead use <tt>/sys/devices/platform/i8042/serio0</tt>.<br />
<br />
(The newer form is used throughout this document.)<br />
}}<br />
|}<br />
<br />
==General Configuration==<br />
The configuration options are reflected by the files you can find in {{path|/sys/devices/platform/i8042/serio0}}. See the [[Patch to enable advanced trackpoint configuration|TrackPoint driver page]] for a complete list.<br />
Configuration is done by echoing the appropriate values into these special files.<br />
{{HINT|If <tt>echo XX > file</tt> isn't working for you, try <tt>echo -n XX > file</tt> instead}}<br />
<br />
==Most common Features==<br />
The most common settings are '''Press to Select''', '''sensitivity''', '''speed''' and '''scrolling'''.<br />
<br />
===Press to Select===<br />
Press to Select allows you to tap the control stick which will simulate a left click. You can enable this feature by typing the following in to a terminal (you may need to be root):<br />
<br />
:{{cmdroot|echo 1 > /sys/devices/platform/i8042/serio0/ptson}}<br />
<br />
Press to Select should now be enabled. You can disable it in a similar manner:<br />
<br />
:{{cmdroot|echo 0 > /sys/devices/platform/i8042/serio0/ptson}}<br />
<br />
===Sensitivity & Speed===<br />
Adjusting the speed and sensitivity of the TrackPoint requires echoing a value between 0 and 255 into the appropriate file. For example, for a speed of 120 and a sensitivity of 250, type the following into a terminal:<br />
<br />
:{{cmdroot|echo 120 > /sys/devices/platform/i8042/serio0/speed}}<br />
:{{cmdroot|echo 250 > /sys/devices/platform/i8042/serio0/sensitivity}}<br />
<br />
Feel free to experiment with your settings until you find a combination that is comfortable.<br />
<br />
===Scrolling===<br />
====Using a kernel prior to 2.6.11====<br />
The scrolling action is essentially the same as is used in the TrackPoint Windows drivers. To enable this feature, type the following in to a terminal (you may need to be root): <br />
<br />
:{{cmdroot|echo 1 > /proc/trackpoint/scroll}}<br />
<br />
Then press the middle button and push the stick up and down to scroll. Similarly, to disable scrolling:<br />
<br />
:{{cmdroot|echo 0 > /proc/trackpoint/scroll}}<br />
<br />
====Using the X server (kernel 2.6.11+)====<br />
The scroll setting has been removed from the trackpoint driver in kernel versions 2.6.11 and above. Scroll emulation should now be handled in the X server. First do:<br />
<br />
:{{cmd|echo -n 0 > /sys/devices/platform/i8042/serio0/middle_btn_disable}}<br />
<br />
Then, for versions of Xorg since ~Oct '04, add these lines to your TrackPoint configuration section in {{path|/etc/X11/xorg.conf}}:<br />
<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelButton" "2"<br />
<br />
Now restart X and hold down button 2 and move the mouse to scroll, or just press and release button 2 for a middle click.<br />
<br />
For older versions of Xorg or for Xfree86 ({{path|/etc/X11/XF86Config}}) try this:<br />
<br />
Option "Emulate3Buttons" "true"<br />
Option "EmulateWheel" "true"<br />
Option "EmulateWheelButton" "2"<br />
<br />
Now restart X and hold down button two and move the mouse for scrolling. To get a middle click, press buttons 1 and 3 simultaneously.<br />
<br />
==Soft Transparent Mode==<br />
If you wish to connect a special device to the external PS/2 port, you should consider using "Soft Transparent Mode" so that the TrackPoint controller does not interpret any commands sent to the external PS/2 port. You can enable soft transparent mode by typing the following in to a terminal:<br />
<br />
:{{cmdroot|echo 1 > /proc/trackpoint/transparent}}<br />
<br />
Disabling soft transparent mode is similar:<br />
<br />
:{{cmdroot|echo 0 > /proc/trackpoint/transparent}}</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=Additional_options_for_the_radeon_driver&diff=9019Additional options for the radeon driver2005-07-20T09:02:15Z<p>84.191.139.74: </p>
<hr />
<div>==AGP speed==<br />
<br />
By default, the open source radeon driver forces 1x AGP speed. Quote from the developers:<br />
<br />
tuning to the highest speed possible has caused hangs on some boxes, with no<br />
discernable pattern, so we default to 'slow but safe' whilst giving the option<br />
to go fast if the user wants to try it.<br />
<br />
<br />
Higher speeds can be enabled by adding '''Option "AGPMode" "X"''' (where X is a number) in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "radeon"<br />
VendorName "IBM Thinkpad"<br />
BoardName "ATIdd Mobility FireGL 7800"<br />
'''Option "AGPMode" "4"'''<br />
EndSection<br />
<br />
<br />
With this option enabled (set to 4x speed), the X11 server should print ({{path|/var/log/Xorg.0.log}}):<br />
<br />
(**) RADEON(0): Option "AGPMode" "4"<br />
(**) RADEON(0): Using AGP 4x mode<br />
<br />
<br />
==AGP Fast Writes==<br />
<br />
By default, the open source radeon driver disables AGP Fast Writes. Fast Writes can be enabled by adding '''Option "AGPFastWrite" "yes"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "radeon"<br />
VendorName "IBM Thinkpad"<br />
BoardName "ATI Mobility FireGL 7800"<br />
'''Option "AGPFastWrite" "yes"'''<br />
EndSection<br />
<br />
<br />
==Dynamic Clock scaling==<br />
<br />
Please see:<br />
<br />
*[[How to make use of Graphics Chips Power Management features]] <tt>(save even more battery power)</tt></div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_make_use_of_Graphics_Chips_Power_Management_features&diff=6772How to make use of Graphics Chips Power Management features2005-07-20T09:00:40Z<p>84.191.139.74: /* x.org on Debian */</p>
<hr />
<div>==Power Saving With A Framebuffer Console==<br />
In order to use the dynamic GPU clock-scaling similar to what X.org has, you need to use the radeonfb kernel module. You'll need to enable the '''CONFIG_FB_RADEON''' in your kernel configuration. If setup correctly you should see something like the following in your kernel log:<br />
radeonfb: Dynamic Clock Power Management enabled<br />
<br />
==DynamicClocks in the Radeon Xorg driver==<br />
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "radeon"<br />
VendorName "IBM Thinkpad"<br />
BoardName "ATI Radeon Mobility M9"<br />
'''Option "DynamicClocks" "on"'''<br />
EndSection<br />
<br />
With this option enabled, the X11 server should print ({{path|/var/log/Xorg.0.log}}):<br />
<br />
(**) RADEON(0): Option "DynamicClocks" "on"<br />
(II) RADEON(0): Dynamic Clock Scaling Enabled<br />
<br />
http://www.ati.com/products/pdf/powerplaywp2.pdf<br />
<br />
==x.org on Debian==<br />
Because debian doesn't have X.org yet - [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian].<br />
<br />
'''Update:''' X.org has made it into Debian. See: [http://packages.debian.org/unstable/x11/xserver-xorg]<br />
[[Category:G40]] [[Category:G41]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_make_use_of_Graphics_Chips_Power_Management_features&diff=6711How to make use of Graphics Chips Power Management features2005-07-20T09:00:25Z<p>84.191.139.74: </p>
<hr />
<div>==Power Saving With A Framebuffer Console==<br />
In order to use the dynamic GPU clock-scaling similar to what X.org has, you need to use the radeonfb kernel module. You'll need to enable the '''CONFIG_FB_RADEON''' in your kernel configuration. If setup correctly you should see something like the following in your kernel log:<br />
radeonfb: Dynamic Clock Power Management enabled<br />
<br />
==DynamicClocks in the Radeon Xorg driver==<br />
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "radeon"<br />
VendorName "IBM Thinkpad"<br />
BoardName "ATI Radeon Mobility M9"<br />
'''Option "DynamicClocks" "on"'''<br />
EndSection<br />
<br />
With this option enabled, the X11 server should print ({{path|/var/log/Xorg.0.log}}):<br />
<br />
(**) RADEON(0): Option "DynamicClocks" "on"<br />
(II) RADEON(0): Dynamic Clock Scaling Enabled<br />
<br />
http://www.ati.com/products/pdf/powerplaywp2.pdf<br />
<br />
==x.org on Debian==<br />
Because debian doesn't have X.org yet - [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian].<br />
<br />
'''Update:''' X.org has made it into Debian. See: [http://packages.debian.org/unstable/x11/xserver-xorg]<br />
[[Category:G40]] [[Category:G41]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[CXategory:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=6792How to make ACPI work2005-07-20T08:58:25Z<p>84.191.139.74: /* using swsusp */</p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.<br />
<br />
If you prefer editing your .config file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10.<br /><br />
So you'll have to compile one yourself or get it as precompiled module for your kernel.<br /><br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br /><br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br /><br />
In general it is a good idea to read the README included with the driver.<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your XF86Config/xorg.conf.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via ctrl-alt-del). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume<br />
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration<br />
* If your suspend is failing, and a tail of /var/log/acpid shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: reboot after wake up.)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12-rc6.diff 2.6.12-rc6 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.<br />
<br />
In case you prefer to edit your config file directly, you should have the following three entries look like here...<br />
CONFIG_PM=y<br />
CONFIG_SOFTWARE_SUSPEND=y<br />
CONFIG_PM_STD_PARTITION="/dev/resume_partition"<br />
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)<br />
<br />
You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel. I am running 2.6.11-rc4-nitro in a Thinkpad T30 2366.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. You can change the <tt>/dev/hda5</tt> to your swap partition<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/hda5"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel<br />
<br />
In the meantime, add the following to the kernel parameters <tt>resume2=swap:/dev/hda5</tt>. Again change <tt>/dev/hda5</tt> to your swap partition.<br />
<br />
Install the hibernation script<br />
<br />
For [[:Category:Gentoo | Gentoo]] users: emerge hibernate-script<br /><br />
For [[:Category:Fedora | Fedora Core]] users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
<br />
Debian users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your /etc/mkinitrd/scripts directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it out.<br />
/usr/sbin/hibernate<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_make_APM_work&diff=7615How to make APM work2005-07-20T08:56:03Z<p>84.191.139.74: /* General */</p>
<hr />
<div>==General==<br />
You need to enable the APM Power Management support in the kernel and install the [[apmd]] to handle the events triggered by the kernel driver.<br />
The configuration for what to do at the different events is done in the proxy script which is usually found in {{path|/etc/apmd_proxy}}.<br />
See {{cmd|man apmd}} for further information on this.<br />
<br />
If both ACPI and APM are enabled in your kernel, ACPI will override APM on boot if an ACPI capable BIOS is detected. To keep it from doing so add <code>acpi=off</code> to your [[kernel parameters]].<br />
<br />
Beware that different kernels and distributions will provide different results. Mandrake has been better than Redhat, Fedora, and Debian generally with e.g. T20, 600X and 240X in providing sleep but no blank or hibernation with 2.4 and 2.6 kernels. Debian Sarge with 2.4 kernels also. On a RH9 distribution you can be successful using a MDK kernel.<br />
<br />
==Screen blanking (Standby)==<br />
{{cmdroot|apm -S}} will standby the machine. {{key|Fn}}{{key|F3}} should result in the same thing.<br />
<br />
==Suspend to RAM (Sleep)==<br />
{{cmdroot|apm -s}} will suspend the machine. {{key|Fn}}{{key|F4}} should do the same thing.<br />
<br />
==Suspend to disk (Hibernate)==<br />
The Phoenix BIOS allows you three ways to hibernate with APM:<br />
*using a special partition<br />
*using a hibernation file on a dos type partition<br />
*using [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2]<br />
<br />
===using a hibernation partition===<br />
The partition to be used for hibernation must be a primary partition that is at least as big as your laptop's memory including its video ram. First set the partition type of this partition to a0 (IBM Thinkpad hibernation) with fdisk, and then use [[tphdisk]] to write a hibernation file directly to this partition.<br />
<br />
Only follow these instructions, if you understand them. You will overwrite a partition on your hard disk and might lose valuable data - consider yourself warned. For example, assume that /dev/hda2 is the partition that is to be converted to a hibernation partition. Become root and type {{cmdroot|/sbin/fdisk /dev/hda}}. At the fdisk prompt type '''t''' to change the partition type, then type '''2''' to indicate that you want to change the type of partition 2, and then enter the partition type: '''a0'''. Now type '''w''' to write the partition table back to disk and exit. After that use [[tphdisk]] to initialize the hibernation partition. First estimate the size of your laptop's memory (main and video). For the sake of this example, let us assume that the main memory is 1024 MB and the video card has 128 MB of memory. Then the command {{cmdroot|tphdisk 1152 > /dev/hda2}} will initialize the hibernation partition. Note that this will only work if the partition is big enough. After a reboot, {{key|Fn}}{{key|F12}} will work as expected.<br />
<br />
I have successfully used this method on a T41 (2373GEU) that runs Fedora Core 3.<br />
<br />
In case you have a floppy drive you can also use the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4PESMK IBMs Standalone Hibernation Utility Diskette II] to create the hibernation partition.<br /><br />
Or you can use [http://www-public.tu-bs.de:8080/~y0015821/hibernation-util-boot.iso this bootable CD image] if you don't.<br />
<br />
===using a hibernation file on a dos partition===<br />
The partition to put the file on must be a dos or vfat partition. Fat32 formatted partitions have been reported successful as well as Fat16 formatted ones. The file is either created with phdisk.exe, if you happen to have a floppy drive and a bootable dos floppy disk that you can start it from.<br />
Under Linux [[tphdisk]] will do this job for you.<br />
<br />
If you have 512MB or more of RAM installed, you will need to use a FAT32 partition, due to file-size limits in FAT16.<br />
<br />
There have been varying reports of success or lack thereof using [[tphdisk]]; see [[APM setup on a type 2379 Thinkpad T40]] for workarounds and notes on required BIOS version, if [[tphdisk]] doesn't do the trick.<br />
<br />
===using SoftwareSuspend2===<br />
ToDo...<br />
<br />
==External Sources==<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4PESMK IBMs Standalone Hibernation Utility Diskette II]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_make_use_of_Dynamic_Frequency_Scaling&diff=6748How to make use of Dynamic Frequency Scaling2005-07-20T08:55:23Z<p>84.191.139.74: /* using the sys interface */</p>
<hr />
<div>===general===<br />
Linux supports Dynamic Frequency Scaling for ThinkPads with mobile Pentium III, Pentium 4 and Pentium M processors.<br />
<br />
===configuring the kernel===<br />
<br />
====2.4 kernels====<br />
Todo...<br />
<br />
====2.6 kernels====<br />
<br />
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):<br />
CONFIG_CPU_FREQ=y<br />
<br />
You need to load enable governors, if not already done in your distros default kernel:<br />
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y<br />
CONFIG_CPU_FREQ_GOV_POWERSAVE=y<br />
CONFIG_CPU_FREQ_GOV_USERSPACE=y<br />
<br />
Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel so you dont need userspace programs like powernowd etc.<br />
It can be enabled with:<br />
CONFIG_CPU_FREQ_GOV_ONDEMAND=y <br />
<br />
*If you have a Coppermine-piix-smi based Thinkpads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-ich</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | this page]].<br />
<br />
*If you have a p4-class celeron based Thinkpad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based Thinkpads | this page]]<br />
<br />
===using the sys interface===<br />
<br />
The files in {{path|/sys/devices/system/cpu/cpu0/cpufreq/}} provide information and a means of controlling the frequency scaling subsystem.<br />
Seed values are given in Khz. You need to be root to access the /sys filesystem.<br />
<br />
Your max speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}.<br />
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}<br />
:{{cmdresult|700000}}<br />
Your min speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}.<br />
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}<br />
:{{cmdresult|500000}}<br />
You can write to {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}} to change the current speed.<br />
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}<br />
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}<br />
:{{cmdresult|cpu MHz : 697.252}}<br />
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}<br />
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}<br />
:{{cmdresult|cpu MHz : 976.152}}<br />
<br />
===configuring SpeedStep daemons===<br />
<br />
Don't forget to enable the userspace governor to have a userspace daemon do the frequency scaling. If it is built as module, load it as <tt>cpufreq-userspace</tt>.<br />
Note that since 2.6.10, there is also the ondemand governor in the kernel, which replaces any userspace daemon for cpu scaling and works very well.<br />
<br />
There are plenty of userspace frequency scaling daemons available:<br />
<br />
*[[How to configure cpufreqd | cpufreqd]]<br />
*[[How to configure cpudynd | cpudynd]]<br />
*[[How to configure speedfreqd | speedfreqd]]<br />
*[[How to configure powersaved | powersaved]]<br />
*[[How to configure powernowd | powernowd]]<br />
*[[How to use cpufrequtils | cpufrequtils]]<br />
<br />
[[Category:570E]] [[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=Template:Path&diff=16871Template:Path2005-07-20T08:54:02Z<p>84.191.139.74: </p>
<hr />
<div><code style="white-space:nowrap;color:#996600;background-color:white;">{{{1}}}</code></div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_make_use_of_Dynamic_Frequency_Scaling&diff=6707How to make use of Dynamic Frequency Scaling2005-07-20T08:50:06Z<p>84.191.139.74: /* using the sys interface */</p>
<hr />
<div>===general===<br />
Linux supports Dynamic Frequency Scaling for ThinkPads with mobile Pentium III, Pentium 4 and Pentium M processors.<br />
<br />
===configuring the kernel===<br />
<br />
====2.4 kernels====<br />
Todo...<br />
<br />
====2.6 kernels====<br />
<br />
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):<br />
CONFIG_CPU_FREQ=y<br />
<br />
You need to load enable governors, if not already done in your distros default kernel:<br />
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y<br />
CONFIG_CPU_FREQ_GOV_POWERSAVE=y<br />
CONFIG_CPU_FREQ_GOV_USERSPACE=y<br />
<br />
Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel so you dont need userspace programs like powernowd etc.<br />
It can be enabled with:<br />
CONFIG_CPU_FREQ_GOV_ONDEMAND=y <br />
<br />
*If you have a Coppermine-piix-smi based Thinkpads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-ich</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | this page]].<br />
<br />
*If you have a p4-class celeron based Thinkpad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based Thinkpads | this page]]<br />
<br />
===using the sys interface===<br />
<br />
The files in /sys/devices/system/cpu/cpu0/cpufreq/ provide information and a means of controlling the frequency scaling subsystem.<br />
Seed values are given in Khz. You need to be root to access the /sys filesystem.<br />
<br />
Your max speed is at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq.<br />
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}<br />
:{{cmdresult|700000}}<br />
Your min speed is at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq.<br />
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}<br />
:{{cmdresult|500000}}<br />
You can write to /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed to change the current speed.<br />
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}<br />
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}<br />
:{{cmdresult|cpu MHz : 697.252}}<br />
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}<br />
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}<br />
:{{cmdresult|cpu MHz : 976.152}}<br />
<br />
===configuring SpeedStep daemons===<br />
<br />
Don't forget to enable the userspace governor to have a userspace daemon do the frequency scaling. If it is built as module, load it as <tt>cpufreq-userspace</tt>.<br />
Note that since 2.6.10, there is also the ondemand governor in the kernel, which replaces any userspace daemon for cpu scaling and works very well.<br />
<br />
There are plenty of userspace frequency scaling daemons available:<br />
<br />
*[[How to configure cpufreqd | cpufreqd]]<br />
*[[How to configure cpudynd | cpudynd]]<br />
*[[How to configure speedfreqd | speedfreqd]]<br />
*[[How to configure powersaved | powersaved]]<br />
*[[How to configure powernowd | powernowd]]<br />
*[[How to use cpufrequtils | cpufrequtils]]<br />
<br />
[[Category:570E]] [[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=Template:Cmdresult&diff=16870Template:Cmdresult2005-07-20T08:48:37Z<p>84.191.139.74: </p>
<hr />
<div><code style="white-space:nowrap;color:#495988;background-color:white;">{{{1}}}</code></div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_make_use_of_Dynamic_Frequency_Scaling&diff=6706How to make use of Dynamic Frequency Scaling2005-07-20T08:41:43Z<p>84.191.139.74: /* using the sys interface */</p>
<hr />
<div>===general===<br />
Linux supports Dynamic Frequency Scaling for ThinkPads with mobile Pentium III, Pentium 4 and Pentium M processors.<br />
<br />
===configuring the kernel===<br />
<br />
====2.4 kernels====<br />
Todo...<br />
<br />
====2.6 kernels====<br />
<br />
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):<br />
CONFIG_CPU_FREQ=y<br />
<br />
You need to load enable governors, if not already done in your distros default kernel:<br />
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y<br />
CONFIG_CPU_FREQ_GOV_POWERSAVE=y<br />
CONFIG_CPU_FREQ_GOV_USERSPACE=y<br />
<br />
Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel so you dont need userspace programs like powernowd etc.<br />
It can be enabled with:<br />
CONFIG_CPU_FREQ_GOV_ONDEMAND=y <br />
<br />
*If you have a Coppermine-piix-smi based Thinkpads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-ich</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | this page]].<br />
<br />
*If you have a p4-class celeron based Thinkpad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based Thinkpads | this page]]<br />
<br />
===using the sys interface===<br />
<br />
The files in /sys/devices/system/cpu/cpu0/cpufreq/ provide information and a means of controlling the frequency scaling subsystem.<br />
Seed values are given in Khz. You need to be root to access the /sys filesystem.<br />
<br />
Your max speed is at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq.<br />
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}<br />
:<tt>700000</tt><br />
Your min speed is at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq.<br />
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}<br />
:<tt>500000</tt><br />
You can write to /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed to change the current speed.<br />
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}<br />
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}<br />
:<tt>cpu MHz : 697.252</tt><br />
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}<br />
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}<br />
:<tt>cpu MHz : 976.152</tt><br />
<br />
===configuring SpeedStep daemons===<br />
<br />
Don't forget to enable the userspace governor to have a userspace daemon do the frequency scaling. If it is built as module, load it as <tt>cpufreq-userspace</tt>.<br />
Note that since 2.6.10, there is also the ondemand governor in the kernel, which replaces any userspace daemon for cpu scaling and works very well.<br />
<br />
There are plenty of userspace frequency scaling daemons available:<br />
<br />
*[[How to configure cpufreqd | cpufreqd]]<br />
*[[How to configure cpudynd | cpudynd]]<br />
*[[How to configure speedfreqd | speedfreqd]]<br />
*[[How to configure powersaved | powersaved]]<br />
*[[How to configure powernowd | powernowd]]<br />
*[[How to use cpufrequtils | cpufrequtils]]<br />
<br />
[[Category:570E]] [[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_configure_powernowd&diff=6719How to configure powernowd2005-07-20T08:38:43Z<p>84.191.139.74: </p>
<hr />
<div>{{NOTE|See the [[How to make use of Dynamic Frequency Scaling|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}<br />
<br />
<br />
powernowd originally was only written for AMD CPUs which support PowerNow! technology, but it supports other CPUs as well.<br />
<br />
Make sure you have loaded the necessary kernel modules. (See [[How to make use of Dynamic Frequency Scaling]])<br />
<br />
Install "powernowd".<br />
<br />
On Debian you can do this with:<br />
<br />
{{cmdroot|apt-get install powernowd}}<br />
<br />
Also, on Debian you may specify different options for powernowd in <tt>/etc/default/powernowd</tt>. This file will be loaded by the init script <tt>/etc/init.d/powernowd</tt>.</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_configure_powernowd&diff=6704How to configure powernowd2005-07-20T08:38:18Z<p>84.191.139.74: </p>
<hr />
<div>{{NOTE|See the [[How_to_make_use_of_Dynamic_Frequency_Scaling|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}<br />
<br />
<br />
powernowd originally was only written for AMD CPUs which support PowerNow! technology, but it supports other CPUs as well.<br />
<br />
Make sure you have loaded the necessary kernel modules. (See [[How_to_make_use_of_Dynamic_Frequency_Scaling]])<br />
<br />
Install "powernowd".<br />
<br />
On Debian you can do this with:<br />
<br />
{{cmdroot|apt-get install powernowd}}<br />
<br />
Also, on Debian you may specify different options for powernowd in <tt>/etc/default/powernowd</tt>. This file will be loaded by the init script <tt>/etc/init.d/powernowd</tt>.</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_use_cpufrequtils&diff=6718How to use cpufrequtils2005-07-20T08:35:50Z<p>84.191.139.74: </p>
<hr />
<div>{{NOTE|See the [[How_to_make_use_of_Dynamic_Frequency_Scaling|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}<br />
<br />
<br />
This package mainly has 2 programs:<br />
/usr/bin/cpufreq-info<br />
/usr/bin/cpufreq-set<br />
<br />
cpufreq-info gives general device information:<br />
xaiki@gonzo:~$ cpufreq-info<br />
cpufrequtils 0.2: cpufreq-info (C) Dominik Brodowski 2004<br />
Report errors and bugs to linux@brodo.de, please.<br />
analyzing CPU 0:<br />
driver: speedstep-smi<br />
CPUs which need to switch frequency at the same time: 0<br />
hardware limits: 500 MHz - 700 MHz<br />
available frequency steps: 700 MHz, 500 MHz<br />
available cpufreq governors: userspace, performance<br />
current policy: frequency should be within 500 MHz and 700 MHz.<br />
The governor "userspace" may decide which speed to use<br />
within this range.<br />
current CPU frequency is 700 MHz.<br />
<br />
and cpufreq-set allows setting<br />
... Never got it working ...</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=HOWTOs_-_Driver_Installation&diff=6994HOWTOs - Driver Installation2005-07-20T08:35:07Z<p>84.191.139.74: </p>
<hr />
<div>This page holds information on how to make additional hardware work on your Thinkpad.<br />
<br />
The pages linked here hold instructions for installing or configuring certain drivers to make them work with ThinkPad hardware. For an overview of the drivers themselves please look at the [[Drivers]] page.<br />
<br />
<!-- adjust these comment markers if you add things to the hidden sections<br />
--><br />
==Graphics==<br />
* [[Additional options for the radeon driver | RADEON driver for X]] <tt>(Additional options for the radeon driver)</tt><br />
<br />
==Input==<br />
*[[How to configure the TrackPoint|TrackPoint configuration]] <tt>(How to make your TrackPoint behave as you wish)</tt><br />
<br />
==PowerManagement==<br />
* [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | SpeedStep on piix4]] <tt>(How to make SpeedStep (cpufreq) work on Coppermine-piix4-smi based Thinkpads)</tt><br />
* [[How to get SpeedStep working on_P4-class-Celeron_based_Thinkpads | SpeedStep on P4-class Celeron]] <tt>(How to get SpeedStep working on P4-class-Celeron based Thinkpads)</tt><br />
* [[How to configure cpufreqd | cpufreqd]]{{footnote|1}} <tt>(How to configure the cpufreqd frequency scaling daemon)</tt><br />
* [[How to use cpufrequtils | cpufrequtils]]{{footnote|1}} <tt>(How to use the cpufrequtils frequency scaling utils)</tt><br />
* [[How to configure powernowd | powernowd]] {{footnote|1}} <tt>(How to configure the powernowd frequency scaling daemon)</tt><br />
* [[How to configure powersaved | powersaved]]{{footnote|1}} <tt>(How to configure the powersaved frequency scaling daemon)</tt><br />
<br />
==Wireless LAN==<br />
* [[How to install ndiswrapper for the Intel 2200bg WLAN adaptor | ndiswrapper for Intel 2200bg]] <tt>(ndiswrapper configuration for intel/pro 2200BG)</tt><br />
<!--<br />
This is a HOWTOs page, it should link to pages that tell how the drivers are installed, not to the driver pages themselves.<br />
* [[Ipw2200 | ipw2200]] <tt>(Open-source native driver for Intel/PRO Wireless 2200BG)</tt><br />
* [[Madwifi | Madwifi]] <tt>(Native driver for cards based on Atheros chipsets)</tt><br />
<br />
==Touchpad/Trackpoint==<br />
* [[ Trackpoint | Trackpoint ]]<br />
<br />
==Internal Modem==<br />
* [[Modem | Modem]] <tt>Drivers for the various internal (soft)modems</tt><br />
<br />
==Graphic==<br />
* [[ Fglrx | Fglrx ]] <tt>ATI Mobility driver</tt><br />
--><br />
<br />
==Additional Hardware==<br />
* [[How to install the IBM Ultracam II driver | IBM UltraCam II]] <tt>(How to make the IBM UltraCam II work under Linux)</tt><br />
<!--<br />
==Windows drivers==<br />
no entry yet<br />
--><br />
<br />
{{footnotes|<br />
#Don't forget that the newer kernels have fancier cpu frequency governors like OnDemand and Conservative that are easy to configure via SysFS. These governors are adequate in many situations and do not require user-space daemons such as cpufreqd, powersaved, or powernowd. Read more about it on the [[How to make use of Dynamic Frequency Scaling|Dynamic Frequency Scaling page]].<br />
}}</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=How_to_make_use_of_Dynamic_Frequency_Scaling&diff=6705How to make use of Dynamic Frequency Scaling2005-07-20T08:25:20Z<p>84.191.139.74: </p>
<hr />
<div>===general===<br />
Linux supports Dynamic Frequency Scaling for ThinkPads with mobile Pentium III, Pentium 4 and Pentium M processors.<br />
<br />
===configuring the kernel===<br />
<br />
====2.4 kernels====<br />
Todo...<br />
<br />
====2.6 kernels====<br />
<br />
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):<br />
CONFIG_CPU_FREQ=y<br />
<br />
You need to load enable governors, if not already done in your distros default kernel:<br />
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y<br />
CONFIG_CPU_FREQ_GOV_POWERSAVE=y<br />
CONFIG_CPU_FREQ_GOV_USERSPACE=y<br />
<br />
Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel so you dont need userspace programs like powernowd etc.<br />
It can be enabled with:<br />
CONFIG_CPU_FREQ_GOV_ONDEMAND=y <br />
<br />
*If you have a Coppermine-piix-smi based Thinkpads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-ich</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | this page]].<br />
<br />
*If you have a p4-class celeron based Thinkpad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based Thinkpads | this page]]<br />
<br />
===using the sys interface===<br />
<br />
The files in /sys/devices/system/cpu/cpu0/cpufreq/ provide information and a means of controlling the frequency scaling subsystem.<br />
Seed values are given in Khz. You need to be root to access the /sys filesystem.<br />
<br />
Your max speed is at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq.<br />
# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq<br />
700000<br />
Your min speed is at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq.<br />
# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq<br />
500000<br />
You can write to /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed to change the current speed.<br />
# echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed<br />
# cat /proc/cpuinfo | grep "cpu MHz"<br />
cpu MHz : 697.252<br />
# echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed<br />
# cat /proc/cpuinfo | grep "cpu MHz"<br />
cpu MHz : 976.152<br />
<br />
===configuring SpeedStep daemons===<br />
<br />
Don't forget to enable the userspace governor to have a userspace daemon do the frequency scaling. If it is built as module, load it as <tt>cpufreq-userspace</tt>.<br />
Note that since 2.6.10, there is also the ondemand governor in the kernel, which replaces any userspace daemon for cpu scaling and works very well.<br />
<br />
There are plenty of userspace frequency scaling daemons available:<br />
<br />
*[[How to configure cpufreqd | cpufreqd]]<br />
*[[How to configure cpudynd | cpudynd]]<br />
*[[How to configure speedfreqd | speedfreqd]]<br />
*[[How to configure powersaved | powersaved]]<br />
*[[How to configure powernowd | powernowd]]<br />
*[[How to use cpufrequtils | cpufrequtils]]<br />
<br />
[[Category:570E]] [[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]]</div>84.191.139.74https://www.thinkwiki.org/w/index.php?title=HOWTOs_-_Driver_Installation&diff=6701HOWTOs - Driver Installation2005-07-20T08:10:40Z<p>84.191.139.74: </p>
<hr />
<div>This page holds information on how to make additional hardware work on your Thinkpad.<br />
<br />
The pages linked here hold instructions for installing or configuring certain drivers to make them work with ThinkPad hardware. For an overview of the drivers themselves please look at the [[Drivers]] page.<br />
<br />
<!-- adjust these comment markers if you add things to the hidden sections<br />
--><br />
==Graphics==<br />
* [[Additional options for the radeon driver | RADEON driver for X]] <tt>(Additional options for the radeon driver)</tt><br />
<br />
==Input==<br />
*[[How to configure the TrackPoint|TrackPoint configuration]] <tt>(How to make your TrackPoint behave as you wish)</tt><br />
<br />
==PowerManagement==<br />
* [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | SpeedStep on piix4]] <tt>(How to make SpeedStep (cpufreq) work on Coppermine-piix4-smi based Thinkpads)</tt><br />
* [[How to get SpeedStep working on_P4-class-Celeron_based_Thinkpads | SpeedStep on P4-class Celeron]] <tt>(How to get SpeedStep working on P4-class-Celeron based Thinkpads)</tt><br />
* [[How to configure cpufreqd | cpufreqd]]{{footnote|1}} <tt>(How to configure the cpufreqd SpeedStep daemon)</tt><br />
* [[How to configure powersaved | powersaved]]{{footnote|1}} <tt>(How to configure the cpufreqd SpeedStep daemon)</tt><br />
<br />
==Wireless LAN==<br />
* [[How to install ndiswrapper for the Intel 2200bg WLAN adaptor | ndiswrapper for Intel 2200bg]] <tt>(ndiswrapper configuration for intel/pro 2200BG)</tt><br />
<!--<br />
This is a HOWTOs page, it should link to pages that tell how the drivers are installed, not to the driver pages themselves.<br />
* [[Ipw2200 | ipw2200]] <tt>(Open-source native driver for Intel/PRO Wireless 2200BG)</tt><br />
* [[Madwifi | Madwifi]] <tt>(Native driver for cards based on Atheros chipsets)</tt><br />
<br />
==Touchpad/Trackpoint==<br />
* [[ Trackpoint | Trackpoint ]]<br />
<br />
==Internal Modem==<br />
* [[Modem | Modem]] <tt>Drivers for the various internal (soft)modems</tt><br />
<br />
==Graphic==<br />
* [[ Fglrx | Fglrx ]] <tt>ATI Mobility driver</tt><br />
--><br />
<br />
==Additional Hardware==<br />
* [[How to install the IBM Ultracam II driver | IBM UltraCam II]] <tt>(How to make the IBM UltraCam II work under Linux)</tt><br />
<!--<br />
==Windows drivers==<br />
no entry yet<br />
--><br />
<br />
{{footnotes|<br />
#Don't forget that the newer kernels have fancier cpu frequency governors like OnDemand and Conservative that are easy to configure via SysFS. These governors are adequate in many situations and do not require user-space daemons such as cpufreqd, powersaved, or powernowd. Read more about it on the [[How to make use of Dynamic Frequency Scaling|Dynamic Frequency Scaling page]].<br />
}}</div>84.191.139.74