ThinkWiki - User contributions [en]

Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad X200

2010-08-23T22:36:36Z

Wbonx: /* =Automatic Brightness Controll */

[[Category: X200]]
Just brief info for now as I didn't have time to test all features yet. Please update if you have info on features marked as untested.

These notes also apply to the x200 tablet.

==Installation==

* Installing from desktop cd: Works fine with external usb drive

* Installing from USB stick: Works fine

* Installing from alternate cd: works fine with optical drive in [[X200 UltraBase]], just follow the steps

* Installing via wubi: works fine, except hibernate (normal for wubi installations)

* Updating from Jaunty: not tested

==Features support==

===Display===
* internal LCD: works fine
* external VGA: works fine
* external VGA via ultraBase: works fine
* DisplayPort via ultraBase: works fine

===Trackpoint===
The middle Scrollbutton won't work out-of-the-box, you can solve it with the help of the following Link: http://samiux.wordpress.com/2008/11/02/howto-lenovo-thinkpad-scroll-button-on-ubuntu-810/ 
I find the middle scrollbutton doesn't works very well for me by following these steps. 
The solution I currently use is to automatically execute the following commands: 
Quote:
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Y Axis" 8 4 5
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emugreatlation X Axis" 8 6 7

Another way to enable scrolling even if the instructions are a little older: http://www.thinkwiki.org/wiki/How_to_configure_the_TrackPoint#Scrolling. You can also try using gpointing-device-settings instructions as described at the top of the page but it's not persistent when you go into suspend-resume.

===WiFi===
*Intel 5100: works fine
After updating the kernel to 2.6.31-15-generic, the old kernel panic problem which used to happen in ubuntu 8.04 or older release, comes up again. I don't know whether this affects a fresh installation of karmic as I update the system immediately after I get a wired connection. 
I have the linux-backports-modules-wireless-karmic-generic package installed. Now it works fine.
*Intel 5300: works fine
*Intel 5350: works fine, kernel sees it as 5300

===Bluetooth===
generally works, but see https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/381913

===3G===
Works fine

===GPS===
Works, with the installation of http://sourceforge.net/apps/mediawiki/mbm/index.php?title=Main_Page#GPS_Control_.28mbm-gpsd.29

Note: mbm-gpsd is not running after wake from suspend

===Webcam===
Works perfectly.

===Sound===
* internal speakers: works fine, good volume
* headphones: works
* headphones via ultrabase: works fine
* internal mic: works fine, good sensitivity
* mic via ultrabase: not tested
* Volume up and down keys Work fine, Mute does not.
(Mute actually works but you won't find an OSD showing you it's on mute, unlike volume up and down. Additionally, plugging in your headphones even while on mute will let you hear sounds)

