Manjaro ARM 21.06 released!

Manjaro ARM 21.06 released!

We are proud to announce the release of Manjaro ARM 21.06, which will soon be available via

This time we increased the amount of devices we do images for. You can find them all on
We also welcome 2 new official editions to the fold. Gnome and Sway editions.

Manjaro ARM is proud to be the default installation on the Pinebook Pro from Pine64.
We have put in a lot of work to get to this point and we are excited that we have been accepted by the creators of this laptop, as a great OS option.

Pine64 also recently announced that Manjaro ARM with Plasma Mobile is going to be the stock OS on the retail PinePhones going forward. What an honor!

Manjaro ARM Gnome edition!

New application for flashing images

We have been working on a new GUI app to make it easy for users to flash a Manjaro ARM image on to an SD card or eMMC card.
Ifyou are on Manjaro ARM, simply install manjaro-arm-flasher and launch the app “Manjaro ARM Flasher” from your menu. This will download and flash the image of your choice.

You can also manually run the application (if you are not running Manjaro ARM) by downloading this python script, make it executable with chmod +x manjaro-arm-flasher and then run it with sudo ./manjaro-arm-flasher. It requires python-blkinfo 0.1.3 to be installed, which can be installed with pip install blkinfo.

First Time setup

This release sports the First Time setup for all images, also via SSH. This means that at first boot, you will be asked about the following:

  • keyboard layout (except on pinebook, that is fixed to us layout)
  • username
  • additional user groups (optional)
  • full name
  • password for that username
  • password for root
  • timezone
  • locale
  • hostname

Then the setup script will set these settings and reboot to the login screen.



KDE Plasma




All the download links can be found on the website

Torrents are also available!


  • New packages from upstream and Manjaro ARM.
  • XFCE 4.16
  • KDE Plasma 5.22
  • Gnome 40.2
  • MATE 1.24
  • Sway 1.6
  • Most edition are now using Pipewire by default
  • Pacman 6.0

Updating from 21.04:

  • Most editions switched to Pipewire. To switch to Pipewire install pipewire-pulse and pipewire-alsa and reboot.

Known issues:

  • No audio cards on Roc-CC.

Tips and Tricks:

Smoothness on Raspberry Pi 3 devices:
To get a smoother experience on your Raspberry Pi 3 device, while running the Raspberry Pi 4 image do this:

  • Install xf86-video-fbturbo-git.
  • Edit /boot/config.txt and comment out dtoverlay=vc4-fkms-v3d and max_framebuffers=2.
  • Save the file and reboot.

Supported Devices:


  • Khadas Vim 2 (maintained by @spikerguy)
  • Khadas Vim 3 (maintained by @spikerguy)
  • Odroid C4
  • Odroid N2
  • Odroid N2+
  • Pine64-LTS
  • Pine-H64
  • Pinebook
  • Pinebook Pro
  • Raspberry Pi 4 (tested on Model B, Raspberry Pi 3 and Raspberry Pi 400) (maintained by @darksky)
  • Rock64
  • Rock Pi 4B
  • Rock Pi 4C (maintained by @spikerguy)
  • RockPro64

With Manjaro ARM Installer (in addition to the above devices): (Download it here)

  • Khadas Vim 1
  • Khadas Edge-V Pro
  • LibreComputer ROC-RK3328-CC
  • NanoPC T4
  • Odroid C2
  • Pine64+

What about other devices?

While we do make images for a lot of devices, we won’t be making images for all the supported devices. If your desired image for your desired supported device does not exist, please use manjaro-arm-installer to install it to an SD/eMMC card.


Please consider supporting Manjaro ARM directly via Patreon, Ko-Fi or Open Collective.
You can also donate to our upstream, which is Arch Linux ARM.


dtoverlay=vc4-kms-v3d is also working again on my rpi400, running sway.

does 210614 & 21.06 are the same except package update?

21.06 is based on stable branch, while 20210614 is a Dev image based on unstable branch.

210614 is arm-unstable
21.06 is arm-stable

so depends on what you want in a system, i toasted my 210614 install earlier in the day after the update left me with a frozen cursor on a gray screen.

unstable = newest untested stuff
stable = better for a daily driver

beat me to it, guess i type to slow.

does the same build profile?

Profile it uses is the same, yes, other than the changes that was made to it, from when 20210614 was made up to 21.06 was made.

Do you have or plan to have support for Apple M1 Macs since it is possible to run some Linux ARM distros via Parallels Desktop?

No current plans, no.

