Acer Aspire E11 Series
Prior to installation, download and install the latest firmware update from Acer under Windows. Older versions of the firmware can only boot from the (black) USB 2.0 port.
To recover the Windows key at a later stage, run:
$ hexdump -C /sys/firmware/acpi/tables/MSDM
Create a recovery drive
A recovery drive can made with the preinstalled Acer eRecovery Management application. This requires a USB-attached flash drive or hard disk with at least 16 GB free space available, and presence of the
C:/OEM directory. All present data on the target drive will be lost.
Choose the option Create Factory Default Backup, select the partition Windows is installed on, and click start. Remove the drive afterwards - booting from the device will now start the recovery software. See  for more information.
The Acer E3-111 does not have an optical drive. See Category:Getting and installing Arch for alternative methods.
Both UEFI and Legacy (BIOS) boot are supported. To switch modes, press
F2 at the boot splash screen to enter the EFI setup, then select the Boot tab. Alternatively, access the EFI setup by rebooting in Windows.
- Installation images prior to
archlinux-2015.05.01-dual.isoreturn a row of errors when accessing the RPMB (Replay Protected Memory Block) partition from the eMMC. 
- eMMC device names start with
/dev/mmcblkinstead of the typical
- Due to limited RAM, it is recommended to create a swap partition of at least 2 GB in size.
To use Arch Linux with UEFI, activate the F12 boot menu option in the EFI setup and disable 'Secure' Boot. To do the latter, you must set a supervisor password beforehand. After disabling 'Secure' Boot, save the settings and reboot, then press F12 and select the USB drive with the Arch Linux setup files.
The first partition should be an EFI system partition. Make sure that the initramfs and vmlinuz-linux files are on the EFI partition, and that it is mounted at /boot. There is no way to specify kernel boot parameters in this computer's EFI setup so you have to go with a boot loader. Simple way is to install gummiboot and create a boot entry:
/boot/loader/entries/archlinux.conf: title Arch Linux linux /vmlinuz-linux initrd /intel-ucode.img initrd /initramfs-linux.img options root=/dev/mmcblk0p2 rootwait
This assumes that your root is on the second partition (first partition is the EFI partition) and states rootwait because the integrated flash storage is not available instantly after kernel startup. When you are done with the Arch setup, reboot and press F2 to enter the EFI setup. Enable 'secure' boot again, then choose the option 'select an UEFI file as trusted for executing' and browse to the gummiboot/gummibootx64.efi file, then press ENTER. Now disable 'secure' boot again, put the gummiboot loader on top of the list in the boot priority menu, and remove the supervisor password. Save the settings and reboot into your fresh Arch system.
.efifile to the location Windows uses. See UEFI#UEFI boot loader does not show up in firmware menu for details.
To use the Broadcom BCM43142 chipset is, install AUR, and load the module:AUR from the
# modprobe wl
The E11 series include a Precision Touchpad, which supports a variety of touch gestures. To enable the touchpad, append the
i8042.nopnp kernel parameter. See Touchpad Synaptics for configuration details.
You may need to use the linux-lst kernel for full support.
Suspend and Hibernate
Suspend and Hibernate should work after following Power management/Suspend and hibernate.
Start up and shutdown freeze
If you have an issue where the computer freezes during start up and shutdown, requiring multiple reboots, try adding the following to
blacklist dw_dmac blacklist dw_dmac_core
Bluetooth can't find any devices
Some laptops have an Atheros AR9565 Wifi/Bluetooth controller built in:
# lsusb ... Bus 001 Device 005: ID 04ca:3014 Lite-On Technology Corp. Qualcoom Atheros Bluetooth ...
Wifi works fine, the bluetooth controller is recognized but no bluetooth
devices are found. The problem is that as of Linux 4.3.3 this devices is not
ath9k.ko which loads the firmware files and patches into
the Atheros bluetooth controllers.
Quick and dirty fix, patching this USB ID into the modules (from: https://bbs.archlinux.org/viewtopic.php?pid=1433352):
cp -i ath3k.ko.gz ath3k.ko.gz.ori cp -i btusb.ko.gz btusb.ko.gz.ori gunzip ath3k.ko.gz btusb.ko.gz sed -e 's/\xca\x04\x10\x30/\xca\x04\x14\x30/g' ath3k.ko > a sed -e 's/\xca\x04\x10\x30/\xca\x04\x14\x30/g' btusb.ko > b mv a ath3k.ko mv b btusb.ko gzip ath3k.ko btusb.ko
You will still need to copy two firmware files (
Fortunately, Ubuntu Forums user Ephialta links to a Windows driver update archive (.cab) containing the missing firmware files: http://ubuntuforums.org/showthread.php?t=2260501&p=13207809#post13207809