ThinkWiki - User contributions [en]

Installing Ubuntu on a ThinkPad X60 Tablet

2009-08-18T16:35:50Z

Samoht: /* What works out-of-the-box */

This report describes the installation and customization of Ubuntu Jaunty (9.04) on a Thinkpad X60 (6363) Tablet.

= Installing without CD-Rom =

I considered going the simple way and created a bootable usbstick with [http://unetbootin.sourceforge.net UNetbootin].
Choose Ubuntu "live" (9.04) and all the required data is downloaded automagically and a proper stick is built.

= What works out-of-the-box =

* Suspend to disk
* Suspend to RAM
* Atheros Wifi (ath5k)
* Fn Hotkeys
* Intel GMA 945 Acceleration (this breaks display rotation though...)
* Bluetooth
* Ethernet
* Wacom stylus input

= What does not work out-of-the-box =

== Automatic screen rotation on swivel ==

1. Check out this repository and build a package:
bzr branch lp:~karl.hegbloom/tabuntu/tablet-screen-rotation-support
cd tablet-screen-rotation-support
dpkg-buildpackage
cd ..
sudo dpkg -i tablet-screen-rotation-support_0.1.8_i386.deb

2. Edit sudoers file...
visudo
... add this line..
%video ALL=NOPASSWD: /usr/bin/setkeycodes
... and add your user to the 'video' group.
sudo adduser $USER video

3. After a reboot the display and stylus rotate but unfortunately the screen gets garbled because of some graphic drivers bug. You have to turn of DRI to fix it. So you can get either DRI and desktop effects OR rotation. :(

sudo gedit /etc/X11/xorg.conf
add following line to your "Devices" section:
Option "DRI" "off"

[[Category:Ubuntu]]

Installing Ubuntu on a ThinkPad X60 Tablet

2009-08-18T16:34:05Z

Samoht: /* Automatic screen rotation on swivel */ intel bug

This report describes the installation and customization of Ubuntu Jaunty (9.04) on a Thinkpad X60 (6363) Tablet.

= Installing without CD-Rom =

I considered going the simple way and created a bootable usbstick with [http://unetbootin.sourceforge.net UNetbootin].
Choose Ubuntu "live" (9.04) and all the required data is downloaded automagically and a proper stick is built.

= What works out-of-the-box =

* Suspend to disk
* Suspend to RAM
* Atheros Wifi (madwifi)
* Fn Hotkeys
* Intel video driver: fancy 3D compositing is enabled
* Bluetooth
* Ethernet
* Wacom stylus input

= What does not work out-of-the-box =

== Automatic screen rotation on swivel ==

1. Check out this repository and build a package:
bzr branch lp:~karl.hegbloom/tabuntu/tablet-screen-rotation-support
cd tablet-screen-rotation-support
dpkg-buildpackage
cd ..
sudo dpkg -i tablet-screen-rotation-support_0.1.8_i386.deb

2. Edit sudoers file...
visudo
... add this line..
%video ALL=NOPASSWD: /usr/bin/setkeycodes
... and add your user to the 'video' group.
sudo adduser $USER video

3. After a reboot the display and stylus rotate but unfortunately the screen gets garbled because of some graphic drivers bug. You have to turn of DRI to fix it. So you can get either DRI and desktop effects OR rotation. :(

sudo gedit /etc/X11/xorg.conf
add following line to your "Devices" section:
Option "DRI" "off"

[[Category:Ubuntu]]

Installing Ubuntu on a ThinkPad X60 Tablet

2009-08-15T11:30:25Z

Samoht:

This report describes the installation and customization of Ubuntu Jaunty (9.04) on a Thinkpad X60 (6363) Tablet.

= Installing without CD-Rom =

I considered going the simple way and created a bootable usbstick with [http://unetbootin.sourceforge.net UNetbootin].
Choose Ubuntu "live" (9.04) and all the required data is downloaded automagically and a proper stick is built.

= What works out-of-the-box =

* Suspend to disk
* Suspend to RAM
* Atheros Wifi (madwifi)
* Fn Hotkeys
* Intel video driver: fancy 3D compositing is enabled
* Bluetooth
* Ethernet
* Wacom stylus input

= What does not work out-of-the-box =

== Automatic screen rotation on swivel ==

Check out and build this repository:
bzr branch lp:~karl.hegbloom/tabuntu/tablet-screen-rotation-support
cd tablet-screen-rotation-support
dpkg-buildpackage
cd ..
sudo dpkg -i tablet-screen-rotation-support_0.1.8_i386.deb

Edit sudoers file...
visudo
... add this line..
%video ALL=NOPASSWD: /usr/bin/setkeycodes
... and add your user to the 'video' group.
sudo adduser $USER video

[[Category:Ubuntu]]

Installing Ubuntu on a ThinkPad X60 Tablet

2009-08-15T11:20:11Z

Samoht: Update to ubuntu 9.04

This report describes the installation and customization of Ubuntu Jaunty (9.04) on a Thinkpad X60 (6363) Tablet.

= Installing without CD-Rom =

I considered going the simple way and created a bootable usbstick with [http://unetbootin.sourceforge.net UNetbootin].
Choose Ubuntu "live" (9.04) and all the required data is downloaded automagically and a proper stick is built.

= What works out-of-the-box =

* Suspend to disk
* Suspend to RAM
* Atheros Wifi (madwifi)
* Fn Hotkeys
* Intel video driver: fancy 3D compositing is enabled
* Bluetooth
* Ethernet
* Wacom stylus input

= What does not work out-of-the-box =

== Automatic screen rotation on swivel ==

Check out and build this repository:
bzr branch lp:~karl.hegbloom/tabuntu/tablet-screen-rotation-support
./configure --prefix=/usr
make
sudo make install

Edit sudoers file...
visudo
... add this line..
%video ALL=NOPASSWD: /usr/bin/setkeycodes
... and add your user to the 'video' group.
sudo adduser $USER video

[[Category:Ubuntu]]

Installing Ubuntu on a ThinkPad X60 Tablet

2008-09-18T13:57:11Z

Samoht: /* What does not work out-of-the-box */

This report describes the installation and customization of Ubuntu Hardy (8.04) on a Thinkpad X60 6363.

= Installing without CD-Rom =

I considered going the simple way and created a bootable usbstick with UNetbootin under Windows.
Choose Ubuntu "netinstall" (8.04) and all the required data is downloaded automagically and a proper stick is built.
Make sure that the ethernet cable is plugged in '''before''' booting the stick. There's a bug in the ethernet driver (e1000/e) which prevents the device from settling down.
Check ubuntuwiki for more: [https://help.ubuntu.com/community/Installation/FromUSBStick Install Ubuntu from usbstick]

= What works out-of-the-box =

* Suspend to disk
* Suspend to RAM
* Atheros Wifi (madwifi)
* Most Fn-Keys
* video driver: fancy 3D compositing is enabled
* Bluetooth

= What does not work out-of-the-box =

* Ethernet (e1000/e) bug
* Wacom stylus input
* Screen rotation on swivel
* Fingerprint reader
* APS harddisk protection

= Powersaving / Performance customizatons =

== Daemons ==
Disable unnecessary daemons which are enabled by default with "sysv-rc-conf":
* brltty
* (pcmciautils)
* (bluetooth)
* pppd-dns
* timidity
* rsync

= TODO =
- stylus, screen rotation, handwriting input panel (cellwriter), fingerprint reader, powersaving customizations

[[Category:Ubuntu]]

Installing Ubuntu on a ThinkPad X60 Tablet

2008-09-16T11:49:59Z

Samoht: /* What does not work out-of-the-box */

This report describes the installation and customization of Ubuntu Hardy (8.04) on a Thinkpad X60 6363.

= Installing without CD-Rom =

I considered going the simple way and created a bootable usbstick with UNetbootin under Windows.
Choose Ubuntu "netinstall" (8.04) and all the required data is downloaded automagically and a proper stick is built.
Make sure that the ethernet cable is plugged in '''before''' booting the stick. There's a bug in the ethernet driver (e1000/e) which prevents the device from settling down.
Check ubuntuwiki for more: [https://help.ubuntu.com/community/Installation/FromUSBStick Install Ubuntu from usbstick]

= What works out-of-the-box =

* Suspend to disk
* Suspend to RAM
* Atheros Wifi (madwifi)
* Most Fn-Keys
* video driver: fancy 3D compositing is enabled
* Bluetooth

= What does not work out-of-the-box =

* Wacom stylus input
* Screen rotation on swivel
* Fingerprint reader
* APS harddisk protection

= Powersaving / Performance customizatons =

== Daemons ==
Disable unnecessary daemons which are enabled by default with "sysv-rc-conf":
* brltty
* (pcmciautils)
* (bluetooth)
* pppd-dns
* timidity
* rsync

= TODO =
- stylus, screen rotation, handwriting input panel (cellwriter), fingerprint reader, powersaving customizations

[[Category:Ubuntu]]

Installing Ubuntu on a ThinkPad X60 Tablet

2008-09-16T11:27:18Z

Samoht:

This report describes the installation and customization of Ubuntu Hardy (8.04) on a Thinkpad X60 6363.

= Installing without CD-Rom =

I considered going the simple way and created a bootable usbstick with UNetbootin under Windows.
Choose Ubuntu "netinstall" (8.04) and all the required data is downloaded automagically and a proper stick is built.
Make sure that the ethernet cable is plugged in '''before''' booting the stick. There's a bug in the ethernet driver (e1000/e) which prevents the device from settling down.
Check ubuntuwiki for more: [https://help.ubuntu.com/community/Installation/FromUSBStick Install Ubuntu from usbstick]

= What works out-of-the-box =

* Suspend to disk
* Suspend to RAM
* Atheros Wifi (madwifi)
* Most Fn-Keys
* video driver: fancy 3D compositing is enabled
* Bluetooth

= What does not work out-of-the-box =

* Wacom stylus input
* Screen rotation on swivel
* Fingerprint reader

= Powersaving / Performance customizatons =

== Daemons ==
Disable unnecessary daemons which are enabled by default with "sysv-rc-conf":
* brltty
* (pcmciautils)
* (bluetooth)
* pppd-dns
* timidity
* rsync

= TODO =
- stylus, screen rotation, handwriting input panel (cellwriter), fingerprint reader, powersaving customizations

[[Category:Ubuntu]]

Installing Ubuntu on a ThinkPad X60 Tablet

2008-09-16T11:26:20Z

Samoht: diable daemons

This report describes the installation and customization of Ubuntu Hardy (8.04) on a Thinkpad X60 6363.

= Installing without CD-Rom =

I considered going the simple way and created a bootable usbstick with UNetbootin under Windows.
Choose Ubuntu "netinstall" (8.04) and all the required data is downloaded automagically and a proper stick is built.
Make sure that the ethernet cable is plugged in '''before''' booting the stick. There's a bug in the ethernet driver (e1000/e) which prevents the device from settling down.
Check ubuntuwiki for more: [https://help.ubuntu.com/community/Installation/FromUSBStick Install Ubuntu from usbstick]

= What works out-of-the-box =

* Suspend to disk
* Suspend to RAM
* Atheros Wifi (madwifi)
* Most Fn-Keys
* video driver: fancy 3D compositing is enabled
* Bluetooth

= What does not work out-of-the-box =

* Wacom stylus input
* Screen rotation on swivel
* Fingerprint reader

= Powersaving / Performance customizatons =
* disable unnecessary daemons which are enabled by default with "sysv-rc-conf".
* brltty
* (pcmciautils)
* (bluetooth)
* pppd-dns
* timidity
* rsync

= TODO =
- stylus, screen rotation, handwriting input panel (cellwriter), fingerprint reader, powersaving customizations

[[Category:Ubuntu]]

Installing Ubuntu on a ThinkPad X60 Tablet

2008-09-15T20:44:05Z

Samoht: â†Created page with 'This report describes the installation and customization of Ubuntu Hardy (8.04) on a Thinkpad X60 6363. = Installing without CD-Rom = I considered going the simple way a...'

This report describes the installation and customization of Ubuntu Hardy (8.04) on a Thinkpad X60 6363.

= Installing without CD-Rom =

I considered going the simple way and created a bootable usbstick with UNetbootin under Windows.
Choose Ubuntu "netinstall" (8.04) and all the required data is downloaded automagically and a proper stick is built.
Make sure that the ethernet cable is plugged in '''before''' booting the stick. There's a bug in the ethernet driver (e1000/e) which prevents the device from settling down.
Check ubuntuwiki for more: [https://help.ubuntu.com/community/Installation/FromUSBStick Install Ubuntu from usbstick]

= What works out-of-the-box =

* Suspend to disk
* Suspend to RAM
* Atheros Wifi (madwifi)
* Most Fn-Keys
* video driver: fancy 3D compositing is enabled
* Bluetooth

= What does not work out-of-the-box =

* Wacom stylus input
* Screen rotation on swivel
* Fingerprint reader

= TODO =
- stylus, screen rotation, handwriting input panel (cellwriter), fingerprint reader, powersaving customizations

[[Category:Ubuntu]]

Talk:Installing Gentoo on a ThinkPad X60 Tablet

2008-03-07T10:03:38Z

Samoht:

Good to see others with Gentoo on the X60T.

Re: Pen not working with particular kernels (known to be affected suspend2-sources-2.6.22-r2, gentoo-sources-2.6.22-r5)

For me I got the error:
Cannot set serial info: Invalid argument
this is a bug with the way the kernel handles serial ports, I believe it may be fixed in later 2.6.22 releases but haven't had the opportunity to test yet.

I also have aiglx working lovely also, worked pretty much out the box with a few tweaks on top of the [http://wiki.gentoo-xeffects.org/ Gentoo xeffects wiki] (which I think is slightly out of date in some places)

Does anybody know of any particular power management tips? I have frequency scaling working, but battery life is much reduced than when running windows (plus my thinkpad gets rather warm on the right palm rest, which it doesn't do in windows)

--[[User:Duwamish|Duwamish]] 11:58, 4 November 2007 (UTC)

----

Hey, I have a weird problem with my stylus:
Your rotate script works fine, and even the cursors directions are rotated with xsetwacom. But it seems that the cursor still uses the old specs of the display, it's not shown on the actual position i move the pen.
So, if i rotate left 90 degrees, the resolution is 768x1024, but the stylus behaves relative to 1024x768. Do you know the problem? I tried different versions of linuxwacom (up to latest development) but can't get it working. :(

Talk:Automatically reduce brightness

2008-02-16T09:54:18Z

Samoht: Removing all content from page

User:Samoht

2008-02-16T09:53:38Z

Samoht: Removing all content from page

Talk:Automatically reduce brightness

2007-08-26T14:35:36Z

Samoht: compile error

Hey,
the new version (0.4_beta1) doesn't compile on Debian Etch.

> make
gcc -g -Wall -lX11 -lXss -o brightd brightd.c
brightd.c:48:25: error: sys/inotify.h: No such file or directory
brightd.c: In function 'main':
brightd.c:530: warning: implicit declaration of function 'inotify_init'
brightd.c:532: warning: implicit declaration of function 'inotify_add_watch'
brightd.c:532: error: 'IN_CREATE' undeclared (first use in this function)
brightd.c:532: error: (Each undeclared identifier is reported only once
brightd.c:532: error: for each function it appears in.)
brightd.c:593: error: invalid application of 'sizeof' to incomplete type 'struct inotify_event'
brightd.c:595: error: dereferencing pointer to incomplete type
brightd.c:715: error: invalid application of 'sizeof' to incomplete type 'struct inotify_event'
brightd.c:716: error: invalid application of 'sizeof' to incomplete type 'struct inotify_event'
brightd.c:718: error: dereferencing pointer to incomplete type
brightd.c:718: error: dereferencing pointer to incomplete type
brightd.c:719: error: dereferencing pointer to incomplete type
make: *** [brightd] Error 1

So I changed the line
#include <sys/inotify.h>
to
#include <linux/inotify.h>
which gives me:

> make
gcc -g -Wall -lX11 -lXss -o brightd brightd.c
brightd.c: In function 'main':
brightd.c:530: warning: implicit declaration of function 'inotify_init'
brightd.c:532: warning: implicit declaration of function 'inotify_add_watch'
/tmp/ccIEzkru.o: In function `main':
/home/thomas/downloads/brightd-0.4_beta4/brightd.c:530: undefined reference to `inotify_init'
/home/thomas/downloads/brightd-0.4_beta4/brightd.c:532: undefined reference to `inotify_add_watch'
/home/thomas/downloads/brightd-0.4_beta4/brightd.c:576: undefined reference to `inotify_init'
/home/thomas/downloads/brightd-0.4_beta4/brightd.c:578: undefined reference to `inotify_add_watch'
collect2: ld returned 1 exit status
make: *** [brightd] Error 1

Do I need a special version of inotify? Sry, I have no real experience in c programming.

> uname -a
Linux phooka 2.6.22 #1 PREEMPT Wed Aug 1 11:47:42 CEST 2007 i686 GNU/Linux

Talk:Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-09T13:06:16Z

Samoht: â†Created page with 'The problem with hdapsd is, that you need a special kernel patch that allows to freeze the head of the harddisk. It's described here: http://www.thinkwiki.org/wiki/How_to_...'

The problem with hdapsd is, that you need a special kernel patch that allows to freeze the head of the harddisk.
It's described here: http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS#Adding_kernel_support

Default meanings of special keys

2007-05-18T12:10:42Z

Samoht: /* Z Series */

{| width="100%" columns="2"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" rowspan="2" | __TOC__
|style="vertical-align:top" |

The following table lists the associated functionalities for special keys on ThinkPads.
|}

{| width="100%" {{prettytable}}
! style="background:#ffdead;"| Models
! style="background:#ffdead;"| {{key|Fn}}{{key|F1}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F2}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F3}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F4}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F5}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F6}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F7}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F8}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F9}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F10}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F11}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F12}}
! style="background:#ffdead;"| {{key|Fn}}{{key|Home}}
! style="background:#ffdead;"| {{key|Fn}}{{key|End}}
! style="background:#ffdead;"| {{key|Fn}}{{key|PageUp}}
! style="background:#ffdead;"| {{key|Fn}}{{key|Space}}
! style="background:#ffdead;"| {{key|Fn}}{{key|left}}
! style="background:#ffdead;"| {{key|Fn}}{{key|right}}
! style="background:#ffdead;"| {{key|Fn}}{{key|up}}
! style="background:#ffdead;"| {{key|Fn}}{{key|down}}
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===Numbered===
|-
| {{240}}, {{240X}}, 240Z
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{365C}}, {{365CD}}, {{365CS}}, {{365CSD}}, {{365E}}, {{365ED}}, {{365X}}, {{365XD}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{380}}, {{380D}}, {{380E}}, {{380ED}}, {{385D}}, {{385ED}}, {{380XD}}, {{385XD}}, {{380Z}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{390}}, {{390E}}, {{390X}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{560}}, {{560E}}, {{560X}}, {{560Z}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{570}}, {{570E}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{600}}, {{600E}}, {{600X}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{750}}, {{750CS}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{755C}}, {{755CS}}, {{755CE}}, {{755CSE}}, {{755CD}}, {{755CX}}, {{755CV}}, {{755CDV}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{760C}}, {{760CD}}, {{760L}}, {{760LD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760XD}}, {{765D}}, {{765L}}, {{760XL}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===i Series===
|-
| {{i1720}}, {{i1721}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===A Series===
|-
| {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22m}}, {{A22p}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{A30}}, {{A30p}}, {{A31}}, {{A31p}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |
===G Series===
|-
| {{G40}}, {{G41}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |
===R Series===
|-
| {{R30}}, {{R31}}, {{R32}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{R40}}, {{R40e}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{R50}}, {{R50e}}, {{R50p}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{R51}}, {{R51e}}, {{R52}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{R60}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===T Series===
|-
| {{T20}}, {{T21}}, {{T22}}, {{T23}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{T30}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
|
|
| blank screen
| suspend to ram
| switch wireless
|
| switch display
| zoom(?)
| (un)dock
|
|
| suspend to disk
| brightness increase
| brightness decrease
| thinklight
| zoom
|
|
|
|
|-
| {{T60}}, {{T60p}}
|
| lock screen
| energy manager/ settings
| suspend to ram
| wireless/bluetooth
|
| switch display
| control ultranav
| eject
|
|
| suspend to disk
| brightness up
| brightness down
| thinklight
| zoom
| last track
| next track
| stop
| play / pause
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===X Series===
|-
| {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X30}}, {{X31}}, {{X32}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X40}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X41}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X41T}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X60}}, {{X60s}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X60t}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===Z Series===
|-
| {{Z60m}}, {{Z60t}}
|
| lock desktop
| show state of battery
| suspend to ram (sleep)
| toggle bluetooth
|
| switch to external vga-output
| switch between trackpoint and touchpad
| eject dock
|
|
| suspend to disk (hibernate)
| brightness increase
| brightness decrease
| thinklight
|
|
|
|
|
|-
| {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}}
|
| ?
| ?
| suspend to ram
| switch wireless
|
| switch display
| switch trackpoint / touchpad
| (un)dock
|
|
| suspend to disk
| brightness increase
| brightness decrease
| thinklight
| zoom
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===Other===
|-
| {{TransNote}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|}

[[Category:Tables]]

Default meanings of special keys

2007-05-18T12:08:33Z

Samoht: /* Z Series */

{| width="100%" columns="2"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" rowspan="2" | __TOC__
|style="vertical-align:top" |

The following table lists the associated functionalities for special keys on ThinkPads.
|}

{| width="100%" {{prettytable}}
! style="background:#ffdead;"| Models
! style="background:#ffdead;"| {{key|Fn}}{{key|F1}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F2}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F3}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F4}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F5}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F6}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F7}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F8}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F9}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F10}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F11}}
! style="background:#ffdead;"| {{key|Fn}}{{key|F12}}
! style="background:#ffdead;"| {{key|Fn}}{{key|Home}}
! style="background:#ffdead;"| {{key|Fn}}{{key|End}}
! style="background:#ffdead;"| {{key|Fn}}{{key|PageUp}}
! style="background:#ffdead;"| {{key|Fn}}{{key|Space}}
! style="background:#ffdead;"| {{key|Fn}}{{key|left}}
! style="background:#ffdead;"| {{key|Fn}}{{key|right}}
! style="background:#ffdead;"| {{key|Fn}}{{key|up}}
! style="background:#ffdead;"| {{key|Fn}}{{key|down}}
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===Numbered===
|-
| {{240}}, {{240X}}, 240Z
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{365C}}, {{365CD}}, {{365CS}}, {{365CSD}}, {{365E}}, {{365ED}}, {{365X}}, {{365XD}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{380}}, {{380D}}, {{380E}}, {{380ED}}, {{385D}}, {{385ED}}, {{380XD}}, {{385XD}}, {{380Z}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{390}}, {{390E}}, {{390X}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{560}}, {{560E}}, {{560X}}, {{560Z}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{570}}, {{570E}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{600}}, {{600E}}, {{600X}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{750}}, {{750CS}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{755C}}, {{755CS}}, {{755CE}}, {{755CSE}}, {{755CD}}, {{755CX}}, {{755CV}}, {{755CDV}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{760C}}, {{760CD}}, {{760L}}, {{760LD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760XD}}, {{765D}}, {{765L}}, {{760XL}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===i Series===
|-
| {{i1720}}, {{i1721}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===A Series===
|-
| {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22m}}, {{A22p}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{A30}}, {{A30p}}, {{A31}}, {{A31p}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |
===G Series===
|-
| {{G40}}, {{G41}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |
===R Series===
|-
| {{R30}}, {{R31}}, {{R32}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{R40}}, {{R40e}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{R50}}, {{R50e}}, {{R50p}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{R51}}, {{R51e}}, {{R52}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{R60}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===T Series===
|-
| {{T20}}, {{T21}}, {{T22}}, {{T23}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{T30}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
|
|
| blank screen
| suspend to ram
| switch wireless
|
| switch display
| zoom(?)
| (un)dock
|
|
| suspend to disk
| brightness increase
| brightness decrease
| thinklight
| zoom
|
|
|
|
|-
| {{T60}}, {{T60p}}
|
| lock screen
| energy manager/ settings
| suspend to ram
| wireless/bluetooth
|
| switch display
| control ultranav
| eject
|
|
| suspend to disk
| brightness up
| brightness down
| thinklight
| zoom
| last track
| next track
| stop
| play / pause
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===X Series===
|-
| {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X30}}, {{X31}}, {{X32}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X40}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X41}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X41T}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X60}}, {{X60s}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| {{X60t}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===Z Series===
|-
| {{Z60m}}, {{Z60t}}
|
| lock desktop
| show state of battery
| suspend to ram (sleep)
| toggle bluetooth
|
| switch to external vga-output
| switch between trackpoint and touchpad
| eject dock
|
|
| suspend to disk (hibernate)
|
|
|
|
|
|
|
|
|-
| {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}}
|
| ?
| ?
| suspend to ram
| switch wireless
|
| switch display
| switch trackpoint / touchpad
| (un)dock
|
|
| suspend to disk
| brightness increase
| brightness decrease
| thinklight
| zoom
|
|
|
|-
! colspan=21 style="text-align:center;background:#efefef;" |

===Other===
|-
| {{TransNote}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|}

[[Category:Tables]]

Installing Debian Etch on a ThinkPad Z60m

2007-04-26T07:10:15Z

Samoht:

== Special Keys ==
For the powermanagement-keys (Fn + F4, ...) install acpi-support:

{{cmdroot|apt-get install acpi-support}}

For Fn - Arrow-keys I have customized my {{path|~/.xmodmap}}:

keycode 164 = XF86AudioStop
keycode 162 = XF86AudioPlay
keycode 153 = XF86AudioNext
keycode 144 = XF86AudioPrev
keycode 234 = F19
keycode 233 = F20

For using the Back/Forward-keys in Firefox go on [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox here].

== Wireless Networking ==

The module for this chip is in kernel mainline (ipw2200). The only showstopper is the missing firmware.

Get it here: [http://ipw2200.sourceforge.net/firmware.php?fid=7 firmware v3.0]

Extract it:

{{cmdroot| tar zxvf ipw2200-fw-3.0.tgz}}

Move the *.fw files to {{path|/lib/firmware/}}

{{cmdroot|mv *.fw /lib/firmware/}}

Reload the module:

{{cmdroot|rmmod ipw2200 && modprobe ipw2200}}

== CPU Throttling ==

Load the kernelmodule:

{{cmdroot|modprobe speedstep_centrino}}

Add line "speedstep_centrino" to {{path|/etc/modules}} to load the module on boot.

Install the throttling-daemon:

{{cmdroot|apt-get install powernowd}}

Done.

== Active Protection System==

=== Preparing the kernel ===

To get the headdisk-parking working you have to build your own kernel with the hdaps_protect-patch applied:

Install the prerequisites that we need to compile the new kernel:

{{cmdroot|apt-get install kernel-package ncurses-dev fakeroot wget bzip2}}

Get the recent debian-etch-kernel (2.6.18):

{{cmdroot|apt-get install linux-tree-2.6.18}}

Go to the sources and unpack them:

{{cmdroot|cd /usr/src}}
{{cmdroot| tar jxvf linux-source-2.6.18.tar.bz2}}

As etchs kernel is 2.6.18-4 its propably a good idea to get the hdaps_protect patch for 2.6.18-3:

{{cmdroot| wget http://www.dresco.co.uk/hdaps/hdaps_protect-2.6.18.3-2.patch}}

Apply the patch:

{{cmdroot|cd linux-source-2.6.18/}}
{{cmdroot|patch -p1 < ../hdaps_protect-2.6.18.3-2.patch}}

Copy the default-config to the sourcetree:

{{cmdroot|cp /boot/config-2.6.18-4-486 ./.config}}

Build the kernel & packages:

{{cmdroot|make-kpkg clean}}
{{cmdroot|make-kpkg fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

Install the new kernel. Grub-menu should be updated automatically.

{{cmdroot| dpkg -i linux-image-2.6.18_thinkpad.1.0_i386.deb }}

Reboot and select the new kernel. Verify with 'uname -a'.
If all things work you can set the new kernel default in {{path|/boot/grub/menu.lst}} with default $entry-number (0..1..2..)

===Preparing userspace===

Installing the daemon:

{{cmdroot|apt-get install hdapsd}}

To set your harddrive, edit {{path|/etc/default/hdapsd}}:

# start hdapsd at boottime?
'''START=yes'''
#
# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
'''DISK=sda'''
#
# other options to pass to hdapsd.
# the -d and -b options are always passed.
OPTIONS=

Restart hdapsd:

{{cmdroot|/etc/init.d/hdapsd restart}}

You should get something like that in {{path| /var/log/syslog}} when throwing your thinkpad off the table: (No, seriously, shaking it carefully should be sufficient :-) )

Mar 20 12:25:37 localhost kernel: ata_scsi_issue_protect_fn(): unload support reported by drive..
Mar 20 12:25:37 localhost kernel: scsi_protect_queue(): head parked..
Mar 20 12:25:38 localhost kernel: scsi_unprotect_queue(): No pending I/O, re-enabling power management..
Mar 20 12:25:38 localhost hdapsd[12522]: Tue Mar 20 12:25:38 2007: un-parking

== Fingerprint-Reader ==

=== Install userspace-tools ===
I got the fingerprint reader working with the new [http://thinkfinger.sourceforge.net/ ThinkFinger-drivers] (opensource). They are working much better than the closed-source UPEK drivers and don't have this ugly QT-dialog.

Get some debian-packages from [http://www.rubixlinux.org/debian/thinkfinger/ here] and install them with:

{{cmdroot| dpkg -i *.deb}}

=== Enroll your fingers ===
Enroll your fingers with:

{{cmdroot|tf-tool --add-user <login>}}

# tf-tool --add-user name
ThinkFinger 0.2.2 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>
Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/etc/pam_thinkfinger/name.bir)... done.

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

Open {{path|/etc/pam.d/common-auth}}:

# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
'''auth sufficient pam_thinkfinger.so'''
auth required pam_unix.so '''try_first_pass'''

Ready! Works flawlessly with gdm for instance!
Enroll user 'root' to use your fingerprint for 'sudo'.

== System Information ==

=== uname -a ===

Linux phooka 2.6.18 #1 PREEMPT Thu Apr 5 13:09:55 CEST 2007 i686 GNU/Linux

=== lspci ===

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
Subsystem: IBM Unknown device [1014:0575]
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA])
Subsystem: IBM Unknown device [1014:058c]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at a0080000 (32-bit, non-prefetchable) [size=512K]
I/O ports at 1800 [size=8]
Memory at c0000000 (32-bit, prefetchable) [size=256M]
Memory at a0040000 (32-bit, non-prefetchable) [size=256K]
Capabilities: [d0] Power Management version 2

00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 03)
Subsystem: IBM Unknown device [1014:058c]
Flags: fast devsel
Memory at 30000000 (32-bit, non-prefetchable) [disabled] [size=512K]
Capabilities: [d0] Power Management version 2

00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 03)
Subsystem: IBM Unknown device [1014:05b7]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at a0000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [70] Express Unknown type IRQ 0
Capabilities: [100] Virtual Channel
Capabilities: [130] Unknown (5)

00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Memory behind bridge: a0100000-a01fffff
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: IBM Unknown device [1014:05b8]
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Unknown (5)

00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 [8086:2662] (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=0a, sec-latency=0
I/O behind bridge: 00002000-00003fff
Memory behind bridge: a2000000-a3ffffff
Prefetchable memory behind bridge: 00000000d0000000-00000000d00fffff
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: IBM Unknown device [1014:05b8]
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Unknown (5)

00:1c.2 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 [8086:2664] (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=0b, subordinate=12, sec-latency=0
I/O behind bridge: 00004000-00005fff
Memory behind bridge: a4000000-a5ffffff
Prefetchable memory behind bridge: 00000000b0100000-00000000b01fffff
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: IBM Unknown device [1014:05b8]
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Unknown (5)

00:1c.3 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 4 [8086:2666] (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=13, subordinate=13, sec-latency=0
I/O behind bridge: 00006000-00007fff
Memory behind bridge: a6000000-a7ffffff
Prefetchable memory behind bridge: 00000000d0100000-00000000d01fffff
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: IBM Unknown device [1014:05b8]
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Unknown (5)

00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03) (prog-if 00 [UHCI])
Subsystem: IBM Unknown device [1014:0565]
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1820 [size=32]

00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 03) (prog-if 00 [UHCI])
Subsystem: IBM Unknown device [1014:0565]
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1840 [size=32]

00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 03) (prog-if 00 [UHCI])
Subsystem: IBM Unknown device [1014:0565]
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1860 [size=32]

00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 03) (prog-if 00 [UHCI])
Subsystem: IBM Unknown device [1014:0565]
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1880 [size=32]

00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 03) (prog-if 20 [EHCI])
Subsystem: IBM Unknown device [1014:0566]
Flags: bus master, medium devsel, latency 0, IRQ 11
Memory at a0004000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d3) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=14, subordinate=17, sec-latency=64
I/O behind bridge: 00008000-0000bfff
Memory behind bridge: a8000000-b00fffff
Prefetchable memory behind bridge: 00000000d8000000-00000000dfffffff
Capabilities: [50] Subsystem: Gammagraphx, Inc. Unknown device [0000:0000]

00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 03)
Subsystem: IBM Unknown device [1014:0568]
Flags: bus master, medium devsel, latency 0

00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 03) (prog-if 80 [Master])
Subsystem: IBM Unknown device [1014:056a]
Flags: bus master, 66MHz, medium devsel, latency 0
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at 1810 [size=16]
Capabilities: [70] Power Management version 2

00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 03)
Subsystem: IBM Unknown device [1014:056b]
Flags: medium devsel, IRQ 11
I/O ports at 18a0 [size=32]

02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express [14e4:167d] (rev 11)
Subsystem: IBM Unknown device [1014:0577]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at a0100000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable-
Capabilities: [d0] Express Endpoint IRQ 0
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel

14:00.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b3)
Subsystem: IBM Unknown device [1014:056c]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at b0000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=14, secondary=15, subordinate=16, sec-latency=176
Memory window 0: d8000000-d9fff000 (prefetchable)
Memory window 1: a8000000-a9fff000 (prefetchable)
I/O window 0: 00008000-000080ff
I/O window 1: 00008400-000084ff
16-bit legacy interface ports at 0001

14:00.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 08) (prog-if 10 [OHCI])
Subsystem: IBM ThinkPad A/T/X Series [1014:0511]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at b0001000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [dc] Power Management version 2

14:00.2 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 17)
Subsystem: IBM Thinkpad Z60m [1014:0598]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at b0001800 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

14:00.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 08)
Subsystem: IBM Unknown device [1014:0596]
Flags: medium devsel, IRQ 11
Memory at b0001c00 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

14:02.0 Network controller [0280]: Intel Corporation PRO/Wireless 2915ABG Network Connection [8086:4224] (rev 05)
Subsystem: Intel Corporation Unknown device [8086:1011]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at b0002000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2

=== lsmod ===

Module Size Used by
wacom 15168 0
i915 17344 2
drm 61140 3 i915
binfmt_misc 10568 1
ipv6 221472 10
ieee80211_crypt_ccmp 6784 3
cpufreq_ondemand 5744 0
speedstep_centrino 7120 1
cpufreq_userspace 3860 1
freq_table 4292 1 speedstep_centrino
ac 5060 0
battery 9476 0
ibm_acpi 24320 0
hdaps 8816 0
sbp2 20744 0
ieee1394 86008 1 sbp2
loop 14536 0
tsdev 7360 0
joydev 8960 0
snd_hda_intel 16916 0
snd_hda_codec 137728 1 snd_hda_intel
ipw2200 93568 0
snd_pcm_oss 38112 0
ieee80211 29064 1 ipw2200
ieee80211_crypt 5824 2 ieee80211_crypt_ccmp,ieee80211
snd_mixer_oss 15168 1 snd_pcm_oss
firmware_class 9536 1 ipw2200
snd_pcm 68616 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 20868 1 snd_pcm
sdhci 16140 0
mmc_core 22608 1 sdhci
i2c_i801 7308 0
snd 46564 6 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9248 1 snd
i2c_core 19792 1 i2c_i801
psmouse 34568 0
snd_page_alloc 9480 2 snd_hda_intel,snd_pcm
intel_agp 20892 1
rtc 12276 0
evdev 8896 1
agpgart 29360 3 drm,intel_agp
sg 31068 0
sr_mod 15716 0
cdrom 32416 1 sr_mod
ext3 117640 3
jbd 51816 1 ext3
mbcache 8260 1 ext3
sha256 10944 0
aes 28032 5
dm_crypt 10696 1
dm_mirror 18704 0
dm_snapshot 15324 0
dm_mod 49848 12 dm_crypt,dm_mirror,dm_snapshot
ide_generic 1280 0 [permanent]
sd_mod 18896 3
generic 5316 0 [permanent]
ide_core 109040 2 ide_generic,generic
ata_piix 13384 2
ahci 17220 0
libata 90200 2 ata_piix,ahci
scsi_mod 125256 6 sbp2,sg,sr_mod,sd_mod,ahci,libata
tg3 94020 0
ehci_hcd 27848 0
uhci_hcd 20876 0
usbcore 111940 4 wacom,ehci_hcd,uhci_hcd
thermal 13384 0
processor 23724 2 speedstep_centrino,thermal
fan 4676 0

=== /proc/cpuinfo ===

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.86GHz
stepping : 8
cpu MHz : 800.000
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx est tm2
bogomips : 1597.51

=== hdparm -I -tT /dev/sda ===

/dev/sda:

ATA device, with non-removable media
Model Number: HTS541080G9SA00
Serial Number: MPBDL0X6H9KRTM
Firmware Revision: MB4IC60H
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 1
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156301488
LBA48 user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Vendor, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 128 (0x80)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
Automatic Acoustic Management feature set
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* IDLE_IMMEDIATE with UNLOAD
* SATA-I signaling speed (1.5Gb/s)
* Host-initiated interface power management
* Device-initiated interface power management
* Software settings preservation
Security:
Master password revision code =
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
52min for SECURITY ERASE UNIT.
Checksum: correct
Timing cached reads: 1140 MB in 2.00 seconds = 569.77 MB/sec
Timing buffered disk reads: 74 MB in 3.07 seconds = 24.13 MB/sec

[[Category:Z60m]][[Category:Debian]]

Installing Debian Etch on a ThinkPad Z60m

2007-04-12T09:54:27Z

Samoht: added hardware & system information

{{NOTE|This article is not finished yet!}}

== Special Keys ==
For the powermanagement-keys (Fn + F4, ...) install acpi-support:

{{cmdroot|apt-get install acpi-support}}

For Fn - Arrow-keys I have customized my {{path|~/.xmodmap}}:

keycode 164 = XF86AudioStop
keycode 162 = XF86AudioPlay
keycode 153 = XF86AudioNext
keycode 144 = XF86AudioPrev
keycode 234 = F19
keycode 233 = F20

For using the Back/Forward-keys in Firefox go on [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox here].

== Wireless Networking ==

The module for this chip is in kernel mainline (ipw2200). The only showstopper is the missing firmware.

Get it here: [http://ipw2200.sourceforge.net/firmware.php?fid=7 firmware v3.0]

Extract it:

{{cmdroot| tar zxvf ipw2200-fw-3.0.tgz}}

Move the *.fw files to {{path|/lib/firmware/}}

{{cmdroot|mv *.fw /lib/firmware/}}

Reload the module:

{{cmdroot|rmmod ipw2200 && modprobe ipw2200}}

== CPU Throttling ==

Load the kernelmodule:

{{cmdroot|modprobe speedstep_centrino}}

Add line "speedstep_centrino" to {{path|/etc/modules}} to load the module on boot.

Install the throttling-daemon:

{{cmdroot|apt-get install powernowd}}

Done.

== Active Protection System==

=== Preparing the kernel ===

To get the headdisk-parking working you have to build your own kernel with the hdaps_protect-patch applied:

Install the prerequisites that we need to compile the new kernel:

{{cmdroot|apt-get install kernel-package ncurses-dev fakeroot wget bzip2}}

Get the recent debian-etch-kernel (2.6.18):

{{cmdroot|apt-get install linux-tree-2.6.18}}

Go to the sources and unpack them:

{{cmdroot|cd /usr/src}}
{{cmdroot| tar jxvf linux-source-2.6.18.tar.bz2}}

As etchs kernel is 2.6.18-4 its propably a good idea to get the hdaps_protect patch for 2.6.18-3:

{{cmdroot| wget http://www.dresco.co.uk/hdaps/hdaps_protect-2.6.18.3-2.patch}}

Apply the patch:

{{cmdroot|cd linux-source-2.6.18/}}
{{cmdroot|patch -p1 < ../hdaps_protect-2.6.18.3-2.patch}}

Copy the default-config to the sourcetree:

{{cmdroot|cp /boot/config-2.6.18-4-486 ./.config}}

Build the kernel & packages:

{{cmdroot|make-kpkg clean}}
{{cmdroot|make-kpkg fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

Install the new kernel. Grub-menu should be updated automatically.

{{cmdroot| dpkg -i linux-image-2.6.18_thinkpad.1.0_i386.deb }}

Reboot and select the new kernel. Verify with 'uname -a'.
If all things work you can set the new kernel default in {{path|/boot/grub/menu.lst}} with default $entry-number (0..1..2..)

===Preparing userspace===

Installing the daemon:

{{cmdroot|apt-get install hdapsd}}

To set your harddrive, edit {{path|/etc/default/hdapsd}}:

# start hdapsd at boottime?
'''START=yes'''
#
# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
'''DISK=sda'''
#
# other options to pass to hdapsd.
# the -d and -b options are always passed.
OPTIONS=

Restart hdapsd:

{{cmdroot|/etc/init.d/hdapsd restart}}

You should get something like that in {{path| /var/log/syslog}} when throwing your thinkpad off the table: (No, seriously, shaking it carefully should be sufficient :-) )

Mar 20 12:25:37 localhost kernel: ata_scsi_issue_protect_fn(): unload support reported by drive..
Mar 20 12:25:37 localhost kernel: scsi_protect_queue(): head parked..
Mar 20 12:25:38 localhost kernel: scsi_unprotect_queue(): No pending I/O, re-enabling power management..
Mar 20 12:25:38 localhost hdapsd[12522]: Tue Mar 20 12:25:38 2007: un-parking

== Fingerprint-Reader ==

=== Install userspace-tools ===
I got the fingerprint reader working with the new [http://thinkfinger.sourceforge.net/ ThinkFinger-drivers] (opensource). They are working much better than the closed-source UPEK drivers and don't have this ugly QT-dialog.

Get some debian-packages from [http://www.rubixlinux.org/debian/thinkfinger/ here] and install them with:

{{cmdroot| dpkg -i *.deb}}

=== Enroll your fingers ===
Enroll your fingers with:

{{cmdroot|tf-tool --add-user <login>}}

# tf-tool --add-user name
ThinkFinger 0.2.2 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>
Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/etc/pam_thinkfinger/name.bir)... done.

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

Open {{path|/etc/pam.d/common-auth}}:

# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
'''auth sufficient pam_thinkfinger.so'''
auth required pam_unix.so '''try_first_pass'''

Ready! Works flawlessly with gdm for instance!
Enroll user 'root' to use your fingerprint for 'sudo'.

== System Information ==

=== uname -a ===

Linux phooka 2.6.18 #1 PREEMPT Thu Apr 5 13:09:55 CEST 2007 i686 GNU/Linux

=== lspci ===

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
Subsystem: IBM Unknown device [1014:0575]
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA])
Subsystem: IBM Unknown device [1014:058c]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at a0080000 (32-bit, non-prefetchable) [size=512K]
I/O ports at 1800 [size=8]
Memory at c0000000 (32-bit, prefetchable) [size=256M]
Memory at a0040000 (32-bit, non-prefetchable) [size=256K]
Capabilities: [d0] Power Management version 2

00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 03)
Subsystem: IBM Unknown device [1014:058c]
Flags: fast devsel
Memory at 30000000 (32-bit, non-prefetchable) [disabled] [size=512K]
Capabilities: [d0] Power Management version 2

00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 03)
Subsystem: IBM Unknown device [1014:05b7]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at a0000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [70] Express Unknown type IRQ 0
Capabilities: [100] Virtual Channel
Capabilities: [130] Unknown (5)

00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Memory behind bridge: a0100000-a01fffff
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: IBM Unknown device [1014:05b8]
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Unknown (5)

00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 [8086:2662] (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=0a, sec-latency=0
I/O behind bridge: 00002000-00003fff
Memory behind bridge: a2000000-a3ffffff
Prefetchable memory behind bridge: 00000000d0000000-00000000d00fffff
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: IBM Unknown device [1014:05b8]
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Unknown (5)

00:1c.2 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 [8086:2664] (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=0b, subordinate=12, sec-latency=0
I/O behind bridge: 00004000-00005fff
Memory behind bridge: a4000000-a5ffffff
Prefetchable memory behind bridge: 00000000b0100000-00000000b01fffff
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: IBM Unknown device [1014:05b8]
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Unknown (5)

00:1c.3 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 4 [8086:2666] (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=13, subordinate=13, sec-latency=0
I/O behind bridge: 00006000-00007fff
Memory behind bridge: a6000000-a7ffffff
Prefetchable memory behind bridge: 00000000d0100000-00000000d01fffff
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: IBM Unknown device [1014:05b8]
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Unknown (5)

00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03) (prog-if 00 [UHCI])
Subsystem: IBM Unknown device [1014:0565]
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1820 [size=32]

00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 03) (prog-if 00 [UHCI])
Subsystem: IBM Unknown device [1014:0565]
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1840 [size=32]

00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 03) (prog-if 00 [UHCI])
Subsystem: IBM Unknown device [1014:0565]
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1860 [size=32]

00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 03) (prog-if 00 [UHCI])
Subsystem: IBM Unknown device [1014:0565]
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1880 [size=32]

00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 03) (prog-if 20 [EHCI])
Subsystem: IBM Unknown device [1014:0566]
Flags: bus master, medium devsel, latency 0, IRQ 11
Memory at a0004000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d3) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=14, subordinate=17, sec-latency=64
I/O behind bridge: 00008000-0000bfff
Memory behind bridge: a8000000-b00fffff
Prefetchable memory behind bridge: 00000000d8000000-00000000dfffffff
Capabilities: [50] Subsystem: Gammagraphx, Inc. Unknown device [0000:0000]

00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 03)
Subsystem: IBM Unknown device [1014:0568]
Flags: bus master, medium devsel, latency 0

00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 03) (prog-if 80 [Master])
Subsystem: IBM Unknown device [1014:056a]
Flags: bus master, 66MHz, medium devsel, latency 0
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at 1810 [size=16]
Capabilities: [70] Power Management version 2

00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 03)
Subsystem: IBM Unknown device [1014:056b]
Flags: medium devsel, IRQ 11
I/O ports at 18a0 [size=32]

02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express [14e4:167d] (rev 11)
Subsystem: IBM Unknown device [1014:0577]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at a0100000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable-
Capabilities: [d0] Express Endpoint IRQ 0
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel

14:00.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b3)
Subsystem: IBM Unknown device [1014:056c]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at b0000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=14, secondary=15, subordinate=16, sec-latency=176
Memory window 0: d8000000-d9fff000 (prefetchable)
Memory window 1: a8000000-a9fff000 (prefetchable)
I/O window 0: 00008000-000080ff
I/O window 1: 00008400-000084ff
16-bit legacy interface ports at 0001

14:00.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 08) (prog-if 10 [OHCI])
Subsystem: IBM ThinkPad A/T/X Series [1014:0511]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at b0001000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [dc] Power Management version 2

14:00.2 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 17)
Subsystem: IBM Thinkpad Z60m [1014:0598]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at b0001800 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

14:00.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 08)
Subsystem: IBM Unknown device [1014:0596]
Flags: medium devsel, IRQ 11
Memory at b0001c00 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

14:02.0 Network controller [0280]: Intel Corporation PRO/Wireless 2915ABG Network Connection [8086:4224] (rev 05)
Subsystem: Intel Corporation Unknown device [8086:1011]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at b0002000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2

=== lsmod ===

Module Size Used by
wacom 15168 0
i915 17344 2
drm 61140 3 i915
binfmt_misc 10568 1
ipv6 221472 10
ieee80211_crypt_ccmp 6784 3
cpufreq_ondemand 5744 0
speedstep_centrino 7120 1
cpufreq_userspace 3860 1
freq_table 4292 1 speedstep_centrino
ac 5060 0
battery 9476 0
ibm_acpi 24320 0
hdaps 8816 0
sbp2 20744 0
ieee1394 86008 1 sbp2
loop 14536 0
tsdev 7360 0
joydev 8960 0
snd_hda_intel 16916 0
snd_hda_codec 137728 1 snd_hda_intel
ipw2200 93568 0
snd_pcm_oss 38112 0
ieee80211 29064 1 ipw2200
ieee80211_crypt 5824 2 ieee80211_crypt_ccmp,ieee80211
snd_mixer_oss 15168 1 snd_pcm_oss
firmware_class 9536 1 ipw2200
snd_pcm 68616 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 20868 1 snd_pcm
sdhci 16140 0
mmc_core 22608 1 sdhci
i2c_i801 7308 0
snd 46564 6 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9248 1 snd
i2c_core 19792 1 i2c_i801
psmouse 34568 0
snd_page_alloc 9480 2 snd_hda_intel,snd_pcm
intel_agp 20892 1
rtc 12276 0
evdev 8896 1
agpgart 29360 3 drm,intel_agp
sg 31068 0
sr_mod 15716 0
cdrom 32416 1 sr_mod
ext3 117640 3
jbd 51816 1 ext3
mbcache 8260 1 ext3
sha256 10944 0
aes 28032 5
dm_crypt 10696 1
dm_mirror 18704 0
dm_snapshot 15324 0
dm_mod 49848 12 dm_crypt,dm_mirror,dm_snapshot
ide_generic 1280 0 [permanent]
sd_mod 18896 3
generic 5316 0 [permanent]
ide_core 109040 2 ide_generic,generic
ata_piix 13384 2
ahci 17220 0
libata 90200 2 ata_piix,ahci
scsi_mod 125256 6 sbp2,sg,sr_mod,sd_mod,ahci,libata
tg3 94020 0
ehci_hcd 27848 0
uhci_hcd 20876 0
usbcore 111940 4 wacom,ehci_hcd,uhci_hcd
thermal 13384 0
processor 23724 2 speedstep_centrino,thermal
fan 4676 0

=== /proc/cpuinfo ===

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.86GHz
stepping : 8
cpu MHz : 800.000
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx est tm2
bogomips : 1597.51

=== hdparm -I -tT /dev/sda ===

/dev/sda:

ATA device, with non-removable media
Model Number: HTS541080G9SA00
Serial Number: MPBDL0X6H9KRTM
Firmware Revision: MB4IC60H
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 1
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156301488
LBA48 user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Vendor, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 128 (0x80)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
Automatic Acoustic Management feature set
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* IDLE_IMMEDIATE with UNLOAD
* SATA-I signaling speed (1.5Gb/s)
* Host-initiated interface power management
* Device-initiated interface power management
* Software settings preservation
Security:
Master password revision code =
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
52min for SECURITY ERASE UNIT.
Checksum: correct
Timing cached reads: 1140 MB in 2.00 seconds = 569.77 MB/sec
Timing buffered disk reads: 74 MB in 3.07 seconds = 24.13 MB/sec

[[Category:Z60m]][[Category:Debian]]

Issues with the Wiki

2007-03-21T09:32:19Z

Samoht: Problem with template cmdroot

This page is a provisorium. It's a list of things that are going wrong after the update to help [[User:akw|Akw]] track and fix them.

== Troubles encountered ==

'''Problem with cmdroot'''

Following String is not handled correct by template cmdroot:
"fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image"

see here:
{{cmdroot|fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

----

'''Can not open page to edit without introducing modifications'''

If I open the [[X31]] model page and without touching anything I hit preview, the div token is decomposed and appears in the preview page, and of course, the photo is not in the right place.

:[[User:Ungoliant|Ungoliant]] 19:24, 20 February 2007 (CET)

----

'''Can not upload SVG'''
I get the upload warning:
".svg" is not a recommended image file format.
:[[User:Matt|Matt]] 14:02, 3 December 2006 (CET)

----

Is there a way to contact a registered user, for example to confirm information. I have found that AdamZ claims that the X20 is bootable via USB. My information indicates the contrary. Isn't there a way to contact a registered user through MediaWiki? --[[User:Rolf|Rolf]] 00:30, 9 September 2006 (CEST)

php error encountered when attempting to update Bios Upgrade page:
<blockquote>
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 133781 bytes) in /home/akw/htdocs/thinkwiki.org/mediawiki-1.5.6/includes/MagicWord.php on line 250
</blockquote>
--[[User:roadends|roadends]] 02:30, 20 March 2006 (EDT)
----

* [[ThinkWiki:SpamBlackList]] does not appear to work anymore
--[[User:Tonko|Tonko]] 03:40, 11 March 2006 (CET)
----
You can't (easliy do a multiline {{cmdresult|cmdresult}}, can you? See:

{{cmdresult|foo
bar
baz}}

or

{{cmdresult|foo
bar (after whitespace)
baz (after whitespace)}}

This works (but is not so nice)

{{cmdresult|foo

bar (after empty line)

baz (after empty line)}}

Any suggestions?

[[User:Pebolle|Paul Bolle]] 10:27, 24 January 2006 (CET)
----
I think the best way is to use single cmdresult calls for each line and prefix them with a colon. Like so:
<pre><nowiki>
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}
</nowiki></pre>, which results in
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}

Alternatively, you can use at the ende of each line within one call, like this:
<tt><nowiki>{{cmdresult|foo 
bar 
baz}}</nowiki></tt>
, which will result in

{{cmdresult|foo 
bar 
baz}}

[[User:Wyrfel|Wyrfel]] 12:13, 24 January 2006 (CET)
----
I have just got a MySQL problem when I edited a page, a query was not to its liking. It is quite easy to reproduce, just edit any page ;-)

History did get updated, and the page was also updated, so I have no idea what broke when that query failed.

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "SearchMySQL4::update". MySQL returned error "1062: Duplicate entry ' ' for key 3 (localhost)".

[[User:Hmh|hmh]] 2006-02-17, 20:12 UTC
----
More database problems, this time the search function:

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "". MySQL returned error "145: Table './thinkwiki/searchindex' is marked as crashed and should be repaired (localhost)".

[[User:Hmh|hmh]] 2006-02-21, 15:07 UTC
----
The server time would appear to be off a lot, is it possible to setup ntpd, or to run ntpdate every hour or so using cron?
--[[User:Tonko|Tonko]] 05:11, 22 February 2006 (CET)
----
Search still seems broken, searching for DVI brings up nothing.
--[[User:Jumpfroggy|Jumpfroggy]] 00:03, 17 March 2006 (CET)

== Troubles confirmed ==
* [[Special:Benchmarks]] doesn't find it's data

== Fixed problems ==
* http://thinkwiki.org/ reverted again to the default MediaWiki theme. '''Cannot reproduce this one (15.01.06, akw)'''
* File upload is disabled - '''Argh. Fixed (15.01.06, akw)'''
* URL contains index.php(/) before the actual page name - '''This has been fixed (28.05.05, akw)'''
* The categories page doesn't link to [[:Category:ThinkWiki]] - '''Fixed (29.05.05, akw)'''
* http://thinkwiki.org/ is broken (no www prefix), this was working before - '''Fixed (29.05.05, akw)'''
* On logging in a requester pops up asking to confirm a password change - '''seems like it's implicitly been fixed (29.05.2005, wyrfel)'''
* In Navigation bar, "&lt;download&gt;" leads to [http://www.thinkwiki.org/wiki/--error:_link_target_missing--] - '''fixed (30.06.2005)'''
* direct link to [[:Category:Models]] missing in Navigation '''Fixed (10.07.05, akw)'''
* It seems the Wiki has trouble updating the edit history, i'm getting mysql query errors on saving pages. The pages get saved, however. '''Fixed (12.05.2005)'''

How to protect the harddisk through APS

2007-03-21T09:20:28Z

Samoht: Added link to my debian instructions

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page tells you how to make the [[Active Protection System]] work under Linux to protect your harddrive from damage in case of a notebook drop or other kind of impact while it is running.

Specific instructions for {{Fedora}} can be found [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]].

For {{Debian}} (Etch) have a look at [[Installing_Debian_Etch_on_a_ThinkPad_Z60m#Active_Protection_System|this]].

== How APS works in Linux ==
APS in Linux consists of four components on the software side:
* The [[HDAPS]] driver (included in recent kernels). It exports a sysfs interface providing the acceleration values.
* The [http://www.dresco.co.uk/hdaps/ <tt>hdaps_protect</tt>] disk protection kernel patch, which exports a sysfs interface that enables an ide or sata disk to be protected by a userspace process.
* The [http://www.dresco.co.uk/hdaps/ <tt>hdapsd</tt>] disk protection userspace daemon. It monitors the acceleration values through the HDAPS interface and automatically initiates disk protection through the hdaps_protect interface - given that the movement exceeds a user specified threshold.
* Optional: the [http://roy.marples.name/node/269 <tt>khdapsmonitor KDE System Tray applet</tt>] or the [http://www.dresco.co.uk/hdaps/ <tt>gnome-hdaps-applet</tt>]. These applets provide a visual indication of the disk protection status and also a graphical interface for adjusting configuration options for <tt>hdapsd</tt>.
|}

==Installation==
As mentioned above, the hdaps kernel driver found in recent kernels is only responsible for reading the accelerometer data and exporting it through the sysfs interface.

In order to use this information to protect the disk, some additional steps are required.

* Download and build the latest hdaps_protect disk protection kernel patches.
* Enable the drivers in the kernel (requires kernel rebuild).
* Download, build and configure the hdapsd userspace daemon.
* Download and build one of the applets to get a real-time representation of the disk protection status.

===Getting the files===
{| border="1" cellspacing="0" cellpadding="2"
! Latest Sources
|
See [[HDAPS#Disk_head_parking|HDAPS - Disk head parking]]
|-
! {{Debian}}
|
*<tt>hdapsd</tt> package: http://packages.debian.org/unstable/misc/hdapsd
|-
! {{Fedora}}
| see instructions [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]]
*kernel RPM packages including <tt>hdaps_protect</tt>: http://www.dresco.co.uk/hdaps/
*kernel RPM packages including <tt>hdaps_protect</tt> and [[Software Suspend 2]]: http://mhensler.de/swsusp/download/yum/development/fc5/ (build 2084_2 and up)
|-
! {{Gentoo}}
|
*<tt>hdapsd</tt>: [http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-laptop/hdapsd available]
*<tt>khdapsmonitor</tt>: [http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-laptop/khdapsmonitor available]
|}

=== Adding kernel support ===
A kernel patch is required for disk head parking and queue freezing.

==== Manually patching and compiling a kernel ====
As root, do:
:{{cmdroot|cd /usr/src/linux}}
:{{cmdroot|patch -p1 < ~/hdaps_protect.20060409.patch}}
:{{cmdroot|make clean}}
:{{cmdroot|make}}
:{{cmdroot|make modules_install}}

=== Installing hdapsd ===
==== Manual compilation from source ====
* Download the <tt>hdapsd</tt> sources (see above)
* Compile using {{cmdroot|gcc -o hdapsd hdapsd-*.c}}
* Run {{cmdroot|./hdapsd -d sda -s 12 -a}} (replace <tt>sda</tt> with your hard disk device; run {{cmdroot|./hdapsd}} without arguments for help)

==== Gentoo ====
{{NOTE|1=hdapsd was added to the official portage tree on the 26th June 2006.}}
{{Gentoo}} users can try the ebuild attached to [http://bugs.gentoo.org/show_bug.cgi?id=119845 gentoo bug 119845].
*Add hdapsd support in your kernel: device drivers -> hardware monitoring -> ... (you need it as a module if you want to use tp_smapi and hdaps, see [[Tp_smapi]])
*Download the ebuild, use same ebuild date as the kernel-patch.
*Make known the portage an extern ebuild path and add the following line to {{path|/etc/make.conf}}:
PORTDIR_OVERLAY="/usr/local/portage/" (or any other location)
*Create directory {{path|/usr/local/portage}} and {{path|/usr/local/portage/app-laptop/}}
*Copy the downloaded ebuild to {{path|/usr/local/portage/app-laptop}} ({{path|/usr/local/portage/app-laptop/hdapsd}} should now exists)
*Make portage known the new ebuild and creat digist with:
:{{cmdroot|ebuild /usr/local/portage/app-laptop/hdapsd/hdapsd-20060326.ebuild digest}}
*Optional: Copy source file to portage distfiles (if no internet connection is available):
:{{cmdroot|cp hdapsd-20060326.c /usr/portage/distfiles}}
*Accept the x86 keyword for this package: {{cmdroot|echo "app-laptop/hdapsd ~x86" >> /etc/portage/package.keywords}}
*Install hdapsd with: {{cmdroot|emerge hdapsd}}.
*Edit {{path|/etc/conf.d/hdapsd}} (change your harddrive if neccessary: mine is sda, and change the value from 5, 5 is to sensitive, 12 is a good value in my opinion).
*start deamon with: {{cmdroot|/etc/init.d/hdapsd start}}
*Optional: add to default runlevel: {{cmdroot|rc-update add hdapsd default, rc-update add hdapsd battery}}
Write an eMail to abartel[Ã¤d]htwm.de, if you want to get my hdapsd-20060326.ebuild and please upload it.

=== Building an applet ===
====hdaps-gl====
*Make sure you have installed hdaps [and loaded] and ?opengl?
*Download <tt>hdaps-gl-0.0.5</tt> from the web.
*Extract files to {{path|/opt/hdaps-gl}}.
*{{cmdroot|make}}
*Start the applet: {{cmdroot|./hdaps-gl}}

==Troubleshooting==
See the [[Problem with APS harddisk parking]] page for troubleshooting APS issues.
{{NOTE|1=If you use [[tp_smapi]], remember to include the option <tt>HDAPS=1</tt> when [[Tp_smapi#Installation|installing tp_smapi]]. Also, you might need to build the hdaps driver as module.}}

==Further Information==
*Additonal information and support is available through the [[Mailinglists#HDAPS Developers Mailinglist|hdaps-devel]] mailinglist and its archive.

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61m]]

Installing Debian Etch on a ThinkPad Z60m

2007-03-21T09:15:25Z

Samoht: added special keys

How to save memory

2007-03-21T08:38:56Z

Samoht: added window manager improved 2 :)

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |This page is meant as a collection of information on how to save memory to make Linux work reasonable on older system with limited amount of RAM.

Most distributions nowadays don't take much care about it anymore, so there are a lot of things you can do to save memory. To get a smoothly working linux environment on a low memory machine you will need to conciously choose a lot of aspects of your system, most importantly the graphical environment, desktop environment and applications. This page provides detailed information about these various optimization possibilities.
|}

==Alternative graphical environments==
{{Todo|...}}

==Streamlining the desktop environment==
The common Desktop environments GNOME and KDE are, in their modern state, focused more on features, integration, and beauty rather than on resource saving. Understandable, but running Linux on an older ThinkPad with limited RAM requires conscious and sensitive resource usage more than anything else. The good thing about Linux is that a lot of things stay adjustable and customizable. So lets see what we can do about desktops.

One of the most important things is to decide for one graphical widget library and stick with that when you are choosing your desktop environment and applications. Having several toolkits in use means more libraries being loaded and hence more memory being used by those. Possibilities are:
* [http://www.fltk.org/ FLTK]
* [http://www.fox-toolkit.org/ FOX toolkit]
* [http://www.gnustep.org GNUstep toolkit]
* [http://www.gtk.org/ GTK] <tt>(not recommended, use GTK 2 if possible)</tt>
* [http://www.gtk.org/ GTK 2]
* [http://www.lesstif.org/ Lesstif] / [http://www.openmotif.org/ OpenMotif]
* [http://www.trolltech.com/products/qt/index.html QT]
* [http://www.windowmaker.org/development-wings.html WINGs] <tt>(kind of a lightweight GNUstep toolkit, provided by the WindowMaker developers)</tt>
* [http://www.x.org/ X Toolkit]

Of those, at current state, there are enough applications for the X Toolkit, GTK, GTK 2 and QT to provide you with a solution for every task you should want.

===GNOME===
It's like with humans, the worst feature is in most cases also the best one. For GNOME it is probably the many little parts it consists of. Makes it hard to install, but enables one to customize the installation. So, the first thing you should do to streamline GNOME is not to launch it. Sound stupid? Well, lets have a look.

GNOME is basically a set of libraries built around the GTK+ libs and extending its functionality. Add some nice little applications, a session manager, a panel, beautiful icons, and some other stuff and you have GNOME as you know it. Reversing those additions is what you can do to use GNOME applications on a machine that this desktop environment would normally take your nerves on.

The GNOME panel, the session manager, the desktop manager and the window manager are all parts of GNOME that eat a lot of memory for something that others can do in a maybe little less beautiful but much more resource saving way.
So first off configure your login manager not to launch gnome-session at login. If you are using GDM this is quite straight forward, you just need to add a different session script, launching your favorite window manager. See the list below and pick one, lets say i.e. WindowMaker. WindowMaker uses a desktop menu, a dock and a notification area to provide you with an organized way of launching applications and iconfying running ones. So we don't need a panel anymore. Also, think if you really need icons on your desktop. If you do, think about using something like ROX filer instead of nautilus for that. In any case, tell nautilus not to manage the desktop by default by unchecking the according setting within gconf-editor. To keep GNOME applications happy we would need to have gconf and gnome-settings-manager running at every session start. One way to do this is to either include them in your new session script. They both need to be running to make GNOME applications realize their settings properly.

===KDE===
{{Todo|...}}

===Alternative Desktop Environments===
First of all, it is important to notice that GNOME and KDE are not the only Desktop Environments around.
Other complete (featuring most of: window management, session management, desktop management, file management and panel) desktop environments are:
* [http://xfce.org/ XFCE] <tt>uses GTK 2</tt>
* [http://rox.sourceforge.net ROX Desktop]
* [http://ede.sourceforge.net Equinox Desktop Environment] <tt>uses eFLTK, a modified version of FLTK</tt>
* [http://www.nongnu.org/antiright/ AntiRight Desktop Environment] <tt>uses LessTif / OpenMotif</tt>
* [http://foxdesktop.sourceforge.net/ FOX Desktop Environment] <tt>uses FOX Toolkit</tt>
* [http://www.gnustep.org/ GNUstep] <tt>provides it's own toolkit</tt>

But also, some Window Managers exceed the task of managing windows towards providing a functional workbench. See below for a list.

===Building your own Desktop===

====Window Manager====
If you want to build your own customized desktop, a good start is choosing the window manager of your liking. A list of window managers is at [http://xwinman.org].

Here's a list of some of them:
*including basic Desktop Environment functionality
**the [[Wikipedia:NextStep|NextStep]] alike ones
***[http://www.windowmaker.org/ WindowMaker] <tt>(probably the most widespread NextStep like WM)</tt>
***[http://www.afterstep.org/ AfterStep] <tt>(another one of those)</tt>
**the Blackbox-like ones
***[http://blackboxwm.sourceforge.net/ BlackBox]
***[http://fluxbox.sourceforge.net/ FluxBox] <tt>(tabbed windows, lighweight)</tt>
**others
***[http://www.icewm.org/ IceWM] <tt>(lightweight, widespread)</tt>
***[http://enlightenment.sourceforge.net/ Enlightenment] <tt>(lots of features and eye candy)</tt>
***[http://www.pekwm.org PekWM] <tt>(kind of a one man show, but feature rich and extremely customizable)</tt>
*pure WindowManagers
**[http://golem.sourceforge.net/ Golem]
**[http://home.earthlink.net/~lab1701/larswm/ LarsWM] <tt>(unique tiling Window Manager)</tt>
**[http://www.nongnu.org/ratpoison/ ratpoison] <tt>(modeled after gnu screen)</tt>
**[http://fvwm.org/ fvwm] <tt>(small but powerful)</tt>
**[http://www.jfc.org.uk/software/lwm.html lwm] <tt>(very small, and fast)</tt>
**[http://www.all-day-breakfast.com/wm2/ wm2] <tt>really small Window Manager</tt>
**[http://www.all-day-breakfast.com/wmx/ wmx] <tt>slightly more featureful version of wm2</tt>
**[http://wmii.suckless.org wmii] <tt>keyboard driven approach, very small, dynamic window managing</tt>

====Taskbar/Panel====
Another thing that especially users coming to Linux from the Windows world would probably like is a Panel or Taskbar.

Here's a collection of independant low resource panels:
*[http://www.chatjunkies.org/fspanel/ F***ing Small Panel] <tt>(doesn't use any toolkit)</tt>
*[http://freshmeat.net/projects/hpanel/ HPanel] <tt>(doesn't use any toolkit)</tt>
*[http://fbpanel.sourceforge.net/ fbpanel] <tt>(depends on GTK 2)</tt>
*[http://jodrell.net/projects/perlpanel Perl Panel] <tt>(depends on GTK 2, gnomevfs, perl)</tt>
*[http://www.gkrellm.net/ GKrellM] <tt>(depends on GTK 2, flexible plugin based skinable vertical panel)</tt>

====Desktop Pinboard====
Then, the next thing you might be looking for is how to get icons onto your desktop. Usually this is done by the file manager who displays the content of a special directory as icons on the desktop. See the File Manager section to follow this approach.

However, you might decide for a really lightwight file manager which doesn't offer this feature. In that case all hope is not lost, for there are also special programs specialized in desktop icon management. Such are:
* [http://idesk.sourceforge.net/ iDesk] <tt>(recent versions need imlib2 only)</tt>

====File Manager====
File Managers are the fourth really important compontent of a desktop environment. There are plenty out their ranging from resource hugs to really lightweight and slim ones.

File Managers come with three distinct general user interface approaches: the two pane gui, the spacial and the browser gui. The browser gui is the one the Windows Explorer starting from Windows 2000 uses as well as earlier versions of Nautilus. The spacial view is the one known from Windows 95 and more recent versions of Nautilus. The two pane view is know to many from Norten Commander, Directory Opus or your favorite FTP client.

The following list provides an overview.
*FLTK
** [http://www.oksid.ch/flfm/ Fast Light File Manager] <tt>(spacial gui)</tt>
* FOX toolkit
** [http://roland65.free.fr/xfe/ X File Explorer] <tt>(browser and two pane gui)</tt>
*GTK
** [http://www.kaisersite.de/dfm/ Desktop File Manager] <tt>(spacial gui, incl. desktop icon management)</tt>
** [http://www.uwyn.com/projects/fm/ FM] <tt>(spacial, MAC OS 9 like gui)</tt>
** [http://radekc.regnet.cz/ Seksi Commander] <tt>(two pane gui)</tt>
*GTK 2
** [http://rox.sourceforge.net/ ROX Filer] <tt>(highly productive spacial gui, incl. panel and desktop icon management)</tt>
** [http://blog.perldude.de/projects/filer/ Filer] <tt>(browser and two pane gui, requires Perl)</tt>
** [http://xffm.sourceforge.net/ XFFM] <tt>(browser and spacial gui, requires some XFCE libs)</tt>
** [http://logicaldesktop.sourceforge.net/ Logical Desktop] <tt>(browser gui, actually a very special approach)</tt>
** [http://tuxcmd.sourceforge.net/ Tux Commander] <tt>(two pane gui)</tt>
** [http://www.nongnu.org/gcmd/index.html Gnome Commander] <tt>(two pane gui)</tt>
** [http://emelfm2.net/emelFM2/ emelFM2] <tt>(two pane gui with full customizable menu and toolbar, the best for power users)</tt>
** [http://thunar.xfce.org/index.xhtml Thunar] <tt>(requires some XFCE libs)</tt>
** [http://pcmanfm.sourceforge.net/ PCMan File Manager] <tt>(An extremly fast and lightweight file manager which features tabbed browsing and user-friendly interface. Requires GTK+ version 2.8.x)</tt>
* OpenMotif
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xplore/xplore.php Xplore] <tt>(browser gui with productive 4 pane concept)</tt>
* QT 2
** [http://www.hi-net.cz/blaza/bfcommander/en/index.html BF-Commander] <tt>(two pane gui)</tt>
*Qt3
** [http://www.beesoft.org/download_bsc.html Beesoft Commander] <tt> (fast & easy two panel file manager, like Norton Commander)</tt>
* Tcl/Tk
** [http://users.tkk.fi/~mkivinie/X-Files/ X-Files] <tt>(two pane gui)</tt>
*X Toolkit
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xfm/ X File Manager] <tt>(spacial gui)</tt>
** [http://www.boomerangsworld.de/worker/ Worker] <tt>(two pane gui, highly productive and configurable)</tt>
** [http://xnc.dubna.su/ X Northern Captain] <tt>(interesting flexible two pane gui)</tt>
*3D Filemanagers
** [http://www.determinate.net/webdata/seg/tdfsb.html TDFSB] <tt>(3D gui, the most impressing 3D file browser so far)</tt>
** [http://www.forchheimer.se/bfm/ Brutal File Manager] <tt>(3D gui more for fun than productivity)</tt>
** [http://turma.sourceforge.net/software/3dfile/ 3DFile] <tt>(3D gui)</tt>
** [http://orbis.sourceforge.net/ Orbis] <tt>(3D gui)</tt>

==Choosing applications==
===Web Browser===
This is highly dependent on the way you use your browser, it's often worth it to try out all and just track general
memory usage. Remember that <tt>top</tt> and <tt>ps</tt> don't report correct memory usage, track totals only.

====Firefox====
Firefox is graphical web browser. One can install features like AdBlock and FlashClicktoplay which will decrease memory and
processor usage by hiding Flash and Java -adverts.

====Opera====
Opera is graphical web browser. You can easily enable/disable plug-ins and java (press F12) and decrease memory usage.
Opera uses QT as toolkit, so you may shave off some Mbytes off memory usage by using dynamically linked version if you use KDE.

====Konqueror====
Konqueror is graphical web browser. It's integrated with KDE and has several advanced features (esp. ca. KDE 3.5).
You may save some megabytes by using it instead of other browsers when using KDE.
It's not necessarily heavy even when used without running KDE.

====Dillo====
Dillo is minimalistic and very small graphical web browser.

====Elinks/Lynx====
elinks/lynx are both text mode web browsers. <tt>elinks</tt> handles tables and formatting much nicer than <tt>lynx</tt>.
Both go very easy on memory footprint.

{{Todo|...}}

==Disabling unneeded system deamons==
Another thing you can do to improve performance is to get rid of unneaded system daemons launched from your init scripts. Disable them by using the according configuration interface of your distro or by deleting links in the according runlevel directories (usually in <code>/etc/rc.d/</code>).

Daemons you usually don't need:
* httpd <tt>(Apache web server)</tt>
* mysqld <tt>(MySQL database server)</tt>
* smbd <tt>(SMB windows filesharing server)</tt>
* pppd <tt>(PPP server for connections through modems and serial lines)</tt>

==Adjusting filesystems==
You can also try to optimize memory usage by making sure that you have as little as possible of your filesystem residing in RAM. To do this make sure that the following mount points are set to reside on your harddisk in {{path|/etc/fstab}}.
* /dev (not possible if you use udev)
* /tmp

Also make sure that you mount filesystems with extensive usage with noatime parameter (mount -o remount,ro /...), which disabled access time writes every time you access some file. Note that many incremental backups needs atime to work, such backups will then behave like full backup everytime. This depends on backup systems.

==Other tips==
===Disk space===
When using Debian/Ubuntu/other derivative, use <tt>aptitude</tt> as package manager, and use it as soon as possible. Use it and only it to install and remove packages.

One of its most useful features is that it tracks packages you install and marks packages installed via dependency as such, so when you remove a package that is no longer used, or package updates and doesn't use a library anymore, that dependency will get uninstalled.

You can mark packages installed as automatically installed by hitting 'M' (uppercase m), it will be marked for deinstallation if it's not longer required.

You could also install <tt>localepurge</tt> wich will remove all unneeded locales and localized manpages for packages you install.

===System clock===
<tt>ntpd</tt> can occupy around 4MB of memory, which is a substantial proportion of many older systems' total. [http://chrony.sunsite.dk/ <tt>chrony</tt>] is a pair of programs that replace the standard <tt>ntp</tt> and require much less memory.

User:Samoht

2007-03-20T12:41:46Z

Samoht: added infos

Contact me via jabber (samoht@mabber.de) or mail (samoht at karmann-paf.de).

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T12:40:13Z

Samoht: /* Wireless Networking */

{{NOTE|This article is not finished yet!}}

== Wireless Networking ==

The module for this chip is in kernel mainline (ipw2200). The only showstopper is the missing firmware.

Get it here: [http://ipw2200.sourceforge.net/firmware.php?fid=7 firmware v3.0]

Extract it:

{{cmdroot| tar zxvf ipw2200-fw-3.0.tgz}}

Move the *.fw files to {{path|/lib/firmware/}}

{{cmdroot|mv *.fw /lib/firmware/}}

Reload the module:

{{cmdroot|rmmod ipw2200 && modprobe ipw2200}}

== CPU Throttling ==

Load the kernelmodule:

{{cmdroot|modprobe speedstep_centrino}}

Add line "speedstep_centrino" to {{path|/etc/modules}} to load the module on boot.

Install the throttling-daemon:

{{cmdroot|apt-get install powernowd}}

Done.

== Active Protection System==

=== Preparing the kernel ===

To get the headdisk-parking working you have to build your own kernel with the hdaps_protect-patch applied:

Install the prerequisites that we need to compile the new kernel:

{{cmdroot|apt-get install kernel-package ncurses-dev fakeroot wget bzip2}}

Get the recent debian-etch-kernel (2.6.18):

{{cmdroot|apt-get install linux-tree-2.6.18}}

Go to the sources and unpack them:

{{cmdroot|cd /usr/src}}
{{cmdroot| tar jxvf linux-source-2.6.18.tar.bz2}}

As etchs kernel is 2.6.18-4 its propably a good idea to get the hdaps_protect patch for 2.6.18-3:

{{cmdroot| wget http://www.dresco.co.uk/hdaps/hdaps_protect-2.6.18.3-2.patch}}

Apply the patch:

{{cmdroot|cd linux-source-2.6.18/}}
{{cmdroot|patch -p1 < ../hdaps_protect-2.6.18.3-2.patch}}

Copy the default-config to the sourcetree:

{{cmdroot|cp /boot/config-2.6.18-4-486 ./.config}}

Build the kernel & packages:

{{cmdroot|make-kpkg clean}}
{{cmdroot|make-kpkg fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

Install the new kernel. Grub-menu should be updated automatically.

{{cmdroot| dpkg -i linux-image-2.6.18_thinkpad.1.0_i386.deb }}

Reboot and select the new kernel. Verify with 'uname -a'.
If all things work you can set the new kernel default in {{path|/boot/grub/menu.lst}} with default $entry-number (0..1..2..)

===Preparing userspace===

Installing the daemon:

{{cmdroot|apt-get install hdapsd}}

To set your harddrive, edit {{path|/etc/default/hdapsd}}:

# start hdapsd at boottime?
'''START=yes'''
#
# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
'''DISK=sda'''
#
# other options to pass to hdapsd.
# the -d and -b options are always passed.
OPTIONS=

Restart hdapsd:

{{cmdroot|/etc/init.d/hdapsd restart}}

You should get something like that in {{path| /var/log/syslog}} when throwing your thinkpad off the table: (No, seriously, shaking it carefully should be sufficient :-) )

Mar 20 12:25:37 localhost kernel: ata_scsi_issue_protect_fn(): unload support reported by drive..
Mar 20 12:25:37 localhost kernel: scsi_protect_queue(): head parked..
Mar 20 12:25:38 localhost kernel: scsi_unprotect_queue(): No pending I/O, re-enabling power management..
Mar 20 12:25:38 localhost hdapsd[12522]: Tue Mar 20 12:25:38 2007: un-parking

== Fingerprint-Reader ==

=== Install userspace-tools ===
I got the fingerprint reader working with the new [http://thinkfinger.sourceforge.net/ ThinkFinger-drivers] (opensource). They are working much better than the closed-source UPEK drivers and don't have this ugly QT-dialog.

Get some debian-packages from [http://www.rubixlinux.org/debian/thinkfinger/ here] and install them with:

{{cmdroot| dpkg -i *.deb}}

=== Enroll your fingers ===
Enroll your fingers with:

{{cmdroot|tf-tool --add-user <login>}}

# tf-tool --add-user name
ThinkFinger 0.2.2 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>
Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/etc/pam_thinkfinger/name.bir)... done.

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

Open {{path|/etc/pam.d/common-auth}}:

# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
'''auth sufficient pam_thinkfinger.so'''
auth required pam_unix.so '''try_first_pass'''

Ready! Works flawlessly with gdm for instance!
Enroll user 'root' to use your fingerprint for 'sudo'.

[[Category:Z60m]][[Category:Debian]]

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T12:39:53Z

Samoht: /* Wireless Networking */

{{NOTE|This article is not finished yet!}}

== Wireless Networking ==

The module for this chip is in kernel mainline (ipw2200). The only showstopper is the missing firmware.

Get it here: [http://ipw2200.sourceforge.net/firmware.php?fid=7 firmware v3.0]

Extract it:

{{cmdroot| tar zxvf ipw2200-fw-3.0.tgz}}

Move the *.fw files to {{path|/lib/firmware/}

{{cmdroot|mv *.fw /lib/firmware/}}

Reload the module:

{{cmdroot|rmmod ipw2200 && modprobe ipw2200}}

== CPU Throttling ==

Load the kernelmodule:

{{cmdroot|modprobe speedstep_centrino}}

Add line "speedstep_centrino" to {{path|/etc/modules}} to load the module on boot.

Install the throttling-daemon:

{{cmdroot|apt-get install powernowd}}

Done.

== Active Protection System==

=== Preparing the kernel ===

To get the headdisk-parking working you have to build your own kernel with the hdaps_protect-patch applied:

Install the prerequisites that we need to compile the new kernel:

{{cmdroot|apt-get install kernel-package ncurses-dev fakeroot wget bzip2}}

Get the recent debian-etch-kernel (2.6.18):

{{cmdroot|apt-get install linux-tree-2.6.18}}

Go to the sources and unpack them:

{{cmdroot|cd /usr/src}}
{{cmdroot| tar jxvf linux-source-2.6.18.tar.bz2}}

As etchs kernel is 2.6.18-4 its propably a good idea to get the hdaps_protect patch for 2.6.18-3:

{{cmdroot| wget http://www.dresco.co.uk/hdaps/hdaps_protect-2.6.18.3-2.patch}}

Apply the patch:

{{cmdroot|cd linux-source-2.6.18/}}
{{cmdroot|patch -p1 < ../hdaps_protect-2.6.18.3-2.patch}}

Copy the default-config to the sourcetree:

{{cmdroot|cp /boot/config-2.6.18-4-486 ./.config}}

Build the kernel & packages:

{{cmdroot|make-kpkg clean}}
{{cmdroot|make-kpkg fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

Install the new kernel. Grub-menu should be updated automatically.

{{cmdroot| dpkg -i linux-image-2.6.18_thinkpad.1.0_i386.deb }}

Reboot and select the new kernel. Verify with 'uname -a'.
If all things work you can set the new kernel default in {{path|/boot/grub/menu.lst}} with default $entry-number (0..1..2..)

===Preparing userspace===

Installing the daemon:

{{cmdroot|apt-get install hdapsd}}

To set your harddrive, edit {{path|/etc/default/hdapsd}}:

# start hdapsd at boottime?
'''START=yes'''
#
# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
'''DISK=sda'''
#
# other options to pass to hdapsd.
# the -d and -b options are always passed.
OPTIONS=

Restart hdapsd:

{{cmdroot|/etc/init.d/hdapsd restart}}

You should get something like that in {{path| /var/log/syslog}} when throwing your thinkpad off the table: (No, seriously, shaking it carefully should be sufficient :-) )

Mar 20 12:25:37 localhost kernel: ata_scsi_issue_protect_fn(): unload support reported by drive..
Mar 20 12:25:37 localhost kernel: scsi_protect_queue(): head parked..
Mar 20 12:25:38 localhost kernel: scsi_unprotect_queue(): No pending I/O, re-enabling power management..
Mar 20 12:25:38 localhost hdapsd[12522]: Tue Mar 20 12:25:38 2007: un-parking

== Fingerprint-Reader ==

=== Install userspace-tools ===
I got the fingerprint reader working with the new [http://thinkfinger.sourceforge.net/ ThinkFinger-drivers] (opensource). They are working much better than the closed-source UPEK drivers and don't have this ugly QT-dialog.

Get some debian-packages from [http://www.rubixlinux.org/debian/thinkfinger/ here] and install them with:

{{cmdroot| dpkg -i *.deb}}

=== Enroll your fingers ===
Enroll your fingers with:

{{cmdroot|tf-tool --add-user <login>}}

# tf-tool --add-user name
ThinkFinger 0.2.2 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>
Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/etc/pam_thinkfinger/name.bir)... done.

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

Open {{path|/etc/pam.d/common-auth}}:

# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
'''auth sufficient pam_thinkfinger.so'''
auth required pam_unix.so '''try_first_pass'''

Ready! Works flawlessly with gdm for instance!
Enroll user 'root' to use your fingerprint for 'sudo'.

[[Category:Z60m]][[Category:Debian]]

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T12:39:29Z

Samoht:

{{NOTE|This article is not finished yet!}}

== Wireless Networking ==

The module for this chip is in kernel mainline (ipw2200). The only showstopper is the missing firmware.

Get it here: [http://ipw2200.sourceforge.net/firmware.php?fid=7 firmware v3.0]

Extract it:

{{cmdroot| tar zxvf ipw2200-fw-3.0.tgz}}

Move the *.fw files to {{path|/lib/firmware/}

{{cmdroot|mv *.fw /lib/firmware/}

Reload the module:

{{cmdroot|rmmod ipw2200 && modprobe ipw2200}}

== CPU Throttling ==

Load the kernelmodule:

{{cmdroot|modprobe speedstep_centrino}}

Add line "speedstep_centrino" to {{path|/etc/modules}} to load the module on boot.

Install the throttling-daemon:

{{cmdroot|apt-get install powernowd}}

Done.

== Active Protection System==

=== Preparing the kernel ===

To get the headdisk-parking working you have to build your own kernel with the hdaps_protect-patch applied:

Install the prerequisites that we need to compile the new kernel:

{{cmdroot|apt-get install kernel-package ncurses-dev fakeroot wget bzip2}}

Get the recent debian-etch-kernel (2.6.18):

{{cmdroot|apt-get install linux-tree-2.6.18}}

Go to the sources and unpack them:

{{cmdroot|cd /usr/src}}
{{cmdroot| tar jxvf linux-source-2.6.18.tar.bz2}}

As etchs kernel is 2.6.18-4 its propably a good idea to get the hdaps_protect patch for 2.6.18-3:

{{cmdroot| wget http://www.dresco.co.uk/hdaps/hdaps_protect-2.6.18.3-2.patch}}

Apply the patch:

{{cmdroot|cd linux-source-2.6.18/}}
{{cmdroot|patch -p1 < ../hdaps_protect-2.6.18.3-2.patch}}

Copy the default-config to the sourcetree:

{{cmdroot|cp /boot/config-2.6.18-4-486 ./.config}}

Build the kernel & packages:

{{cmdroot|make-kpkg clean}}
{{cmdroot|make-kpkg fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

Install the new kernel. Grub-menu should be updated automatically.

{{cmdroot| dpkg -i linux-image-2.6.18_thinkpad.1.0_i386.deb }}

Reboot and select the new kernel. Verify with 'uname -a'.
If all things work you can set the new kernel default in {{path|/boot/grub/menu.lst}} with default $entry-number (0..1..2..)

===Preparing userspace===

Installing the daemon:

{{cmdroot|apt-get install hdapsd}}

To set your harddrive, edit {{path|/etc/default/hdapsd}}:

# start hdapsd at boottime?
'''START=yes'''
#
# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
'''DISK=sda'''
#
# other options to pass to hdapsd.
# the -d and -b options are always passed.
OPTIONS=

Restart hdapsd:

{{cmdroot|/etc/init.d/hdapsd restart}}

You should get something like that in {{path| /var/log/syslog}} when throwing your thinkpad off the table: (No, seriously, shaking it carefully should be sufficient :-) )

Mar 20 12:25:37 localhost kernel: ata_scsi_issue_protect_fn(): unload support reported by drive..
Mar 20 12:25:37 localhost kernel: scsi_protect_queue(): head parked..
Mar 20 12:25:38 localhost kernel: scsi_unprotect_queue(): No pending I/O, re-enabling power management..
Mar 20 12:25:38 localhost hdapsd[12522]: Tue Mar 20 12:25:38 2007: un-parking

== Fingerprint-Reader ==

=== Install userspace-tools ===
I got the fingerprint reader working with the new [http://thinkfinger.sourceforge.net/ ThinkFinger-drivers] (opensource). They are working much better than the closed-source UPEK drivers and don't have this ugly QT-dialog.

Get some debian-packages from [http://www.rubixlinux.org/debian/thinkfinger/ here] and install them with:

{{cmdroot| dpkg -i *.deb}}

=== Enroll your fingers ===
Enroll your fingers with:

{{cmdroot|tf-tool --add-user <login>}}

# tf-tool --add-user name
ThinkFinger 0.2.2 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>
Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/etc/pam_thinkfinger/name.bir)... done.

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

Open {{path|/etc/pam.d/common-auth}}:

# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
'''auth sufficient pam_thinkfinger.so'''
auth required pam_unix.so '''try_first_pass'''

Ready! Works flawlessly with gdm for instance!
Enroll user 'root' to use your fingerprint for 'sudo'.

[[Category:Z60m]][[Category:Debian]]

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T12:32:34Z

Samoht: added cpu throttling

{{NOTE|This article is not finished yet!}}

== CPU Throttling ==

Load the kernelmodule:

{{cmdroot|modprobe speedstep_centrino}}

Add line "speedstep_centrino" to {{path|/etc/modules}} to load the module on boot.

Install the throttling-daemon:

{{cmdroot|apt-get install powernowd}}

Done.

== Active Protection System==

=== Preparing the kernel ===

To get the headdisk-parking working you have to build your own kernel with the hdaps_protect-patch applied:

Install the prerequisites that we need to compile the new kernel:

{{cmdroot|apt-get install kernel-package ncurses-dev fakeroot wget bzip2}}

Get the recent debian-etch-kernel (2.6.18):

{{cmdroot|apt-get install linux-tree-2.6.18}}

Go to the sources and unpack them:

{{cmdroot|cd /usr/src}}
{{cmdroot| tar jxvf linux-source-2.6.18.tar.bz2}}

As etchs kernel is 2.6.18-4 its propably a good idea to get the hdaps_protect patch for 2.6.18-3:

{{cmdroot| wget http://www.dresco.co.uk/hdaps/hdaps_protect-2.6.18.3-2.patch}}

Apply the patch:

{{cmdroot|cd linux-source-2.6.18/}}
{{cmdroot|patch -p1 < ../hdaps_protect-2.6.18.3-2.patch}}

Copy the default-config to the sourcetree:

{{cmdroot|cp /boot/config-2.6.18-4-486 ./.config}}

Build the kernel & packages:

{{cmdroot|make-kpkg clean}}
{{cmdroot|make-kpkg fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

Install the new kernel. Grub-menu should be updated automatically.

{{cmdroot| dpkg -i linux-image-2.6.18_thinkpad.1.0_i386.deb }}

Reboot and select the new kernel. Verify with 'uname -a'.
If all things work you can set the new kernel default in {{path|/boot/grub/menu.lst}} with default $entry-number (0..1..2..)

===Preparing userspace===

Installing the daemon:

{{cmdroot|apt-get install hdapsd}}

To set your harddrive, edit {{path|/etc/default/hdapsd}}:

# start hdapsd at boottime?
'''START=yes'''
#
# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
'''DISK=sda'''
#
# other options to pass to hdapsd.
# the -d and -b options are always passed.
OPTIONS=

Restart hdapsd:

{{cmdroot|/etc/init.d/hdapsd restart}}

You should get something like that in {{path| /var/log/syslog}} when throwing your thinkpad off the table: (No, seriously, shaking it carefully should be sufficient :-) )

Mar 20 12:25:37 localhost kernel: ata_scsi_issue_protect_fn(): unload support reported by drive..
Mar 20 12:25:37 localhost kernel: scsi_protect_queue(): head parked..
Mar 20 12:25:38 localhost kernel: scsi_unprotect_queue(): No pending I/O, re-enabling power management..
Mar 20 12:25:38 localhost hdapsd[12522]: Tue Mar 20 12:25:38 2007: un-parking

== Fingerprint-Reader ==

=== Install userspace-tools ===
I got the fingerprint reader working with the new [http://thinkfinger.sourceforge.net/ ThinkFinger-drivers] (opensource). They are working much better than the closed-source UPEK drivers and don't have this ugly QT-dialog.

Get some debian-packages from [http://www.rubixlinux.org/debian/thinkfinger/ here] and install them with:

{{cmdroot| dpkg -i *.deb}}

=== Enroll your fingers ===
Enroll your fingers with:

{{cmdroot|tf-tool --add-user <login>}}

# tf-tool --add-user name
ThinkFinger 0.2.2 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>
Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/etc/pam_thinkfinger/name.bir)... done.

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

Open {{path|/etc/pam.d/common-auth}}:

# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
'''auth sufficient pam_thinkfinger.so'''
auth required pam_unix.so '''try_first_pass'''

Ready! Works flawlessly with gdm for instance!
Enroll user 'root' to use your fingerprint for 'sudo'.

[[Category:Z60m]][[Category:Debian]]

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T11:55:30Z

Samoht:

{{NOTE|This article is not finished yet!}}

== Active Protection System==

=== Preparing the kernel ===

To get the headdisk-parking working you have to build your own kernel with the hdaps_protect-patch applied:

Install the prerequisites that we need to compile the new kernel:

{{cmdroot|apt-get install kernel-package ncurses-dev fakeroot wget bzip2}}

Get the recent debian-etch-kernel (2.6.18):

{{cmdroot|apt-get install linux-tree-2.6.18}}

Go to the sources and unpack them:

{{cmdroot|cd /usr/src}}
{{cmdroot| tar jxvf linux-source-2.6.18.tar.bz2}}

As etchs kernel is 2.6.18-4 its propably a good idea to get the hdaps_protect patch for 2.6.18-3:

{{cmdroot| wget http://www.dresco.co.uk/hdaps/hdaps_protect-2.6.18.3-2.patch}}

Apply the patch:

{{cmdroot|cd linux-source-2.6.18/}}
{{cmdroot|patch -p1 < ../hdaps_protect-2.6.18.3-2.patch}}

Copy the default-config to the sourcetree:

{{cmdroot|cp /boot/config-2.6.18-4-486 ./.config}}

Build the kernel & packages:

{{cmdroot|make-kpkg clean}}
{{cmdroot|make-kpkg fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

Install the new kernel. Grub-menu should be updated automatically.

{{cmdroot| dpkg -i linux-image-2.6.18_thinkpad.1.0_i386.deb }}

Reboot and select the new kernel. Verify with 'uname -a'.
If all things work you can set the new kernel default in {{path|/boot/grub/menu.lst}} with default $entry-number (0..1..2..)

===Preparing userspace===

Installing the daemon:

{{cmdroot|apt-get install hdapsd}}

To set your harddrive, edit {{path|/etc/default/hdapsd}}:

# start hdapsd at boottime?
'''START=yes'''
#
# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
'''DISK=sda'''
#
# other options to pass to hdapsd.
# the -d and -b options are always passed.
OPTIONS=

Restart hdapsd:

{{cmdroot|/etc/init.d/hdapsd restart}}

You should get something like that in {{path| /var/log/syslog}} when throwing your thinkpad off the table: (No, seriously, shaking it carefully should be sufficient :-) )

Mar 20 12:25:37 localhost kernel: ata_scsi_issue_protect_fn(): unload support reported by drive..
Mar 20 12:25:37 localhost kernel: scsi_protect_queue(): head parked..
Mar 20 12:25:38 localhost kernel: scsi_unprotect_queue(): No pending I/O, re-enabling power management..
Mar 20 12:25:38 localhost hdapsd[12522]: Tue Mar 20 12:25:38 2007: un-parking

== Fingerprint-Reader ==

=== Install userspace-tools ===
I got the fingerprint reader working with the new [http://thinkfinger.sourceforge.net/ ThinkFinger-drivers] (opensource). They are working much better than the closed-source UPEK drivers and don't have this ugly QT-dialog.

Get some debian-packages from [http://www.rubixlinux.org/debian/thinkfinger/ here] and install them with:

{{cmdroot| dpkg -i *.deb}}

=== Enroll your fingers ===
Enroll your fingers with:

{{cmdroot|tf-tool --add-user <login>}}

# tf-tool --add-user name
ThinkFinger 0.2.2 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>
Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/etc/pam_thinkfinger/name.bir)... done.

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

Open {{path|/etc/pam.d/common-auth}}:

# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
'''auth sufficient pam_thinkfinger.so'''
auth required pam_unix.so '''try_first_pass'''

Ready! Works flawlessly with gdm for instance!
Enroll user 'root' to use your fingerprint for 'sudo'.

[[Category:Z60m]][[Category:Debian]]

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T11:37:07Z

Samoht:

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T11:28:35Z

Samoht:

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T10:50:04Z

Samoht:

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T10:44:20Z

Samoht:

Installing Debian Etch on a ThinkPad Z60m

2007-03-20T10:43:20Z

Samoht:

How to enable the integrated fingerprint reader with ThinkFinger

2007-03-13T19:09:30Z

Samoht:

[[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're on Gentoo, you can find an ebuild at [https://bugs.gentoo.org/show_bug.cgi?id=162297 bug 162297].

{{NOTE|packages for Debian (testing) are available here: [http://www.rubixlinux.org/debian/thinkfinger/]}}

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

{{cmduser|cd thinkfinger-0.2.2}}

<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, it may vary for your distro!}}

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 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:

{{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

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.

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-03-13T19:08:46Z

Samoht: added url to debian packages

[[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're on Gentoo, you can find an ebuild at [https://bugs.gentoo.org/show_bug.cgi?id=162297 bug 162297].

{{NOTE|packages for Debian are available here: [http://www.rubixlinux.org/debian/thinkfinger/]}}

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

{{cmduser|cd thinkfinger-0.2.2}}

<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, it may vary for your distro!}}

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 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:

{{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

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.

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

Talk:How to enable integrated fingerprint reader with BioAPI

2007-02-05T19:28:26Z

Samoht: /* Alternative ThinkFinger "Driver" */

== Removing the GUI Prompt ==
For all of you that have had the oppertunity to see the fingerprint image, I think we can all agree that this needs to be changed at ounce. A couple of ideas come to mind, first is to trick bioapi to think that X is not running, and secound is to figure out where the images are being pulled from and then edit them. The later would be nice, but I have been experimenting with strace for several hours and have came up with nothing. Any other ideas?

--[[User:Paul Strefling|Paul Strefling]] 18:42, 18 July 2006 (CEST)
----

== chmod 777 -R /usr/local/var/bioapi/ ==

Is the above necessary? I just made a debian package of xscreensaver with the patch applied, and when using the bioapi debian pacakge from [http://www.qrivy.net/~michael/temp/ Michael R. Crusoe's site] which has this directory put in /usr/var/bioapi I had not to change the permissions to world-writeable there. Write access to the logfile and usb device are necessary, but that directory works with 755 as well (even though it comes with 777 in Michael's package), and all files and subdirectories are 644/755 too.

--[[User:Spiney|spiney]] 00:08, 11 Nov 2005 (CET)
----

== Qt Compilation Success ==

Here it worked with qt ;)

--

I didn't get it to work anyway, but I'm curious about your Qt version(s) as it seemed to want Qt 3 when I was playing with it.

--[[User:Keegan|keegan]] 05:07, 24 Dec 2005 (CET)

== using absolute paths for commands ==

I don't know whether using absolute paths in the articles is a good idea, at least not for tools like {{cmd|lsusb|}} which are not established utilities (i.e. used for more than a decade or something ;)) and happen to be in different locations in different distributions. E.g. said {{cmd|lsusb|}} resides in {{path|/usr/sbin|}} on Debian systems.

--[[User:Spiney|spiney]] 16:45, 12 Nov 2005 (CET)
----

I'm using debian testing and it's in {{path|/usr/bin|}}. I agree that the confusion is bad; dropping the absolute paths and adding a general note about checking {{cmd|$PATH|}} in case of problems is probably good.

--[[User:keegan|keegan]]

== BioAPI error #3 ==

Its kind of strage it used to work with everythig (kdm,console,lock,etc)
Now it only works with kdm. It allways gives back:

pam_bioapi[8113]: Unable to initialize Bioapi framework, BioAPI error #:3.

Even when I set the right permissions on /proc/bus/usb.

I am able to run the Sample program as normal user after setting the permissions, but when I change within a user session by su I amnot able to run the Sample program a also get an error Code #3.

From an other terminal (alt+strg+Fx) I am able to run the Sample program but at the login I still get the error #3.

I cant remember to have changed anything an d bevor I was able to login in a console with my fingerprint now only kdm is working even kde lock-session
isnt working anymore.

Any suggestions ?

==Permission errors exclusive to xscreensaver==

I followed the instructions above and got everything working, including non-root programs like xscreensaver. However, the script to change usbfs permissions is finicky and fails to work with a lot of things like suspend/resume. Therefore, I switched to specifying <tt>devgid=108,devmode=0660,busgid=108,busmode=0770,listgid=108,listmode=0660</tt> as mount parameters for usbfs, where group 108 is a group I created and added my normal user to. This seems like a much better way of doing things, and it almost works. However, xscreensaver (using the newer patch) gives the familiar <tt>Unable to load BioAPI BSP with UUID of <nowiki>{</nowiki>5550454b-2054-464d-2f45-535320425350<nowiki>}</nowiki>, BioAPI error #194d.</tt> error in {{path|/var/log/auth.log|}}. I don't think this is a straightfoward permissions problem because
<ul>
<li>the permissions in {{path|/proc/bus/usb|}} are correct by inspection</li>
<li>I can write to the device file as my normal user</li>
<li>other programs like {{cmd|test_verify-pam_bioapi|}} and [http://pamtester.sourceforge.net/ {{cmd|pamtester|}}] work as my normal user</li>
<li>the weirdest one: xscreensaver works when the {{cmd|xscreensaver|}} daemon is launched from within {{cmd|strace|}}. It's still running as my normal user ({{cmd|strace|}} is not setuid root). I have absolutely no idea what would cause this. I thought it might be an environment issue, but the difference in environment between the {{cmd|strace|}} session and my normal session is trivial.</li>
</ul>

At this point I'm hoping it's something dumb, but I'm out of ideas. The {{cmd|xscreensaver|}} error is <tt>pam_authenticate (...) ==> 7 (Authentication failure)</tt>, for the record.

--[[User:keegan|keegan]]
----

I had the same problem and found that it was caused by the setuid permission on xscreensaver. After chmod'ing it to 755 and restarting xscreensaver, bioapi authentication worked.

--[[User:henning|henning]] 09:22, 8 Aug 2006 (CET)
----

Could you provide all the log lines between pam_start and pam_end when running {{cmd|xscreensaver -verbose|}}?

BTW, the idea with using the mount options for usbfs is very good, maybe you should add that info to the article page? I use the permission changing script without problems, also after resume, but the usbfs version is probably easier to set up, most people will be able to find {{path|/etc/fstab|}}.

--[[User:Spiney|spiney]] 10:12, 23 Dec 2005 (CET)
----
<pre>
xscreensaver: 20:56:01: alternative_pam: 1 -> pam service: xscreensaver-alternative
xscreensaver: 20:56:01: pam_start ("xscreensaver-alternative", "keegan", ...) ==> 0 (Success)
xscreensaver: 20:56:01: pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver: 20:56:01: PAM ECHO_OFF("Password: ") ==> password
xscreensaver: 20:56:03: pam_authenticate (...) ==> 7 (Authentication failure)
xscreensaver: 20:56:03: pam_end (...) ==> 0 (Success)
xscreensaver: 20:56:03: prompting for password.
xscreensaver: 20:56:03: 0: creating password dialog.
xscreensaver: 20:56:03: 0: mouse is at 442,412.
xscreensaver: 20:56:03: grabbing server...
xscreensaver: 20:56:03: 0: ungrabbing mouse (was 0x48).
xscreensaver: 20:56:03: 0: grabbing mouse on 0xe0002b... GrabSuccess.
xscreensaver: 20:56:03: ungrabbing server.
xscreensaver: 20:56:05: alternative_pam: 12582928 -> pam service: xscreensaver
xscreensaver: 20:56:05: pam_start ("xscreensaver", "keegan", ...) ==> 0 (Success)
xscreensaver: 20:56:05: pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver: 20:56:05: PAM ECHO_OFF("Password: ") ==> password
xscreensaver: 20:56:05: pam_authenticate (...) ==> 0 (Success)
xscreensaver: 20:56:05: pam_acct_mgmt (...) ==> 9 (Authentication service cannot retrieve authentication info.)
xscreensaver: 20:56:05: pam_setcred (...) ==> 0 (Success)
xscreensaver: 20:56:05: pam_end (...) ==> 0 (Success)
xscreensaver: 20:56:05: password correct.
</pre>
So we've got the first attempt with {{cmd|pam_bioapi|}}, which fails immediately (no sign of the GUI fingerprint prompt, nor a "silent" chance to swipe the finger as with xdm), then the fallback to {{cmd|pam_unix|}} which succeeds. Earlier I had xscreensaver set up to only try {{cmd|pam_bioapi|}}, with essentially the same result -- it gives up on pam entirely and does unix auth itself.

I'd really like to strace the pam module and see what it's attempting to do to {{path|/proc/bus/usb|}}, but as that actually fixes the problem I'm kinda at a loss. Maybe there's some kernel option to print debugging info for usbfs? I'd be all for changing the article to suggest using mount options in {{path|/etc/fstab|}}, if it weren't for this one weird bug. Has anyone else had the same problem?

-- [[User:keegan|keegan]]

Same here, I had the whole setup workin flawlessly (I really need to get that 'never-touch-a-running-system' mantra burnt into the back of my hands), but after a fresh install of the same distro (Ubuntu) and following the same procedure to get things working i get exactly this behaviour. Login works (now even with multifinger, although there are other issues with that), I can use test_verify-pam_bioapi as a user. and the stock xscreensaver works, albeit only after entering a bogus password first.
The patched xscreensaver works when run within a strace (Now that sucks) but fails otherwise. And as i said before, I had this working...

----
<pre>
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 13
fstat64(13, {st_mode=S_IFDIR|0755, st_size=140, ...}) = 0
fcntl64(13, F_SETFD, FD_CLOEXEC) = 0
getdents64(13, /* 7 entries */, 4096) = 168
getdents64(13, /* 0 entries */, 4096) = 0
close(13) = 0
open("/dev/bus/usb/003", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 13
fstat64(13, {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
fcntl64(13, F_SETFD, FD_CLOEXEC) = 0
getdents64(13, /* 4 entries */, 4096) = 96
open("/dev/bus/usb/003/002", O_RDWR) = -1 EACCES (Permission denied)
open("/dev/bus/usb/003/002", O_RDONLY) = 14
ioctl(14, USBDEVFS_CONNECTINFO, 0xafd5bd34) = -1 EPERM (Operation not permitted)
read(14, "\22\1\0\1\0\0\0\10\203\4\26 \1\0\1\2\0\1", 18) = 18
read(14, "\t\2\'\0\1\1\0\240", 8) = 8
read(14, "2\t\4\0\0\3\377\0\0\0\7\5\201\2@\0\0\7\5\2\2@\0\0\7\5\203"..., 31) = 31
close(14) = 0
</pre>

Here is all the excitement from the strace on xscreensaver. As I originally thought, you cannot get away with just playing with the proc entries :P You also need to deal with the counterpart in /dev. We can wrap up all the permissions issues with a single UDEV rule:

<pre>
# fingerprint fun
BUS=="usb", DRIVER=="usb", SYSFS{product}=="Biometric Coprocessor", GROUP="bioapi", SYMLINK="misc/fingerprint", RUN+="/bin/sh -c 'chgrp bioapi /proc/$RESULT; chmod g+rw /proc/$RESULT'"
</pre>

I created a 'bioapi' group and configured pam to add groups to anyone logging in ''locally''. Now all you need to do is amend the pam configuraion files below. We use 'wdm', but of course its as applicable for all those resource hungry touchy-feely gdm/kdm folk out there too ;)

/etc/security/group.conf
<pre>
# local group settings
login; tty*; *; al0000-2400; audio,floppy,video,cdrom,nvram,plugdev,bioapi
wdm; :*; *; al0000-2400; audio,floppy,video,cdrom,nvram,plugdev,bioapi
</pre>

/etc/pam.d/login
<pre>
[snipped]

# group *has* to go here
auth optional pam_group.so

# fingerprint action
auth sufficient /usr/local/lib/security/pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi1.10/pam/

# Standard Un*x authentication.
@include common-auth

# This allows certain extra groups to be granted to a user
# based on things like time of day, tty, service, and user.
# Please edit /etc/security/group.conf to fit your needs
# (Replaces the `CONSOLE_GROUPS' option in login.defs)
#auth optional pam_group.so

[snipped]
</pre>

/etc/pam.d/wdm
<pre>
#%PAM-1.0
auth required pam_nologin.so
auth required pam_env.so

# local tweak
auth optional pam_group.so

# fingerprint action
auth sufficient /usr/local/lib/security/pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi1.10/pam/

@include common-auth
@include common-account
@include common-session
</pre>

'''N.B.''' as with all pam related things, the order is important

-- [[User:Jim diGriz|Jim diGriz]]
----

==Driver Expiring!!!==
Don't anyone notice that both betas of the UPEK driver is expiring in
about a month in the new year, Jan 1st 2006? They really mean it!
I set my computer date to next year and get a message "the driver has expired" when using fingerprint reader! This is a grave threat to our computer lifestyle, i.e. for those of us who got it working and use it
daily:)
Is there any workaround other than setting the date back a year when
new year come and wait for new driver? Is there a way to figure out where exactly in the driver it checked the date and how? The must have set it
somewhere in file libtfmessbsp.so, but it is binary and I can't figure out how to Reverse Engineer it.

---Jiang

Yes, the beta driver will expire. The final version (which is due REALLY soon now) will not.

Sumedha

Any news? Just 9 days left to expiry. --[[User:Thinker|Thinker]] 21:36, 22 Dec 2005 (CET)

The final is out, get it at [http://www.upek.com/support/dl_linux_bsp.asp UPEK's download page]. And how does one edit the industry watch section of the main page?

--[[User:Spiney|spiney]] 21:39, 22 Dec 2005 (CET)

Ah, great! Both the article page and the driver page it points to are out of date... For the news, just follow the "[[ThinkWiki:News|News]]" link in the main page.

--[[User:Thinker|Thinker]] 21:44, 22 Dec 2005 (CET)

As this is now very soon I've updated the article page to link to the final driver, which is better in a few ways anyway. This is unless anyone minds (are there any unresolved issues with the final that don't exist in the betas?).

--[[User:Keegan|keegan]] 05:06, 24 Dec 2005 (CET)

== Updated xscreensaver patch ==

I've tried to address some usability issues with the old patch, e.g. that it calls the PAM bioapi module twice before falling back to the normal authentication methods. It can be found on my [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_fingerprint_reader Fingerprint Reader] page, feedback is very welcome.

--[[User:Spiney|spiney]] 20:36, 22 Dec 2005 (CET)
----

== Fingerprint or password ==

Is there any way to have PAM accept either a password or a finger swipe, right away? Sometimes one is more convenient, sometimes the other, so and it's a lot of trouble to wait for the UPEK scanner prompt and then cancel it in order to reach the password entry.

--[[User:Thinker|Thinker]] 19:27, 24 Dec 2005 (CET)

== KDE screensaver ==

If you get the following in {{path|/var/log/secure}} when you try to unlock the KDE screensaver, it means you forgot to set the USB device permissions.
localhost pam_bioapi[24981]: Unable to load BioAPI BSP with UUID of {5550454b-2054-464d-2f45-535320425350}, BioAPI error #194d.

--[[User:Thinker|Thinker]] 21:21, 24 Dec 2005 (CET)
----

== fingerprint reader in action. ==

small video with fingerprint reader in action with login: http://chao.ch/tmp/mov01302.mpg

--[[User:62.202.35.30|62.202.35.30]] 17:57, 29 Dec 2005 (CET)

==A little feedback...==
...for all the editors of this article:

"[[How to enable the fingerprint reader]] over at ThinkWiki.org is some real exhaustive documentation for getting the fingerprint scanner working on the ThinkPads. There is also a troubleshooting section towards the end that might be very useful to anyone messing around with it.

Thanks to those responsible for taking the time to write up this excellent guide."

Those thanks come from [http://linuxbiometrics.com/modules/news/ LinuxBiometrics.com]

[[User:Wyrfel|Wyrfel]] 01:24, 9 Jan 2006 (CET)
----

==pam_bioapi.so is not linked to libbioapi100.so==
I downloaded the pam_bioapi package and patched the file by following the wiki. However, I got the following result:

~/soft/thinkpad/pam_bioapi-0.2.1/libpam_bioapi/.libs$ ls -la
total 48
drwxr-xr-x 2 louis users 248 2006-01-12 01:18 ./
drwxr-xr-x 4 louis users 312 2006-01-12 01:18 ../
lrwxrwxrwx 1 louis users 16 2006-01-12 01:18 pam_bioapi.la -> ../pam_bioapi.la
-rw-r--r-- 1 louis users 824 2006-01-12 01:18 pam_bioapi.lai
-rw-r--r-- 1 louis users 19716 2006-01-12 01:18 pam_bioapi.o
lrwxrwxrwx 1 louis users 19 2006-01-12 01:18 pam_bioapi.so -> pam_bioapi.so.0.0.0*
lrwxrwxrwx 1 louis users 19 2006-01-12 01:18 pam_bioapi.so.0 -> pam_bioapi.so.0.0.0*
-rwxr-xr-x 1 louis users 21789 2006-01-12 01:18 pam_bioapi.so.0.0.0*

~/soft/thinkpad/pam_bioapi-0.2.1/libpam_bioapi/.libs$ ldd pam_bioapi.so
linux-gate.so.1 => (0xffffe000)
libc.so.6 => /lib/tls/libc.so.6 (0x40025000)
/lib/ld-linux.so.2 (0x80000000)
~/soft/thinkpad/pam_bioapi-0.2.1/libpam_bioapi/.libs$

pam_bioapi.so is NOT linked to libbioapi100.so. The latter is in the ld path:

~/soft/thinkpad/pam_bioapi-0.2.1/libpam_bioapi/.libs$ ldconfig -p |grep bioapi
libtfmessbsp.so (libc6) => /opt/bioapi/lib/libtfmessbsp.so
libpwbsp.so.0 (libc6) => /opt/bioapi/lib/libpwbsp.so.0
libpwbsp.so (libc6) => /opt/bioapi/lib/libpwbsp.so
libmds_util.so.0 (libc6) => /opt/bioapi/lib/libmds_util.so.0
libmds_util.so (libc6) => /opt/bioapi/lib/libmds_util.so
libbioapi100.so.0 (libc6) => /opt/bioapi/lib/libbioapi100.so.0
libbioapi100.so (libc6) => /opt/bioapi/lib/libbioapi100.so
libbioapi_mds300.so.0 (libc6) => /opt/bioapi/lib/libbioapi_mds300.so.0
libbioapi_mds300.so (libc6) => /opt/bioapi/lib/libbioapi_mds300.so
libbioapi_dummy100.so.0 (libc6) => /opt/bioapi/lib/libbioapi_dummy100.so.0
libbioapi_dummy100.so (libc6) => /opt/bioapi/lib/libbioapi_dummy100.so

and the Sample program also works allowing me to enroll and test a fingerprint.

My system is SuSE 10 with the kernel of 2.6.13-15. Any ideas?

Thanks.

--[[User:Tyne|Tyne]] 09:51, 12 Jan 2006 (CET)

==xscreensaver 4.23+fingerprint.patch causes xscreensaver-gl to crash kernel==

I've gotten bioapi and 'Sample' to allow me to enroll my fingerprint, and I've also experienced the 'two logon' issue.

I compiled xscreensaver 4.23 (though it seemed that apt came with 4.24) and applied the patch. My goal was to have the fingerprint prompt come up and to see the "bad image" of the fingerprint scan.

The first time I did this, xscreensaver-gl took a dump and was causing kernel crashes. So I went and got the newest xscreensaver source and patches, and applied the bioapi patch to those. It worked (meaning it didnt crash the kernel anymore ;b )

It would seem that there is a /etc/pam.d/xscreensaver, so I commented everything out of that except the bioapi line.

Locking xscreensaver, then attempting to unlock didnt show me any fingerprint requirements, and my password didnt work.

I'm wondering if theres something that was left out of the xscreensaver howto? or if theres anyone out there who's gotten the xscreensaver portion of this to work, who would be willing to help me out :)

--[[User:Viss|Viss]] 11:15am, 5 Feb 2006 (PST)

== gdm hangs on kde logout ==

Hi.

I am using a Thinkpad t43, installed with gentoo.
I run gdm as the login manager, with kde 3.4 and enlightenment dr16 as the window manager.

I followed the steps in the wiki, and the biometric scanner is now working fine, appart from the fact that when I close/end the session I just get a blank screen, in place of the gdm login screen.

Disabling the biometrics (by setting the pam.d file back to their originals), the session ends fine. I do this for a few times, and then set the biometrics back again, and it work fine for a few logouts, and then back to the blank screen again.

I can do ctrl+shift+f1 to get to a console window and from there I can issue a shutdown.
Although this works ok, it is a bit of a pain.

Any ideas ?

== 'gksudo' Doesn't show biopam finger swipe prompt... ==

Hey all,

First off... this is an excellent how-to! I have no real interest in using fingerprint scanner with xscreensaver, but it was up and working with everything else on my system pretty much effortlessly.

I'm running Ubuntu Breezy Badger 5.10 on an IBM T43p (2678) and have run into two oddities:
1) /etc/pam.d/xscreensaver - as it is initially configured, if you have an xscreensaver session set to require password (or xlock with screensaver) then you get prompted for the normal text-password entry and then will be prompted to swipe your finger... This is easily fixed by commenting out the '@include common-auth' line in /etc/pam.d/xscreensaver and adding the line 'auth required pam_unix.so nullok_secure'. After that change it only prompts for the text-password entry challenge.

2) gksudo - This is more of a pain... I can use the fingerprint scanner with gksudo, but gksudo doesn't prompt with the (ugly-but-functional) finger swipe dialog the way that gdm does during login or xscreensaver does when configured as mentioned above (pre-fix). So, if I start a Gnome app launcher that is prepended with gksudo, nothing appears to happen until I swipe my finger and then the app gets launched. That's cool and all, but there are times (esp. when multi-tasking) when I forget to swipe and then go "what happened to xxxxx? oh yeah..."

Anyway... does anyone have an idea of what I can do to get the dialog to appear?

thanx

--[[User:JELaVallee|JELaVallee]] 05:56, 20 February 2006 (CET)

The gksudo problem is a restriction from the X server. It doesn't allow to grab the display for other users than the logged-in one. And the pam_bioapi is invoked as root.

--[[User:Whoopie|Whoopie]] 13:10, 20 February 2006 (CET)

That makes sense... so, now I have to wonder, is there a patchable work-around like the xscreensaver one that could allow for this to work? Where should I research such? gksu's project or is this more an issue at the X11-level?

--[[User:JELaVallee|JELaVallee]] 19:38, 27 February 2006 (CET)

I got it working. Grab out the newer pam-bioapi from CVS (http://savannah.nongnu.org/cvs/?group=pam-bioapi). This version supports "multi-finger" when using the sqlite3 database. And it supports defining the used display.
Change your line in your /etc/pam.d/ files like this:

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/bioshadow.db :0

--[[User:Whoopie|Whoopie]] 14:27, 1 March 2006 (CET)

Very cool... Did you run into any issues rebuilding/installing this? I'll give it a shot this evening... THANKS!

--[[User:JELaVallee|JELaVallee]] 21:07, 1 March 2006 (CET)

Invoke 'xhost +local:' should be able to let gksudo work. Or just blindly sweap the finger. ;)

--[[User:YChao|YChao]] 21:25, 7 March 2006 (CET)

Where do I have to put 'xhost +local:'?

== Multifinger ==

Wow, theres a new version of pam_bioapi which supports multifinger enrollment and user identification.
I'll break my system with that this evening :)

Yes, but I'm searching the patch for xdm. The download page from Josef Hajas (http://nax.hn.org/pub/bioapi/) is down. Does anybody have it?

Update: The patch can be found here: http://www.qrivy.net/~michael/blua/xdm_bio.patch

--[[User:Whoopie|Whoopie]] 17:43, 1 March 2006 (CET)

Tried the newest pam-bioapi from CVS (http://savannah.nongnu.org/cvs/?group=pam-bioapi) on FC3. Failed on enrolling fingerprints: ({{path|/var/log/secure|}})

<code>Mar 9 15:30:40 localhost pam_bioapi[32407]: Can't open database: library routine called out of
sequence</code>

Could anyone help?

--[[User:Ychao|Ychao]] 00:38, 10 March 2006 (CET)

I don't know how to solve it. It seems to be a problem with sqlite3. Which version do you use? Under Ubuntu Breezy, it's 3.2.1.

--[[User:Whoopie|Whoopie]] 12:27, 10 March 2006 (CET)

Did anybody tried multifinger with BioAPI? I am interested in multifinger at all, not only PAM.

Updated:

succesfully installed pam_bioapi with multifinger support, some info:

use: <code>auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/bioshadow.db :0</code> in pam.d, the bioshadow column is path to bioapi sqlite database.

if authentication doesn't work, edit /etc/syslog.conf and write line *.alert /var/log/syslog, so you see pam_bioapi messages in /var/log/syslog
most common error is missing biodata table, newest pam_bioapi version should create it automatically, but if it doesn't, go to /etc/bioapi/pam/ and run command <code>sqlite3 bioshadow.db</code>, then insert this:

<code>CREATE TABLE biodata (id INTEGER PRIMARY KEY,uid INTEGER,uuid TEXT,header BLOB,data BLOB,signature BLOB,type INTEGER,other BLOB);</code>

you must then enroll at least one fingerprint to the database, do it using test_enroll-pam_bioapi from pam_bioapi distribution. note that you must have root user enrolled in order to use <code>su</code> command.

--[[User:MeBa|MeBa]] 16:58, 22 March 2006 (CET)

== GNOME Screensaver support ==

Did anybody try to port the xscreensaver patch to gnome-screensaver? Since Ubuntu Dapper will be shiped with it, it would be nice to have it working then with the fingerprint reader.

Update: Initial support can be found in gnome-screensaver CVS. See [http://bugzilla.gnome.org/show_bug.cgi?id=338635 bugreport].

--[[User:Whoopie|Whoopie]] 12:36, 16 March 2006 (CET)

I'm just working on changes in pam_bioapi which makes gui callbacks from gnome-screensaver possible. But first I have to debug BioAPI error #194d after hibernation because gnome-screensaver is one of the applications returning this error.

--[[User:Nax|nax]] 23:59, 9 July 2006 (CEST)

== No sources for bioapi 1.2.3 ==

There doesn't seem to be any sources available for the recommended Debian package bioapi-1.2.3. That's rather distressing since this is security-related software. A google search doesn't seem to be turning up anything, either. Anybody have a lead on where to find sources?

--[[User:TedTso|TedTso]] 7:47, 29 Apri 2006 (EDT)

== Strange issue on GDM login ==

I successfully have the fingerprint reader running. Everything is working nicely, except when I try to login with GDM for the first time. The login seems to work fine (the PAM_BIOAPI seems to return true) but GDM hangs then. This issue does not occur when I already logged in using password and logged out again or if I kill GDM when it hangs after the first attempt. Anyone an idea on this?

--[[User:Dotxp|dotxp]] 22:54, 2 May 2006 (CEST)

== Don't ask for finger scan when lid closed ==

When using an external CRT+keyboard+mouse with the LD lid closed, it's quiet annoying to have to reach over and open the lid in order to do a finger scan.
Any idea how to make PAM use the fingerprint reader when the lid is open, but skip it when the lid is closed?

--[[User:Thinker|Thinker]] 13:30, 7 May 2006 (CEST)

I edited my /etc/gdm/Init/Default script in a way, that it changes /etc/pam.d/common-auth depending on the lid state: When the lid is closed, the file is replaced by a version without the lines for the finterprint reader, and of course the opposite action when the lid is open.

--[[User:Aerials|Aerials]] 15:52, 9 July 2006 (CEST)
----

== Unable to initialize Bioapi framework, BioAPI error #:3 ==

I see some other discussion on this page about the dreaded "Unable to initialize Bioapi framework, BioAPI error #:3" error, but the only solution i can see seems really complicated -- adding users to groups when they log in, etc. Is that really the simplest way to make xscreensaver work? I'm the only user of my laptop -- the only account who will ever log in, the only fingerprint in the database, the only person who will ever run xscreensaver. Is there some quick easy way to make xscreensaver unlock when i swipe my finger?

-- [[User:Mike Schiraldi|Mike Schiraldi]] 19:52, 16 May 2006 (CEST)

== Security level ==

[http://www.upek.com/support/pdf/BioAPI_PerfectMatchBSP1.7.pdf UPEK PerfectMatch Algorithm]
According to this link, highest security level is 0 which is opposite to 5 mentioned in the article. What is correct?

Update: Well,TFMESS_BSP_LIN.pdf, i downloaded somewhere stated 5 as highest security level. So, ?

== How good is it? ==

How strong is the security that results? Is it actually as good as, say, a 10-character password, or is it the sort of thing you can fool
with some gelatin and a used glass? My inclination is not to trust it - but perhaps someone more knowledgeable would care to comment?
-- [[User:RichardNeill|RichardNeill]] 16:58, 25 July 2006 (CEST)

== Patch for new versions of xdm ==

I was having some trouble getting the xdm patch to work using the version of xdm in Debian unstable (1.0.5). Turns out that xdm now checks for blank username and doesn't even bother to call pam. Here's an updated version of the patch that works for me: [http://www.ugcs.caltech.edu/~q/code/xdm_bio-1.0.5.patch]

[[User:Virtualphtn|Virtualphtn]] 02:40, 16 September 2006 (CEST)

== Using instructions with OpenSuSE 10.1 ==

Now, as OpenSuSE has the problem with the gcc4 I followed the (by the way not very detailed) instructions about patching it. I've done the first patch before installing the BioApi($ wget http://upir.cz/linux/patches/bioapi-1.2.2-gcc4.patch
$ patch -p1 < bioapi-1.2.2-gcc4.patch) but it didn't work(dal_classes.h:460: error: extra qualification 'DAL_DATABASE_INFO_LIST::' on member 'GetDBNamesAndParameters')
Can somebody help me?
--[[User:SQLMosquito|SQLMosquito]] 19:53, 29 September 2006 (CEST)

I've been having the same problem for quite a while. Though when using the script found here http://www.cryptosecurity.net/Suse_T60_DRAFT.htm (based on the thinkwikiscript) things worked just fine. Don't ask me why, I really tried everything I know to be able to build it by myself. Anyway, it works good now.
--[[User:Stooofer|Stooofer]] 00:12, 8 January 2007 (CET)

== 64-bit architecture/OSS release ==

Hi,

To all ThinkWiki contributors: Thanks for all the help so far! I've made a lot of progress, but I have a show-stopper for the fingerprint reader. I'm not using x86 architecture! I am using the (new) Thinkpad X60, which just got upgraded to the Core 2 Duo with EM64T support a couple of weeks ago (along with a ton of other upgrades to the product, without changing its name...........!) So consequently I have Fedora Core 6 x86_64 installed. Works great, in general - standby, trackpoint, special buttons, nvram, and wifi supported (although not all out of the box; the ipw3945 driver had to be downloaded from atrpms.)

The distributed shared library provided by the vendor doesn't link against any 64-bit programs, because it's a 32-bit library. Of course, my desktop manager, PAM, etc. are all 64-bit. Without "downgrading" to a 32-bit distro, is there any way to either hack around this, or to bring up Pavel Machek's open-source enrollment program (thinkfinger) up to the vendor's driver's level of integration with BioAPI? Sounds like some development work, but I'm willing to help any way I can!

There should be a way to get this moving - either using a wrapper a la nspluginwrapper to enable an interface to the 32-bit driver on another architecture, or building upwards from Pavel's small test program.

Thanks!

Sean

== Alternative ThinkFinger "Driver" ==

The thinkfinger Project http://thinkfinger.sf.net is a GPL library with a own pam module.

It works...
It works with all pam application.
(dont try to display a own gui window).
It works without the bioapi.
wow! this is so easy to set up and just works!

Talk:How to enable integrated fingerprint reader with BioAPI

2006-11-24T13:42:42Z

Samoht: /* 'gksudo' Doesn't show biopam finger swipe prompt... */

== Removing the GUI Prompt ==
For all of you that have had the oppertunity to see the fingerprint image, I think we can all agree that this needs to be changed at ounce. A couple of ideas come to mind, first is to trick bioapi to think that X is not running, and secound is to figure out where the images are being pulled from and then edit them. The later would be nice, but I have been experimenting with strace for several hours and have came up with nothing. Any other ideas?

--[[User:Paul Strefling|Paul Strefling]] 18:42, 18 July 2006 (CEST)
----

== chmod 777 -R /usr/local/var/bioapi/ ==

Is the above necessary? I just made a debian package of xscreensaver with the patch applied, and when using the bioapi debian pacakge from [http://www.qrivy.net/~michael/temp/ Michael R. Crusoe's site] which has this directory put in /usr/var/bioapi I had not to change the permissions to world-writeable there. Write access to the logfile and usb device are necessary, but that directory works with 755 as well (even though it comes with 777 in Michael's package), and all files and subdirectories are 644/755 too.

--[[User:Spiney|spiney]] 00:08, 11 Nov 2005 (CET)
----

== Qt Compilation Success ==

Here it worked with qt ;)

--

I didn't get it to work anyway, but I'm curious about your Qt version(s) as it seemed to want Qt 3 when I was playing with it.

--[[User:Keegan|keegan]] 05:07, 24 Dec 2005 (CET)

== using absolute paths for commands ==

I don't know whether using absolute paths in the articles is a good idea, at least not for tools like {{cmd|lsusb|}} which are not established utilities (i.e. used for more than a decade or something ;)) and happen to be in different locations in different distributions. E.g. said {{cmd|lsusb|}} resides in {{path|/usr/sbin|}} on Debian systems.

--[[User:Spiney|spiney]] 16:45, 12 Nov 2005 (CET)
----

I'm using debian testing and it's in {{path|/usr/bin|}}. I agree that the confusion is bad; dropping the absolute paths and adding a general note about checking {{cmd|$PATH|}} in case of problems is probably good.

--[[User:keegan|keegan]]

== BioAPI error #3 ==

Its kind of strage it used to work with everythig (kdm,console,lock,etc)
Now it only works with kdm. It allways gives back:

pam_bioapi[8113]: Unable to initialize Bioapi framework, BioAPI error #:3.

Even when I set the right permissions on /proc/bus/usb.

I am able to run the Sample program as normal user after setting the permissions, but when I change within a user session by su I amnot able to run the Sample program a also get an error Code #3.

From an other terminal (alt+strg+Fx) I am able to run the Sample program but at the login I still get the error #3.

I cant remember to have changed anything an d bevor I was able to login in a console with my fingerprint now only kdm is working even kde lock-session
isnt working anymore.

Any suggestions ?

==Permission errors exclusive to xscreensaver==

I followed the instructions above and got everything working, including non-root programs like xscreensaver. However, the script to change usbfs permissions is finicky and fails to work with a lot of things like suspend/resume. Therefore, I switched to specifying <tt>devgid=108,devmode=0660,busgid=108,busmode=0770,listgid=108,listmode=0660</tt> as mount parameters for usbfs, where group 108 is a group I created and added my normal user to. This seems like a much better way of doing things, and it almost works. However, xscreensaver (using the newer patch) gives the familiar <tt>Unable to load BioAPI BSP with UUID of <nowiki>{</nowiki>5550454b-2054-464d-2f45-535320425350<nowiki>}</nowiki>, BioAPI error #194d.</tt> error in {{path|/var/log/auth.log|}}. I don't think this is a straightfoward permissions problem because
<ul>
<li>the permissions in {{path|/proc/bus/usb|}} are correct by inspection</li>
<li>I can write to the device file as my normal user</li>
<li>other programs like {{cmd|test_verify-pam_bioapi|}} and [http://pamtester.sourceforge.net/ {{cmd|pamtester|}}] work as my normal user</li>
<li>the weirdest one: xscreensaver works when the {{cmd|xscreensaver|}} daemon is launched from within {{cmd|strace|}}. It's still running as my normal user ({{cmd|strace|}} is not setuid root). I have absolutely no idea what would cause this. I thought it might be an environment issue, but the difference in environment between the {{cmd|strace|}} session and my normal session is trivial.</li>
</ul>

At this point I'm hoping it's something dumb, but I'm out of ideas. The {{cmd|xscreensaver|}} error is <tt>pam_authenticate (...) ==> 7 (Authentication failure)</tt>, for the record.

--[[User:keegan|keegan]]
----

I had the same problem and found that it was caused by the setuid permission on xscreensaver. After chmod'ing it to 755 and restarting xscreensaver, bioapi authentication worked.

--[[User:henning|henning]] 09:22, 8 Aug 2006 (CET)
----

Could you provide all the log lines between pam_start and pam_end when running {{cmd|xscreensaver -verbose|}}?

BTW, the idea with using the mount options for usbfs is very good, maybe you should add that info to the article page? I use the permission changing script without problems, also after resume, but the usbfs version is probably easier to set up, most people will be able to find {{path|/etc/fstab|}}.

--[[User:Spiney|spiney]] 10:12, 23 Dec 2005 (CET)
----
<pre>
xscreensaver: 20:56:01: alternative_pam: 1 -> pam service: xscreensaver-alternative
xscreensaver: 20:56:01: pam_start ("xscreensaver-alternative", "keegan", ...) ==> 0 (Success)
xscreensaver: 20:56:01: pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver: 20:56:01: PAM ECHO_OFF("Password: ") ==> password
xscreensaver: 20:56:03: pam_authenticate (...) ==> 7 (Authentication failure)
xscreensaver: 20:56:03: pam_end (...) ==> 0 (Success)
xscreensaver: 20:56:03: prompting for password.
xscreensaver: 20:56:03: 0: creating password dialog.
xscreensaver: 20:56:03: 0: mouse is at 442,412.
xscreensaver: 20:56:03: grabbing server...
xscreensaver: 20:56:03: 0: ungrabbing mouse (was 0x48).
xscreensaver: 20:56:03: 0: grabbing mouse on 0xe0002b... GrabSuccess.
xscreensaver: 20:56:03: ungrabbing server.
xscreensaver: 20:56:05: alternative_pam: 12582928 -> pam service: xscreensaver
xscreensaver: 20:56:05: pam_start ("xscreensaver", "keegan", ...) ==> 0 (Success)
xscreensaver: 20:56:05: pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver: 20:56:05: PAM ECHO_OFF("Password: ") ==> password
xscreensaver: 20:56:05: pam_authenticate (...) ==> 0 (Success)
xscreensaver: 20:56:05: pam_acct_mgmt (...) ==> 9 (Authentication service cannot retrieve authentication info.)
xscreensaver: 20:56:05: pam_setcred (...) ==> 0 (Success)
xscreensaver: 20:56:05: pam_end (...) ==> 0 (Success)
xscreensaver: 20:56:05: password correct.
</pre>
So we've got the first attempt with {{cmd|pam_bioapi|}}, which fails immediately (no sign of the GUI fingerprint prompt, nor a "silent" chance to swipe the finger as with xdm), then the fallback to {{cmd|pam_unix|}} which succeeds. Earlier I had xscreensaver set up to only try {{cmd|pam_bioapi|}}, with essentially the same result -- it gives up on pam entirely and does unix auth itself.

I'd really like to strace the pam module and see what it's attempting to do to {{path|/proc/bus/usb|}}, but as that actually fixes the problem I'm kinda at a loss. Maybe there's some kernel option to print debugging info for usbfs? I'd be all for changing the article to suggest using mount options in {{path|/etc/fstab|}}, if it weren't for this one weird bug. Has anyone else had the same problem?

-- [[User:keegan|keegan]]

Same here, I had the whole setup workin flawlessly (I really need to get that 'never-touch-a-running-system' mantra burnt into the back of my hands), but after a fresh install of the same distro (Ubuntu) and following the same procedure to get things working i get exactly this behaviour. Login works (now even with multifinger, although there are other issues with that), I can use test_verify-pam_bioapi as a user. and the stock xscreensaver works, albeit only after entering a bogus password first.
The patched xscreensaver works when run within a strace (Now that sucks) but fails otherwise. And as i said before, I had this working...

----
<pre>
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 13
fstat64(13, {st_mode=S_IFDIR|0755, st_size=140, ...}) = 0
fcntl64(13, F_SETFD, FD_CLOEXEC) = 0
getdents64(13, /* 7 entries */, 4096) = 168
getdents64(13, /* 0 entries */, 4096) = 0
close(13) = 0
open("/dev/bus/usb/003", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 13
fstat64(13, {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
fcntl64(13, F_SETFD, FD_CLOEXEC) = 0
getdents64(13, /* 4 entries */, 4096) = 96
open("/dev/bus/usb/003/002", O_RDWR) = -1 EACCES (Permission denied)
open("/dev/bus/usb/003/002", O_RDONLY) = 14
ioctl(14, USBDEVFS_CONNECTINFO, 0xafd5bd34) = -1 EPERM (Operation not permitted)
read(14, "\22\1\0\1\0\0\0\10\203\4\26 \1\0\1\2\0\1", 18) = 18
read(14, "\t\2\'\0\1\1\0\240", 8) = 8
read(14, "2\t\4\0\0\3\377\0\0\0\7\5\201\2@\0\0\7\5\2\2@\0\0\7\5\203"..., 31) = 31
close(14) = 0
</pre>

Here is all the excitement from the strace on xscreensaver. As I originally thought, you cannot get away with just playing with the proc entries :P You also need to deal with the counterpart in /dev. We can wrap up all the permissions issues with a single UDEV rule:

<pre>
# fingerprint fun
BUS=="usb", DRIVER=="usb", SYSFS{product}=="Biometric Coprocessor", GROUP="bioapi", SYMLINK="misc/fingerprint", RUN+="/bin/sh -c 'chgrp bioapi /proc/$RESULT; chmod g+rw /proc/$RESULT'"
</pre>

I created a 'bioapi' group and configured pam to add groups to anyone logging in ''locally''. Now all you need to do is amend the pam configuraion files below. We use 'wdm', but of course its as applicable for all those resource hungry touchy-feely gdm/kdm folk out there too ;)

/etc/security/group.conf
<pre>
# local group settings
login; tty*; *; al0000-2400; audio,floppy,video,cdrom,nvram,plugdev,bioapi
wdm; :*; *; al0000-2400; audio,floppy,video,cdrom,nvram,plugdev,bioapi
</pre>

/etc/pam.d/login
<pre>
[snipped]

# group *has* to go here
auth optional pam_group.so

# fingerprint action
auth sufficient /usr/local/lib/security/pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi1.10/pam/

# Standard Un*x authentication.
@include common-auth

# This allows certain extra groups to be granted to a user
# based on things like time of day, tty, service, and user.
# Please edit /etc/security/group.conf to fit your needs
# (Replaces the `CONSOLE_GROUPS' option in login.defs)
#auth optional pam_group.so

[snipped]
</pre>

/etc/pam.d/wdm
<pre>
#%PAM-1.0
auth required pam_nologin.so
auth required pam_env.so

# local tweak
auth optional pam_group.so

# fingerprint action
auth sufficient /usr/local/lib/security/pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi1.10/pam/

@include common-auth
@include common-account
@include common-session
</pre>

'''N.B.''' as with all pam related things, the order is important

-- [[User:Jim diGriz|Jim diGriz]]
----

==Driver Expiring!!!==
Don't anyone notice that both betas of the UPEK driver is expiring in
about a month in the new year, Jan 1st 2006? They really mean it!
I set my computer date to next year and get a message "the driver has expired" when using fingerprint reader! This is a grave threat to our computer lifestyle, i.e. for those of us who got it working and use it
daily:)
Is there any workaround other than setting the date back a year when
new year come and wait for new driver? Is there a way to figure out where exactly in the driver it checked the date and how? The must have set it
somewhere in file libtfmessbsp.so, but it is binary and I can't figure out how to Reverse Engineer it.

---Jiang

Yes, the beta driver will expire. The final version (which is due REALLY soon now) will not.

Sumedha

Any news? Just 9 days left to expiry. --[[User:Thinker|Thinker]] 21:36, 22 Dec 2005 (CET)

The final is out, get it at [http://www.upek.com/support/dl_linux_bsp.asp UPEK's download page]. And how does one edit the industry watch section of the main page?

--[[User:Spiney|spiney]] 21:39, 22 Dec 2005 (CET)

Ah, great! Both the article page and the driver page it points to are out of date... For the news, just follow the "[[ThinkWiki:News|News]]" link in the main page.

--[[User:Thinker|Thinker]] 21:44, 22 Dec 2005 (CET)

As this is now very soon I've updated the article page to link to the final driver, which is better in a few ways anyway. This is unless anyone minds (are there any unresolved issues with the final that don't exist in the betas?).

--[[User:Keegan|keegan]] 05:06, 24 Dec 2005 (CET)

== Updated xscreensaver patch ==

I've tried to address some usability issues with the old patch, e.g. that it calls the PAM bioapi module twice before falling back to the normal authentication methods. It can be found on my [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_fingerprint_reader Fingerprint Reader] page, feedback is very welcome.

--[[User:Spiney|spiney]] 20:36, 22 Dec 2005 (CET)
----

== Fingerprint or password ==

Is there any way to have PAM accept either a password or a finger swipe, right away? Sometimes one is more convenient, sometimes the other, so and it's a lot of trouble to wait for the UPEK scanner prompt and then cancel it in order to reach the password entry.

--[[User:Thinker|Thinker]] 19:27, 24 Dec 2005 (CET)

== KDE screensaver ==

If you get the following in {{path|/var/log/secure}} when you try to unlock the KDE screensaver, it means you forgot to set the USB device permissions.
localhost pam_bioapi[24981]: Unable to load BioAPI BSP with UUID of {5550454b-2054-464d-2f45-535320425350}, BioAPI error #194d.

--[[User:Thinker|Thinker]] 21:21, 24 Dec 2005 (CET)
----

== fingerprint reader in action. ==

small video with fingerprint reader in action with login: http://chao.ch/tmp/mov01302.mpg

--[[User:62.202.35.30|62.202.35.30]] 17:57, 29 Dec 2005 (CET)

==A little feedback...==
...for all the editors of this article:

"[[How to enable the fingerprint reader]] over at ThinkWiki.org is some real exhaustive documentation for getting the fingerprint scanner working on the ThinkPads. There is also a troubleshooting section towards the end that might be very useful to anyone messing around with it.

Thanks to those responsible for taking the time to write up this excellent guide."

Those thanks come from [http://linuxbiometrics.com/modules/news/ LinuxBiometrics.com]

[[User:Wyrfel|Wyrfel]] 01:24, 9 Jan 2006 (CET)
----

==pam_bioapi.so is not linked to libbioapi100.so==
I downloaded the pam_bioapi package and patched the file by following the wiki. However, I got the following result:

~/soft/thinkpad/pam_bioapi-0.2.1/libpam_bioapi/.libs$ ls -la
total 48
drwxr-xr-x 2 louis users 248 2006-01-12 01:18 ./
drwxr-xr-x 4 louis users 312 2006-01-12 01:18 ../
lrwxrwxrwx 1 louis users 16 2006-01-12 01:18 pam_bioapi.la -> ../pam_bioapi.la
-rw-r--r-- 1 louis users 824 2006-01-12 01:18 pam_bioapi.lai
-rw-r--r-- 1 louis users 19716 2006-01-12 01:18 pam_bioapi.o
lrwxrwxrwx 1 louis users 19 2006-01-12 01:18 pam_bioapi.so -> pam_bioapi.so.0.0.0*
lrwxrwxrwx 1 louis users 19 2006-01-12 01:18 pam_bioapi.so.0 -> pam_bioapi.so.0.0.0*
-rwxr-xr-x 1 louis users 21789 2006-01-12 01:18 pam_bioapi.so.0.0.0*

~/soft/thinkpad/pam_bioapi-0.2.1/libpam_bioapi/.libs$ ldd pam_bioapi.so
linux-gate.so.1 => (0xffffe000)
libc.so.6 => /lib/tls/libc.so.6 (0x40025000)
/lib/ld-linux.so.2 (0x80000000)
~/soft/thinkpad/pam_bioapi-0.2.1/libpam_bioapi/.libs$

pam_bioapi.so is NOT linked to libbioapi100.so. The latter is in the ld path:

~/soft/thinkpad/pam_bioapi-0.2.1/libpam_bioapi/.libs$ ldconfig -p |grep bioapi
libtfmessbsp.so (libc6) => /opt/bioapi/lib/libtfmessbsp.so
libpwbsp.so.0 (libc6) => /opt/bioapi/lib/libpwbsp.so.0
libpwbsp.so (libc6) => /opt/bioapi/lib/libpwbsp.so
libmds_util.so.0 (libc6) => /opt/bioapi/lib/libmds_util.so.0
libmds_util.so (libc6) => /opt/bioapi/lib/libmds_util.so
libbioapi100.so.0 (libc6) => /opt/bioapi/lib/libbioapi100.so.0
libbioapi100.so (libc6) => /opt/bioapi/lib/libbioapi100.so
libbioapi_mds300.so.0 (libc6) => /opt/bioapi/lib/libbioapi_mds300.so.0
libbioapi_mds300.so (libc6) => /opt/bioapi/lib/libbioapi_mds300.so
libbioapi_dummy100.so.0 (libc6) => /opt/bioapi/lib/libbioapi_dummy100.so.0
libbioapi_dummy100.so (libc6) => /opt/bioapi/lib/libbioapi_dummy100.so

and the Sample program also works allowing me to enroll and test a fingerprint.

My system is SuSE 10 with the kernel of 2.6.13-15. Any ideas?

Thanks.

--[[User:Tyne|Tyne]] 09:51, 12 Jan 2006 (CET)

==xscreensaver 4.23+fingerprint.patch causes xscreensaver-gl to crash kernel==

I've gotten bioapi and 'Sample' to allow me to enroll my fingerprint, and I've also experienced the 'two logon' issue.

I compiled xscreensaver 4.23 (though it seemed that apt came with 4.24) and applied the patch. My goal was to have the fingerprint prompt come up and to see the "bad image" of the fingerprint scan.

The first time I did this, xscreensaver-gl took a dump and was causing kernel crashes. So I went and got the newest xscreensaver source and patches, and applied the bioapi patch to those. It worked (meaning it didnt crash the kernel anymore ;b )

It would seem that there is a /etc/pam.d/xscreensaver, so I commented everything out of that except the bioapi line.

Locking xscreensaver, then attempting to unlock didnt show me any fingerprint requirements, and my password didnt work.

I'm wondering if theres something that was left out of the xscreensaver howto? or if theres anyone out there who's gotten the xscreensaver portion of this to work, who would be willing to help me out :)

--[[User:Viss|Viss]] 11:15am, 5 Feb 2006 (PST)

== gdm hangs on kde logout ==

Hi.

I am using a Thinkpad t43, installed with gentoo.
I run gdm as the login manager, with kde 3.4 and enlightenment dr16 as the window manager.

I followed the steps in the wiki, and the biometric scanner is now working fine, appart from the fact that when I close/end the session I just get a blank screen, in place of the gdm login screen.

Disabling the biometrics (by setting the pam.d file back to their originals), the session ends fine. I do this for a few times, and then set the biometrics back again, and it work fine for a few logouts, and then back to the blank screen again.

I can do ctrl+shift+f1 to get to a console window and from there I can issue a shutdown.
Although this works ok, it is a bit of a pain.

Any ideas ?

== 'gksudo' Doesn't show biopam finger swipe prompt... ==

Hey all,

First off... this is an excellent how-to! I have no real interest in using fingerprint scanner with xscreensaver, but it was up and working with everything else on my system pretty much effortlessly.

I'm running Ubuntu Breezy Badger 5.10 on an IBM T43p (2678) and have run into two oddities:
1) /etc/pam.d/xscreensaver - as it is initially configured, if you have an xscreensaver session set to require password (or xlock with screensaver) then you get prompted for the normal text-password entry and then will be prompted to swipe your finger... This is easily fixed by commenting out the '@include common-auth' line in /etc/pam.d/xscreensaver and adding the line 'auth required pam_unix.so nullok_secure'. After that change it only prompts for the text-password entry challenge.

2) gksudo - This is more of a pain... I can use the fingerprint scanner with gksudo, but gksudo doesn't prompt with the (ugly-but-functional) finger swipe dialog the way that gdm does during login or xscreensaver does when configured as mentioned above (pre-fix). So, if I start a Gnome app launcher that is prepended with gksudo, nothing appears to happen until I swipe my finger and then the app gets launched. That's cool and all, but there are times (esp. when multi-tasking) when I forget to swipe and then go "what happened to xxxxx? oh yeah..."

Anyway... does anyone have an idea of what I can do to get the dialog to appear?

thanx

--[[User:JELaVallee|JELaVallee]] 05:56, 20 February 2006 (CET)

The gksudo problem is a restriction from the X server. It doesn't allow to grab the display for other users than the logged-in one. And the pam_bioapi is invoked as root.

--[[User:Whoopie|Whoopie]] 13:10, 20 February 2006 (CET)

That makes sense... so, now I have to wonder, is there a patchable work-around like the xscreensaver one that could allow for this to work? Where should I research such? gksu's project or is this more an issue at the X11-level?

--[[User:JELaVallee|JELaVallee]] 19:38, 27 February 2006 (CET)

I got it working. Grab out the newer pam-bioapi from CVS (http://savannah.nongnu.org/cvs/?group=pam-bioapi). This version supports "multi-finger" when using the sqlite3 database. And it supports defining the used display.
Change your line in your /etc/pam.d/ files like this:

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/bioshadow.db :0

--[[User:Whoopie|Whoopie]] 14:27, 1 March 2006 (CET)

Very cool... Did you run into any issues rebuilding/installing this? I'll give it a shot this evening... THANKS!

--[[User:JELaVallee|JELaVallee]] 21:07, 1 March 2006 (CET)

Invoke 'xhost +local:' should be able to let gksudo work. Or just blindly sweap the finger. ;)

--[[User:YChao|YChao]] 21:25, 7 March 2006 (CET)

Where do I have to put 'xhost +local:'?

== Multifinger ==

Wow, theres a new version of pam_bioapi which supports multifinger enrollment and user identification.
I'll break my system with that this evening :)

Yes, but I'm searching the patch for xdm. The download page from Josef Hajas (http://nax.hn.org/pub/bioapi/) is down. Does anybody have it?

Update: The patch can be found here: http://www.qrivy.net/~michael/blua/xdm_bio.patch

--[[User:Whoopie|Whoopie]] 17:43, 1 March 2006 (CET)

Tried the newest pam-bioapi from CVS (http://savannah.nongnu.org/cvs/?group=pam-bioapi) on FC3. Failed on enrolling fingerprints: ({{path|/var/log/secure|}})

<code>Mar 9 15:30:40 localhost pam_bioapi[32407]: Can't open database: library routine called out of
sequence</code>

Could anyone help?

--[[User:Ychao|Ychao]] 00:38, 10 March 2006 (CET)

I don't know how to solve it. It seems to be a problem with sqlite3. Which version do you use? Under Ubuntu Breezy, it's 3.2.1.

--[[User:Whoopie|Whoopie]] 12:27, 10 March 2006 (CET)

Did anybody tried multifinger with BioAPI? I am interested in multifinger at all, not only PAM.

Updated:

succesfully installed pam_bioapi with multifinger support, some info:

use: <code>auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/bioshadow.db :0</code> in pam.d, the bioshadow column is path to bioapi sqlite database.

if authentication doesn't work, edit /etc/syslog.conf and write line *.alert /var/log/syslog, so you see pam_bioapi messages in /var/log/syslog
most common error is missing biodata table, newest pam_bioapi version should create it automatically, but if it doesn't, go to /etc/bioapi/pam/ and run command <code>sqlite3 bioshadow.db</code>, then insert this:

<code>CREATE TABLE biodata (id INTEGER PRIMARY KEY,uid INTEGER,uuid TEXT,header BLOB,data BLOB,signature BLOB,type INTEGER,other BLOB);</code>

you must then enroll at least one fingerprint to the database, do it using test_enroll-pam_bioapi from pam_bioapi distribution. note that you must have root user enrolled in order to use <code>su</code> command.

--[[User:MeBa|MeBa]] 16:58, 22 March 2006 (CET)

== GNOME Screensaver support ==

Did anybody try to port the xscreensaver patch to gnome-screensaver? Since Ubuntu Dapper will be shiped with it, it would be nice to have it working then with the fingerprint reader.

Update: Initial support can be found in gnome-screensaver CVS. See [http://bugzilla.gnome.org/show_bug.cgi?id=338635 bugreport].

--[[User:Whoopie|Whoopie]] 12:36, 16 March 2006 (CET)

I'm just working on changes in pam_bioapi which makes gui callbacks from gnome-screensaver possible. But first I have to debug BioAPI error #194d after hibernation because gnome-screensaver is one of the applications returning this error.

--[[User:Nax|nax]] 23:59, 9 July 2006 (CEST)

== No sources for bioapi 1.2.3 ==

There doesn't seem to be any sources available for the recommended Debian package bioapi-1.2.3. That's rather distressing since this is security-related software. A google search doesn't seem to be turning up anything, either. Anybody have a lead on where to find sources?

--[[User:TedTso|TedTso]] 7:47, 29 Apri 2006 (EDT)

== Strange issue on GDM login ==

I successfully have the fingerprint reader running. Everything is working nicely, except when I try to login with GDM for the first time. The login seems to work fine (the PAM_BIOAPI seems to return true) but GDM hangs then. This issue does not occur when I already logged in using password and logged out again or if I kill GDM when it hangs after the first attempt. Anyone an idea on this?

--[[User:Dotxp|dotxp]] 22:54, 2 May 2006 (CEST)

== Don't ask for finger scan when lid closed ==

When using an external CRT+keyboard+mouse with the LD lid closed, it's quiet annoying to have to reach over and open the lid in order to do a finger scan.
Any idea how to make PAM use the fingerprint reader when the lid is open, but skip it when the lid is closed?

--[[User:Thinker|Thinker]] 13:30, 7 May 2006 (CEST)

I edited my /etc/gdm/Init/Default script in a way, that it changes /etc/pam.d/common-auth depending on the lid state: When the lid is closed, the file is replaced by a version without the lines for the finterprint reader, and of course the opposite action when the lid is open.

--[[User:Aerials|Aerials]] 15:52, 9 July 2006 (CEST)
----

== Unable to initialize Bioapi framework, BioAPI error #:3 ==

I see some other discussion on this page about the dreaded "Unable to initialize Bioapi framework, BioAPI error #:3" error, but the only solution i can see seems really complicated -- adding users to groups when they log in, etc. Is that really the simplest way to make xscreensaver work? I'm the only user of my laptop -- the only account who will ever log in, the only fingerprint in the database, the only person who will ever run xscreensaver. Is there some quick easy way to make xscreensaver unlock when i swipe my finger?

-- [[User:Mike Schiraldi|Mike Schiraldi]] 19:52, 16 May 2006 (CEST)

== Security level ==

[http://www.upek.com/support/pdf/BioAPI_PerfectMatchBSP1.7.pdf UPEK PerfectMatch Algorithm]
According to this link, highest security level is 0 which is opposite to 5 mentioned in the article. What is correct?

Update: Well,TFMESS_BSP_LIN.pdf, i downloaded somewhere stated 5 as highest security level. So, ?

== How good is it? ==

How strong is the security that results? Is it actually as good as, say, a 10-character password, or is it the sort of thing you can fool
with some gelatin and a used glass? My inclination is not to trust it - but perhaps someone more knowledgeable would care to comment?
-- [[User:RichardNeill|RichardNeill]] 16:58, 25 July 2006 (CEST)

== Patch for new versions of xdm ==

I was having some trouble getting the xdm patch to work using the version of xdm in Debian unstable (1.0.5). Turns out that xdm now checks for blank username and doesn't even bother to call pam. Here's an updated version of the patch that works for me: [http://www.ugcs.caltech.edu/~q/code/xdm_bio-1.0.5.patch]

[[User:Virtualphtn|Virtualphtn]] 02:40, 16 September 2006 (CEST)

== Using instructions with OpenSuSE 10.1 ==

Now, as OpenSuSE has the problem with the gcc4 I followed the (by the way not very detailed) instructions about patching it. I've done the first patch before installing the BioApi($ wget http://upir.cz/linux/patches/bioapi-1.2.2-gcc4.patch
$ patch -p1 < bioapi-1.2.2-gcc4.patch) but it didn't work(dal_classes.h:460: error: extra qualification 'DAL_DATABASE_INFO_LIST::' on member 'GetDBNamesAndParameters')
Can somebody help me?
--[[User:SQLMosquito|SQLMosquito]] 19:53, 29 September 2006 (CEST)

== 64-bit architecture/OSS release ==

Hi,

To all ThinkWiki contributors: Thanks for all the help so far! I've made a lot of progress, but I have a show-stopper for the fingerprint reader. I'm not using x86 architecture! I am using the (new) Thinkpad X60, which just got upgraded to the Core 2 Duo with EM64T support a couple of weeks ago (along with a ton of other upgrades to the product, without changing its name...........!) So consequently I have Fedora Core 6 x86_64 installed. Works great, in general - standby, trackpoint, special buttons, nvram, and wifi supported (although not all out of the box; the ipw3945 driver had to be downloaded from atrpms.)

The distributed shared library provided by the vendor doesn't link against any 64-bit programs, because it's a 32-bit library. Of course, my desktop manager, PAM, etc. are all 64-bit. Without "downgrading" to a 32-bit distro, is there any way to either hack around this, or to bring up Pavel Machek's open-source enrollment program (thinkfinger) up to the vendor's driver's level of integration with BioAPI? Sounds like some development work, but I'm willing to help any way I can!

There should be a way to get this moving - either using a wrapper a la nspluginwrapper to enable an interface to the 32-bit driver on another architecture, or building upwards from Pavel's small test program.

Thanks!

Sean