Difference between revisions of "Thinkpad W510"
From Blue-IT.org Wiki
(→Operation System) |
(→Troubleshooting) |
||
Line 25: | Line 25: | ||
== Troubleshooting == | == Troubleshooting == | ||
+ | |||
+ | === 90W power supply not enough - use standard 135 W === | ||
+ | |||
+ | Due to the heavy components in this laptop, an '''original 135 W power supply''' is needed! | ||
+ | Do not use a power supply from another manufacture (no name). You will not succeed! | ||
+ | |||
+ | If you don't do this, the laptop components do not run at full speed! | ||
+ | |||
+ | Solution: None! Use the 135W power supply or run at battery power. | ||
+ | |||
=== Ultrabay === | === Ultrabay === | ||
==== Eject the ultrabay ==== | ==== Eject the ultrabay ==== |
Revision as of 13:05, 5 January 2014
Contents
Operation System
- Working on Ubuntu 12.04 LTS
- Updated to Ubuntu 13.10
Nvidia Quadro FX
VDPAU
sudo apt-get install livdpau-va-driver bvdpau-va-gl1 vainfo
For flashplayer:
sudo mkdir /etc/adobe/ && sudo bash -c "echo 'EnableLinuxHWVideoDecode=1' >> /etc/adobe/mms.cfg"
X11
Problems with brightness-control:
vim /etc/X11/xorg.conf
Section "Device" Identifier "DefaultDevice" Option "NoLogo" "True" Option "RegistryDwords" "EnableBrightnessControl=1" EndSection
Troubleshooting
90W power supply not enough - use standard 135 W
Due to the heavy components in this laptop, an original 135 W power supply is needed! Do not use a power supply from another manufacture (no name). You will not succeed!
If you don't do this, the laptop components do not run at full speed!
Solution: None! Use the 135W power supply or run at battery power.
Ultrabay
Eject the ultrabay
http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Script_for_Ultrabay_eject
Create this script and run it as root!
Don't forget to alter the DEVICEPATH path at the beginning of the scrip according to your machine!.
udevadm info --query=path --name=/dev/sr0 | perl -pe 's!/block/...$!!'
Make the button for the DVD drive less sensitive
The problem is caused by udev
sudo cp /lib/udev/rules.d/60-cdrom_id.rules /etc/udev/rules.d/.
Uncomment the containing ENV{DISK_EJECT_REQUEST}
sudo vim /etc/udev/rules.d/60-cdrom_id.rules
# media eject button pressed #ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $devnode", GOTO="cdrom_end"
Restart udev
sudo service udev force-reload sudo service udev restart
You should emediately see, that the button.
Lock the device button
Lock:
eject -i on /dev/sr0
Unlock:
eject -i off /dev/sr0
Toggle script:
#!/bin/bash DEVICE="/dev/sr0" if eject "${DEVICE}" then eject -i on "${DEVICE}" else eject -i off "${DEVICE}" fi