Installing Debian Lenny on a ThinkPad T60 - Revision history

Jdthood at 15:49, 5 August 2011

2011-08-05T15:49:49Z

Jdthood: /* Fingerprint reader */

2011-08-05T15:48:17Z

‎Fingerprint reader

Jdthood: /* Fingerprint reader */

2011-08-05T15:47:19Z

‎Fingerprint reader

Jdthood: /* Fingerprint reader */

2011-08-05T15:39:06Z

‎Fingerprint reader

BrigitteShopen: /* Before I begin */

2010-07-23T21:28:45Z

‎Before I begin

Tonko: /* Debian Lenny on a T60 6371-6NU */

2010-03-02T13:24:37Z

‎Debian Lenny on a T60 6371-6NU

Kevmitch: /* Debian Lenny on a T60 6371-6NU */

2008-09-16T06:52:59Z

‎Debian Lenny on a T60 6371-6NU

Kevmitch: /* automated sleep */

2008-02-24T06:08:36Z

‎automated sleep

Kevmitch: /* automated sleep */

2008-02-24T06:01:55Z

‎automated sleep

Kevmitch: /* sleep */

2008-02-24T06:01:15Z

‎sleep

@@ Line 457: / Line 457: @@
 Ok, admit it. This is the '''real''' reason you got a ThinkPad. Getting the [[Integrated_Fingerprint_Reader|integrated fingerprint reader]] working is surprisingly easy with the new open source [[How_to_enable_the_integrated_fingerprint_reader_with_ThinkFinger|thinkfinger]] driver. This is highly recommended over the binary only driver which much more difficult to install and less stable even leading xscreensaver to crash and expose the desktop without a provided fingerprint or password!
