User Tools

Site Tools


Acer Aspire V3-571


This is a report of my experience with installing and running Linux on the Acer Aspire V3-571.

This page is just for discussing using Linux on the Acer Aspire V3-571. For a general discussion about this laptop you can visit the Acer Aspire V3-571 page on LapWik.

Editing This Page

If you would like to edit this page please first view our Editing Guidelines.


For full specifications see the Acer Aspire V3-571 specifications page.

These are the specifictions from the original template. I have not modified them, but I have included the exact specifications of my machine in the Summary section.

NameAcer Aspire V3-571
ProcessorIntel Core i7-3612QM processor (6 MB L3 cache, 2.10 GHz with Turbo Boost up to 3.10 GHz)
Intel Core i5-3210M/i5-3320M/i5-3360M processor (3 MB L3 cache, 2.50/2.60/2.80 GHz with Turbo Boost up to 3.10/3.30/3.50 GHz)
Intel Core i3-3110M processor (3 MB L3 cache, 2.30 GHz, DDR3 1600 MHz, 35 W), i3-2350M/i3-2370M processor (3 MB L3 cache, 2.30/2.40 GHz)
Intel Core i3-3110M processor (3 MB L3 cache, 2.30 GHz, DDR3 1600 MHz, 35 W), i3-2350M/i3-2370M processor (3 MB L3 cache, 2.30/2.40 GHz)
Screen15.6“ HD 1366 x 768 resolution, high-brightness (200-nit) Acer CineCrystal LED-backlit TFT LCD
RAMUp to 8 GB
HDD320/500/640/750 GB or larger(depending on model)
Optical Drive4X Blu-ray Disc / DVD-Super Multi double-layer drive
8X DVD-Super Multi double-layer drive
GraphicsIntel HD Graphics 4000
NetworkRJ-45 port,Gigabit Ethernet
Acer InviLink Nplify 802.11b/g/n
Acer InviLink 802.11b/g

Linux Compatibility

Graphics ChipWorks
VGA OutNot Tested
HDMI OutNot Tested
Optical DriveWorks
MicrophoneWorksNot tested thoroughly
Headphone PortWorks
Microphone-In PortWorksNot tested thoroughly
WirelessWorksSee note 1.
BluetoothNot Tested
ModemNot present
FirewireNot Tested
Card ReaderNot Tested
WebcamWorksTested with cheese
Suspend/ResumeWorksSee note 2.


  1. I cannot connect to WiFi if bluetooth is enabled.
  2. Initially, the computer did not wake up after a suspend to RAM. Later, I discovered that the problem is probably caused by the 'acer_wmi' kernel module. Blacklisting it solved the problem.


Here comes a summary of the configuration of my Acer Aspire V3-571.

