* microphone (barely - it does capture sound but it is unusably noisy on my setup)

* microphone (barely - it does capture sound but it is unusably noisy on my setup)

+

* headphones (tested with Gnome 3.4)

* 2 "Think" LEDs

* 2 "Think" LEDs

* HDD in AHCI mode

* HDD in AHCI mode

* boot from USB key, USB HDD, internal HDD

* boot from USB key, USB HDD, internal HDD

−

* SD card reader

+

Working but not out of the box:

Working but not out of the box:

Line 39:

Line 38:

Partly working:

Partly working:

* VGA out to external monitor (connection generally goes OK but disconnect frequently freezes X and sometimes causes hard lock up forcing cold reboot; could be configuration or DE related - see below)

* VGA out to external monitor (connection generally goes OK but disconnect frequently freezes X and sometimes causes hard lock up forcing cold reboot; could be configuration or DE related - see below)

+

* SD card reader : In order to read SDHC cards, you need to install and run as daemon the [https://aur.archlinux.org/packages.php?ID=52437 Ricoh e823 fix]

Not working:

Not working:

Line 45:

Line 45:

Untested:

Untested:

* HDMI out

* HDMI out

−

* headphones

* security chip thing

* security chip thing

* boot from USB FDD, network boot

* boot from USB FDD, network boot

Line 66:

Line 65:

{{Warning|Do not add these options without checking them out first as they may cause problems depending on your setup. Be prepared to disable them as necessary.}}

{{Warning|Do not add these options without checking them out first as they may cause problems depending on your setup. Be prepared to disable them as necessary.}}

−

If using laptop-mode-tools stops your machine from shutting down while on battery power, try setting the following configuration line in /etc/laptop-mode/conf.d/runtime-pm.conf:

+

If using laptop-mode-tools stops your machine from shutting down while on battery power, try the solution described in [https://bbs.archlinux.org/viewtopic.php?id=133108 this thread].

−

CONTROL_RUNTIME_PM="0"

tp_smapi does not currently support the x121e and is apparently not likely to do so in the foreseeable future. Apparently the x121e is not quite a "real" ThinkPad.

tp_smapi does not currently support the x121e and is apparently not likely to do so in the foreseeable future. Apparently the x121e is not quite a "real" ThinkPad.

Line 94:

Line 92:

== Arch Forums x121e related threads ==

== Arch Forums x121e related threads ==

−

Some people experience difficulties booting if their disk is partitioned using a GPT partition map. It may work to use a GPT partition map, UEFI boot and a fat 16 formatted EFI partition (this violates UEFI spec but may have the advantage of actually working). See https://bbs.archlinux.org/viewtopic.php?id=131149 and https://bbs.archlinux.org/viewtopic.php?id=133074.

+

Some people experience difficulties booting if their disk is partitioned using a GPT partition map. The correct way to avoid this problem is to ensure that the EFI partition is at least 512M. The UEFI wiki page now includes this instruction. If for some bizarre reason you do not wish to do this, it may work to use a GPT partition map, UEFI boot and a fat 16 formatted EFI partition (this violates UEFI spec but may have the advantage of actually working). See https://bbs.archlinux.org/viewtopic.php?id=131149 and https://bbs.archlinux.org/viewtopic.php?id=133074.

−

If bluetooth doesn't work or stops working and cannot be unblocked by rfkill, check that it is enabled in the BIOS. If that's not the problem, a BIOS upgrade may help. See https://bbs.archlinux.org/viewtopic.php?id=137346.

+

If bluetooth doesn't work or stops working and cannot be unblocked by rfkill, check that it is enabled in the BIOS. If that's not the problem, a BIOS upgrade may help. See https://bbs.archlinux.org/viewtopic.php?id=137346. If that doesn't help either, boot to BIOS, reload the defaults, reconfigure BIOS and reboot. '''Note that this will wipe any entries in the EFI boot menu.''' (If anybody knows a less annoying way, please comment!)

VGA disconnect problems: https://bbs.archlinux.org/viewtopic.php?id=134886. The best "solution" appears to be to make the VGA output inactive ''before'' pulling the plug. This seems to prevent the confusion which otherwise ensues.

+

+

If you cannot power off when running on battery, see this thread for a possible solution: https://bbs.archlinux.org/viewtopic.php?id=133108. This seems to be unnecessary with systemd which is now default.

+

+

If you get errors on boot or resume complaining about the TPM, try changing the settings for the security chip in the BIOS as described in [https://bbs.archlinux.org/viewtopic.php?id=139415 this thread].

Contents

Arch user blogs about the x121e

Power saving options for the x121e

In /etc/rc.conf, add acpi-cpufreq to the MODULES array to enable CPU frequency scaling. If you use laptop-mode-tools, that's enough. Otherwise, add the governor you want to use, too e.g. cpufreq_ondemand.

Then add the following to the DAEMONS array:

either laptop-mode or cpufreq

acpid

sensors (if you want to monitor fan speed, temperature etc.)

thinkpad_acpi should be loaded automatically. Check this with lsmod | grep think.

Warning: Do not add these options without checking them out first as they may cause problems depending on your setup. Be prepared to disable them as necessary.

If using laptop-mode-tools stops your machine from shutting down while on battery power, try the solution described in this thread.

tp_smapi does not currently support the x121e and is apparently not likely to do so in the foreseeable future. Apparently the x121e is not quite a "real" ThinkPad.

Bluetooth

Getting bluetooth enabled can be a bit tricky. If bluetooth doesn't work or stops working and cannot be unblocked by rfkill, check first that it is enabled in the BIOS. If that isn't the problem, you may need a BIOS upgrade (see below).

Even after a BIOS upgrade, it seems that bluetooth may stop working in some cases. For example, changing the RAM in my machine seems to result in a hard block which rfkill can't touch even though bluetooth is enabled in BIOS. Repeating the post-bios-upgrade procedure of loading the default BIOS settings, booting and then redoing your custom settings seems to help. (I don't know if the reboot with the default settings is actually needed or if loading the defaults, saving them and then re-customising would be enough.) If you do this, remember that you may need to re-add grub to your boot menu to get everything working normally again. (This applies to GRUB2, at least.)

Arch Forums x121e related threads

Some people experience difficulties booting if their disk is partitioned using a GPT partition map. The correct way to avoid this problem is to ensure that the EFI partition is at least 512M. The UEFI wiki page now includes this instruction. If for some bizarre reason you do not wish to do this, it may work to use a GPT partition map, UEFI boot and a fat 16 formatted EFI partition (this violates UEFI spec but may have the advantage of actually working). See https://bbs.archlinux.org/viewtopic.php?id=131149 and https://bbs.archlinux.org/viewtopic.php?id=133074.

If bluetooth doesn't work or stops working and cannot be unblocked by rfkill, check that it is enabled in the BIOS. If that's not the problem, a BIOS upgrade may help. See https://bbs.archlinux.org/viewtopic.php?id=137346. If that doesn't help either, boot to BIOS, reload the defaults, reconfigure BIOS and reboot. Note that this will wipe any entries in the EFI boot menu. (If anybody knows a less annoying way, please comment!)