Laptop/Acer

From ArchWiki
< Laptop(Redirected from Acer Travelmate 370)
AcerAppleASUSDellFujitsuHPIBM/LenovoMSISamsungSonyToshibaOther

Aspire

Model version Date Video Sound Ethernet Wireless Bluetooth Power management Modem Other Remarks
Aspire 5100-3825 2006-12-18 (Arch Linux 0.8 Voodoo) Yes Yes Yes Yes Untested Untested: Hot keys
Aspire 1501LMi 2007-08-01 (Arch Linux 0.9 Don't Panic) Yes Yes Yes Untested Untested: Sleep Untested Untested: Hot keys
Aspire 5024 2006-05-23 (Arch Linux 0.7.2 Gimmick) Yes Yes Yes Yes Partial Untested Suspend: Video and Wi-Fi problems
Aspire 7720 2009-02 Yes Yes Yes Yes Yes Partial Untested card reader: only SD cards seem to work; special keys (Acer Arcade, direct access to browser/mail) seem to not work; FireWire: untested. Update BIOS to fix ACPI and wireless problems.
Hibernation: still flaky (often hangs in the middle of restoring)
Aspire 5745(P)G 2014-04-20 Yes Yes Yes Yes Untested Yes Install xf86-input-egalaxAUR for the P version touchscreen Update to BIOS v1.15 to see battery informations.
Aspire E5-573 2015-12 Yes Yes Yes Yes Untested Yes
Aspire 7730 2009-08 Yes Yes Yes Yes Yes Untested:
HDMI
Card reader
options snd-hda-intel model=laptop added to /etc/modprobe.d/sound.conf to get headphone output working
Problem booting install CD
Solved with ln -sf /dev/sr0 /dev/archiso at ramfs
Aspire 4935 2009-08 Yes Yes Yes Yes Untested Yes Untested No: Audio "hot key"/"touch panel"
Aspire 2920Z 2009-02 Yes Yes Yes Yes Yes Untested No: Blue e on the left
Aspire 5735z 2014-09-03 Yes Yes Yes Yes Untested Yes
Aspire E1-531 2016-07-01 Yes Yes Yes Yes Yes Yes
Aspire V3-572G 2017-09-11 Yes Yes Yes Yes Yes Yes Suspend/resume + nvidia prop. drivers ("gpu has fallen off the bus"). Fix/workaround: append rcutree.rcu_idle_gp_delay=1 acpi_osi=! acpi_osi="Windows 2009" to kernel parameters.
Aspire F5-573G-7791 2016-12-01 Yes Yes Yes Yes Yes Hibernation: Untested Untested
Webcam
HDMI
USB-C
See #Flaky Secure Boot. Reportedly fixed on firmware update 1.31.
Aspire E5-575G-5538 2017-02-01 Yes Yes Yes Yes Untested Hibernation: Untested See #Flaky Secure Boot.
Aspire E5-553-T337 2018-08-07 Yes Yes Yes Yes Yes Yes
Aspire E5-422G-68PL 2020-07-21 Yes Yes Yes Yes Yes Partial Disable "Advanced Features" for the Touchpad in BIOS to unlock more functions than with it on Windows. Sleep & Hibernation issues when R5 GPU gets used in any way
Aspire 3 A315-41-R09T 2019-03-01 Yes Yes Yes Yes Yes Yes Add ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2: fixes erratic behavior and stuck at boot or shutdown. noapic during installation only is suggested.
Aspire 3 A315-51-524S 2019-11-11 Yes Yes Yes Yes Yes Yes
Aspire 3 A315-53G-52A4 2019-11-01 Yes Yes Yes Yes Yes Yes
Aspire E5-476G 2019-06-01 Yes Yes Untested Yes Untested Yes
Aspire 5 A515-51G-5072 2020-06-01 Yes Yes Yes Yes Yes Yes If BIOS bootable USB detection is slow re/start the laptop again.
Add pci=noaer to disable error messages for Wi-Fi
Disable Wi-Fi power management if speed gets throttled on battery

AspireOne

Model version Date Video Sound Ethernet Wireless Bluetooth Power management Modem Other Remarks
AspireOne D255e 2011-04-27 Yes Yes Yes Yes Untested Untested
Aspire One Cloudbook 11 2016-08 Yes Yes Yes Yes Hibernate: Untested HDMI: Untested See #Flaky Secure Boot.

Travelmate

Model version Date Video Sound Ethernet Wireless Bluetooth Power management Modem Other Remarks
Travelmate 6292 2008-06-24 (Arch Linux 2008.06 Overlord) Yes Yes Yes Yes Yes Untested Untested Untested:
Hot keys
FireWire
TravelMate 8371G (TM8371G-944G32n) 2010-05 Partial: iGPU only Yes Yes Yes Yes Yes Fingerprint reader does not seem to have a driver No fan control
Suspend to RAM requires i8042.reset=1
TravelMate TimelineX 8473T 2016-02-01 Yes Yes Untested Yes Untested Untested Sound, sleep, wireless, brightness require configuration

Nitro

Model version Date Video Sound Ethernet Wireless Bluetooth Power management Modem Other Remarks
Nitro AN515-43 2022-02-01 Yes Yes Yes Yes No Yes Untested: HDMI For fan control, use nbfc-linuxAUR
Nitro VN7-572G 2019-02-01 Yes Yes Yes Yes Yes Yes Sound Recording: problem seems already reported
See #Flaky Secure Boot.
Nitro VN7-791G-74DL 2016-01-01 Yes Yes Yes Yes Yes Yes Fan control requires porting drivers from windows
Nitro VN7-792G-710p 2016-10-01 Yes Yes Yes Yes Yes Yes Untested: Webcam
HDMI
Nitro VN7-792G-751Y 2016-12-01 Partial Partial Yes Yes Yes Yes HDMI and Microphone do not work

Predator

Model version Date Video Sound Ethernet Wireless Bluetooth Power management Modem Other Remarks
Predator Helios 300, PH315-53 2021-07 Partial for NVIDIA Yes Yes Yes Yes Untested

Swift

Model version Date Video Sound Ethernet Wireless Bluetooth Power management Modem Other Remarks
Swift 3 SF315-52-52YN 2020-09-05 Yes Yes* Yes Yes Yes *See Acer Swift 5#Kernel modules parameters
Swift 5 SF515-51T 2019-06-01 Yes Yes* Yes Untested Yes *See Acer Swift 5#Kernel modules parameters
Enduro N3 EN314-51W-55LW 2021-08-28 Yes Yes Yes Yes Yes Yes Untested:
SD Card Reader
VGA
HDMI
USB-C DisplayPort
RS232
Smart Card Reader
Fingerprint Reader

Troubleshooting

Flaky Secure Boot

Some models have a peculiar Secure Boot implementation which requires the following workaround to boot successfully the installation medium:

  1. To start on a clean slate, clear trusted bootloaders within the Secure Boot settings
  2. Save, reboot, return to UEFI
  3. Add the bootloader as a trusted UEFI file
    1. To add a file as a trusted bootloader, you may have to set a supervisor password: don't loose it
  4. Save, reboot, return to UEFI
  5. Disables Secure Boot
  6. The bootloader should now appear in the list even if Secure Boot is disabled

You may have to repeat these steps every firmware update.

Aspire 3 A315-56 internal storage not showing up

Tango-go-next.pngThis article or section is a candidate for moving to Acer Aspire 3 A315-56.Tango-go-next.png

Notes: This is getting long enough to warrant a dedicated page, if anyone with this laptop and enough time can make it while following Help:Laptop page guidelines? (Discuss in Talk:Laptop/Acer)

The firmware has a bug where you cannot see the internal SATA storage after first booting up. At boot (without CSM) the initial ramdisk is unable to see the internal storage due to this.

The only known solution to this is suspending and waking it up.

Add an early custom hook to put the laptop to sleep before the step to mount the filesystems:

/etc/initcpio/install/suspend-to-ram
#!/bin/bash
build() { 
        add_binary date
        add_runscript
}
help() {
        echo "Suspend to RAM before filesystems get mounted so the initial ramdisk can see the internal storage"
}
/etc/initcpio/hooks/suspend-to-ram
#!/bin/bash
run_hook() {
        FILE='/sys/class/rtc/rtc0/wakealarm'
        echo 0 > $FILE
        SEC=2
        EPOCH_TIME="$(date '+%s')"
        if ! echo "$((EPOCH_TIME + SEC))" > $FILE; then
                reboot -f
        fi
        if ! echo mem > /sys/power/state; then
                reboot -f
        fi
}

This custom hook will reset the RTC alarm clock and set an alarm 2 seconds into the future for device wake-up, so you do not have to manually wake-up the laptop.

Add it the mkinitcpio HOOKS:

/etc/mkinitcpio.conf
...
HOOKS=(base udev autodetect modconf block filesystems suspend-to-ram keyboard fsck)
...

Finally regenerate the initramfs.

Warning: If you are using a Solid State Drive as your internal storage, after waking up from sleep, your SSD will most likely have lost its "frozen" status and changed to "not frozen". This will leave your SSD vulnerable to any ATA Secure Erase commands, with anyone with root access being able to issue the aforementioned command and irrecoverably destroy all data on the SSD.

It is therefore highly recommended to issue a "SECURITY FREEZE" command immediately after waking up in order to block anyone from executing the ATA Secure Erase command. This can be done by adding add_binary hdparm to the build hook and adding the following code block to the runtime hook after putting the laptop to sleep and waking up:

sleep 2
hdparm --security-freeze /dev/disk/by-id/ata-name-of-your-ssd
Tip: Using this solution, when waking up from sleep, you cannot see the rest of the boot process until you reach the login screen, so consider adding rd.debug rd.log=file to your kernel parameters so you can see the boot messages from the initial ramdisk in /run/initramfs/init.log.