Many (but not all) initial and common issues with Antergos (or many other systems) can be solved with the instructions and ideas shown in this thread.
Often the problems relate to booting, graphics, or hardware drivers. But the problems vary quite a lot, so precise answers are challenging to provide. Well, let’s try!
The more solutions we have, the better for all Antergos users!
- download the latest “full” ISO: https://antergos.com/try-it/
- “burn” the USB installer stick the right way: https://antergos.com/wiki/uncategorized/create-a-working-live-usb/
- UEFI vs. BIOS legacy systems require different methods related to booting, be sure to understand the main differences
- UEFI systems require an EFI partition (may already contain Windows stuff!), in vfat or FAT32 format. Disk has gpt partition table.
- BIOS legacy systems uses MBR. Disk has msdos partition table.
- optional: you may check (and even create) disk partitions with gparted program before installing
- advanced: terminal command lsblk -fm shows all partitions in detail
- many things to consider; easy start is to use and only one ext4 partition for Antergos (and an EFI partition in UEFI systems). Low RAM systems may need swap space, e.g. a swap file
- file systems: use ext4 if other alternatives don’t seem to work. Note that Linux cannot be installed on FAT32
- Sometimes Arch devs move official packages to AUR and that can create problems for the installer. As a workaround:
- check this for more info and a helper script
- edit /usr/share/cnchi/data/packages.xml and remove the problematic package reference
- restart the installer as root:
cnchi -p /usr/share/cnchi/data/packages.xml
- if grub menus generated by Antergos fail to boot other systems (in multiboot setup), see: grub-fix-generation
- download (or copy/paste) the PKGBUILD file
- run commands:
wget -q -O PKGBUILD https://github.com/manuel-192/Antergos/raw/master/grub-fix-generation/PKGBUILD makepkg -sic sudo update-grub reboot
Here are some useful ways to solve common problems. The following may apply to several problem types:
- update motherboard’s BIOS/firmware (NOTE: use exactly the right version for your machine!)
- install the correct driver for the hardware (check AUR if not in official packages)
- install another kernel (default is linux, try linux-lts), since sometimes kernel updates cause problems
- use dkms versions (e.g. nvidia-dkms) of packages (requires kernel headers: linux-headers and/or linux-lts-headers)
- downgrade (install package downgrade) a problematic package, but only temporarily until a real fix is available. Note that downgrading a package or library may cause problems in other packages or libraries, so be very careful if using it.
- users coming from other distros may find this useful: https://wiki.archlinux.org/index.php/Pacman/Rosetta
Graphics or booting related solutions
- change display manager (one of: lightdm, sddm, gdm). For example, commands to replace lightdm with sddm:
sudo pacman -S sddm sudo systemctl disable lightdm sudo systemctl enable sddm reboot
- blacklist unwanted graphics driver (e.g. nouveau)
- for Nvidia: use package nvidia-installer
- tip: use option
--testto see what would be changed
- tip: use option
- Intel graphics: older machines may require xf86-video-intel. For newer machines it is not recommended. If you have issues with Intel graphics, try to install (or uninstall) this package.
How to avoid some potential problems
- Rule of thumb: update your system at least once a week to keep it in good shape. Once a month or worse may cause annoying problems.
- Always write down changes you make to the system or settings! That may be very helpful later when trying to solve strange problems.
- Do not remove installed packages lightly, since that may render your install unable to boot. If you want to remove packages, make sure you know exactly what you are doing. Note that many packages have dependencies, so don’t delete the dependencies unless you are sure they are no more needed. However, usually AUR packages can be removed (unless it replaces a similar official package) without affecting your system’s stability. In case of problems, check the pacman logs at /var/log/pacman.log.
- In general, it is better to avoid AUR packages since they are not officially supported. Use them only if similar official package is not available and you really, really need that package. Still make sure the AUR package is not malware by reading its PKGBUILD file. If in doubt, you can show the PKGBUILD in the Antergos forum.
- Replacing or “blocking” official packages with AUR counterparts (or external packages) can cause hard to find problems.
pacman -Qmshows your installed foreign (usually AUR) packages.
Fixing stuff after install
- use arch-chroot to fix your system if you cannot boot the installed Antergos
And finally, don’t forget the mother of all remedies:
Reboot is important after making important system changes, like e.g. grub-mkconfig etc.
Some simple tips for troubleshooting
- start the app from a terminal and show the terminal output in case of trouble
- show logs and system info. There are quite a few logs (at /var/log) and system info apps available:
- systemctl status <service>
- inxi (AUR package)
More detailed info about the methods above are available have been discussed at the Antergos forum several times.
More info about the solutions above is available by searching the internet, especially at:
- Arch wiki
- Antergos wiki and forums
And Dear Reader, thanks for reading this far already!
If you have more solutions to common problems, please contribute and post them into this thread. Many other users are very happy to read the actual solutions!