CPUIntel Core i5-3230M 2.6GHz with Turbo Boost up to 3.2GHz
GraphicsIntel HD Graphics 4000, up to 1760 MB Dynamic Video Memory
Screen15.6” HD LED LCD
RAM6GB DDR3 Memory
Hard disk500 GB
WiFiAcer Nplify 802.11a/g/n (Chip: Atheros Communications Inc. AR9462 Wireless Network Adapter (rev 01)

Here is the output of lspci:

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe (rev 10) 02:00.1 SD Host controller: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader (rev 10) 02:00.2 System peripheral: Broadcom Corporation Device 16be (rev 10) 02:00.3 System peripheral: Broadcom Corporation Device 16bf (rev 10) 03:00.0 Network controller: Atheros Communications Inc. AR9462 Wireless Network Adapter (rev 01)

Installation of Fedora 18

The Acer came with Windows 8 preinstalled.

I first made a backup of the recovery partition on a 32GB USB stick, as recommended by the Acer User manuel.

This laptop is equipped with UEFI instead of BIOS. I have changed 3 things in the UEFI.

  1. I have set a supervisor password (section “Security”). Without that it seemed impossible to disable 'Secure boot'.
  2. I have disabled 'Secure boot' (section “Boot”).
  3. I have enabled the boot menu such that it can be invoked with F12 at boot (section “Main”).

To enter the UEFI settings, press F2 just after power on or reboot.

I did not want to let the Fedora installer repartition the drive. So, I started the computer with the SystemRescueCD (see

Then I have used GParted to repartition the disk like so:

PartitionFile systemMount pointLabelSizeFlags
/dev/sda1ntfs Recovery400MiBhidden,diag
/dev/sda3unknown Microsoft reserved partition128MiBmsftres
/dev/sda4ntfs Acer100 GiB
/dev/sda6ntfs/windowsCommon8 GiB
/dev/sda7linux-swap 16 GiB
/dev/sda8ext4/fedora1816 GiB
/dev/sda9ext4/datadata32 GiB
unusedkept free for future experiments ±250 GiB
/dev/sda5ntfs Push Button Reset18.76 GiBhidden,diag

The partitions 1 through 5 where originally on the disk. The windows partition (partition 4) used the entire space up to partition 5, which is a recovery partition.

I have shrunk the Windows partition (/dev/sda4) from over 400 GiB to 100 GiB.

Remark that I did not move any partition. In particular I have left partition 5 at the end of the disk.

I did not mount the Windows partiton (/dev/sda4) in Fedora, but I have created a separate partition (/dev/sda6) to exchange data between the Windows and Linux system.

Then I have rebooted with the Fedora 18 netinstall disk and started the installation.

The Fedora 18 installer is very different from the earlier Fedoras. I did not like the new partitioning tool, but I managed to let it use the partitions I had prepared before. Remark especially that it is necessary to set the mount point '/boot/efi' to the EFI System Partition (/dev/sda2 in this case).

Intitially, I had 2 problems:

  1. After a suspend to RAM the system did not wake up again;
  2. I could not connect to WiFi when bluetooth was enabled.

I could solve the first problem by blacklisting the acer_wmi kernel module. To do so I have written a small text file no-acer-wmi.conf in /etc/modprobe.d with the following contents:

blacklist acer_wmi

Suspend/resume to/from disk now also works with Fedora 18, but I have had some problems, that I do not fully understand. Maybe they stem from the fact that I have also installed Arch Linux (my favourite Linux distribution) as a third operating system. At any rate, when I tried to resume Fedora 18 after a suspend to disk, Arch Linux booted, instead of Fedora 18. I don't know how suspend/resume is supposed to work in a multi-boot UEFI environment. I could get it to work by adding a boot entry for Fedora 18 in the GRUB2 of Arch Linux. I have also appended the boot parameter resume=/dev/sda7 where /dev/sda7 is the swap paratition.

From Arch Linux suspend/resume to/from disk does not work yet.

In this context, it is interesting to note that both Fedora 18 and Arch Linux boot and shutdown so quickly, that it is almost not worth while to try to use suspend/resume to/from disk.

Connecting to WiFi while bluetooth is enabled is still a problem.

I can confirm the note of jordicoma on 2012-12-19 about the brightness setting of the LCD screen, but again, it seems that the 'acer_wmi' kernel module was part of the problem. After blacklisting kernel module acer_wmi, I only had to append the boot parameter acpi_osi=Linux. So I have appended acpi_osi=Linux to GRUB_CMDLINE_LINUX in /etc/default/grub and I have run

grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

to append this boot parameter permanently. The keys 'Fn + Left arrow' and 'Fn + Right arrow' now control the brightness of the LCD screen, but the brightness setting returns to its default after a reboot.

Note: For the meaning of acpi_osi=Linux, I quote the text from kernel-parameters.txt from the kernel documentation:

acpi_osi= [HW,ACPI] Modify list of supported OS interface strings acpi_osi=“string1” # add string1 – only one string acpi_osi=“!string2” # remove built-in string2 acpi_osi= # disable all strings

UEFI Problems

I have had some hair raising UEFI problems at some point time.

The Aspire V3-571 has UEFI InsydeH20.

After having installed Fedora 18, I also installed Arch Linux, as a third operating system.

Arch Linux does not have an automated installation. I followed the In particular I installed the GRUB2 bootloader as follows:

grub-install –target=x86_64-efi –efi-directory=/boot/efi –bootloader-id=arch_grub –recheck

This also installed an UEFI boot option, as it should. So far, so good. I could boot all 3 operating systems: Fedora 18, Windows 8 and Arch linux. They all appeared in the boot menu which the UEFI InsydeH20 displays after pressing F12 at boot. I could also add boot entries for both Fedora and Windows in the GRUB menu of the Arch installation, such that I did not have to use the F12 button to boot Fedora or Windows.

The only “strange” thing I noticed was that “Fedora” was no longer shown in the “Boot” section of InsydeH20 which can be displayed by pressing F2 at boot. Only “Arch” and “Windows” were present.

Then I wanted to resinstall Fedora 18, with GNOME 3 instead of XFCE desktop which I had intially installed. I thought it would be a good idea to first clear the Fedora UEFI boot entry to force the Fedora installer to reinstall it, in the hope that it would then appear again in the “Boot” section of InsydeH20. To do so, I used the efibootmgr utility.




BootCurrent: 0003 Timeout: 2 seconds BootOrder: 0003,0002,0001 Boot0001* Windows Boot Manager Boot0002* Fedora Boot0003* arch

Then calling:

efibootmgr –disk /dev/sda –part 2 –bootnum 0002 –delete-bootnum




BootCurrent: 0003 Timeout: 2 seconds BootOrder: 0003,0002,0001 Boot0001* Windows Boot Manager Boot0003* arch

So, the Fedora boot entry was deleted, but it was still in the BootOrder. Trying to change the BootOrder with

efibootmgr –disk /dev/sda –part 2 –bootorder 0003,0001

did not work, 0002 stayed in the BootOrder.

Then I did something more drastic, with drastic results. I called:

efibootmgr –delete-bootorder

Then, only 0001 (Windows) was still in the BootOrder and it turned out to be impossible to get 0003 (Arch) back into the BootOrder. Even deleting and reintroducing the Arch boot option:

efibootmgr –disk /dev/sda –part 2 –bootnum 0003 –delete-bootnum efibootmgr –disk /dev/sda –part 2 –bootnum 0003 –loader \\EFI\\arch_grub\\grubx64.efi –label “arch”

did not work at all.

So, I was left with a computer that could only boot Windows. The efibootmgr could not help.

Then, fearing the worst, I reinstalled Fedora 18. The Fedora installer did at least restore the Fedora UEFI boot option. So, the F12 boot menu showed again Fedora 18 and Windows 8.

I could now also boot Arch by adding an entry for Arch in the Fedora GRUB2 menu, but I still wanted also Arch to appear in the UEFI boot options. efibootmgr did not help. Maybe, the grubinstall command that I had used when installing Arch (see above) could have worked, but I did not try that.

Instead I used the UEFI shell that is on the Arch linux installation CD. After booting into the UEFI shell, I issued this command:

bcfg boot add 3 fs0:\EFI\arch_grub\grubx64.efi “arch”

That worked. I verified it with:

bcfg boot dump -v

That showed that Arch was back in, but at the last place. I still wanted it to be first. So, I did:

bcfg boot mv 3 0

That also worked. I am happy again.

Invoking the boot menu with F12 at boot, shows the options Arch, Fedora, Windows in that order. But again, in the “Boot” section of the InsydeH20 utility that is displayed when pressing F2 at boot, only Arch and Windows are shown. Apparently, only 2 boot entries can be shown there and Windows is probably more or less hard coded there.

My conclusion is that the efibootmgr does not work well with InsydeH20 of the Acer Aspire V3-571. The Fedora installer, grub-install and the UEFI shell can manage the UEFI boot options, but I am very reluctant to do more experiments for fear of blocking the UEFI boot settings and making the computer unable to boot Linux.

With versions 3.9.9 and 0.6.0 of kernel and efibootmgr, this problem did not appear anymore. Unfortunately, I did not record the versions having this problem. Nevertheless, I keep this section because it is not impossible that someone else also encounters this problem and it shows how it can be solved.

rEFInd bootmanager

After reading Managing EFI Boot Loaders for Linux by Rod Smith, I have decided to replace the GRUB2 bootmanager/bootloader with the combination of the rEFInd bootmanager and the EFI-stub bootloader of the Linux kernel.

I have installed the rEFInd bootmanager on the EFI system partition, which is partition 2 on my computer, in the directory \EFI\refind.

In the directory \EFI\refind\drivers, I have installed the filesystem drivers ext4_x64.efi and iso9660_x64.efi.

Using the ext4 driver enables rEFInd and EFI to read the ext4 filesystems, such that I can avoid to copy the Linux kernels of my Linux systems to the EFI system partition.

reFInd can automatically detect Linux kernels on the partitions it can read, but I have decided to configure the boot entries manually. Here are the most important modifications that I have made to the refind.conf file:

# # refind.conf # Configuration file for the rEFInd boot menu # timeout 0 screensaver 300 resolution 1366 768 # Which types of boot loaders to search, and in what order to display them: # internal - internal EFI disk-based boot loaders # external - external EFI disk-based boot loaders # optical - EFI optical discs (CD, DVD, etc.) # hdbios - BIOS disk-based boot loaders # biosexternal - BIOS external boot loaders (USB, eSATA, etc.) # cd - BIOS optical-disc boot loaders # manual - use stanzas later in this configuration file # Note that the legacy BIOS options require firmware support, which is # not present on all computers. # On UEFI PCs, default is internal,external,optical,manual # On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual # #scanfor internal,external,optical,manual scanfor manual,external,optical # Manual configuration stanzas. Each begins with the “menuentry” # keyword followed by a name that's to appear in the menu (use quotes # if you want the name to contain a space) and an open curly brace # (“{”). Each entry ends with a close curly brace (“}”). Common # keywords within each stanza include: # # volume - identifies the filesystem from which subsequent files # are loaded. You can specify the volume by label or by # a number followed by a colon (as in “0:” for the first # filesystem or “1:” for the second). # loader - identifies the boot loader file # initrd - Specifies an initial RAM disk file # icon - specifies a custom boot loader icon # ostype - OS type code to determine boot options available by # pressing Insert. Valid values are “MacOS”, “Linux”, # “Windows”, and “XOM”. Case-sensitive. # graphics - set to “on” to enable graphics-mode boot (useful # mainly for MacOS) or “off” for text-mode boot. # Default is auto-detected from loader filename. # options - sets options to be passed to the boot loader; use # quotes if more than one option should be passed or # if any options use characters that might be changed # by rEFInd parsing procedures (=, /, #, or tab). # disabled - use alone or set to “yes” to disable this entry. # # Note that you can use either DOS/Windows/EFI-style backslashes (\) # or Unix-style forward slashes (/) as directory separators. Either # way, all file references are on the ESP from which rEFInd was # launched. # Use of quotes around parameters causes them to be interpreted as # one keyword, and for parsing of special characters (spaces, =, /, # and #) to be disabled. This is useful mainly with the “options” # keyword. Use of quotes around parameters that specify filenames is # permissible, but you must then use backslashes instead of slashes, # except when you must pass a forward slash to the loader, as when # passing a root= option to a Linux kernel. menuentry “Arch” { icon EFI/refind/icons/os_arch.icns volume arch loader /boot/vmlinuz-linux initrd /boot/initramfs-linux.img options “ro root=/dev/sda9 resume=/dev/sda7” submenuentry “Fallback initramfs” { initrd /boot/initramfs-linux-fallback.img } submenuentry “acpi_osi=Linux” { add_options “acpi_osi=Linux” } submenuentry “Single user mode” { add_options “1” } } menuentry “Arch KDE” { icon EFI/refind/icons/os_arch.icns volume archkde loader /boot/vmlinuz-linux initrd /boot/initramfs-linux.img options “ro root=/dev/sda8 acpi_osi=Linux resume=/dev/sda7” submenuentry “Fallback initramfs” { initrd /boot/initramfs-linux-fallback.img } submenuentry “acpi_osi=Linux” { add_options “acpi_osi=Linux” } submenuentry “Single user mode” { add_options “1” } } menuentry “Fedora 19” { icon EFI/refind/icons/os_fedora.icns volume fedora19 loader /boot/vmlinuz initrd /boot/initramfs.img options “ro root=/dev/sda10 resume=/dev/sda7” submenuentry “Single user mode” { add_options “1” } } menuentry “openSUSE” { icon EFI/refind/icons/os_suse.icns volume opensuse loader /boot/vmlinuz initrd /boot/initrd options “ro root=/dev/sda11 acpi_osi=Linux resume=/dev/sda7” submenuentry “Single user mode” { add_options “1” } } menuentry “GRUB2” { icon EFI/refind/icons/boot_linux.icns loader /EFI/arch_grub/grubx64.efi } menuentry “Windows 8” { icon \EFI\refind\icons\os_win.icns loader \EFI\Microsoft\Boot\bootmgfw.efi }

Finally, I have registered rEFInd with the UEFI of the computer by issuing the command:

efibootmgr –disk /dev/sda –part 2 –create –loader \\EFI\\refind\\refind_x64.efi –label rEFInd

I have also removed the GRUB2 of Fedora 8 with:

efibootmgr –disk /dev/sda –part 2 –bootnum 2 –delete-bootnum

Contrary to my earlier experience, efibootmgr now worked without problems.

Calling efibootmgr –disk /dev/sda –part 2 now displays:

BootCurrent: 0004 Timeout: 2 seconds BootOrder: 0004,0000,0001 Boot0000* arch_grub Boot0001* Windows Boot Manager Boot0004* rEFInd

as it should.

After rebooting, a nice graphical screen is displayed which lets us choose the operating system to load. You can see screenshots at the rEFInd project page on Sourceforge.

I like this setup very much. It is very nice, both visually and conceptually.

The rEFInd boot manager is installed completely on the EFI system partition. So, it is not linked to any of the operating systems installed on the computer.

If a bootable CD or USB-stick is present at reboot, rEFInd automatically detects it. No need to press F12 anymore.

When installing another Linux system, I request the installer to skip the installation of a bootloader.

To avoid having to update the refind.conf file everytime a new kernel is installed, I make sure that the filename of the kernels and initramfs do not change. Some Linux distributions do that automatically by installing symbolic links to the latest kernel and initramfs, e.g. Debian and openSUSE. Other Linux distributions, such as Arch Linux, always use the same filename for the installed kernel and initramfs. Some Linux distributions, such as Fedora, have different filenames for every version of kernel and initramfs. To solve that, I have installed symbolic links as follows.

On my Fedora 19 system, this is the result of ls -l /boot:

totaal 69324 -rw-r–r– 1 root root 127676 27 jun 21:29 config-3.9.8-300.fc19.x86_64 -rw-r–r– 1 root root 127676 4 jul 17:17 config-3.9.9-301.fc19.x86_64 drwxr-xr-x 3 root root 4096 5 jul 11:40 efi drwxr-xr-x 3 root root 4096 9 mei 2012 grub2 -rw——- 1 root root 25735201 5 jul 12:05 initramfs-0-rescue-ad09822025524c20ad9e937cc590cecc.img -rw——- 1 root root 16097654 5 jul 12:05 initramfs-3.9.8-300.fc19.x86_64.img -rw——- 1 root root 7937270 6 jul 11:42 initramfs-3.9.9-301.fc19.x86_64.img lrwxrwxrwx 1 root root 35 6 jul 11:44 initramfs.img → initramfs-3.9.9-301.fc19.x86_64.img -rw-r–r– 1 root root 558419 5 jul 12:04 initrd-plymouth.img -rw——- 1 root root 2595454 27 jun 21:29 -rw——- 1 root root 2595981 4 jul 17:17 lrwxrwxrwx 1 root root 29 6 jul 11:44 vmlinuz → vmlinuz-3.9.9-301.fc19.x86_64 -rwxr-xr-x 1 root root 5058584 5 jul 12:05 vmlinuz-0-rescue-ad09822025524c20ad9e937cc590cecc -rwxr-xr-x 1 root root 5058584 27 jun 21:29 vmlinuz-3.9.8-300.fc19.x86_64 -rwxr-xr-x 1 root root 5058520 4 jul 17:17 vmlinuz-3.9.9-301.fc19.x86_64

To maintain these symbolic links I have made a script /usr/sbin/ that I call after every kernel update:

#!/bin/sh # /usr/sbin/ echo “cd /boot” cd /boot echo “rm vmlinuz” rm vmlinuz echo “rm initramfs.img” rm initramfs.img LATEST_KERNEL=$(ls vmlinuz* | sort –version-sort –reverse | head –lines=1) echo “ln -s $LATEST_KERNEL vmlinuz” ln -s $LATEST_KERNEL vmlinuz LATEST_RAMFS=$(ls initramfs*.img | sort –version-sort –reverse | head –lines=1) echo “ln -s $LATEST_RAMFS initramfs.img” ln -s $LATEST_RAMFS initramfs.img

Alternative solution for LCD brightness

As I explained above, it is possible to get the Fn → and Fn ← keys to work by adding the bootparameter acpi_osi=Linux. However, that solution has 2 disadvantages: the brightness setting returns to maximum after each reboot and the brightness cannot be changed by the desktop environment software.

I have been able to implement another solution as explained in the Arch wiki about Intel graphics.

Instead of using the bootparameter acpi_osi=Linux, I have used bootparameter acpi_backlight=vendor.

Without acpi_backlight=vendor, there are 2 entries in /sys/class/backlight: acpi_video0 and intel_backlight. Then the Xorg-server uses the acpi_video0 control, which does not work on this computer.

With acpi_backlight=vendor, that there is only 1 entry in /sys/class/backlight/: intel_backlight. Then the Xorg-server uses the intel_backlight control, which does work.

Now, the backlight can be controlled by the desktop environment (XFCE in my case).

The Fn → and Fn ← keys now work via the XFCE software and probably also in many other desktop environments (I have only tested it in XFCE and KDE). The brightness can now also be controlled with the xbacklight utility.

But outside the desktop environment, the function keys don't work. That is the disadvantage of this solution.

To set the LCD brightness to about 50% at boot, I have installed a systemd service file /etc/systemd/system/setbacklight.service with the following contents:

[Unit] Description=Sets the backlight of the LCD screen to 488 [Service] Type=simple ExecStart=/bin/sh -c '/usr/bin/echo 488 > /sys/class/backlight/intel_backlight/brightness' [Install]

I have enabled this service with

systemctl enable setbacklight.service.

This alternative solution works for Arch Linux, Fedora 19 and Debian Wheezy, but fails for openSUSE 12.3.

In openSUSE 12.3, there is no /sys/class/backlight/intel_backlight. I suspect that this is a bug in some kernel versions. I think to remember that I initially had the same problem in Arch Linux and Fedora 18.


Wim Herremans

Last update: 2013-07-23

acer_aspire_v3-571.txt · Last modified: 2017/09/24 20:42 by don