ThinkWiki - User contributions [en]

Intel WiMAX/WiFi Link 5150/5350

2009-08-10T12:06:32Z

Tony2001: â†Created page with '= Models = Models: {{T500}} = Identification = <pre> # lspci | grep Netw 00:19.0 Ethernet controller: Intel Corporation 82567LF Gigabit Network Connection (rev 03) 03:00...'

= Models =
Models: {{T500}}

= Identification =

<pre>
# lspci | grep Netw
00:19.0 Ethernet controller: Intel Corporation 82567LF Gigabit Network Connection (rev 03)
03:00.0 Network controller: Intel Corporation Device 423d
</pre>

'''423d''' seems to be a cryptic alias for Intel WiMAX/WiFi Link 5150 controller.

= Support =

Support for Intel WiMAX/WiFi Link 5150/5350 WiFi/WiMAX was added to the kernel since version '''2.6.27''', driver '''iwlagn''' is used for that.

= Firmware =

In order to get it working you need to download proprietary firmware (freely distributed, though) from Intel's site: http://www.intellinuxwireless.org/?n=downloads , look for '''5150 Images'''.<br>
After downloading unpack the archive and copy the .ucode file into /lib/firmware dir.

How to control fan speed

2007-12-18T10:53:58Z

Tony2001: /* Using a patched kernel */

This page discusses methods for controlling the system fan.

==For Linux==
===Using a patched kernel===
{{NOTE|The ibm-acpi driver is part of the Linux kernel 2.6.10 and later (option CONFIG_ACPI_IBM), so patching is not needed anymore.}}
{{WARN|This patch is superceded by the patches in [[ibm-acpi]] [[Git]] repository or [http://ibm-acpi.sourceforge.net ibm-acpi.sf.net] releases}}
{{NOTE|Advanced fan control through ibm-acpi has been merged in Linux 2.6.20-rc2 mainline, so users of 2.6.20 won't need to patch their kernels to get the '''fan level''' functionality anymore}}

The [[Patch for controlling fan speed]] provides a convenient interface via {{path|/proc/acpi/ibm/fan}}.

Manual speed control can be done through the [[patch for controlling fan speed]]:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: auto
speed: 4219
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

'''#echo level 2 > /proc/acpi/ibm/fan'''

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: 2
speed: 3142
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

===Using a stock kernel===

If you have the [[ibm-acpi]] module loaded with <tt>experimental=1</tt>, you can control the fan without patching the kernel by directly writing to the relevant embedded controller register using {{path|/proc/acpi/ibm/ecdump}}.

For example:

{{cmdroot|echo 0x2F 0x00 > /proc/acpi/ibm/ecdump}} (fan off)

{{cmdroot|echo 0x2F 0x02 > /proc/acpi/ibm/ecdump}} (low speed)

{{cmdroot|echo 0x2F 0x04 > /proc/acpi/ibm/ecdump}} (medium speed)

{{cmdroot|echo 0x2F 0x07 > /proc/acpi/ibm/ecdump}} (maximum speed)

{{cmdroot|echo 0x2F 0x80 > /proc/acpi/ibm/ecdump}} (automatic - default)

{{cmdroot|echo 0x2F 0x40 > /proc/acpi/ibm/ecdump}} (disengaged)

See the specifications below for the meaning of these modes.

===On/off control using stock kernel===

