Lenovo ThinkPad T400
- 1 System Specification
- 2 Network
- 3 Graphics/Xorg Configuration
- 4 Audio
- 5 Multimedia Keys
- 6 ACPI
- 7 SUSPEND-RESUME
- 8 7-1 Media Card Reader
Below is an overview of the T400 specifications as originally used to start this article:
- CPU : Intel® Core™2 Duo Processor T9400 (6M Cache, 2.53 GHz, 1066 MHz FSB)
- Memory : 3GB PC3-8500 DDR3
- WiFi : Intel WiFi Link 5300
- Hard-Drive : 160GB, 7200rpm
- Optical Drive : DVD Recordable
- Integrated Graphics : Intel 4500MHD
- Discrete Graphics : AMD M82XT Hybrid 256 MB (ATI Mobility Radeon HD 3470)
- Screen : 14.1" WXGA+ TFT with LED Backlight
- Gigabit Ethernet, Modem
- Express Card & PC Card Slots
- Integrated Bluetooth PAN
- No camera
- No fingerprint reader
- No Intel Turbo Memory
The kernel module to get the network card to work is
Lenovo offers different options in wireless hardware:
- Wifi link 5100 and 5300
The drivers are included in the 2.6.27 kernel. However, it's important to make sure that you have the correct firmware. I installed the iwlwifi-5000-ucode. See this section for more details.
Since the 2.6.34 kernel update, the firmware files were moved to the
linux-firmware package. Manually installing other firmware packages is not required.
11b/g/n Wireless Lan Mini-PCI Express Adapter II 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8172 (rev 10)
See http://www.thinkwiki.org/wiki/ThinkPad_11b/g/n_Wireless_LAN_Mini-PCI_Express_Adapter_II for more details.
There is a module "hsfmodem" provided by http://www.linuxant.com/.
If you have thinkpad-acpi kernel module loaded, you can enable and disable Bluetooth from command line. To enable:
# echo 1 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable
# echo 0 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable
To disable or enable Bluetooth at startup, add one of the above commands to
The bluetooth module requires
uhci_hcd. Make sure
/etc/modprobe.d/modprobe.conf does not blacklist it.
For everything else related to Bluetooth, follow the procedure described in Bluetooth section of the Arch Wiki.
Note that it's possible to switch the graphics adapter by only restarting X, but It's quite useless since you can't power up/down a graphic-card without rebooting. So it's either both graphic-card on at all times, or do the switching in the BIOS.
So please press the ThinkVantag-button» during boot up and enable either the Integrated or the Discrete graphics cards in your BIOS's "Config->Display" menu.
I could not get the
xf86-video-radeonhd drivers to detect my external monitor, but
xf86-video-ati worked fine. Remember to remove
catalyst-utils and reboot before using an open source ATI drivers. ATI uses its own OpenGL library in its proprietary drivers, which is included in
catalyst-utils and conflicts with libgl. As it did with the integrated graphics, running X -configure generated a working xorg.conf.
To get the catalyst drivers working, you do have to configure your xorg.conf properly. I used aticonfig --initial to generate a working xorg.conf. I did encounter a problem that I have not been able to solve yet : resizing a window in a compositing window manager takes 1-2 seconds. This makes the drivers pretty much unusable.
Is currently not supported by the kernel. You can enable switchable-graphics in the BIOS and make Xorg do the switching, but then both cards will always use power and generate lots of heat. See the gentoo-wiki to keep up too date on the issue.
If you want to enable hotplugging you probably do not need a xorg.conf. But if you are using xf86-video-ati you might temporarely need to disable KMS, by adding "nomodeset" to your kernel-line in "/boot/grub/menu.lst". If you do not want to disable KMS you can probably install some radeon firmware, see the Ati-wiki.
Since all the mouse/keyboard configuration is taken care of by HAL you will need some config files in "/etc/hal/fdi/policy/" For instant "mouse-wheel.fdi" to enable TrackPoint-scrolling:
<match key="info.product" string="TPPS/2 IBM TrackPoint"> <merge key="input.x11_options.EmulateWheel" type="string">true</merge> <merge key="input.x11_options.EmulateWheelButton" type="string">2</merge> <merge key="input.x11_options.YAxisMapping" type="string">4 5</merge> <merge key="input.x11_options.XAxisMapping" type="string">6 7</merge> <merge key="input.x11_options.Emulate3Buttons" type="string">true</merge> <merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge> </match>
More information in the TrackPoint can be found here: http://www.thinkwiki.org/wiki/How_to_configure_the_TrackPoint. The Keyboard layout is controlled by "/etc/hal/fdi/policy/10-keymap.fdi" Modify it like this to change your layout. If you have any more questions on hotplugging (like how to enable tapping), take a look at it's wiki page.
If you want to be able to use horizontal and vertical scroll with your touchpad add this lines to your xorg.conf
Section "Module" ...... Load "synaptics" EndSection Section "InputDevice" Identifier "Touchpad" Driver "synaptics" Option "AlwaysCore" Option "Device" "/dev/input/mouse1" Option "Protocol" "auto-dev" Option "SendCoreEvents" "true" Option "LeftEdge" "1632" Option "RightEdge" "5312" Option "TopEdge" "1575" Option "BottomEdge" "4281" Option "FingerLow" "25" Option "FingerHigh" "30" Option "MaxTapTime" "180" Option "MaxTapMove" "220" Option "VertScrollDelta" "100" Option "MinSpeed" "0.06" Option "MaxSpeed" "0.12" Option "AccelFactor" "0.0010" Option "VertEdgeScroll" "on" Option "HorizEdgeScroll" "on" # Option HorizScrollDelta""0" Option "SHMConfig" "on" EndSection
for trakpoint with third button paste & scroll add this few lines to xorg.conf too
Section "InputDevice" Identifier "Trackpoint" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "Auto" Option "Emulate3Buttons" Option "Emulate3Timeout" "50" Option "EmulateWheel" "on" Option "EmulateWheelTimeout" "200" # adjust third button paste timeout. Option "EmulateWheelButton" "2" Option "YAxisMapping" "4 5" Option "XAxisMapping" "6 7" Option "YAxisMapping" "4 5" EndSection
finally update your layout
Section "ServerLayout" InputDevice "Trackpoint" "CorePointer" InputDevice "Touchpad" InputDevice "Keyboard0" "CoreKeyboard" EndSection
Once you have ALSA installed, fire up alsamixer and make sure that sound is not muted. You might also want to press the Volume Up or Volume Down button. It seems than the Mute button mutes everything, even system beeps. Pressing the Volume Up or Volume Down button can unmute, but not pressing the Mute button again.
Here's the modules I have loaded that are relevant to sound :
$ lsmod | grep snd snd_seq_oss 35584 0 snd_seq_midi_event 9344 1 snd_seq_oss snd_seq 58336 4 snd_seq_oss,snd_seq_midi_event snd_seq_device 9364 2 snd_seq_oss,snd_seq snd_hda_intel 474672 2 snd_hwdep 10632 1 snd_hda_intel snd_pcm_oss 45568 0 snd_pcm 82440 2 snd_hda_intel,snd_pcm_oss snd_timer 24720 2 snd_seq,snd_pcm snd_page_alloc 10640 2 snd_hda_intel,snd_pcm snd_mixer_oss 18944 1 snd_pcm_oss snd 64840 16 snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss soundcore 9632 1 snd
The screen brightness controls and the flashlight work without any tweaking. The other keys can be mapped using xev and xbindkeys. By following this guide you should be able to get everything working, but here's summary :
- First, open a terminal and type
xev. This starts the "Event tester".
- Place your cursor on the "Event tester" window.
- When you press a key on your keyboard or move your mouse, it should get displayed in a terminal. For instance, this is what shows up if you press Fn+F2
KeyRelease event, serial 33, synthetic NO, window 0x3000001, root 0x86, subw 0x0, time 5537544, (76,110), root:(81,938), state 0x0, keycode 146 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
It basically says that keycode 146 is not bound (NoSymbol). Here are all the keycodes of all multimedia buttons:
Volume Down : keycode 174 Volume Up : keycode 176 Fn+F2 : keycode 146 Fn+F3 : keycode 241 Fn+F4 : keycode 223 Fn+F5 : Not responding to events ?? Fn+F7 : keycode 214 Fn+F8 : keycode 249 Fn+F9 : keycode 207 Fn+F12 : keycode 165 Fn+Up : keycode 164 Fn+Down : keycode 162 Fn+Left : keycode 144 Fn+Right : keycode 153 Fn+Home : keycode 212 Fn+End : keycode 101
xmodmap -pke > ~/.Xmodmapin a terminal. This creates a file,
.Xmodmap, containing your current keyboard mapping.
- Now open the file with a text editor and find the keycodes you're interested in. You can map any keycode with a symbol from this list.
- To get your new
.Xmodmaploaded when you start X, just add
xmodmap ~/.Xmodmapto your .xinitrc.
- To get your new
.Xmodmaploaded immediately, type
xmodmap ~/.Xmodmapin a terminal.
You can now assign functions to your newly bound keys by using facilities provided by your window desktop environment or by using
- Start by installing it
pacman -S xbindkeys
- Then add
xbindkeys &to your .xinitrc.
- And finally, in your home directory, create a file called
.xbindkeysrc.scmwith content that would look something like
(xbindkey '("XF86Standby") "sudo killall dhcpcd && sudo pm-suspend") (xbindkey '("XF86AudioRaiseVolume") "amixer set Master 2dB+ unmute") (xbindkey '("XF86AudioLowerVolume") "amixer set Master 2dB- unmute")
Note, in more recent Arch (kernel 3.4.2, xorg-server 1.12.2, laptop-mode-tools 1.61), on the T400, related keys combinations binding seems to be:
- Fn+2 → XF86ScreenSaver
- Fn+4 → XF86Sleep & XF86Wakeup
- Fn+12 → XF86Suspend
Now, the actual action will performed on XF86Sleep or XF86Suspend is configurable in session policy, so it may vary (e.g. depending on desktop environment). If nomenclature of XF86Standby, XF86Hibernate or XF86Sleep is confusing, check the thread suspend / hibernate nomenclature for in-depth explanation.
To get the mute button to work, it is necessary to pass the string
acpi_osi="Linux" to the kernel as a boot parameter. In GRUB2, add it to the "linux" line. See here for more details.
With the 3.1 bios, it seems that the mute button works normally (set it up the same as the volume buttons with, for instance, "amixer set Master toggle").
To enable the fan speed control, it's necessary to load the thinkpad_acpi with option fan_control=1. After the thinkpad_acpi module is loaded with this option, you can monitor and adjust the fan speed via /proc/acpi/ibm/fan.
People have been having issues with suspend resume with the current intel xf86-video-intel 188.8.131.52 drivers in combination with the 4500mhd chipset. This is apparently an issue with concurrency as adding the following script (with mod 755) in /etc/pm/sleep.d fixes things. to some extent...
#!/bin/sh # Workaround for concurrency bug in xserver-xorg-video-intel 2:2.4.1-1ubuntu10. # Save this as /etc/pm/sleep.d/00CPU . "/usr/lib/pm-utils/functions" case "$1" in hibernate|suspend) for i in /sys/devices/system/cpu/cpu*/online ; do echo 0 >$i done ;; thaw|resume) sleep 10 # run with one core for 10 secs for i in /sys/devices/system/cpu/cpu*/online ; do echo 1 >$i done ;; *) ;; esac
From http://ubuntu-virginia.ubuntuforums.org/showpost.php?p=6105510&postcount=12 petri4 on the ubuntu forums.
7-1 Media Card Reader
Tested for SD cards only. Works after loading modules sdhci and ricoh_mmc in /etc/rc.conf. Sometimes there are problems initializing the SD card (check dmesg) after inserting it. In such cases, try re-inserting it again.