Linux on the X220

[twotoneblue]

This worked for me when the grub2 procedure failed

X220, Ubuntu 11.10, Corsair Flash Voyager 8GB

You'll loose everything on your USB-drive so beware

[kyriu]

Originally Posted by twotoneblue

This worked for me when the grub2 procedure failed

X220, Ubuntu 11.10, Corsair Flash Voyager 8GB

You'll loose everything on your USB-drive so beware

You just made my day! If you drop by Lisbon I'll tour you around. Great tip.

[ALLurGroceries]

I just got an X220, and I'm running Debian Sid on it. It's running off an intel 310m 40GB msata, and I have the intel 6205 wifi card.

Everything is great except for the clickpad. Out of the box the only way to right click is to hold one finger on the touchpad and then click either of the integrated buttons. Click and drag does not work either.

I took this modified patch and made a small change to make it work for Debian Sid: https://bugs.launchpad.net/xserver-x...9/comments/275

Here is my modified version: 200_clickpad_support.patch

I then used the directions from here to create a patched .deb, using my own version of the patch above instead of the SuSE tarball:
https://help.ubuntu.com/community/X220#Touchpad

After this, right-click works fine, and it is possible to minimize the amount of freakout from the bottom edge of the trackpad using two new synaptics variables, TouchButtonArea and TouchButtonSticky

I set the touchbutton area to the smallest possible (which makes it just above the line) and the pressure the maximum (so that touches in this area do not move the cursor):

synclient TouchButtonArea=1
synclient TouchButtonSticky=1000

Two finger scrolling and click-and-drag seem to be mutually exclusive. There needs to be more work done to get this clickpad working 100% correctly... bug report here:
https://bugs.freedesktop.org/show_bug.cgi?id=38303

My 3.1 kernel config: http://www.mediafire.com/?2e3uq4004pk6pn8

The mute button LED works with the following config option, but it doesn't always seem to sync correctly with the actual status:

CONFIG_THINKPAD_ACPI_UNSAFE_LEDS=y

Update:
Power consumption and thinkfan settings

[ThinkRob]

Originally Posted by ALLurGroceries

The mute button LED works with the following config option, but it doesn't always seem to sync correctly with the actual status:

CONFIG_THINKPAD_ACPI_UNSAFE_LEDS=y

FWIW, I had this same problem when I used ALSA and thinkpad_acpi. I removed ALSA, removed thinkpad_acpi, upgraded to OSS4, set up an ACPI script to respond to the "button/mute" ACPI event, and now the mute button now works flawlessly with no synchronization issues.

[ALLurGroceries]

I'm only talking about the LED, is that what you mean? The button itself works fine.

[ThinkRob]

Originally Posted by ALLurGroceries

I'm only talking about the LED, is that what you mean? The button itself works fine.

Yes.

Mute worked just fine when I used ALSA -- but thinkpad_acpi seemed to interfere with the light working. I removed thinkpad_acpi when I migrated to OSS4 (since it required ALSA support in my kernel), and viola!

[ALLurGroceries]

Is expresscard hotplugging/pciehp working for anyone? Not so much here on both 3.0 and 3.1-rc with bios 1.22

Sort of a letdown... I use a lot of cards and having to reboot (while it only takes 20 seconds) is a bother.

edit: nevermind, I'm a doofus - just needed to modprobe acpiphp

[paulmcfonty]

Hi,

nobody has any suggestion for the incredible low volume of the internal speakers ? Even in Win 7 the volume is low, but not so much as in linux ..

[ALLurGroceries]

The speakers are actually incredibly loud for me using pulseaudio's gain on linux. They can almost break up... maybe you need to check your mixer?

[paulmcfonty]

I've tried to set up the mixer, but when I set gain a bit higher than flat, speakers becomes noisy in a boring way .. (and this not happens in win, so probably it's not an hardware problem)