Manjaro-architect 0.8


I’m happy to announce the version 0.8 of the new (unofficial) manjaro command line installer, manjaro-architect. The installer should now be stable enough for general use, although some exotic combinations of options can still result in dysfunctional system.

If your install media doesn’t include it, you can install manjaro-architect with the command

   sudo pacman -Sy manjaro-architect 

Manjaro-architect is a fork of the famous Architect Linux installer by Carl Duff, that has been modified to install manjaro instead of Arch linux. It is a netinstaller that downloads always the latest packages, so your system is always up to date after installation, regardless of how old your install media is.

Manjaro-architect offers currently unparalleled customization on your manjaro installation:

  • choose freely which kernel to use from all manjaro kernels. You can also choose multiple kernels.
  • choose your initsystem from systemd and openrc
  • choose any manjaro branch (stable, testing or unstable)
  • choose your desktop from all up to date manjaro editions, regardless of what install media you run the installer from. You can also choose to install just base system without graphical user interface.
  • add any number of unconfigured desktop environments
  • choose the default shell for user (bash, zsh or fish)
  • choose your graphics drivers that are installed with mhwd
  • choose arbitrary extra packages to be installed

Other features:

  • support for lvm and luks encryption
  • support for btrfs and nilfs root file system, as well as other common filesystems
  • translated to danish, dutch, english, french, german, hungarian, italian, portugese, russian and spanish (some translations may still be incomplete)

Changes sense last version can be found here:

Many thanks to our developers @oberon and @papajoke, and our most active testers @sueridgepipe and @eugen-b and all others that have contributed to the project!

What happened to Manjaro Net edition?
LVM installation on top of crypted partition
Manjaro OpenRC 17.0 Xfce ISO [RC]
[unstable] Manjaro-architect beta testing
What is the essence of Manjaro?
[Testing Update] 2017-03-22 - Elogind, Plasma, Deepin, Manjaro-Architect
512mb RAM - can't install Manjaro 17 XFCE - how to install on low ram PC?
[Stable Update] 2017-04-02 - Mesa-Stack, Kernels, Plasma, Firefox
Can't install due to missing /dev/rtc
Can't start instalation
Manjaro LXQt 17.0 (net edition)
Dell Inspiron 15 7567 4K

Just two little extra notes:

  • manjaro-architect package is currently only available on unstable branch

  • We provide a small GUI-less ISO of < 500MB with nothing but an architect-launcher installed.
    You simply login to the tty (maia-themed - couldn’t resist :rolling_eyes:) and type ‘setup’ .
    Now the latest available version of the architect will be downloaded, installed and launched.
    Like that we will be able to update the installer ‘on the fly’ as needed and you can use that ISO as long as you like without ever being outdated.

The Manjaro-Architect-ISO can be downloaded from >> here <<.


Menu structure is still very unituitive, illogical, and TBH barely usable. It is very obviously designed by technical users for technical users in its current form, which is inappropriate for an installer as predominently new users will be using it, but this is old news.

Why is update-grub run after each base install AND after each Manjaro desktop install? This makes no sense.

Free and non free drivers in Hardware drivers section are for video drivers, the current text doesn’t indicate this. Anyone without a knowledge of mhwd and how it works would be confused as hell with this layout.

Did a couple of installs and they worked, but the worlflow was clunky and for a new user to Manjaro would be very confusing.

The disparate technical components work, but as an overall installer it does not really work ATM.


Hi @sueridgepipe, you made a lot of very helpful suggestions about your idea of a more intuitive menu structure already in a very constructive way and you know that we are currently considering several different approaches for the future.
My impression right now is that you might have some hard feelings about not all your suggestions being integrated immediately and exactly as you find them best and I must say that I am quite surprised by your hard words after such intense and very constructive collaboration over the last time :disappointed:

I think the installer is very usable the way it is now already. Of course there will be continuous discussions about changes and improvements.


