Manjaro ARM 19.04 released!


Manjaro ARM 19.04 released!

I am proud to announce the immediate availability of Manjaro ARM 19.04.

With this release is also our addition to the website. All our currently supported images can now be downloaded from

This release sports the custom install option for all images. This means that at first boot, you will be asked about the following:

  • username
  • password for that username
  • password for root
  • timezone
  • locale
  • keyboard layout (except on pinebook, that is fixed to us layout)
  • hostname

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



New images are available.

No torrents this time!


  • New kernels and packages all around.
  • LXQT 0.14.1
  • KDE/Plasma 5.15.4
  • Snappier performance on KDE/Plasma
  • Kernel on Rock64 changed to mainline linux-aarch64.
  • Firefox now ships with uBlock Origin and Youtube-Classic extensions.

Updating from 19.02:

  • Old releases should just keep on rolling.
  • To get some system commands to function correctly please run sudo chown -R root:root /etc on your device from the terminal. And then run sudo chown root:polkitd /etc/polkit-1/rules.d.
  • If you want the 19.04 experience, I recommend re-installing the system.

Known issues:

  • No lockscreen installed (LXQT only).
  • No audio cards on the rock64 and oc2.
  • For some reason I can't get audio to play on rpi3 anymore (any ideas?).

What about other devices?

Manjaro ARM is dropping armv7h support entirely this August. So if you have/use an armv7h device, you should be looking at other distro's that might fit your need. Some could be:

  • Arch Linux ARM
  • Armbian
  • Raspbian (for the raspberrypi)
  • Ubuntu Mate
  • Parabola

Firstly, I have already stopped making images for armv7h devices. No new images will be made.

From today I will also stop all the Manjaro package updates for armv7h. Packages directly from Arch Linux ARM will still get updated.

From June 1st, all package updates will stop for armv7h. That means, no more package updates for armv7h at all from June 1st. I will also remove any armv7h support still present in manjaro-arm-tools, arm-profiles and manjaro-arm-installer.

August 1st, the armv7h repo will be removed from the repo server and mirrors.

I am still working on supporting the rockpro64 and the Pinebook Pro.

I 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 card.


Please consider supporting Manjaro ARM via Patreon, Ko-Fi or to Manjaro's Paypal.


Just curious, is there a way to merge the installation images for the 4 devices together so that you don't have to build so many images? Like all of the Minimal in one, LXQt in one, KDE in one.


No. Each device has it's own bootloader and partition layout.


@Strit, this could well get a life on it's own.


Not sure I follow. A life on it's own? It's a separate community project already: :slight_smile:

1 Like

Amazing work as always!


Thanks for the update. Is there a reason why there is no KDE version for Rpi3? I understand that you can't generate all possible combinations, I am curious to understand why this one is not available.


Which device is used for this screenshot?

Did they release it ?

I would like to give some of my time to build and support devices which needs support - Only if someone can send it to me.

@Strit Can you please help me with some data and screenshots of LXQT on oc2, if you can contact someone who have oc2 to test?
I need to understand how is the GPU supported on oc2 ? I request oc2 users to contact me so I can understand what workaround did they do to make the gpu work.



Probably THE best update and the best OS for my pinebook. LXQT on the new Linux 5.0 kernel is rock solid! I had screen tearing in the past but with the Cedrus support released by the Linux mainlining effort these issues are now gone.

Thank you so much for your work.


Yes. The Rpi3 is simply not powerful enough to run it.

Device used for the screenshot is the pinebook.

Not yet.

Sure, explain what command output you need and what I need to screenshot and I will do that for you.

GPU works fine on the oc2. Manjaro ARM just has no hardware acceleration.


Cpu load with Firefox on with few tabs and youtube video playing.

Does it regoznise the gpu in neofetch? Check and share screenshot.

But without it how is the videos playing in 720p or above? And the framebuffer is slow in my case.


Have I ever claimed that it does? :stuck_out_tongue:

Will provide some into tomorrow for the rest.
I need to know which pages in the tabs in firefox.


Anything goes as long as you have 1 youtube page playing video and others like, etc.