-If you didn't install it among the packages above, see the [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#Debian|relevant section]] of the howto.
+If you didn't install it among the packages above, see the [[How_to_enable_the_integrated_fingerprint_reader_with_ThinkFinger#Debian|relevant section]] of the howto.
 Once you have it installed, you must [[How_to_enable_the_integrated_fingerprint_reader_with_ThinkFinger#Configuring_PAM_to_use_ThinkFinger|instruct PAM to use it]] so that it will ask for your fingerprint when you login with gdm or at the command line (or any thing else that uses PAM). To make it brief and more Debian-specific, you want your <tt>/etc/pam.d/common-auth</tt> file's only uncommented lines to be
@@ Line 474: / Line 474: @@
 </pre>
-Now for the icing on the cake. If you have xscreensaver (>=5.0) or a sufficiently recent version of gnome-screensaver, you can [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver|use your fingerprint to unlock the screen]] as well.
+Now for the icing on the cake. If you have xscreensaver (>=5.0) or a sufficiently recent version of gnome-screensaver, you can [[How_to_enable_the_integrated_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver|use your fingerprint to unlock the screen]] as well.
 Update: See [[How to enable the integrated fingerprint reader]].

@@ Line 459: / Line 459: @@
 If you didn't install it among the packages above, see the [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#Debian|relevant section]] of the howto.
-Once you have it installed, you must [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#Configuring_PAM_to_use_ThinkFinger|instruct PAM to use it]] so that it will ask for your fingerprint when you login with gdm or at the command line (or any thing else that uses PAM). To make it brief and more Debian-specific, you want your <tt>/etc/pam.d/common-auth</tt> file's only uncommented lines to be
+Once you have it installed, you must [[How_to_enable_the_integrated_fingerprint_reader_with_ThinkFinger#Configuring_PAM_to_use_ThinkFinger|instruct PAM to use it]] so that it will ask for your fingerprint when you login with gdm or at the command line (or any thing else that uses PAM). To make it brief and more Debian-specific, you want your <tt>/etc/pam.d/common-auth</tt> file's only uncommented lines to be
 <pre>
 auth    sufficient      pam_thinkfinger.so

@@ Line 455: / Line 455: @@
 ==Fingerprint reader==
-Ok, admit it. This is the '''real''' reason you got a ThinkPad. Getting the [[Integrated_Fingerprint_Reader|integrated fingerprint reader]] working is surprisingly easy with the new open source [[How_to_enable_the_fingerprint_reader_with_ThinkFinger|thinkfinger]] driver. This is highly recommended over the binary only driver which much more difficult to install and less stable even leading xscreensaver to crash and expose the desktop without a provided fingerprint or password!
+Ok, admit it. This is the '''real''' reason you got a ThinkPad. Getting the [[Integrated_Fingerprint_Reader|integrated fingerprint reader]] working is surprisingly easy with the new open source [[How_to_enable_the_integrated_fingerprint_reader_with_ThinkFinger|thinkfinger]] driver. This is highly recommended over the binary only driver which much more difficult to install and less stable even leading xscreensaver to crash and expose the desktop without a provided fingerprint or password!
 If you didn't install it among the packages above, see the [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#Debian|relevant section]] of the howto.

@@ Line 455: / Line 455: @@
 ==Fingerprint reader==
-Ok, admit it. This is the '''real''' reason you got a thinkpad. Getting the [[Integrated_Fingerprint_Reader|fingerprint reader]] working is surprisingly easy with the new open source [[How_to_enable_the_fingerprint_reader_with_ThinkFinger|thinkfinger]] driver. This is highly recommended over the binary only driver which much more difficult to install and less stable even leading xscreensaver to crash and expose the desktop without a provided fingerprint or password!
+Ok, admit it. This is the '''real''' reason you got a ThinkPad. Getting the [[Integrated_Fingerprint_Reader|integrated fingerprint reader]] working is surprisingly easy with the new open source [[How_to_enable_the_fingerprint_reader_with_ThinkFinger|thinkfinger]] driver. This is highly recommended over the binary only driver which much more difficult to install and less stable even leading xscreensaver to crash and expose the desktop without a provided fingerprint or password!
 If you didn't install it among the packages above, see the [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#Debian|relevant section]] of the howto.
@@ Line 475: / Line 475: @@
 Now for the icing on the cake. If you have xscreensaver (>=5.0) or a sufficiently recent version of gnome-screensaver, you can [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver|use your fingerprint to unlock the screen]] as well.
 ==A few /etc configurations==

@@ Line 27: / Line 27: @@
 ==Before I begin==
-I remove as much of the crap ware as possible from windows. I burnt a bunch of the stuff in the SOFTWARE directory to DVD and deleted it. I managed to get the disk usage down to around 5GB or so. I'm sure I could do better, but I only want to spend so much time in windows. I keep however a few essential things like BIOS update and finger print management software. This later is as far as I know the only way to enrol finger prints in the bios for bootup fingerprint checking. I upgrade the bios in windows using the Lenovo utility. I want to have someone to hold responsible (other than myself) if my computer gets fried while flashing the bios. In the bios itself, I have the SATA controller set to AHCI. I've read quite a few people saying that they need to set it to "compatibility". Perhaps this is no longer an issue with newer kernels (>~2.6.18). I note that my kernel config has the <tt>SATA_AHCI</tt> option enabled (module should be fine as long as you use an initrd).
+I remove as much of the crap ware as possible from windows. I burnt a bunch of the stuff in the SOFTWARE directory to DVD and deleted it. I managed to get the disk usage down to around 5GB or so. I'm sure I could do better, but I only want to spend so much time in windows. I keep however a few essential things like BIOS update and finger print management software. This later is as far as I know the only way to [http://www.research-service.com/ paper writing service] enrol finger prints in the bios for bootup fingerprint checking. I upgrade the bios in windows using the Lenovo utility. I want to have someone to hold responsible (other than myself) if my computer gets fried while flashing the bios. In the bios itself, I have the SATA controller set to AHCI. I've read quite a few people saying that they need to set it to "compatibility". Perhaps this is no longer an issue with newer kernels (>~2.6.18). I note that my kernel config has the <tt>SATA_AHCI</tt> option enabled (module should be fine as long as you use an initrd).
 ==Installation==

@@ Line 17: / Line 17: @@
 |Audio    ||[[AD1981HD]] HD Audio 1.0 controller
 |-
-|Ethernet || [[Ethernet Controllers#Intel Gigabit (10/100/1000)|82573L Gigabit Ethernet Controller]]
+|Ethernet || [[Intel Gigabit Ethernet (10/100/1000)|82573L Gigabit Ethernet Controller]]
 |-
 |Optical  || [[UltraBay Slim Super Multi-Burner Drive|LG-Hitatchi HL-DT-ST DVDRAM GSA-4083N Dual Layer DVD+/-RW]]

@@ Line 21: / Line 21: @@
 |Optical  || [[UltraBay Slim Super Multi-Burner Drive|LG-Hitatchi HL-DT-ST DVDRAM GSA-4083N Dual Layer DVD+/-RW]]
 |-
-|Wireless || [[ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter| Atheros AR5418]] <-- big mistake! Go with [http://intellinuxwireless.org/ Intel].
+|Wireless || [[ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter| Atheros AR5418]].
 |-
 |Biometric || [[Integrated Fingerprint Reader|STMicroelectronics Fingerprint Reader]]

@@ Line 1,028: / Line 1,028: @@
 PARAMS="-u 180 -U 1800 -s /etc/acpi/sleep.sh -i 1 -i 12 -i 23"
 </pre>
-This tells sleepd to sleep after three minutes of inactivity while on battery(<tt>-u 180</tt>) and after half an hour of inactivity while on ac (<tt>-U 1800</tt>). I have defined "activity" as signals on irqs 1(keyboard), 12(mouse), and 23(usb mouse) (<tt>-i 1 -i 12 -i 23</tt>). 1 and 12 will be autodetected, but 23 may not be. You can use the <tt>xosview</tt> utility to discover when the various IRQ's are used. Finally sleepd itself doesn't actually know how to put the computer to sleep, so you have to supply it with the command to do so (<tt>-s /etc/acpi/sleep.sh</tt>). You could really put anything at all here.
+This tells sleepd to sleep after three minutes of inactivity while on battery(<tt>-u 180</tt>) and after half an hour of inactivity while on ac (<tt>-U 1800</tt>). I have defined "activity" as signals on irqs 1(keyboard), 12(mouse), and 23(usb mouse) (<tt>-i 1 -i 12 -i 23</tt>). 1 and 12 will be autodetected, but 23 may not be. You can see what uses the various interrupts by running the command <tt>cat /proc/interupts</tt>.You can also use the <tt>xosview</tt> utility to discover when the various IRQ's are used. Finally sleepd itself doesn't actually know how to put the computer to sleep, so you have to supply it with the command to do so (<tt>-s /etc/acpi/sleep.sh</tt>). You could really put anything at all here.
 You'll note however, that the above is a rather limited definition of "inactivity". Unfortunately, it's the best sleepd has to offer. Alas, none of the above mentioned background tasks that I want my computer to continue doing can be reliably mapped to the use of a particular IRQ. The next best thing then is to have our sleep command be a script that before putting the computer to sleep checks for a wider range of activity before actually going to sleep and aborts the sleep process if such activity is detected. This will reset the sleepd timer so that it must wait for an other interval of human inactivity before running the sleep/check script again.

@@ Line 1,037: / Line 1,037: @@
 #Network activity
 #Is sound playing?
-The first three can be checked using the <tt>sar</tt> utility included in the <tt>sysstat</tt> package, while the latter can be checked using teh <tt>rec</tt> utility included in the <tt>sox</tt> package. If you haven't already, install those packages. Sox is additionally going to <tt>need alsa support</tt>, so you could install that package, or just go ahead an install off of <tt>sox</tt> since its a handy program to have the full functionality of.
+The first three can be checked using the <tt>sar</tt> utility included in the <tt>sysstat</tt> package, while the latter can be checked using the <tt>rec</tt> utility included in the <tt>sox</tt> package. If you haven't already, install those packages. Sox is additionally going to <tt>need alsa support</tt>, so you could install that package, or just go ahead an install off of <tt>sox</tt> since its a handy program to have the full functionality of.
 <pre>
 aptitude install sysstat sox sox-fmt-all

@@ Line 1,015: / Line 1,015: @@
 The <tt>/etc/acpi/sleep.sh</tt> script wraps this command in some other niceties that may ease the transition in and out of sleep. In particular, it sources the scripts in <tt>/etc/acpi/suspend.d</tt> before sleeping and those in <tt>/etc/acpi/resume.d</tt> after awaking. If you feel uneasy about playing with these scripts yourself, you can alter some of their behaviour by editing the <tt>/etc/defaults/acpi-support</tt>.
-It would seem to make sense to bind the Fn-F4 key with the moon on it to the <tt>/etc/acpi/sleep.sh</tt> script. You could also set it up so that your laptop [[How_to_configure_acpid#Example:_go_to_sleep_on_lid_close|goes to sleep when you close the lid]]. I however prefer to have my laptop remain awake when the lid is closed so that it can continue background tasks such as ripping a cd, downloading a file, compiling a kernel, playing music, etc. I do however want to have some system of going to sleep during inactivity. For this I use the <tt>sleepd</tt> package which automatically puts the laptop to sleep after a period of inactivity. It does however requires some configuration to make it actually do this.
+It would seem to make sense to bind the Fn-F4 key with the moon on it to the <tt>/etc/acpi/sleep.sh</tt> script.
 First of all, if you haven't already installed it, do so