To simply move the automatic installation entries (free/proprietary) inside the ‘Install Display Driver’ submenu and label them ‘automatic’ will be clearer, I agree.



Just redid a test with latest version:

  • the header of the installer still shows 0.7 (see screeshot above, not an issue at all), version in pacman and the log is correct.
  • First tried an optimistic install with kernel 4.11 , additional kernel modules were not installed, no errors in the log:

    After a check the new modules are not available for 4.11, so I did a test with 4.10 and same result.
  • choose openrc as init system
  • I then choose a kde minimal install and was a bit surprised by the size (kde-desktop package is about 150 MiB):

    And got an error at the end:

    error is also present in the log
  • In the addiditional package section, is see some preselected packages which are not mandatory but the manjaro packages are not selected by default:
  • If I review the configuration files, i can see the systemd conf files not the openrc ones:
    <img src="/uploads/default/original/2X/b/b8b19a1e04c81a49f79127ec423442d2fd55d03e.png" width="150 height=“250”>
  • After reboot the the DM is not loaded. If I install the vbox modules not installed previously and reboot then the DM shows up correctly but the vboxservice is not started completely and the shared folders are not mounted.

Hope this helps

I’ve seen already a lot of improvements since the first versions and will continue to test further versions on VM, but will not do it on real HW for the moment as there are still many glitches.

Test environment:


That means linux411 was still installed? Might be a problem then because that module still doesn’t exist at all and maybe therefor installation also of linux410-module was aborted. Need to look into that!


Not at all, and I apologise if you interpreted my words as being harsh, it was genuinely not my intent.

I was simply repeating my previous views on the menu structure using more succinct language.

I am about to head out for the evening so I was a little rushed in my response… it was meant to be brief, not terse.



No I reinstalled with 4.10. Issue is present since a long time, I already reported it.

For me the selection screen can be removed as it does nothing afterwards.


good point. needs to be adjusted.


The kde-minimal profile consists of a lot more than that.
All packages listed here that is not preceeded by an >extra or >systemd tag in this case will be installed together with all their dependencies…


No problem with that but if there is 20 MiB difference between the full and the minimall, should it be an option?


Your suggestion about alternative menu structure is coming in the experimental branch, it takes some time to implement.

This is done by pacman hooks, pretty much nothing we can do about it without merging desktop and base installation. This is one of the reasons that I would have wanted to merge them for: many actions are repeated unnecessarily now. Mkinitcpio is run many times, grub is updated repeatedly and repos are synced twice.


Good question! :laughing: It’s a question for the profile in itself. The installer simply ‘sees’ the “minimal” and “extra” flags and so offers those options… :wink:
I’m opening issues about the kernel-modules problem the config files page and custom packages selection on our github

btw. discussing any problems or suggestions with the installer there is more than welcome. You will just need to create a github account for that …


Did you install vbox-video driver later in the process, or use the automatic driver installation? That should have installed host-modules also.
We are about to add a check for installed video-driver at the end of installation…


I forgot to bump version in the Makefile :rolling_eyes:
will adjust and build a pkgrel 2 :blush:


Just installed the virtualbox-guest-utils whih come with vboxsf, vboxvideo, vboxguest. On guest vm the host modules are not needed and the video driver is enough for the kernel.
mhwd does not recognize it which can be normal as not HW related.

The VBoxService is not launched by openrc, but the VBoxClient is.
The vboxservice is installed in systemd folders which can explain it.


please do not recommend to use -Sy in official announcements. instead, -Syu should ALWAYS be used as described in the warning here:


@excalibur1234 in a live environment it makes no sense to update the whole (live) system! @Chrysostomus is talking about installing a single up-to-date package there. In that context -Sy is perfectly fine and what we need.


We may be able to disable a hook

mv usr/share/libalpm/hooks/99-grub{.hook,}
run ...
mv usr/share/libalpm/hooks/99-grub{,.hook}

but if the second fonction is not run, we have a problem … hook never call