'''To get OSD working with Mute:''' (http://www.codefx.biz/2009/11/x200-mute-button)

Edit the file {{path|/etc/grub.d/10_linux}} and add {{bootparm|acpi_osi|Linux}} to the line with $GRUB_CMDLINE_LINUX_DEFAULT, so it will look like this:

"${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_EXTRA} ${GRUB_CMDLINE_LINUX_DEFAULT} acpi_osi=Linux" \

Then run '''{{cmduser|sudo update-grub}}'''

{{NOTE|Up to kernel 2.6.32 this seems to be the only way to fix the mute problem. However, this fix introduces new issues. Therefore, another, clean solution is being implemented as soon as kernel 2.6.33.}}

===Sensors===
mostly work, for HDD hddtemp is needed

===Fingerprint===
Doesn't work, see http://www.reactivated.net/fprint/wiki/Unsupported_devices#AuthenTec_AES2550_.26_AES2810

===HDAPS===
I couldn't make hdaps module to use [[Tp smapi]]. It seems module-assistant does not build patched version of hdaps module from tp-smapi-source package. 
Nevertheless hdaps seems to work fine with thinkpad_ec. After installing hdapsd edit /etc/default/hdapsd make sure START is set to "yes", DISK to "sda" and adjust SENSITIVITY (50 works ok for most people).

edit: use tp-smapi as in [http://elf.org/x200-tablet-accelerometer]

===Fan===
While the X200 is known for it's good cooling system, when running Ubuntu the fan seems to run constantly at around 3000rpm after it reached a certain threshold temperature. See the related bugreport on Launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/380303

For reasons of power consumption and noise reduction you might want to control the fans on your own using tp-fan, see [[ACPI_fan_control_script#ThinkPad_Fan_Control_GTK_GUI_tool]]. The Jaunty PPA seems to work fine on Karmic.

For me the following settings seem to work:
Check both boxes, set all sensors to 15% and the temperature threshold of all sensors to 25°C/68°F. With this settings the fan runs constantly with 2000rpm.

===Suspending===
Works fine as long as you don't suspend when docked.

edit: Suspend with dock works for me.

===Hibernating===
Works fine when hibernating when undocked. Not tested when docked.

===Docking and Undocking===
* Docking works ok. System even tries to switch automatically to saved external monitor display configuration and sometimes it even does the smart thing
* Before undocking you must always press "pre-undock" button on the left side of docking station and wait until green arrow allows you to proceed. Otherwise system will start to beep at you and it will probably get confused.
* Undocking and/or pressing "pre-undock" button switches automatically display to internal LCD only so you don't have to worry about it.
* Undocking doesn't umount automatically devices connected to docking station (usb pendrives, optical drive) so you must remember to do this manually. See https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/433682
* Suspending or hibernating when docked is not a good idea as system will probably get confused when resumed not docked also.

===MemoryCardReader===
Works

==Tablet==

===Screen===
* Screen rotation can be enabled with xrandr and https://launchpad.net/~thjaeger/+archive/tabletpc/+packages 
* TouchScreen requires recalibration as described https://help.ubuntu.com/community/X61T 
* Pen pressure sensitivity works
[[Category:Ubuntu_9.10]]

== Automatic Brightness Controll==
Possible using a script like the one at this link: 
http://gnome-look.org/content/show.php?content=128780&vote=good&tan=54635248 
Remember to install php5-cli and php5-gd, in the cfg file: pbr=1 (or lower if preferred a brighter screen) 
There is an error in the script.... some [] have to be added at the if statement (line 108 and the others) 
The scrpt has to be run with sudo privileges, the password in the cfg file doesn't work (8-2010).

Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad X200

2010-08-20T05:59:58Z

Wbonx:

[[Category: X200]]
Just brief info for now as I didn't have time to test all features yet. Please update if you have info on features marked as untested.

These notes also apply to the x200 tablet.

==Installation==

* Installing from desktop cd: Works fine with external usb drive

* Installing from USB stick: Works fine

* Installing from alternate cd: works fine with optical drive in [[X200 UltraBase]], just follow the steps

* Installing via wubi: works fine, except hibernate (normal for wubi installations)

* Updating from Jaunty: not tested

==Features support==

===Display===
* internal LCD: works fine
* external VGA: works fine
* external VGA via ultraBase: works fine
* DisplayPort via ultraBase: works fine

===Trackpoint===
The middle Scrollbutton won't work out-of-the-box, you can solve it with the help of the following Link: http://samiux.wordpress.com/2008/11/02/howto-lenovo-thinkpad-scroll-button-on-ubuntu-810/ 
I find the middle scrollbutton doesn't works very well for me by following these steps. 
The solution I currently use is to automatically execute the following commands: 
Quote:
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Y Axis" 8 4 5
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emugreatlation X Axis" 8 6 7

Another way to enable scrolling even if the instructions are a little older: http://www.thinkwiki.org/wiki/How_to_configure_the_TrackPoint#Scrolling. You can also try using gpointing-device-settings instructions as described at the top of the page but it's not persistent when you go into suspend-resume.

===WiFi===
*Intel 5100: works fine
After updating the kernel to 2.6.31-15-generic, the old kernel panic problem which used to happen in ubuntu 8.04 or older release, comes up again. I don't know whether this affects a fresh installation of karmic as I update the system immediately after I get a wired connection. 
I have the linux-backports-modules-wireless-karmic-generic package installed. Now it works fine.
*Intel 5300: works fine
*Intel 5350: works fine, kernel sees it as 5300

===Bluetooth===
generally works, but see https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/381913

===3G===
Works fine

===GPS===
Works, with the installation of http://sourceforge.net/apps/mediawiki/mbm/index.php?title=Main_Page#GPS_Control_.28mbm-gpsd.29

Note: mbm-gpsd is not running after wake from suspend

===Webcam===
Works perfectly.

===Sound===
* internal speakers: works fine, good volume
* headphones: works
* headphones via ultrabase: works fine
* internal mic: works fine, good sensitivity
* mic via ultrabase: not tested
* Volume up and down keys Work fine, Mute does not.
(Mute actually works but you won't find an OSD showing you it's on mute, unlike volume up and down. Additionally, plugging in your headphones even while on mute will let you hear sounds)

'''To get OSD working with Mute:''' (http://www.codefx.biz/2009/11/x200-mute-button)

Edit the file {{path|/etc/grub.d/10_linux}} and add {{bootparm|acpi_osi|Linux}} to the line with $GRUB_CMDLINE_LINUX_DEFAULT, so it will look like this:

"${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_EXTRA} ${GRUB_CMDLINE_LINUX_DEFAULT} acpi_osi=Linux" \

Then run '''{{cmduser|sudo update-grub}}'''

{{NOTE|Up to kernel 2.6.32 this seems to be the only way to fix the mute problem. However, this fix introduces new issues. Therefore, another, clean solution is being implemented as soon as kernel 2.6.33.}}

===Sensors===
mostly work, for HDD hddtemp is needed

===Fingerprint===
Doesn't work, see http://www.reactivated.net/fprint/wiki/Unsupported_devices#AuthenTec_AES2550_.26_AES2810

===HDAPS===
I couldn't make hdaps module to use [[Tp smapi]]. It seems module-assistant does not build patched version of hdaps module from tp-smapi-source package. 
Nevertheless hdaps seems to work fine with thinkpad_ec. After installing hdapsd edit /etc/default/hdapsd make sure START is set to "yes", DISK to "sda" and adjust SENSITIVITY (50 works ok for most people).

edit: use tp-smapi as in [http://elf.org/x200-tablet-accelerometer]

===Fan===
While the X200 is known for it's good cooling system, when running Ubuntu the fan seems to run constantly at around 3000rpm after it reached a certain threshold temperature. See the related bugreport on Launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/380303

For reasons of power consumption and noise reduction you might want to control the fans on your own using tp-fan, see [[ACPI_fan_control_script#ThinkPad_Fan_Control_GTK_GUI_tool]]. The Jaunty PPA seems to work fine on Karmic.

For me the following settings seem to work:
Check both boxes, set all sensors to 15% and the temperature threshold of all sensors to 25°C/68°F. With this settings the fan runs constantly with 2000rpm.

===Suspending===
Works fine as long as you don't suspend when docked.

edit: Suspend with dock works for me.

===Hibernating===
Works fine when hibernating when undocked. Not tested when docked.

===Docking and Undocking===
* Docking works ok. System even tries to switch automatically to saved external monitor display configuration and sometimes it even does the smart thing
* Before undocking you must always press "pre-undock" button on the left side of docking station and wait until green arrow allows you to proceed. Otherwise system will start to beep at you and it will probably get confused.
* Undocking and/or pressing "pre-undock" button switches automatically display to internal LCD only so you don't have to worry about it.
* Undocking doesn't umount automatically devices connected to docking station (usb pendrives, optical drive) so you must remember to do this manually. See https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/433682
* Suspending or hibernating when docked is not a good idea as system will probably get confused when resumed not docked also.

===MemoryCardReader===
Works

==Tablet==

===Screen===
* Screen rotation can be enabled with xrandr and https://launchpad.net/~thjaeger/+archive/tabletpc/+packages 
* TouchScreen requires recalibration as described https://help.ubuntu.com/community/X61T 
* Pen pressure sensitivity works
[[Category:Ubuntu_9.10]]

===Automatic Brightness Controll==
Possible using a script like the one at this link: 
http://gnome-look.org/content/show.php?content=128780&vote=good&tan=54635248 
Remember to install php5-cli and php5-gd, in the cfg file: pbr=2

Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad X200

2010-08-20T05:58:51Z

Wbonx:

[[Category: X200]]
Just brief info for now as I didn't have time to test all features yet. Please update if you have info on features marked as untested.

These notes also apply to the x200 tablet.

==Installation==

* Installing from desktop cd: Works fine with external usb drive

* Installing from USB stick: Works fine

* Installing from alternate cd: works fine with optical drive in [[X200 UltraBase]], just follow the steps

* Installing via wubi: works fine, except hibernate (normal for wubi installations)

* Updating from Jaunty: not tested

==Features support==

===Display===
* internal LCD: works fine
* external VGA: works fine
* external VGA via ultraBase: works fine
* DisplayPort via ultraBase: works fine

===Trackpoint===
The middle Scrollbutton won't work out-of-the-box, you can solve it with the help of the following Link: http://samiux.wordpress.com/2008/11/02/howto-lenovo-thinkpad-scroll-button-on-ubuntu-810/ 
I find the middle scrollbutton doesn't works very well for me by following these steps. 
The solution I currently use is to automatically execute the following commands: 
Quote:
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Y Axis" 8 4 5
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emugreatlation X Axis" 8 6 7

Another way to enable scrolling even if the instructions are a little older: http://www.thinkwiki.org/wiki/How_to_configure_the_TrackPoint#Scrolling. You can also try using gpointing-device-settings instructions as described at the top of the page but it's not persistent when you go into suspend-resume.

===WiFi===
*Intel 5100: works fine
After updating the kernel to 2.6.31-15-generic, the old kernel panic problem which used to happen in ubuntu 8.04 or older release, comes up again. I don't know whether this affects a fresh installation of karmic as I update the system immediately after I get a wired connection. 
I have the linux-backports-modules-wireless-karmic-generic package installed. Now it works fine.
*Intel 5300: works fine
*Intel 5350: works fine, kernel sees it as 5300

===Bluetooth===
generally works, but see https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/381913

===3G===
Works fine

===GPS===
Works, with the installation of http://sourceforge.net/apps/mediawiki/mbm/index.php?title=Main_Page#GPS_Control_.28mbm-gpsd.29

Note: mbm-gpsd is not running after wake from suspend

===Webcam===
Works perfectly.

===Sound===
* internal speakers: works fine, good volume
* headphones: works
* headphones via ultrabase: works fine
* internal mic: works fine, good sensitivity
* mic via ultrabase: not tested
* Volume up and down keys Work fine, Mute does not.
(Mute actually works but you won't find an OSD showing you it's on mute, unlike volume up and down. Additionally, plugging in your headphones even while on mute will let you hear sounds)

'''To get OSD working with Mute:''' (http://www.codefx.biz/2009/11/x200-mute-button)

Edit the file {{path|/etc/grub.d/10_linux}} and add {{bootparm|acpi_osi|Linux}} to the line with $GRUB_CMDLINE_LINUX_DEFAULT, so it will look like this:

"${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_EXTRA} ${GRUB_CMDLINE_LINUX_DEFAULT} acpi_osi=Linux" \

Then run '''{{cmduser|sudo update-grub}}'''

{{NOTE|Up to kernel 2.6.32 this seems to be the only way to fix the mute problem. However, this fix introduces new issues. Therefore, another, clean solution is being implemented as soon as kernel 2.6.33.}}

===Sensors===
mostly work, for HDD hddtemp is needed

===Fingerprint===
Doesn't work, see http://www.reactivated.net/fprint/wiki/Unsupported_devices#AuthenTec_AES2550_.26_AES2810

===HDAPS===
I couldn't make hdaps module to use [[Tp smapi]]. It seems module-assistant does not build patched version of hdaps module from tp-smapi-source package. 
Nevertheless hdaps seems to work fine with thinkpad_ec. After installing hdapsd edit /etc/default/hdapsd make sure START is set to "yes", DISK to "sda" and adjust SENSITIVITY (50 works ok for most people).

edit: use tp-smapi as in [http://elf.org/x200-tablet-accelerometer]

===Fan===
While the X200 is known for it's good cooling system, when running Ubuntu the fan seems to run constantly at around 3000rpm after it reached a certain threshold temperature. See the related bugreport on Launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/380303

For reasons of power consumption and noise reduction you might want to control the fans on your own using tp-fan, see [[ACPI_fan_control_script#ThinkPad_Fan_Control_GTK_GUI_tool]]. The Jaunty PPA seems to work fine on Karmic.

For me the following settings seem to work:
Check both boxes, set all sensors to 15% and the temperature threshold of all sensors to 25°C/68°F. With this settings the fan runs constantly with 2000rpm.

===Suspending===
Works fine as long as you don't suspend when docked.

edit: Suspend with dock works for me.

===Hibernating===
Works fine when hibernating when undocked. Not tested when docked.

===Docking and Undocking===
* Docking works ok. System even tries to switch automatically to saved external monitor display configuration and sometimes it even does the smart thing
* Before undocking you must always press "pre-undock" button on the left side of docking station and wait until green arrow allows you to proceed. Otherwise system will start to beep at you and it will probably get confused.
* Undocking and/or pressing "pre-undock" button switches automatically display to internal LCD only so you don't have to worry about it.
* Undocking doesn't umount automatically devices connected to docking station (usb pendrives, optical drive) so you must remember to do this manually. See https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/433682
* Suspending or hibernating when docked is not a good idea as system will probably get confused when resumed not docked also.

===MemoryCardReader===
Works

==Tablet==

===Screen===
* Screen rotation can be enabled with xrandr and https://launchpad.net/~thjaeger/+archive/tabletpc/+packages 
* TouchScreen requires recalibration as described https://help.ubuntu.com/community/X61T 
* Pen pressure sensitivity works
[[Category:Ubuntu_9.10]]

===Automatic Brightness Controll==
Possible using a script like the one at this link:
http://gnome-look.org/content/show.php?content=128780&vote=good&tan=54635248
Remember to install php5-cli and php5-gd, in the cfg file: pbr=2

How to rotate X41t screen with gravity sensor(hdaps)

2009-01-13T16:17:08Z

Wbonx: edited a couple of errors : positions of the files

[[:Category:X41 Tablet|X41 Tablet]][[Category:X41 Tablet]][[Category:Scripts]]

The X41t has a acceleration sensor build in. Originally it can protect the hard drive, if Laptop is falling down. See the [[HDAPS]] Page.
Now lets use that for funny stuff like emulate a joystick for Neverball [http://de.wikipedia.org/wiki/Neverball]. Or we use it for a very useful thing: Rotating the screen by recognizing where is downward. Like a lot of handy tools, like mobiles, mp3 player or photo cameras.

Basic concept is the following:
-Rotate the screen and the stylus to the steepest decent direction.
-Rotate only in stylus mode.
-Rotate only if it is really necessary.
-Rotate only if it cants more than 10 degrees.
-An easy program.

There are other programs witch can do that, but I have not found one that works out off the box. And I can not understand that much ''python''. So I tried it out myself.
I have written a set of small ''shell'' scripts that rotates the screen of the X41 Tablet by using the gravity sensor coordinates and some ACPI events.
It consist of two parts, fist the main part that contains the code for deciding and rotating and the second part which starts and stops the fist one. Maybe some one can make suggestions to get this in a real deamon style.

I have tested it on an x41t with ubuntu 8.04 with the standard kernel 2.6.24-19-generic.
''sudo apt-get install x11-xserver-utils wacom-tools'' should install all stuff.

First Part. Usually this is saved as {{path|/etc/acpi/x41t_gravity}}

#!/bin/bash

#usage: just start or kill it

#load configuration
. /etc/gravity/gravity.conf

get_orientation(){
string=`cat /sys/devices/platform/hdaps/position`
string=`echo $string | tr -d '[=-=][:blank:][=(=][=)=]'`
x=`echo $string | awk -v FS="," '{print $1}'`
y=`echo $string | awk -v FS="," '{print $2}'`
dx=`expr $x - $x_horizontal` #dx away from middle
dy=`expr $y - $y_horizontal` #dy away form the middle

#get actual orientation from last rotation, saved in a file :
if [ ! -f /tmp/actual_orientation.txt ];then
echo 0 > /tmp/actual_orientation.txt #0 means normal orientation
fi
actual_orientation=`cat /tmp/actual_orientation.txt`
}

prepare_rotate(){
echo "Nothing to prepare. I can rotate now."
#ps -A | grep compiz.real && (kwin --replace)& #because compiz sometimes crashes.
}

do_rotate(){
prepare_rotate
#rotate screen
xrandr -o $1
#rotate stylus
case $1 in
right)
/usr/bin/xsetwacom set stylus rotate 1;;
left)
/usr/bin/xsetwacom set stylus rotate 2;;
inverted)
/usr/bin/xsetwacom set stylus rotate 3;;
*)
/usr/bin/xsetwacom set stylus rotate 0;;
esac
#save the orientation
echo $1 > /tmp/actual_orientation.txt
}

######### Main ########################

while [ true ]; do
get_orientation
if [ `expr $dx \* $dx` -ge `expr $dy \* $dy` ];then #checks for the absolute greater value
if [ $dx -gt $eps ] && [ ! $actual_orientation = right ] ;then #check if the screen have to rotate
do_rotate right
elif [ $dx -lt -$eps ] && [ ! $actual_orientation = left ];then #check if the screen have to rotate
do_rotate left
fi
else
if [ $dy -gt $eps ] && [ ! $actual_orientation = normal ];then #check if the screen have to rotate
do_rotate normal
elif [ $dy -lt -$eps ] && [ ! $actual_orientation = inverted ];then #check if the screen have to rotate
do_rotate inverted
fi
fi
sleep 1
done

exit 0

Second Part. Usually this is saved as {{path|/etc/acpi/x41t_control_gravity.sh}}

#!/bin/bash

#load configuration
. /etc/gravity/gravity.conf

################ set DISPLAY ####################
#export DISPLAY=$Default_DISPLAY #a work around for right DISPLAY varialbe (I do not like it).
#export XAUTHORITY=$Default_XAUTHORITY #THIS GIVED ME AN ERROR SO I COMMENTED IT: wbonx
#xset -display $DISPLAY dpms

################# Main ##########################

if [ ! $1 ] || [ ! $1 = start ];then
killall x41t_gravity #return to normal state
xrandr -o normal
/usr/bin/xsetwacom set stylus rotate 0
rm /tmp/actual_orientation.txt
elif [ $1 = start ];then
#check for the kernel modul for gyroscope
lsmod | grep hdaps || modprobe hdaps
lsmod | grep hdaps || exit 1
(/etc/acpi/x41t_gravity)& #will be endless repeated (kill see up)
fi

exit 0

Some settings that have to tune. Usually this is saved as {{path|/etc/gravity/gravity.conf}}

x_horizontal=433 #horizontal position, get it by calibration
y_horizontal=390 #just read the value in /sys/devices/platform/hdaps/position
#the first value is x, second one is y

eps=40 #define a neighbourhood interpreted as horizontal

Default_DISPLAY=":0.0"
Default_XAUTHORITY=/home/smjb0803/.Xauthority

Now lets begin! Just add two ACPI events, first to start the ''x41t_gravity'', second for ending it.

Fist. Usually this is saved as {{path|/etc/acpi/events/x41t-swivel-down}}.
# /etc/acpi/events/x41t-swivel-down
# called when tablet head swivels down
event=ibm/hotkey HKEY 00000080 00005009
action=/etc/acpi/x41t_control_gravity.sh start

Second. Usually this is saved as {{path|/etc/acpi/events/x41t-swivel-up}}.
# /etc/acpi/events/x41t-swivel-up
# called when tablet head swivels up
event=ibm/hotkey HKEY 00000080 0000500a
action=/etc/acpi/x41t_control_gravity.sh stop

And restart the ACPID.
sudo /etc/init.d/acpid restart

That`s it. Have fun and make suggestions. Please use it only if you trust in it. On personal risk. You have to prevent losing data.
--[[User:Jonasbergel|Jonasbergel]] 09:27, 16 October 2008 (CEST)

Problem with hard drive clicking

2008-05-29T14:52:22Z

Wbonx:

Many users have reported a '''problem with hard drive clicking''', sometimes described as a repeating '''tick tick tick''' type of ticking sound.
The [[Hitachi Travelstar 5K80]] series which shipped with many T series Thinkpads in particular is reported to suffer from this problem. The clicks occur rapidly, and are quiet but noticeable. While in use in a quiet environment the clicks can be relatively loud and very irritating to some users. The clicks seem to happen when the drive is idle and the power has been on for a significant period of time. The clicking is also reported on other vendor's laptop hard drives too and is therefore almost certainly a hard drive related rather than a laptop chassis related.

The clicking sound appears to only occur when the drive is idle. Forcing the drive to be busy silences the ticking while the drive is busy. Launching programs that access the hard drive such as searching or defragmenting the drive helps for a time. Cycling the power on the hard drive such as through a full power off reboot of the system stops the ticking for the moment and has been used as a temporary solution. Also see use of hdparm for another way to reset the drive without a power off reboot.

Others recommend using Hitachi's drive feature tool to increase the acoustic management level, and/or set power management settings.

===Possible Cause and Speculation===

Laptop drives (especially Hitachi [[Hitachi Travelstar 5K80]], [[Hitachi Travelstar 5K100]] and SAMSUNG MP0804H) can unload heads very often, and they can produce a noticeable click when doing that. Some ThinkPad BIOSes can be very eager to program the HD Advanced Power Management feature (hdparm -B) even when told to always keep the HD in "Maximum Performance mode" and will do so every time AC state changes, and when coming out of suspend (be it S3 or S4). Unless you reset the HD's APM mode, it will unload its heads eventually thus producing the clicks.

Another proposed possible cause is the drive firmware running a low level surface media check periodically during drive idle time.

It is not known whether the problem is a sign of impending drive failure. The root cause of the problem is not yet known. It is quite likely to be a normal mode of drive operation. The problem is very prevalent.

Do not confuse this with regular activity. Many daemons poll (config) files every few seconds. Despite files being cached, POSIX-compliant filesystems like ext2 or ext3 must update (=write) the last access time. More details and workaround in [[How to reduce power consumption#Hard_Drives]].

===Tracking down the cause of the clicks===

Using "'''smartctl -A'''", it is possible to check if any of the drive's attributes related to platter spin-up/down or head unload are increasing when a click is heard.
That can help pinpointing the cause of the clicks.

A shell script like this may help:
<pre>#!/bin/bash
lastval=0
while :
do
newval=`smartctl -A /dev/sda | awk '$2=="Load_Cycle_Count" {print $10}'`
if [[ $newval != $lastval ]] # i.e. anything has changed (here: load cycle count only)
then
date
echo $newval
fi
lastval=$newval
sleep 30 # or some other interval
done
</pre>

===Possible Solution (Windows)===

On X41T, do bios, firmware and IBM updates.
Then simply disable the ShockProtection of the HardDrive.
On a native X41T windows installation it solved the problems, you will hear a click every hour.
Seems that the problem is related to an aggressive setting that will try to park the head often to protect the drive, so the problem is not related with power management settings, perhaps a similar approach works also under linux.
WBonX (Hitachi drive)

===Possible solution (Linux)===

Temporary relief has been seen by using '''hdparm''' to reset the drive. But note the warning in the hdparm man page indicating that it is a dangerous operation. This is very likely due to the possibility of losing data in the write cache not yet stored to the hard drive. This would be dependent upon the particular hard drive. When used in the following to stop the clicking I have not seen any data loss. YMMV.

# hdparm /dev/hda
# sync
# sleep 5
# sync
# hdparm -w /dev/hda

The clicking noise apparently occurs when the drive is parking its heads (and ramping them off the drive surface in the process) after a timeout after the last disk access. Try turning off power management for the drive; that should stop the drive from parking the heads except when turning off:

# hdparm -B 255 /dev/hda

You can also try

# hdparm -B 254 /dev/hda

which doesn't turn power management off, but is the least agressive setting: it will still unload heads, but far less often. The drives '''are''' prepared to withstand a great number of head unloads (200k unloads are typical, Hitachi drives tolerate about 600k unloads).

These commands have immediate effect, and need to be re-issued at every boot, after resuming from disk or RAM, and after hotswapping. '''You have to reissue the -B commands every time the ThinkPad BIOS might have tried to override them'''.

===Specific models===

====Hitachi C4K60 (HTC426060G9AT00)====

On a Thinkpad X41 with a has a 60GB Hitachi C4K60 (HTC426060G9AT00) hard-disk that had the clicking problem (even in Windows), the hdparm solution above did not work. The problem was indeed caused by the hard-disk unloading the heads when idle, and the Load_Cycle_Count SMART statistic could be seen increasing when the clicks occurred.

hdparm -B settings did not seem to help, and a check of the harddrives specs (available in [http://www.hitachigst.com/tech/techlib.nsf/products/Travelstar_C4K60 hitachigst.com]) verified that setting the APM mode off (hdparm -B 255) would set it actually to the lowest APM mode (the same as hdparm -B 254). In this drive, even the lowest APM mode unloads the heads very aggressively causing the clicking sounds. Another problem is that the drive is rated only for 600000 unload/load cycles, which means that the drive will break in at most a couple of years.

{{NOTE|This observation is only about the specific model (Hitachi C4K60), and is not true for more recent Hitachi drives, which do disable APM with -B 255.}}

====Samsung MP0804H 80GB====

On this drive, the ''clicking noise'' can be immediately stopped just by enabling ''automatic offline tests'' using
# smartctl -o on /dev/hda
Even more strange is that SMART wasn't enabled by default, although the drive supports it.

The drive had already performed 15.539 load cycles (out of 600.000) within only one week.

Note that enabling SMART (-s on) without enabling ''offline tests'' -- which is what I did immediately after observing the ''clicks'' -- did not solve the problem, but made it quite clear that the drive was ''badly in need of some care''.

==== Seagate Momentus 7200.1 ====
(I got this drive in my x61 tablet)

On this drive, each click does indeed correspond to an increase in SMART attribute 193, "193 Load_Cycle_Count", as you can see by doing a
# smartctl -A /dev/sda

before and after a click.

It seems like the problem is that the default powersaving mode for the drive is one which causes clicking. In fact, executing
# hdparm -B 255 /dev/sda
(which is supposed to turn off power management) actually leaves power management on, and is equivalent to
# hdparm -B 128 /dev/sda

as you can see by comparing the results of
# hdparm -B 1 /dev/sda; hdparm -I /dev/sda | grep Advanced
# hdparm -B 128 /dev/sda; hdparm -I /dev/sda | grep Advanced
# hdparm -B 254 /dev/sda; hdparm -I /dev/sda | grep Advanced
# hdparm -B 255 /dev/sda; hdparm -I /dev/sda | grep Advanced

This may or may not be related to something else strange; the drive reports that the Advanced power management level is 0x8000 more than what you set it to, presumably leading hdparm to report that it is always set to "unknown setting" (since the number should be between 1 and 255). FYI the results of the above sequence of commands is:

# hdparm -B 1 /dev/sda; hdparm -I /dev/sda | grep Advanced

/dev/sda:
setting Advanced Power Management level to 0x01 (1)
Advanced power management level: unknown setting (0x8001)
* Advanced Power Management feature set

# hdparm -B 128 /dev/sda; hdparm -I /dev/sda | grep Advanced

/dev/sda:
setting Advanced Power Management level to 0x80 (128)
Advanced power management level: unknown setting (0x8080)
* Advanced Power Management feature set

# hdparm -B 254 /dev/sda; hdparm -I /dev/sda | grep Advanced

/dev/sda:
setting Advanced Power Management level to 0xfe (254)
Advanced power management level: unknown setting (0x80fe)
* Advanced Power Management feature set

# hdparm -B 255 /dev/sda; hdparm -I /dev/sda | grep Advanced

/dev/sda:
setting Advanced Power Management level to disabled
Advanced power management level: unknown setting (0x8080)
Advanced Power Management feature set

The workaround seems to be to execute
# hdparm -B 254 /dev/sda

So it seems like the drive is interpreting "hdparm -B 255 /dev/sda", which I'm guessing is the default (and which is supposed to be NOT powersaving mode) as a request to go into powersaving mode, which causes it to spin down alot and to and click. And I'm guessing that "hdparm -B 254 /dev/sda" actually takes it out of powersaving mode.

Somewhat annoying because
# smartctl -A /dev/sda
shows that I have already accumulated a Load_Cycle_Count 106680 after owning the laptop for just a few weeks! I'm not sure that I understand this stuff, but if this corresponds to "Load/Unload Cycles" in http://www.seagate.com/docs/pdf/datasheet/disc/ds_momentus7200.pdf, then that's more than 1/6 of the drive's lifetime!

==== [http://sdd.toshiba.com/main.aspx?Path=HardDrivesOpticalDrives/2.5-inchHardDiskDrives/MK2035GSS/MK2035GSSSpecifications Toshiba MK2035GSS] ====

Issue happens with "laptop mode" disabled. BIOS is an "AMIBIOS 8.00.14", and the chipset is "Mobile Intel GM965 Express".

I can solve the problem with the hdparm workaround, the lowest value that makes the trick for me is:
# sudo hdparm -B 192 /dev/sda

===Firmware upgrades===

There are two HD firmware upgrades on Lenovo's support website. One is specific to X41's, and will upgrade Hitachi's to Release A0L0 (document [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67238 MIGR-67238], 2007/01/24). The upgrade comes in three forms: diskette, windows executable or ISO CD-ROM image.
IBM's latest posted firmware, A5DA, does not appear to solve the problem.

A newer upgrade set ([http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-62282 MIGR-62282], 2007/05/02) updates HD firmwares of several brands, including Hitachi. The patch upgrades firmware for HTC4260xxG9AT00 to A0L2 (according to program output, from 00P3A0B5 to 00P3A0L2). The upgrade comes in a large (20 MB) ISO format, or as several diskettes. There is seemingly no windows executable; therefore upgrading a diskless machine can be problematic (it involves making a DOS-based USB bootable drive).

The upgrade caused one X41 Tablet HTC426060G9AT00 drive to stop clicking.

===Another Possible Solution===

IBM, when notified about this occurance, may replace the drive with a Fujitsu 5k 80GB hard drive, as to them the sound is indicative of a potential hard drive failure.

==External links==
*Ubuntu reported bugs: [https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 59695] [https://bugs.launchpad.net/ubuntu/+bug/104535 104535]
*[http://www.hitachigst.com/hdd/support/download.htm Hitachi Global Storage Technologies Downloads] - The drive feature tool may help with this problem.
*[http://forum.thinkpads.com/viewtopic.php?t=7462 Thread on thinkpads.com]
*[http://notebookforums.com/showthread.php?t=46058 Thread on notebookforums.com]
*[http://forums.silentpcreview.com/viewtopic.php?p=143203 Thread on silentpcreview.com]
*[http://forum.thinkpads.com/viewtopic.php?t=15769 Another Thread on thinkpads.com]
*[http://www.tabletpcbuzz.com/forum/topic.asp?TOPIC_ID=28538&whichpage=1 Thread on tabletpcbuzz.com]
*[http://thinkpad-forum.de/forum/viewtopic.php?t=2255 German Thread on thinkpad-forum.de (Containing an interesting remark about a possible problem with the Cache)]

[[Category:T40]] [[Category:T41]] [[Category:T42]] [[Category:T43]] [[Category:X41]] [[Category:G41]]