Lol if a basic video wont work then there are very few use case for a DE on arm hahaha, headless server will be the only use without a gpu support.

Currently i am testing video with Chromium and i see 50% less load than Firefox.
Will share some screenshots soon.


Manjaro LXQT, MATE & KDE for Khadas Vim 1
CPU: Amlogic S905X
Core: Quad Core
GPU: Mali-450
RAM Type: DDR3


Wrong. Webpages are very different in how many resources they cause the browser to use.
So I need the specific pages you used, before you can make a direct comparison.

Then Manjaro ARM probably does not fit your usecase.

Sure, I would like to have GPU acceleration on all the devices, but that's not available in mainline kernel for the most part. It's almost there with the Pine64 boards, which have a really good track record of getting things mainlined. Those will have LIMA support in linux 5.2 and Mesa 19.1.

I have no idea about the state of Odroid devices.
And Raspberry Pi 3 probably will never get GPU acceleration on mainline, because they don't contribute much of their code upstream.


How do I install Manjaro ARM on the eMMC of my pinebook?


There are 2 ways:

  1. Take out the eMMC from the Pinebook and install it using an adapter.
  2. Copy the image onto an SD card that has a bootable OS on it, then dd the image to the internal eMMC.

Unfortunately my Pinebook 1080 boots only to a black screen. I believe there was a similar problem before.
What was the solution?


It looks that I have the same problem I had with the19.3 version.
The Pinebook boots and run, just the display does not come up.

Here are some sections from the Xorg.0.log that might shed some light on it for someone, although I am not sure what is the problem.

 17.209] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    17.210] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    17.219] (==) No Layout section.  Using the first Screen section.
[    17.219] (==) No screen section available. Using defaults.
[    17.219] (**) |-->Screen "Default Screen Section" (0)
[    17.219] (**) |   |-->Monitor "<default monitor>"
[    17.220] (==) No device specified for screen "Default Screen Section".
        Using the first device section listed.
[    17.221] (**) |   |-->Device "Allwinner A10/A13 FBDEV"
[    17.221] (==) No monitor specified for screen "Default Screen Section".


 17.771] (II) Loading sub module "fb"
[    17.771] (II) LoadModule: "fb"
[    17.772] (II) Loading /usr/lib/xorg/modules/
[    17.802] (II) Module fb: vendor="X.Org Foundation"
[    17.802]    compiled for 1.20.4, module version = 1.0.0
[    17.802]    ABI class: X.Org ANSI C Emulation, version 0.4
[    17.802] (**) FBTURBO(0): using shadow framebuffer
[    17.802] (II) Loading sub module "shadow"
[    17.802] (II) LoadModule: "shadow"
[    17.803] (II) Loading /usr/lib/xorg/modules/
[    17.816] (II) Module shadow: vendor="X.Org Foundation"
[    17.816]    compiled for 1.20.4, module version = 1.1.0
[    17.816]    ABI class: X.Org ANSI C Emulation, version 0.4
[    18.567] (II) FBTURBO(0): can't load 'g2d_23' kernel module
[    18.568] (II) FBTURBO(0): failed to enable the use of sunxi display controller
[    18.568] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp and /dev/g2d)
[    18.568] (II) FBTURBO(0): G2D hardware acceleration can't be enabled
[    18.568] (==) FBTURBO(0): Backing store enabled
[    18.574] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.574] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.574] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.574] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.574] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.574] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.574] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.574] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument


[    18.582] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.582] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.582] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.582] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.582] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.582] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.582] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.582] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[    18.582] (==) FBTURBO(0): DPMS enabled
[    18.582] (II) FBTURBO(0): failed to enable hardware cursor
[    18.582] (II) FBTURBO(0): no 3D acceleration because the driver has been compiled without libUMP
[    18.582] (II) FBTURBO(0): if this is wrong and needs to be fixed, please check ./configure log

For me these lines don't look so good.
If someone with a working Pinebook could compare their log and see what's different, maybe then the problem could be fond.

Just to explain the standard KDE version that is on the eMMC starts every time..

Every help appreciated