sway-21.06 stop BTRFS support(test)?

Hi @Strit and @spikerguy,

Just downloaded Gnome Khadas Vim3 21.06 and burn on USB. After numerous boot up (kernel panic due to linux-vim 12.9.1-1) during booting process or right after login, was able to finally switch to mainline linux 5.12.11-1.

I noticed that there is NO Hardware Acceleration eventhough /run/media/jfl/ROOT_MNJRO/etc/X11/xorg.conf.d/01-panfrost.conf is set to “glamor”.

Section "Device"
    Identifier  "Default Device"
    Driver      "modesetting"
    Option      "AccelMethod"    "glamor"     ### "glamor" to enable 3D acceler>

Section "ServerFlags"
        Option  "AutoAddGPU" "off"
        Option "Debug" "dmabuf_capable"

Section "OutputClass"
        Identifier "Panfrost"
        MatchDriver "meson"
        Driver "modesetting"
        Option "PrimaryGPU" "true"

 jfl@MNJROGTKPro    glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa/ (0xffffffff)
    Device: llvmpipe (LLVM 12.0.0, 128 bits) (0xffffffff)
    Version: 21.1.2
    Accelerated: no
    Video memory: 3773MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Mesa/
OpenGL renderer string: llvmpipe (LLVM 12.0.0, 128 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 21.1.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.1 Mesa 21.1.2
OpenGL shading language version string: 1.40
OpenGL context flags: (none)

Both in GNOME or GNOME Xorg session NO Hardware Acceleration. Appreciate yourguidance on how to enable Hardware Acceleration in GNOME or GNOME Xorg session?

Another perculiar situation is that the keyboard keys. @ key and " key are switched! Only in this Manjaro GNOME (keyboard selected is US).

@strit & @spikerguy,
Edit: For whatever reason, after reboot Hardware Acceleration is available on GNOME (Wayland) Session. For your info, I did not modify the /etc/X11/xorg.conf.d/01-panfrost.conf as it already set with “glamor” on first boot up or any other gdm3 settings. Will check GNOME Xorg session later and update.

Manjaro-Arm GNOME 40.2 desktop is quite different from the Ubuntu-Desktop (GNOME 3.38.5).

Edit 2: Login to GNOME Xorg, check with “glxinfo -B”, Panfrost NOT enabled. Open /etc/X11/xorg.conf.d/01-panfrost.conf: Option “AccelMethod” “none”. Changed to “glamor” and re-login to GNOME-Xorg session, Now Panfrost enabled.


For the keyboard settings: looks like a bug related to ISO/ANSI version of keyboard settings. Can you please check in the gnome settings?

Somehow the according to “Settings” the keyboard is “ENGLISH (UK)”. During the first boot up setup I have selected US keyboard, don’t know why the system configured “ENGLISH (UK)”. Resolve it by adding another keyboard “ENGLISH (US)” and select “ENGLISH (US)” on the top right menu bar.


Btrfs is an option when building the OS images via Manjaro-arm-tools. The default is ext4 (and it still seems to be the preferred option of most users). If you want to go with btrfs you can either build your own image, or use the Manjaro-arm-installer script…

I’m not into the details of this specific device, but the output device: llvmpipe caught my interest. To me looks like it falls back to a software rendering mode…

For the keyboard settings: looks like a bug related to ISO/ANSI version of keyboard settings. Can you please check in the gnome settings?

Will check for the keyboard issue… usually the oem-installer script should set the keyboard settings according to your selection on first boot…

Would like to thank @Strit and Manjaro Team for a great work on the new Manjaro-Arm GNOME Edition. This is the firm GNOME-Arm that I have use where GNOME-Wayland and GNOME-Xorg works with Desktop Acceleration (Panfrost Enabled) without any typical Panfrost visual artifacts. Two of the other distros GNOME-Xorg session have bad visual artifacts when desktop acceleration (Panfrost) is enabled. In Gnome-Wayland no or very minor visual artifacts.

So far Manjaro-Arm GNOME (40.2.0) both GNOME (Wayland) and GNOME-Xorg function well with desktop acceleration (Panfrost). Congratulation.

Don’t why the other distros I tried had issue on GNOME-Xorg session with Panfrost enabled.

sway took 10+ second to menu show up after login.
wonder it waiting wifi to connect?

which menu?
the first time you use anything, it creates settings & things.
just go about setting up, then reboot a few times & you’ll find it takes less time.

recommend you setup keyboard shortcuts in ~/.config/sway/config