Several issues with the Graphical and Non-Graphical installers.

[maranda]

Hi all,

I recently moved away from Ubuntu on my ASUS Ultrabook (S56CM), I must admit I was about to frankly drop out the idea of having an Arch based distribution installed given all the issues I had installing Antergos (laptop requires UEFI & GPT), but I insisted out of stubborness because I needed a rollover distribution for working purpose (I'm a software developer).

I'll share some feedbacks about installation and also issues related to post-installation so sorry if I go a little out of topic, but I think this should improve user experience overall so it's relevant:

• UEFI installation using the Graphic installer, even if done manually, seems to fail at GRUB configuration (it doesn't find the EFI fw required files from the /installed mount point, sorry didn't manage to gather the related chchi logs)
• Setting it up via the CLI installer works as long as I use the EFI grubx64 bootloaded, but it seems to install a more limited set of packages compared to the other. And if there're differences between the CLI installer and the graphical one maybe it's a good idea to put 'em on pair regarding installed packages and features (see below)...

Note that it took also a lot of time to get Antergos to work properly post-install because:

• A good amount of presented Gnome3 functions were not functioning properly..
• Online accounts, since to use that you need telepathy-haze and it wasn't installed
• Empathy for the same reason since it missed all backends
• Hibernation and Suspension weren't working properly.. I had to configure kernel support install pm-tools, configure it to disable some modules prior of sleep and replace the scripts called by the related systemd services with the pm-tools executables
• A good amount of vital system services were disabled e.g. avahi, modemmanager etc.. some were not even installed and still disabled e.g. ntpd, gvfs essential plugins, tracker etc.

It's very possible a good chunk of issues were caused by my little "unacquintance" with systemd but..

It took me a day and a good half to have the laptop work properly which is far from desiderable for the average beginner user (and I sort of had an idea of where to put my hands into to straight things out). If for now using the CLI installer is the only option for UEFI / GPT enabled hardware owners maybe it should at least give the same amount of features available on the fly (I noticed it was 645 packages vs 745 or so).

Regards.

[lots0logs]

Were you using the latest code from testing branch? If not then MUCH has changed from the last official release. We are still working on the GPT and UEFI issues as can be seen here: #112 and here: #120 and here: #121 and here: #122 :stuck_out_tongue_winking_eye:

.. I had to configure kernel support install pm-tools, configure it to disable some modules prior of sleep and replace the scripts called by the related systemd services with the pm-tools executables

You definitely need to learn systemd (its not very hard) because that is not the best solution. It should be done with systemd.

If for now using the CLI installer is the only option for UEFI / GPI enabled hardware owners maybe it should at least give the same amount of features available on the fly (I noticed it was 645 packages vs 745 or so).

When we prepare a release their will not be any difference between the two. All of our attention is with Cnchi until it's time for a release then we catch up the CLI installer (well, normally @faidoc does hehe)

Ah, I have to go to work so I'll have to cut this short. Thanks for the feedback though! :thumbsup:

[maranda]

Yes it was the latest snapshot iso, with the other I couldn't get it to work at all.

Regarding pm-tools and systemd, it may not be the best solution but it's the only one that works for me, I couldn't get the system to resume correctly after using systemd-sleep hooks, while replacing the systemd-sleep call with the related pm util into the ExecStart directive of the service did the trick.

[lots0logs]

Hmmm...Mine works. Perhaps it varies based on hardware?

On Fri 07 Feb 2014 12:59:06 PM CST, Marco Cirillo wrote:

Yes it was the latest snapshot iso, with the other I couldn't get it to work at all.

Regarding pm-tools and systemd, it may not be the best solution but it's the only one that works for me, I couldn't get the system to resume correctly after using systemd-sleep hooks, while replacing the systemd-sleep call with the related pm util into the ExecStart directive of the service did the trick.

— Reply to this email directly or view it on GitHub https://github.com/Antergos/Cnchi/issues/123#issuecomment-34488155.

Dustin Falgout Antergos Developer

E-mail: dustin@falgout.us mailto:dustin@falgout.us Google/Skype: dustinfalgout Freenode IRC: #antergos http://webchat.freenode.net/?channels=antergos&uio=d4

Antergos http://antergos.com

[maranda]

@lots0logs I'm not sure.

However I decided to investigate a bit further (looking at how things are done in pm-utils) and got it to work in a more systemd-sleep compatible way but still won't work without pm-utils installed (calling modprob -r/modprob on pre/post directly fails to even make it suspend).

script I placed into /usr/lib/systemd/system-sleep:

#!/bin/sh
modules="uhci_hd button ehci_hd iwlwifi"

unload_modules()
{
    for module in $modules; do
        modunload $module
    done
}

reload_modules()
{
    modreload
}

action="$1-$2"
case $action in
   pre-suspend)
    unload_modules
    ;;
   post-suspend)
    reload_modules
    ;;
   pre-hibernate)
    unload_modules
    ;;
   post-hibernate)
    reload_modules
    ;;
esac

[karasu]

@lots0logs : I don't know what to do with this issue. It's not Cnchi related (just the UEFI part is, and that's already in other issues). The CLI part is faidoc's work :grin: Closing.

[lots0logs]

@karasu agreed. This has been addressed in Cnchi and we always take care of the CLI right before a release