If you only wish to turn the fan on and off (with automatic control when it's on), you can use the following.

When loading [[ibm-acpi]] v0.11 with experimental switch ({{cmdroot|1=modprobe ibm_acpi experimental=1}}), it is possible to read and write the status of fan:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
speed: 3580
commands: enable, disable

'''#echo disable > /proc/acpi/ibm/fan'''

'''cat /proc/acpi/ibm/fan'''
status: disabled
speed: 0
commands: enable, disable

When off, the fan will then '''never''' wake up. It is advised to use an automated control script to reduce the chance of hardware damage.

===Automated control scripts===

An [[ACPI fan control script#Variable speed control scripts|ACPI fan control script]] can be used to override the firmware's fan algorithm with gentler, quieter version. It monitors the laptop's [[thermal sensors]] and sets the fan speed accordingly, according to customizable thresholds. For the default behavior, simply save {{CodeRef|tp-fancontrol}} as {{path|tp-fancontrol}}, make sure you've loaded [[thinkpad-acpi]] with the "fan_control=1" parameter, and run:<br />
{{cmdroot|./tp-fancontrol}}

There is an distro independent daemon (http://projekte.f4.fhtw-berlin.de/trac/s0332819-linuxtools/wiki/), written in python. Packages are available for debian based linux systems.

==For Windows==

Shimodax's ThinkPad fan control tool offers similar functionality (see [http://forum.thinkpads.com/viewtopic.php?t=17715 forum discussion] at thinkpads.com). Source and binaries are available through the [http://sourceforge.net/projects/tp4xfancontrol "Tp4xFanControl"] project on SourceForge.

==Hardware specs==

The following hardware behavior was discovered experimentally by [[User:Thinker|Thinker]] and neither provided by nor confirmed by IBM/Lenovo. The following description may be inaccurate and may vary by model (see list of models above). The terminology probably does not match the one used by IBM/Lenovo engineers.

{{NOTE|Information on other models is included in the [[ibm-acpi]] [[Git]] version.}}

ACPI DSDT register HFSP (8 bits, offset 0x2F in the <tt>EmbeddedController</tt> address space, accessed through the standard EC interface at IO ports 0x62 and 0x66) is read/writable and has the following meaning:

Bits 7 6 5 4 3 2 1 0
---------------
Value 1 0 * * * * * * - automatic
* 1 * * * * * * - disengaged
0 0 N N N N N N - manual (0..63; 0=disable fan, 1=min, ..., 7=max)

Changing modes may not be immediate on all ThinkPads. Later ThinkPad models seem to take at least 5s to start responding to a fan mode change, for example.

After boot, the HFSP register may not reflect the true state of the EC (on some models it reads 0x07 even though the EC is actually in automatic mode).

=== Fan Tachometer ===

The embedded controller registers 0x84 (LSB), 0x85 (MSB) are the main fan tachometer, and report fan speed in RPM in everything since the {{A31}} and maybe a little earlier. Not much is know about the tachometer in earlier models, or even whether they had one or not.

=== Automatic mode ===
In ''automatic'' mode, the embedded controller sets the fan speed automatically according to system temperatures and some unknown algorithm.

Note that the ACPI DSDT may supplement this in some models. The {{X40}}, for example, changes the profile of speeds the automatic mode should use depending on battery status.

=== Manual mode ===

In ''manual'' mode, the fan level is forced to the given value and the EC will auto-regulate the fan to maintain at a (roughly) constant RPM, which is model-dependent. Manual speed levels 8-63 yield the same behavior as level 7, and the the ACPI DSDT uses level 7 for the emergency mode it enters upon critical CPU/GPU temperature, so apparently 7 is the real maximum level.

=== Disengaged (full-speed) mode ===

In ''disengaged'' mode, the embedded controller does not monitor the fan speed. It "disengages" the closed-loop control function that keeps track of fan speed, and uses an open-loop control function that ramps up the fan to its maximum speed (100% duty-cycle). The end speed is not stable, but it is often much faster than the maximum speed manual and automatic modes would set the fan to.

Most newer ThinkPads take quite a while (in excess of one minute) to fully enter disengaged mode. Exiting it is much faster. The {{A31}} acts differently, and switches to disengaged mode as fast as it switches to other modes.

For some reason, the embedded controller may stop updating the tachometer registers while entering or exiting disengaged mode in some ThinkPad firmware versions (hence the EC tachometer registers will not be updated on these models while entering/exiting disengaged mode). Once it arrives at maximum speed, or once it gets back at closed-loop cruise speed, the embedded controller starts updating the tachometer registers again. Later T models such as the {{T43}} have this problem, while the {{A31}} does not.

{{HINT|Apparently the [[Problem with fan noise|pulsing fan noise]] experienced by some users can be cured by repeatedly running 2-4 seconds of manual control followed by 0.5-1 seconds of disengaged mode. The pulse occurs when the the embedded controller computes the fan speed and adjusts the fan voltage adaptively every few seconds (~4.8sec for the ThinkPad T43); the aforementioned mode switching doesn't give it a chance to do so. One of the [[ACPI fan control script#Variable speed control scripts|ACPI fan control scripts]] implements this solution.}}

==Supported models==

The above was successfully tested on the following models:

* ThinkPad {{A31}} (fan levels RPM: 0 = off, 1-2 = ~3280-3380 (!), 3-5 = ~3200, 6-7 = ~3380, "disengaged" = ~4000 (see NOTE above))
* ThinkPad {{R50}} (highest manual level is 3; disengage mode works and reaches much higher RPM)
* ThinkPad {{R50p}} (fan levels RPM: 0 = off, 1-2 = ~3200, 3-5 = ~3500-3600, 6-7 = ~3700-3800, disengaged = ~5300)
* ThinkPad {{R51}} (fan levels RPM: 0 = off, 1-2 = ~3150, 3-5 = ~3350, 6 = ~3750, disengaged = ~5100)
* ThinkPad {{R51e}} (fan levels RPM: 0 = off, 1-2 = ~3300, 3-5 = ~3800, 6 = ~4150, disengaged = ~5100)
* ThinkPad {{R52}} (fan levels RPM: 0 = off, 1-2 = ~3350, 3-5 = ~3650, 6 = ~4250, disengaged = ~5245)
* ThinkPad {{R60}} (fan levels RPM: 0 = off, 1-1 = ~2650, 3-5 = ~3300, 6-7 = ~3950, disengaged = ~4800)
* ThinkPad {{R60e}}
* ThinkPad {{T22}}
* ThinkPad {{T23}} (low speed = ~2200, medium and maximum speed = ~4800; disengaged mode works at ~5800)
* ThinkPad {{T30}}
* ThinkPad {{T40}} (fan levels RPM: 1-2 = ~2950, 3-5 = ~3600, 6-7 = ~4050)
* ThinkPad {{T41}}, {{T41p}} (fan levels RPM: 1-2 = ~2980, 3-5 = ~3500, 6-7 = ~4050; disengaged mode works at ~5100)
* ThinkPad {{T42}}, {{T42p}} (fan levels RPM: 1-2 = ~2900, 3-5 = ~3700, 6-7 = ~4700; disengaged mode works at ~5200)
* ThinkPad {{T43}}, {{T43p}} (fan levels RPM: 1-2 = ~3300, 3-5 = ~4100, 6-7 = ~4700; disengaged mode works at ~6450)
* ThinkPad {{T60}} (fan levels RPM: 1-2 = 3000-3100, 3-5 = ~3600, 6-7 = ~4500; disengaged mode works at ~5500)
* ThinkPad {{X30}} (level 0 = off, low = ~3900, medium = ~4200, maximum = ~4650, disengaged = ~5900)
* ThinkPad {{X31}} (fan levels RPM: 0 = off, 1-2 = ~2850, 3-5 = ~3450, 6 = ~4050, 7 = ~4150; disengaged mode works at ~4975)
* ThinkPad {{X40}}
* ThinkPad {{X41}}
* ThinkPad {{X41T}}
* ThinkPad {{X60}}
* ThinkPad {{X61s}}
* ThinkPad {{Z60t}}, {{Z60m}} (fan levels RPM: 1-2 = ~1700, 3-5 = ~2800, 6-7 = ~3500)
* ThinkPad {{Z61m}}
* Thinkpad {{Z61p}} (fan levels 0-7, auto, disengaged; enable, disable; watchdog (untested))
Probably other models are supported too (please update this page if you confirm this; maintain some ordering too).

==Models using a different interface==

The following models also work, use a different access method which supported (only) via the {{path|/proc/acpi/ibm/fan}} of [[ibm-acpi]]. No need for patching.

* ThinkPad {{600E}}, {{600X}}, {{770E}}, {{770X}} (these use a different fan control interface)

==Unsupported models==

* ThinkPad {{560}} (these models don't have a fan)

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-11-20T08:38:41Z

Tony2001: /* '''Video''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.
2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

---

All these steps are not required if you have T61 with Intel graphics card (as I do), in this case everything works just fine out of the box.

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

---

My T61 comes with "Intel Corporation PRO/Wireless 3945ABG" wifi controller, which worked out of the box without installing any additional drivers (yeah, I did not forgot to insteall iwlwifi and iwl3945 packages during the installation).

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

---

Don't forget to raise volume levels in alsamixer, they are muted by default!
Everything else is works as expected (mute button mutes, volume up button raises volume and volume down vice versa).

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

---

No idea about NVidia (I intentionally decided to buy a machine without it, since I'm tired of bugs in their binary-only drivers), but kpowersave is able to change the brightness here. You can do the same using /proc/acpi/ibm/brightness (see `cat /proc/acpi/ibm/brightness`).

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

---

Bluetooth freezes my machine after waking up from suspend-to-ram (making it almost impossible to debug).
I don't use any bluetooth devices, so I have just disabled it by `echo "disable" > /proc/acpi/ibm/bluetooth`.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

---

Yes, it works fine in console, though neither kdm, nor gdm support it, which makes this thing pretty much useless.
The only advantage is that you don't need to type root password when doing 'su -'.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

---

Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Also working here with the S2RAM_OPTS set properly as above.

== '''Multimedia''' ==

codecs are available here : http://opensuse-community.org/Multimedia#openSUSE_10.3

== '''ThinkVantage''' ==

In order to boot with ThinkVantage, opensuse boot loader should be installed on /.
The root partition must be a primary partition and must be active.

KThinkBat

2007-11-11T12:48:34Z

Tony2001: /* openSuSE */

==Description==

[http://lepetitfou.dyndns.org/KThinkBat KThinkBat] is a laptop battery monitor for the KDE-Kicker. It is inspired by the Windows Application "Battery Maximizer" which is included with ThinkPads.

It can use the SMAPI BIOS (through the [[tp_smapi]] driver) or [[How to make ACPI work|ACPI]] to collect the data. It shows you the current power consumption of the laptop and brings support for a second battery. It is fully customizable including sizes, color, fonts and battery number

Homepage: http://lepetitfou.dyndns.org/KThinkBat

Author: [http://lepetitfou.dyndns.org Tobias Roeser]

Latest Version (2007-07-29): 0.2.8

==Screenshot==

[[Image:KThinkBat.png]]

Offline Mode: you see how much charge is left and the current discharging rate.

[[Image:KThinkBat_dual.png]]

Online Mode: you see how much charge is left and the current charging rate. This screenshot is taken with the disabled "summarize batteries" option.

==Installation==

KThinkBat uses the autotools. For a standard installation use

./configure
make
su -c 'make install'

Alternatively, to minimize filesystem clutter you can install KThinkBat into {{path|/opt/kthinkbat}} and add just a few symlinks under {{path|/usr}}:

mkdir -p /opt/kthinkbat
./configure --prefix=/opt/kthinkbat
make
make install
cd /usr/lib/kde3
ln -vfs ../../../opt/kthinkbat/lib/* ./
cd /usr/share/apps/kicker/applets
ln -vfs ../../../../../opt/kthinkbat/share/apps/kicker/applets/kthinkbat.desktop ./

(The above paths are for {{Fedora}} 4 and 5, and may need to be adjusted for other distributions.)

If you already have the applet running, run {{cmduser|killall kicker; kicker}} to restart it.

==Gentoo==
You can use the ebuild from this [https://lepetitfou.dyndns.org/svn/gentoo/lefous_portage_overlay/ portage overlay], category/package: [https://lepetitfou.dyndns.org/svn/gentoo/lefous_portage_overlay/app-laptop app-laptop]/[https://lepetitfou.dyndns.org/svn/gentoo/lefous_portage_overlay/app-laptop/kthinkbat kthinkbat].

==openSuSE==

KThinkBat is included into the community builds (see KDE/Community/openSUSE_Factory, [[ftp://ftp5.gwdg.de/%2fpub/linux/suse/opensuse/repositories/KDE%3A/Community/openSUSE_Factory/x86_64/ here]] for example), though the version is quite outdated atm - 0.2.2.
You can find newer versions on [http://linux01.gwdg.de/~pbleser/index.php Guru's RPM Site], see [http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=System/kthinkbat/ RPMs for KThinkBat] compiled for all SuSE versions back to 9.3.

==Debian==

deb http://debian.cp69.de/ unstable main non-free contrib
deb-src http://debian.cp69.de/ unstable main non-free contrib

deb http://debian.cp69.de/ testing main non-free contrib
deb-src http://debian.cp69.de/ testing main non-free contrib

To get the repository key, do a:

wget http://debian.cp69.de/repo.asc -O - | sudo apt-key add -

==Download==

* [http://lepetitfou.dyndns.org/KThinkBat#Download Download from the KThinkBat Site]

==See Also==

* [[How to use UltraBay batteries]]

[[Category:Tools]] [[Category:Gentoo]]

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-10-08T14:33:13Z

Tony2001: /* '''Display''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.

2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

---

All these steps are not required if you have T61 with Intel graphics card (as I do), in this case everything works just fine out of the box.

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

---

My T61 comes with "Intel Corporation PRO/Wireless 3945ABG" wifi controller, which worked out of the box without installing any additional drivers (yeah, I did not forgot to insteall iwlwifi and iwl3945 packages during the installation).

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

---

Don't forget to raise volume levels in alsamixer, they are muted by default!
Everything else is works as expected (mute button mutes, volume up button raises volume and volume down vice versa).

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

---

No idea about NVidia (I intentionally decided to buy a machine without it, since I'm tired of bugs in their binary-only drivers), but kpowersave is able to change the brightness here. You can do the same using /proc/acpi/ibm/brightness (see `cat /proc/acpi/ibm/brightness`).

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

---

Bluetooth freezes my machine after waking up from suspend-to-ram (making it almost impossible to debug).
I don't use any bluetooth devices, so I have just disabled it by `echo "disable" > /proc/acpi/ibm/bluetooth`.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

---

Yes, it works fine in console, though neither kdm, nor gdm support it, which makes this thing pretty much useless.
The only advantage is that you don't need to type root password when doing 'su -'.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

---

Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-10-08T14:31:00Z

Tony2001: /* '''Sound''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.

2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

---

All these steps are not required if you have T61 with Intel graphics card (as I do), in this case everything works just fine out of the box.

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

---

My T61 comes with "Intel Corporation PRO/Wireless 3945ABG" wifi controller, which worked out of the box without installing any additional drivers (yeah, I did not forgot to insteall iwlwifi and iwl3945 packages during the installation).

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

---

Don't forget to raise volume levels in alsamixer, they are muted by default!
Everything else is works as expected (mute button mutes, volume up button raises volume and volume down vice versa).

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

---

Bluetooth freezes my machine after waking up from suspend-to-ram (making it almost impossible to debug).
I don't use any bluetooth devices, so I have just disabled it by `echo "disable" > /proc/acpi/ibm/bluetooth`.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

---

Yes, it works fine in console, though neither kdm, nor gdm support it, which makes this thing pretty much useless.
The only advantage is that you don't need to type root password when doing 'su -'.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

---

Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-10-08T14:28:51Z

Tony2001: /* '''Wireless''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.

2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

---

All these steps are not required if you have T61 with Intel graphics card (as I do), in this case everything works just fine out of the box.

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

---

My T61 comes with "Intel Corporation PRO/Wireless 3945ABG" wifi controller, which worked out of the box without installing any additional drivers (yeah, I did not forgot to insteall iwlwifi and iwl3945 packages during the installation).

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

---

Bluetooth freezes my machine after waking up from suspend-to-ram (making it almost impossible to debug).
I don't use any bluetooth devices, so I have just disabled it by `echo "disable" > /proc/acpi/ibm/bluetooth`.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

---

Yes, it works fine in console, though neither kdm, nor gdm support it, which makes this thing pretty much useless.
The only advantage is that you don't need to type root password when doing 'su -'.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

---

Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-10-08T14:26:40Z

Tony2001: /* '''Video''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.

2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

---

All these steps are not required if you have T61 with Intel graphics card (as I do), in this case everything works just fine out of the box.

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

---

Bluetooth freezes my machine after waking up from suspend-to-ram (making it almost impossible to debug).
I don't use any bluetooth devices, so I have just disabled it by `echo "disable" > /proc/acpi/ibm/bluetooth`.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

---

Yes, it works fine in console, though neither kdm, nor gdm support it, which makes this thing pretty much useless.
The only advantage is that you don't need to type root password when doing 'su -'.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

---

Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-10-08T14:25:36Z

Tony2001: /* '''Bluetooth''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.

2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

---

Bluetooth freezes my machine after waking up from suspend-to-ram (making it almost impossible to debug).
I don't use any bluetooth devices, so I have just disabled it by `echo "disable" > /proc/acpi/ibm/bluetooth`.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

---

Yes, it works fine in console, though neither kdm, nor gdm support it, which makes this thing pretty much useless.
The only advantage is that you don't need to type root password when doing 'su -'.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

---

Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-10-08T14:24:02Z

Tony2001: /* '''Suspend and Suspend to Disk''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.

2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

---

Yes, it works fine in console, though neither kdm, nor gdm support it, which makes this thing pretty much useless.
The only advantage is that you don't need to type root password when doing 'su -'.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

---

Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-10-08T14:23:51Z

Tony2001: /* '''Think finger''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.

2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

---

Yes, it works fine in console, though neither kdm, nor gdm support it, which makes this thing pretty much useless.
The only advantage is that you don't need to type root password when doing 'su -'.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

----

Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-10-08T14:22:11Z

Tony2001: /* '''Suspend and Suspend to Disk''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.

2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

----

Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Installing openSUSE 10.3 GM on a ThinkPad T61

2007-10-08T14:21:26Z

Tony2001: /* '''Suspend and Suspend to Disk''' */

Here are my specs on my thinkpad t61

2.0GHz 4meg cache core 2 duo

2 gigs of ram

nvidia nv140 128 megs of ram

14.1 inch 1440x900 display

atheros a/b/g wireless card

Think finger

100 GB 7200 RPM hard drive

There are other configurations out there, so hopefully people with the different parts can do their part and chip with how they got their to work.

== '''Video''' ==
Thinkpads have an option for either an nv140 or an Intel card. I only have the nvidia option, so someone else can add the Intel card.

'''Nvidia'''
There are multiple ways to do it, but I am going to do the old fashioned way from nvidia, while it may be a little harder, you can do it with any driver.

1. Download the linux x86_64 driver from http://www.nvidia.com, note where you download it to. Also ensure that you installed "Linux kernel development" under yast, software.

2. once done, open a terminal console with a "ctrl- alt - f2"

3. login as root

4. execute the command ''init 3''

5. After it is done (a few seconds later), hit enter once

6. cd to where you downloaded the file (by default /home/$USERNAME/Desktop where $USERNAME is the user WHO DOWNLOADED THE FILE)

7. execute''sh NVIDIA-Linux-x86_64-100.14.19-pkg2.run''

8. Answer a bunch of questions, at the end answer yes to setting up you xorg.conf file.

9. Run a ''init 6'' to reboot

== '''Wireless''' ==

To my knowledge this laptop comes with an option for 3 different wireless network cards. Here are my instructions for the atheros, I am hoping someone else can write the instructions for everything else.

'''Atheros:'''
1.Go to madwifi's home page (using the wired Ethernet will work, or you can use another machine) http://madwifi.org/. From this website you can download the driver.

2. Open up the command line (konsole) and "Untar" the file with a ''tar xvf madwifi-0.9.3.2.tar.gz''

3. Switch to the root user with ''su'' then change into the directory with a ''cd madwifi-0.9.3.2''

4. compile the driver and load the module (it is really easy, I promise) with a ''make ; make install; modprobe ath_pci''. You should get a bunch of jibberish on your screen and a few minutes later it will be done.

4. Open up yast by hitting "alt-f2" and typing in "yast".

5. Go to network devices -> Network card -> add

6. Select the device type to wireless

7. add to the module name ath_pci and hit next.

8. configure it for your network

9. Once you reboot you should be good to go.

== '''Sound''' ==

Sound works out of the box, it is just set up a little funky. In KDE if you go to the speaker icon and click on it, then go to "mixer" to get to the settings. Here you will raise the volume on "PCM". Then go to the tab "switches" and ensure that speaker is turned on. Once you are done right click on the speaker icon again and go to "select master control". Select "PCM" and hit ok. Your buttons will now to raise and lower the volume. Mute does nothing though.

== '''Display''' ==

1440x900 working great. Selected 16:10 aspect ratio when installing and then the resolution and it is working fine.
The brightness adjuster doesn't work in X.org. You need to switch to a console (ctrl - alt - f2) to lower the brightness, then switch back (ctrl - alt - f7). Hopefully someone gets this working! I am pretty sure it is an issue with the nvidia driver, but I can't be for sure.

== '''Bluetooth''' ==

Works like a champ, I set up a wireless mouse with it using KDE, no problem.

== '''Think finger''' ==

Coolest feature of this laptop, of course we need to get it working.

1. Go to yast (alt-f2 and type in yast) then "hardware" -> "Fingerprint Reader". Just simply enable it and then hit finish. Yast will install a few packages and you are ready to set it up.

2. From the console execute ''tf-tool --add-user $USERNAME'' where username is your username.

3. Swipe your finger successfully three times and you are done, to login type in your username and then swipe your finger.

== '''Suspend and Suspend to Disk''' ==

Not working so well, hit suspend and it does nothing. Suspend to disk works, and then won't successfully wake up.

***
Works like a charm here, both to ram and to disk.
Checkout kpowersave settings and make sure you have this line: S2RAM_OPTS="-f -a3" in /etc/pm/config.d/defaults (-f is needed because T61 is quite new and not yet listed in s2ram database).

Problems with ACPI suspend-to-ram

2007-09-06T20:28:13Z

Tony2001: /* Troubles on resume */

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /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.

;Hangs on "switching to UP code":You may be using a [[How to make use of Dynamic Frequency Scaling|frequency scaling governor]] such as "conservative" or "ondemand", which sometimes have problems with suspending. Switching to a governor such as "powersave" or "performance" before suspending may solve this problem.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep: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.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

;Immediate Resume, but Suspend "moon" light continues to flash:???

;Hard system lock up:If you are using savagefb, make sure to [[Problem_with_unusable_console|disable the "Console Acceleration" option]] (CONFIG_FB_SAVAGE_ACCEL) in the kernel config. Otherwise, susped-to-RAM may lock up your system such that you must remove the AC adapter and battery to get it to boot again.

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;Garbage on text consoles on resume:When resuming from suspend-to-ram the text console displays may show garbage instead of actual text. The machine is otherwise still responsive and X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|echo 7 off > /proc/acpi/ibm/led}}

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with {{cmdroot|echo mem > /sys/power/state}}, make sure '''uswsusp''' and '''hibernate''' are uninstalled.

;System hang on resume:
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20,T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''
:See also [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/73546 this bug report], I can confirm some strange problems on resume with Bluetooth enabled - my T61 may freeze in a couple of minutes after resuming. This problem is gone as soon as I disable Bluetooth (stop all bluetooth related services and `echo "disable" > /proc/acpi/ibm/bluetooth`).

;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq?action=recall&rev=28#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18.

User talk:Tony2001

2007-08-29T18:13:25Z

Tony2001: /* tp_smapi inhbit_charge_minutes */

==tp_smapi inhbit_charge_minutes==
Regarding your edit to [[tp_smapi]]: how does inhbit_charge_minutes fail, and what's does ''dmesg'' say when you write to that attribute?

--[[User:Thinker|Thinker]] 21:05, 28 August 2007 (UTC)

It does not fail, but it doesn't take any effect.
dmesg says that inhabit_charge_minutes has been set, but the battery's state is still "idle".

# echo 1 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes
# dmesg
...
smapi smapi: set_inhibit_charge_minutes: set to 1 for bat=0

# cat /sys/devices/platform/smapi/BAT0/state
idle

--[[User:tony2001|tony2001]]

That's the expected behavior. To test, write 3 to inhibit_charge_minutes when the battery is charging. It should stop charging for 3 minutes, and then resume charging.

--[[User:Thinker|Thinker]] 17:45, 29 August 2007 (UTC)

Oh. Ok, then I guess everything works fine.

--[[User:tony2001|tony2001]]

----

User talk:Thinker

2007-08-29T10:14:08Z

Tony2001:

Hi,

regarding those issues with R&R from grub: two things seem quite crucial to me after a bit of experimenting: one must not touch the mbr and one must not touch the partition type for that recovery partition (T43). As long as these two are observed, the rest seems to be fine. I am using this in my grub.conf:

title=IBM rescue and recover
rootnoverify (hd0,1)
chainloader +1

Partition type is 0x12 (compaq diagnostics in fdisk) and the MBR is T43's "factory" one.

[[User:Igor|Igor]]
----

I had to put GRUB in the MBR, since the default MBR would always boot into the Windows partition, even if I put GRUB in a primary partition and marked (only) that partition bootable.

--[[User:Thinker|Thinker]] 01:10, 25 January 2006 (CET)
----

Okey, here is what I did. I hosed the MBR during my bizarre experiments, but IBM has been kind enough to release a floppy fixer for that (somewhere else on the wiki). In no particular order:

* Restore the original MBR
* Install grub into the boot partition (sda3). Not the drive (sda), but the boot partition (sda3).
* Mark sda3 as bootable. This must be the ONLY bootable partition.
* Make sure that the partition types are correct: NTFS for WinXP (sda1), 0x12 for R&R (sda2), 0x83 for /boot
* Conjure a suitable grub.conf. Mine is:

title=Gentoo Linux 2.6.15-r1 (gentoo-sources) + (ibm-acpi)
root (hd0,2)
kernel /vmlinuz-2.6.15-gentoo-r1 acpi_sleep=s3_bios pci=noacpi libata.atapi_enabled=1

title=Windows XP
rootnoverify (hd0,0)
chainloader +1

That's it folks :)
--[[User:Igor|Igor]]
----

Another thing to try for restauring the MBR is to restore the laptop to the factory state. If other OSes are *NOT* on the first primary partition, a little fiddling with the partition layout in fdisk should restore the partition picture before the restore (factory state restore will restore windows, but it will not touch any partitions except for the first one).

--[[User:Igor|Igor]]
----

Thanks, but I did exactly that, and it never booted into GRUB. No idea why; I triple-checked the bootable partition flags, but the factory MBR just didn't seem to care about them. Eventually I just gave up on R&R and relaimed its 4GB of diskspace (of course, I have backup discs). Is there something particularly exciting that R&R can and IBM's PC Doctor bootable CD can't do?

--[[User:Thinker|Thinker]] 09:47, 25 January 2006 (CET)
----

Not that I know of. The only useful scenario is a diagnostic by PC doctor, without any rescue CDs around. BIOS POST -> R&R -> reboot -> Diagnostic. It is just that it is supposed to work. Strange that it did not boot into GRUB.

--[[User:Igor|Igor]]

>Regarding your edit to tp_smapi: how does inhbit_charge_minutes fail, and what's does dmesg say when you write to that attribute?

It does not fail, but it doesn't take any effect.
dmesg says that inhabit_charge_minutes has been set, but the battery's state is still "idle".

# echo 1 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes
# dmesg
...
smapi smapi: set_inhibit_charge_minutes: set to 1 for bat=0

# cat /sys/devices/platform/smapi/BAT0/state
idle

--[[User:tony2001|tony2001]]

How to enable the integrated fingerprint reader with ThinkFinger

2007-08-28T20:20:00Z

Tony2001:

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

== Installing from source ==
Speaking for Debian, there are no packages of ThinkFinger in the repositories yet (cf. [http://bugs.debian.org/409563 bug #409563]), so I describe the installation from source. If you are using Gentoo, you can just emerge sys-auth/thinkfinger.

{{NOTE|packages for Debian (testing) are available here: [http://www.rubixlinux.org/debian/thinkfinger/]}}
{{NOTE|packages for Fedora Core 6 are available in "extras" repository (#yum install thinkfinger)}}
{{NOTE|openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages here: [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/]}}

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkgconfig, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the dir, where pam assumes its modules on Debian and openSUSE, it may vary for your distro!}}

{{NOTE|for openSUSE use this configure-command:}}
<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

If everything went ok assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

== Testing the driver ==
Now the driver is installed and should be working. You can try it (as root) with

{{cmdroot|tf-tool --acquire}}

and

{{cmdroot|tf-tool --verify}}

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

== Configuring PAM to use ThinkFinger ==
Now you can configure pam to use ThinkFinger:

Open /etc/pam.d/common-auth:
{{NOTE|In FC6 this file is "/etc/pam.d/system-auth"}}

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance my /etc/pam.d/common-auth looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2 it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

Now we are ready to add users to thinkfinger. As make install did not create /etc/pam_thinkfinger, we need to create it now:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

And now we can add a fingerprint for a user with:

{{cmdroot|tf-tool --add-user $USERNAME}}

Now the user should be able to login with his finger, instead of the password.

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

{{NOTE|If you would like to use thinkfinger for su, you have to enroll fingerprint for root user! (tf-tool --add-user root)}}
{{NOTE|gksu/gksudo seems to break. However, it just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.}}

{{NOTE|Using gksu/gksudo in ubuntu Feist Fawn (7.04) with thinkfinger enabled, crashed gksu/gksudo everytime I tried to authenticate.
Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory, fixed this behavior ( I'm using thinkfinger 0.3 ). Of course in the Console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime :).}}

Integration in KDE and kdm seems not to be easily possible now. There is a filed bug at kde.org where you can vote for this: [https://bugs.kde.org/show_bug.cgi?id=116682].

Moreover, kdm in openSUSE 10.3 crashes for me when pam_thinkfinger enabled.
I was able to "workaround" this by downgrading thinkfinger to 0.22 instead of 0.3 (the latest at the moment).
So atm kdm does not crash anymore, but pam_thinkfinger is only used in shell.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified by me.

How to enable the integrated fingerprint reader with ThinkFinger

2007-08-28T20:17:54Z

Tony2001:

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

== Installing from source ==
Speaking for Debian, there are no packages of ThinkFinger in the repositories yet (cf. [http://bugs.debian.org/409563 bug #409563]), so I describe the installation from source. If you are using Gentoo, you can just emerge sys-auth/thinkfinger.

{{NOTE|packages for Debian (testing) are available here: [http://www.rubixlinux.org/debian/thinkfinger/]}}
{{NOTE|packages for Fedora Core 6 are available in "extras" repository (#yum install thinkfinger)}}
{{NOTE|openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages here: [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/]}}

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkgconfig, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the dir, where pam assumes its modules on Debian and openSUSE, it may vary for your distro!}}

{{NOTE|for openSUSE use this configure-command:}}
<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

If everything went ok assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

== Testing the driver ==
Now the driver is installed and should be working. You can try it (as root) with

{{cmdroot|tf-tool --acquire}}

and

{{cmdroot|tf-tool --verify}}

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

== Configuring PAM to use ThinkFinger ==
Now you can configure pam to use ThinkFinger:

Open /etc/pam.d/common-auth:
{{NOTE|In FC6 this file is "/etc/pam.d/system-auth"}}

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance my /etc/pam.d/common-auth looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2 it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

Now we are ready to add users to thinkfinger. As make install did not create /etc/pam_thinkfinger, we need to create it now:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

And now we can add a fingerprint for a user with:

{{cmdroot|tf-tool --add-user $USERNAME}}

Now the user should be able to login with his finger, instead of the password.

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

{{NOTE|If you would like to use thinkfinger for su, you have to enroll fingerprint for root user! (tf-tool --add-user root)}}
{{NOTE|gksu/gksudo seems to break. However, it just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.}}

{{NOTE|Using gksu/gksudo in ubuntu Feist Fawn (7.04) with thinkfinger enabled, crashed gksu/gksudo everytime I tried to authenticate.
Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory, fixed this behavior ( I'm using thinkfinger 0.3 ). Of course in the Console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime :).}}

Integration in KDE and kdm seems not to be easily possible now. There is a filed bug at kde.org where you can vote for this: [https://bugs.kde.org/show_bug.cgi?id=116682].
Moreover, kdm in openSUSE 10.3 crashes for me when pam_thinkfinger enabled.
I was able to "workaround" this downgrading thinkfinger to 0.22 instead of 0.3 (the latest at the moment).
So atm it works in shell, but kdm does not crash anymore.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified by me.

Tp smapi

2007-08-28T20:13:37Z

Tony2001:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
The <tt>tp_smapi</tt> kernel module exposes some features of the ThinkPad hardware/firmware via a <tt>sysfs</tt> interface. Currently, the main implemented functionality is control of battery charging and extended battery status. The underlying hardware interfaces are [[SMAPI support for Linux|SMAPI]] and direct access to the embedded controller.

For older ThinkPad models, see also [[tpctl]].

{{WARN|This driver uses undocumented features and direct hardware access. It thus cannot be guaranteed to work and could conceivably damage your computer (though so far no incidents have been reported).}}
|}

===Features===
*Battery charge/discharge control
*Battery status information

===Project Homepage / Availability===
* Project page: http://tpctl.sourceforge.net/
* You need to [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=171579 download] only the <tt>tp_smapi</tt> package.

===Installation===
====Installation from source====
You will need the kernel headers and makefiles corresponding to your current kernel version. On {{Fedora}}, this means {{cmdroot|yum install kernel-devel-$(uname -r)}} .

For testing, you can simply compile and load the driver within the current
working directory:
:{{cmdroot|tar xzvf tp_smapi-0.32.tgz}}
:{{cmdroot|cd tp_smapi-0.32}}
:{{cmdroot|make load}}

To compile and install into the kernel's module path:
:{{cmdroot|make install}}

If you use the [[HDAPS]] driver, add <tt>HDAPS=1</tt> to also patch the <tt>hdaps</tt> for compatibility with <tt>tp_smapi</tt> (this requires a kernel source tree matching the current kernel):
:{{cmdroot|1=make load HDAPS=1}}
or, to compile and install into the kernel's module path:
:{{cmdroot|1=make install HDAPS=1}}

To prepare a stand-alone patch against the current kernel tree (including
a patch against <tt>hdaps</tt> and new <tt>Kconfig</tt> entries):
:{{cmdroot|make patch}}

To delete all autogenerated files:
:{{cmdroot|make clean}}

The original kernel tree is never modified by any these commands.
The {{path|/lib/modules}} directory is modified only by {{cmdroot|make install}}.

====Installation in Gentoo====
The {{Gentoo}} portage system carries a [http://packages.gentoo.org/packages/?category=app-laptop;name=tp_smapi tp_smapi package], which follows the latest version pretty closely. On a Gentoo system, you can install and load as follows.

If you use the [[HDAPS]] driver, do this first:

* Configure <tt>hdaps</tt> as module in your kernel
* Add the <tt>HDAPS</tt> use flag in {{path|/etc/make.conf}}
* {{cmdroot|rmmod hdaps}}

Then:

* {{cmdroot|emerge tp_smapi}} (or install tp_smapi with hdaps support manually, as above)
* {{cmdroot|echo "tp_smapi" >> /etc/modules.autoload.d/kernel-2.6}}
* {{cmdroot|echo "hdaps" >> /etc/modules.autoload.d/kernel-2.6}}

Then reboot, or run:
* {{cmdroot|modprobe tp_smapi}}
* {{cmdroot|modprobe hdaps}}

====Installation on Ubuntu/Debian====

Installation on Ubuntu or Debian is quite easy, but there are a few things to look after:

To get your system ready for compiling code, install the build-essentials (as root, of course, as all of the following comands; Ubuntu users have to prepend 'sudo' to every line and enter their own password when prompted):
<pre><nowiki>apt-get install build-essentials</nowiki></pre>

To get tp_smapi to work, obtain the latest source as mentioned above and unpack it. If you want to use HDAPS, you need to install the kernel source matching te kernel you are running. To do so, issue this:
<pre><nowiki>uname -r</nowiki></pre>
This will give you the version of your current kernel. As Ubuntu adds '-generic' to the kernel-version, the following command works for Debian users only:
<pre><nowiki>apt-get install linux-source-`uname -r`</nowiki></pre>
Ubuntu users use the kernel-version they got by the command before, e.g. 'linux-source-2.6.20'

Now change to the tp_smapi dir:
<pre><nowiki>cd tp_smapi-X.YY</nowiki></pre> (X.YY being the version-number of [[tp_smapi]])
and make and install tp_smapi as instructed above.

If you get an error that the kernel version isn't matching, please check that there is a symlink from the modules dir to the kernel source:
<pre><nowiki>root@localhost:~#ls -l /lib/modules/2.6.20-6-generic
lrwxrwxrwx 1 root root 28 2007-02-02 08:39 source -> /usr/src/linux-source-2.6.20</nowiki></pre>
Create the link if the line above is not existent:
<pre><nowiki>root@localhost:~#ln -s /usr/src/linux-source-2.6.20 /lib/modules/2.6.20-6-generic/source</nowiki></pre>

Now the following will build and install the correct modules to their locations:
<pre><nowiki>make install HDAPS=1</nowiki></pre>
To make sure your system loads the modules at boot time, do this:
<pre><nowiki>echo "tp_smapi" >> /etc/modules
echo "hdaps" >> /etc/modules</nowiki></pre>
and update your initramfs:
<pre><nowiki>update-initramfs -u</nowiki></pre>

To get tp_smapi running now, just load the modules:
<pre><nowiki>modprobe -a tp_smapi hdaps</nowiki></pre>

This description was tested on Kubuntu 'Feisty Fawn' and should work on all Debian-based distros with minor tweaks.

===Battery charge control features===
To set the thresholds for starting and stopping battery charging (in percent of current full charge capacity):
:{{cmdroot|echo 40 > /sys/devices/platform/smapi/BAT0/start_charge_thresh}}
:{{cmdroot|echo 70 > /sys/devices/platform/smapi/BAT0/stop_charge_thresh}}
:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/*_charge_thresh}}
{{HINT|Battery charging thresholds can be used to keep Li-Ion ad Li-Polymer batteries partially charged, in order to [[Maintenance#Battery_treatment|increase their lifetime]].}}
To unconditionally inhibit charging for 17 minutes:
:{{cmdroot|echo 17 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}
{{HINT|Charge inhibiting can be used to reduce the power draw of the laptop, in order to use an under-spec power supply that can't handle the combined power draw of running and charging. It can also be used to control which battery is charged when [[How to use UltraBay batteries|using an Ultrabay battery]].}}

To cancel charge inhibiting:
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}

To force battery discharging even if connected to AC, use one of these:
:{{cmdroot|echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge}}
{{HINT|This can be used to choose which battery is discharged when [[How to use UltraBay batteries|using an UltraBay battery]].}}

To cancel forced discharge:
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/force_discharge}}

===Battery status features===
To view extended battery status such as charging state, voltage, current, capacity, cycle count and model information:

<pre>
# cat /sys/devices/platform/smapi/BAT0/installed
# cat /sys/devices/platform/smapi/BAT0/state # idle/charging/discharging
# cat /sys/devices/platform/smapi/BAT0/cycle_count
# cat /sys/devices/platform/smapi/BAT0/current_now # instantaneous current
# cat /sys/devices/platform/smapi/BAT0/current_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/power_now # instantaneous power
# cat /sys/devices/platform/smapi/BAT0/power_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/last_full_capacity
# cat /sys/devices/platform/smapi/BAT0/remaining_percent
# cat /sys/devices/platform/smapi/BAT0/remaining_running_time
# cat /sys/devices/platform/smapi/BAT0/remaining_charging_time
# cat /sys/devices/platform/smapi/BAT0/remaining_capacity
# cat /sys/devices/platform/smapi/BAT0/design_capacity
# cat /sys/devices/platform/smapi/BAT0/voltage
# cat /sys/devices/platform/smapi/BAT0/design_voltage
# cat /sys/devices/platform/smapi/BAT0/manufacturer
# cat /sys/devices/platform/smapi/BAT0/model
# cat /sys/devices/platform/smapi/BAT0/barcoding
# cat /sys/devices/platform/smapi/BAT0/chemistry
# cat /sys/devices/platform/smapi/BAT0/serial
# cat /sys/devices/platform/smapi/BAT0/manufacture_date
# cat /sys/devices/platform/smapi/BAT0/first_use_date
# cat /sys/devices/platform/smapi/BAT0/temperature # in milli-Celsius
# cat /sys/devices/platform/smapi/ac_connected
</pre>

The raw status data is also available, including some fields not listed above (in case you can figure them out):

:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/dump}}

In all of the above, replace <tt>BAT0</tt> with <tt>BAT1</tt> to address the 2nd battery.

Note that the battery status readout conflicts with the stock [[HDAPS|hdaps]] driver, so if you use <tt>hdaps</tt> you will need to load <tt>tp_smapi</tt> using {{cmdroot|1=make load HDAPS=1}} (see [[#Bundled hdaps driver|Bundled hdaps driver]] below).

On [[ACPI]]-enabled systems, most of above information is also available through the files under {{path|/proc/acpi/battery}}. However, the ACPI interface does not include the instantaneous power and cycle count readouts, and does not work well when [[How to use UltraBay batteries|hotswapping UltraBay batteries]].

===Other features===

There is also [[sysfs]] attribute for making direct SMAPI requests to the SM BIOS firmware. Don't touch it unless you really know what you're doing. Example:
# echo '211a 100 0 0 > /sys/devices/platform/smapi/smapi_request; cat /sys/devices/platform/smapi/smapi_request
211a 34b b2 0 0 0 'OK'
The 4b" in the 2nd value, converted to decimal is 75: the current charge stop threshold.

===Bundled <tt>hdaps</tt> driver===

The tp_smapi package includes a modified version of the <tt>hdaps</tt> Linux kernel driver used by the [[HDAPS]] system. To use <tt>tp_smapi</tt> and <tt>hdaps</tt> concurrently, you '''must''' use the modified version.

To build the modified version, simply append the <tt>HDAPS=1</tt> parameter to the <tt>make</tt> command (see [[#Installation|Installation]] above):
:{{cmdroot|1=make load HDAPS=1}}
or
:{{cmdroot|1=make install HDAPS=1}}

If you don't do that, you will not be able to load <tt>tp_smapi</tt> (and its support module <tt>thinkpad_ec</tt>) when <tt>hdaps</tt> is loaded, and vice versa. You can use <tt>rmmod</tt> to switch between these modules.

Note that some of the battery status is also visible through ACPI ({{path|/proc/acpi/battery/*}}), independently of <tt>tp_smapi</tt>.

The modified <tt>hdaps</tt> has several changes:
* The <tt>hdaps</tt> driver in mainline kernels conflicts with the extended battery status (they use the same IO ports). The modified <tt>hdaps</tt> coordinates this access through the bundled <tt>thinkpad_ec</tt> driver.
* The modified <tt>hdaps</tt> driver fixes reliability and improves support for recent ThinkPad models (*60 and newer), since unlike the mainline driver, it correctly follows the Embedded Controller communication protocol.
* Several other improvements, such as the ability to control the polling rate.

===Troubleshooting===

If you get <tt>thinkpad_ec: no ThinkPad embedded controller!</tt> when trying to load the module on a supported model listed below, you should [[BIOS_Upgrade|upgrade your BIOS]]. Some early BIOS (like 1.x on the X31) don't handle the embedded controller.

===Model-specific status===

<div style="font-size: 92%">
{| border="1" cellspacing="0" cellpadding="2"
|+<tt>tp_smapi</tt> feature support matrix
|-
! colspan=11 style="text-align:center;background:#efefef;" |
=====A series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{A22p}} 2629-USG
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{A30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
=====G series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{G41}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || || ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
=====R series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{R31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || No SMAPI BIOS
|-
! {{R40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{R50}}
| {{Cunk}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{R50e}} 1834-JAG
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{R50p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{R51}} 18*
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=X, Y'=Y || 0.32 || 3.22 || Machine types 1829, 1830, 1831 and 1836
|-
! {{R51}} 28*
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || 1.29 || Machine types 2883, 2887, 2888, 2889, 2894 and 2495
|-
! {{R52}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=X, Y'=Y || 0.32 || 1.29 ||
|-
! {{R60}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||{{Cyes}} || {{Cunk}} || || ||
|-

! colspan=11 style="text-align:center;background:#efefef;" |

=====T series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{T20}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T22}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T23}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T40p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T41p}} 2373-AM9
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=-X, Y'=-Y || 0.32 || 3.20 || EC v3.04
|-
! {{T42}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T42p}} 2373-KXU
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=-X, Y'=-Y || 0.32 || 3.21 || Stop charge threshold works in Windows. dmesg output:
smapi smapi: smapi_request: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)
smapi smapi: __get_real_thresh: cannot get stop_thresh of bat=0: Function is not supported by SMAPI BIOS
|-
! {{T42p}} 2373-KUU
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T43}} 2686
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=X, Y'=Y || 0.32 || 1.27 ||
|-
! {{T43p}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T60}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} X'=Y, Y'=-X || 0.32 || ||
|-
! {{T60p}} 8743-CTO
| {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=-X, Y'=-Y || 0.32 || ||
|-
! {{T61}}
| {{Cyes}} || {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || 0.32 || || [http://ubuntuforums.org/showthread.php?p=3146719 ref]
|-
! colspan=11 style="text-align:center;background:#efefef;" |

=====X series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{X20}} 2662-31G
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{X24}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{X31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{X32}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{X40}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} X'=X, Y'=-Y || 0.32 || 2.08 || EC v1.62
|-
! {{X41}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cno|text=}} X'=X, Y'=-Y || 0.32 || ||
|-
! {{X60}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || || 2.07 || EC v1.10, 2.6.20 issue (see discussion)
|-
! {{X61s}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cno|text=}} X'=X, Y'=-Y || 0.32 || || [http://www.slackwiki.org/ThinkPad_X61s ref]
|-
! {{X60T}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || || || [http://luke.no-ip.org/x60tablet/ ref] [http://rad.bioinfo.ulaval.ca/hardware/x60tablet ref]
|-
! {{X61T}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}}X'=-Y, Y'=X || 0.32 || ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |

=====Z series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{Z60m}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{Z60t}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{Z61m}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=X, Y'=Y || 0.32 || ||
|-
! {{Z61t}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || || || [https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/45014 ref]
|}
</div>

SMAPI capabilities may depend on the BIOS version as well, so upgrading to the latest version of the BIOS might provide more SMAPI functions (especially true for long-lived BIOS with lots of releases, like the TP-1R).

Please update the above and report your experience on the [[Talk:tp_smapi|discussion]] page. If the module loads but gives a "<tt>not supported</tt>" or "<tt>not implementeded</tt>" error when you try to use some specific file in {{path|/sys/devices/platform/smapi/}}, please report the <tt>dmesg</tt> output and whether the corresponding functionality is available under Windows - maybe your ThinkPad just can't do that.

While at it, you may also want to add your laptop to the [[list of DMI IDs]].

=====HDAPS axis orientation=====
HDAPS axis orientation notation: X,Y are the hardware readouts, X',Y' are horizontal and vertical. You can use [[HDAPS#Visualisation_of_ThinkPad_orientation|hdaps visualisation]] to check for correctness.

[[Category:Drivers]] [[Category:Patches]]

===Tools using this driver===

The driver's interface can be accessed directly through the files under {{path|/sys/devices/platform/smapi}}, or via the following tools:
* [[KThinkBat]] - display battery status on the KDE <tt>kicker</tt> panel.
* [[gkrellm-ThinkBat]] - battery status plugin for Gkrellm2
* {{CodeRef|thinkpad-smapi.sh}} - script to display various SMAPI information using tp_smapi module.