If you use AntergosPrime please do not upgrade SDDM.
There’s maybe a problem with the newest version (sddm-0.17.0-3), however not with sddm-0.17.0-2.
I am not 100% sure if this is a local problem on my system or for anybody.
However just as a little warning, that this might causes a problem that you can not start your system with the NVIDIA GPU anymore.
If you want update your system, you can also just upgrade it and later downgrade the package
sddmwith the awesome tool
downgraderfrom the AUR.
Get the tool with yaourt or your favourite AUR-helper:
yaourt -S downgraderor e.g.
pacaur -S downgrader.
Syntax to downgrad is:
So for SDDM:
Maybe some @developers can mention this as a possible bug.
Unfortunately I can not track down this error today anymore, but I’ll have a look at it so I can say 100% sure if it’s a local problem or can happen for anybody.
EDIT: It looks like it there has been an update to
sddm-0.17.0-4which fixed the problem (at least for me ), so anybody should be good now
@joekamprad Unfortunately no. Antergos-Prime is only for intel / NVIDIA configs. For switching GPUs it’s using bbswitch (package of Bumblebee) so it would need a complete different approach for an AMD card:/
However maybe you can power down one GPU in a different way?
Have you looked here: https://wiki.archlinux.org/index.php/Hybrid_graphics ?
Problem is that you might need a script that switches your config files if you switch your GPUs, otherwise you have to do a lot by hand every time you switch your GPU (thats what Antergos-Prime does for NVIDIA users ;))
EDIT: Maybe check out this: https://www.unixmen.com/using-hybrid-graphic-card-intel-amd-arch-linux/
I have no intel / AMD config, so I can not test, but you might find better working solutions for AMD than NVIDIA
No problem I’ll do it.
I can also create an antergos-prime-lts package.
I’ll get back to you when it’s done.
Thanks a lot
if I suspend or hibernate my system e.g. close the laptop lid or do this with the KDE options I can not use the system anymore.
After some seconds after the login the system has problems with commands like “ls” or “cd” and freezes. Only pushing the power button can reboot the system. Other TTYs work only for showing plenty lines of errors, I added the errors for you guys, maybe someone has an idea.
EDIT: Adding a picture does not work for me??
So here’s the link to the imgur-image:
I tried different setups however I think this is a general problem.
Maybe the SSD gets unmounted???
I am using Antergos on a NVME m.2 SSD (root and home and swap) with a dual-boot, so Windows and the EFI partition are also on this SSD. Other files are on a HDD.
Here’s also the output of fdisk:
sudo fdisk -l [sudo] Passwort für $USER: Festplatte /dev/nvme0n1: 232,9 GiB, 250059350016 Bytes, 488397168 Sektoren Einheiten: Sektoren von 1 * 512 = 512 Bytes Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes Festplattenbezeichnungstyp: gpt Festplattenbezeichner: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX Gerät Anfang Ende Sektoren Größe Typ /dev/nvme0n1p1 2048 616447 614400 300M Windows-Wiederherstellungsumgebung /dev/nvme0n1p2 616448 821247 204800 100M EFI-System /dev/nvme0n1p3 821248 1083391 262144 128M Microsoft reserviert /dev/nvme0n1p4 1083392 209717247 208633856 99,5G Microsoft Basisdaten /dev/nvme0n1p5 209717248 217529747 7812500 3,7G Linux-Dateisystem /dev/nvme0n1p6 217529748 488397134 270867387 129,2G Linux-Dateisystem Festplatte /dev/sda: 931,5 GiB, 1000204886016 Bytes, 1953525168 Sektoren Einheiten: Sektoren von 1 * 512 = 512 Bytes Sektorgröße (logisch/physikalisch): 512 Bytes / 4096 Bytes E/A-Größe (minimal/optimal): 4096 Bytes / 4096 Bytes Festplattenbezeichnungstyp: gpt Festplattenbezeichner: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX Gerät Anfang Ende Sektoren Größe Typ /dev/sda1 2048 1953523711 1953521664 931,5G Microsoft Basisdaten
EDIT: It looks like it’s the partition nvme0n1p6 which makes problems which is my / directory.
I also found this bug, using
nvme_core.default_ps_max_latency_us=0as a GRUB option should work and fix the problem. However not for me. Maybe this is a different bug?
Hope someone can help
Almost tried everything
I simply packaged it, didn’t do any tests…
sudo pacman -S antergos-prime
I did a complete reinstall and used
antergos-primeso I now know exactly which packages are needed.
I have no idea of antergos packages but can you also the commands
sudo systemctl disable lightdmand
sudo systemctl enable sddm?
Or how @joekamprad recommended:
sudo systemctl -f enable sddm?
I guess than it would work ootb.
And maybe a message after a succesful installation that the user should switch to both GPUs after the installation once, using the following commands:
sudo prime-select inteland
sudo prime-select nvidia
Later then the user can change with this command the current GPU and just have to reboot.
Would be awesome
If you don’t have enough time then just send me a link on how to build packages for antergos