thinkfinger

ThinkFinger is a driver for the UPEK/SGS Thomson Microelectronics fingerprint reader (USB ID 0483:2016).
download from driver from http://sourceforge.net/projects/thinkfinger/
install libpam0g-dev from repo.

#cd /thinkfinger-0.3
#./configure
no libusb found.....then install libusb-dev package
#./configure
#make
#make install

#tf-tool --acquire

ThinkFinger 0.2.2 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig




Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

# tf-tool --verify

ThinkFinger 0.2.2 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.



Link Used..
http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
https://wiki.ubuntu.com/ThinkFinger

Understanding /proc/cpuinfo

Understanding /proc/cpuinfo
Example:

$ uname -r
2.6.22-3-486

How many physical processors are there?
$ grep 'physical id' /proc/cpuinfo | sort | uniq | wc -l
2

How many virtual processors are there?
$ grep ^processor /proc/cpuinfo | wc -l
4

Are the processors dual-core (or multi-core)?
$ grep 'cpu cores' /proc/cpuinfo
cpu cores : 2
cpu cores : 2
cpu cores : 2
cpu cores : 2

"2" indicates the two physical processors are dual-core, resulting in 4 virtual processors.

If "1" was returned, the two physical processors are single-core. If the processors are single-core, and the number of virtual processors is greater than the number of physical processors, the CPUs are using hyper-threading. Hyper-threading is supported if ht is present in the CPU flags and you are using an SMP kernel.

Are the processors 64-bit?
A 64-bit processor will have lm ("long mode") in the flags section of cpuinfo. A 32-bit processor will not.

e.g.,

flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc

What do the CPU flags mean?
The CPU flags are briefly described in the kernel header file cpufeature.h.

how to dump content of BIOS in Linux???

run following command as a ROOT
#dd if=/dev/mem bs=1k skip=768 count=256 2>/dev/null | strings -n 8

xrandr to change display resolution setting

xrandr --newmode 1600x1200 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
xrandr --addmode default 1600x1200
xrandr --output default --mode 1600x1200

replace 'default' with proper output (xrandr -command should show it. It can be VGA, VGA1, VGA2, LVDS etc...)

if above method fails, you may need to add Virtual 2048 2048 to your xorg.conf. example:

Section "Screen"
Subsection "Display"
Virtual 2048 2048
EndSubsection
EndSection

then restart your x and try xrandr commands again.

XDMCP for remote login

Here's how to enable xdmcp in the terminal server client (tsclient/rdesktop) for Ubuntu (tested under dapper). By default the terminal server client program has xdmcp disabled. To fix this just install xnest:
# apt-get install xnest

Alternatively, if you are looking to enable xdmcp in BOSS:

1. Go to System -> Administration -> Login window (or run gdmsetup).
2. Under the Remote tab change Style to same as local. The different choices just change what login screen the user sees.
3. You will need to restart GDM which will kill your X session.
# kill -HUP `cat /var/run/gdm.pid`

Or if you prefer to edit the files by hand:

1. Edit /etc/gdm/gdm.conf (make sure there is no overriding settings in gdm.conf-custom)
2. Uncomment RemoteGreeter in the daemon section.
3. Under the xdmcp section, change Enable to true.
4. Do step 3 above to restart gdm.

also change setting @security..

logitech webcam

uninstall spca5xx module and then install gspca compiled driver pkg.

PCI cannot allocate resource region one of device 0000:00:14.0

problem in installation of BOSS linux on AMD athlon X2--solution

system was getting hang while installation...

add extra kernel parameter at installation time , noapic nolapic acpi=off irqpoll
and it will install properly.

(tested with extra param like hda=noprobe dma=none io=parallel port addr(0x378/0x278/0x3bc) irq=any in 5-7...but useless try)

Mounting LVM

Mounting an LVM may seem a bit intimidating, it's not. In reality, despite the length of this entry, you will only be running a handful of commands, and most of those just to get the needed information. Do not despair, this will be as painless as possible. All of these commands will be run as root from a terminal. Please also remember that your volume names may differ from the guide, please make sure to adjust accordingly.

# pvs

This should give you an output similar to

sabayonx86 sabayonuser # pvs

PV VG Fmt Attr PSize PFree
/dev/sda2 VolGroup00 lvm2 a- 7.88G 32.00M

If we look closely we can see that /dev/sda2 holds a lvm that is 7.88 gig in size. In this case, thats the one we want, as it is the only one.

So now we want to see what is actually in that lvm

# lvdisplay /dev/VolGroup00

sabayonx86 sabayonuser # lvdisplay /dev/VolGroup00


--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID SWp2V0-1xPU-0tOP-UnPs-snxF-THUl-pZMKb2
LV Write Access read/write
LV Status available
# open 0
LV Size 6.88 GB
Current LE 220
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 251:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID MGBeJP-ohrX-KLju-5V78-iJOi-pP3w-huaOmC
LV Write Access read/write
LV Status available
# open 0
LV Size 992.00 MB
Current LE 31
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 251:1

We are looking for two things out of that list. LV name and LV Size. We have one that is 6.88 GB and one that is 992 MB. We can safely assume that the smaller of the two is /swap so the larger must be our real filesystem. That one is named /dev/VolGroup00/LogVol00.

So now we have all the information that we need. We need only to make a mount point and actually mount the volume.

# cd /mnt
# mkdir lvm
# vgscan --mknodes
# lvchange -ay /dev/VolGroup00/LogVol00
# mount /dev/VolGroup00/LogVol00 /mnt/lvm

If all went well then can now get inside and look around, make changes, chroot in, or whatever caused us to want to mount the LVM in the first place.