Manjaro - User contributions [en]

Manjaro-ARM

2023-01-03T19:16:01Z

Strit: remove extra devices from ugoos

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 
Devices listed here are either supported by having device specific images, runs from the Generic images with board firmware on SPI or is still installable via the [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer Manjaro ARM Installer] script.

==Device List== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Hardkernel
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Odroid C2
| 2016
| Amlogic
| 28nm
| S905
| Quad-core: 4 x Cortex-A53
| 4 x 1.5GHz
| Mali-450 MP3
| 2GB DDR3
| No
|-
| Odroid C4
| 2020
| Amlogic
| 12nm
| S905X3
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G31 MP2
| 4GB DDR4
| No
|-
| Odroid N2
| 2019
| Amlogic
| 12nm
| S922X
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.0GHz 2 x 1.8GHz
| Mali-G52 MP4
| 2-4GB DDR4
| Yes
|-
| Odroid N2+
| 2020
| Amlogic
| 12nm
| S922X
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.4GHz 2 x 1.9GHz
| Mali-G52 MP4
| 2-4GB DDR4
| Yes
|-
| Odroid M1
| 2021
| Rockchip
| 22nm
| RK3568B2
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G52 2EE MC2
| 4–8GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Khadas
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Edge-V
| 2018
| Rockchip
| 28nm
| RK3399
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| 2 x 1.8GHz 4 x 1.5GHz
| Mali-T860 MP4
| 2-4GB LPDDR4
| No
|-
| Vim 1
| 2016
| Amlogic
| 28nm
| S905X
| Quad-core: 4 x Cortex-A53
| 4 x 1.5GHz
| Mali-450 MP3
| 2GB DDR3
| No
|-
| Vim 2
| 2017
| Amlogic
| 28nm
| S912
| Octa-core: 8 x Cortex-A53
| 8 x 1.5GHz
| Mali-T820 MP3
| 2-3GB LPDDR4
| No
|-
| Vim 3
| 2019
| Amlogic
| 12nm
| A311D
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.2GHz 2 x 1.8GHz
| Mali-G52 MP4
| 2-4GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Orange Pi
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Orange Pi 3 LTS
| 2019
| Allwinner
| 28nm
| H6
| Quad-core: 4 x Cortex-A53
| 4 x 1.8GHz
| Mali-T720 MP2
| 1-2GB LPDDR3
| No
|-
| Orange Pi 4 LTS
| 2021
| Rockchip
| 28nm
| RK3399
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 2-4GB LPDDR4
| No
|-
| Orange Pi 800
| 2022
| Rockchip
| 28nm
| RK3399
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 2-4GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Pine64
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Rock64
| 2017
| Rockchip
| 28nm
| RK3328
| Quad-core: 4 x Cortex-A53
| 4 x 1.5GHz
| Mali-450 MP2
| 1-4GB LPDDR3
| No
|-
| RockPro64
| 2017
| Rockchip
| 28nm
| RK3399
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 2-4GB LPDDR4
| Yes
|-
| Pine H64
| 2019
| Allwinner
| 28nm
| H6
| Quad-core: 4 x Cortex-A53
| 4 x 1.8GHz
| Mali-T720 MP2
| 2-4GB LPDDR3
| Yes
|-
| Pinebook
| 2017
| Allwinner
| 40nm
| A64
| Quad-core: 4 x Cortex-A53
| 4 x 1.152GHz
| Mali-400 MP2
| 2GB LPDDR3
| Yes
|-
| Pinebook Pro
| 2019
| Rockchip
| 28nm
| RK3399
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 4GB LPDDR4
| Yes
|-
| Pinephone
| 2019
| Allwinner
| 40nm
| A64
| Quad-core: 4 x Cortex-A53
| 4 x 1.2GHz
| Mali-400 MP2
| 2-3GB LPDDR3
| No
|-
| Pinephone Pro
| 2022
| Rockchip
| 28nm
| RK3399
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| 2 x 1.5GHz 4 x 1.5GHz
| Mali-T860 MP4
| 4GB LPDDR4 @800 MHz
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Radxa
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Rock Pi 4B & 4C
| 2019
| Rockchip
| 28nm
| RK3399
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 1–4GB LPDDR4
| Yes
|-
| Radxa Zero
| 2021
| Amlogic
| 12nm
| S905Y2
| Quad-core: 4 x Cortex-A53
| 4 x 1.8GHz
| Mali-G31 MP2
| 1-4GB LPDDR4
| No
|-
| Rock 3A
| 2022
| Rockchip
| 22nm
| RK3568
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G52 2EE
| 2-8GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Raspberry Pi
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Pi 3B
| 2016
| Broadcom
| 28nm
| BCM2837
| Quad-core: 4 x Cortex-A53
| 4 x 1.2GHz
| VideoCore IV
| 1GB LPDDR2
| No
|-
| Pi 3B+
| 2018
| Broadcom
| 28nm
| BCM2837B0
| Quad-core: 4 x Cortex-A53
| 4 x 1.4GHz
| VideoCore IV
| 1GB LPDDR2
| No
|-
| Pi 400
| 2020
| Broadcom
| 28nm
| BCM2711
| Quad-core: 4 x Cortex-A72
| 4 x 1.5GHz
| VideoCore VI
| 4GB LPDDR4
| No
|-
| Pi 4B
| 2019
| Broadcom
| 28nm
| BCM2711
| Quad-core: 4 x Cortex-A72
| 4 x 1.5GHz
| VideoCore VI
| 1-8GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Ugoos
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| AM6 Plus
| 2019?
| Amlogic
| 12nm
| S922XJ
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.2GHz 2 x 1.9GHZ
| Mali-G52 MP6
| 4GB LPDDR4
| No
|}

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

=Raspberry Pi Tips= 

==Sensors== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

==Overclocking== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

=Raspberry Pi Troubleshooting= 

==Pi 400 Power Button== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

==Blocked Update== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

==Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

=Unsupported Devices= 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-12-20T19:59:41Z

Strit: Redo the entire device list

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 
Devices listed here are either supported by having device specific images, runs from the Generic images with board firmware on SPI or is still installable via the [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer Manjaro ARM Installer] script.

==Device List== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Hardkernel
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Odroid C2
| 2016
| Amlogic
| 28nm
| S905
| Quad-core: 4 x Cortex-A53
| 4 x 1.5GHz
| Mali-450 MP3
| 2GB DDR3
| No
|-
| Odroid C4
| 2020
| Amlogic
| 12nm
| S905X3
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G31 MP2
| 4GB DDR4
| No
|-
| Odroid N2
| 2019
| Amlogic
| 12nm
| S922X
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.0GHz 2 x 1.8GHz
| Mali-G52 MP4
| 2-4GB DDR4
| Yes
|-
| Odroid N2+
| 2020
| Amlogic
| 12nm
| S922X
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.4GHz 2 x 1.9GHz
| Mali-G52 MP4
| 2-4GB DDR4
| Yes
|-
| Odroid M1
| 2021
| Rockchip
| 22nm
| RK3568B2
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G52 2EE MC2
| 4–8GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Khadas
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Edge-V
| 2018
| Rockchip
| 28nm
| RK3399
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| 2 x 1.8GHz 4 x 1.5GHz
| Mali-T860 MP4
| 2-4GB LPDDR4
| No
|-
| Vim 1
| 2016
| Amlogic
| 28nm
| S905X
| Quad-core: 4 x Cortex-A53
| 4 x 1.5GHz
| Mali-450 MP3
| 2GB DDR3
| No
|-
| Vim 2
| 2017
| Amlogic
| 28nm
| S912
| Octa-core: 8 x Cortex-A53
| 8 x 1.5GHz
| Mali-T820 MP3
| 2-3GB LPDDR4
| No
|-
| Vim 3
| 2019
| Amlogic
| 12nm
| A311D
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.2GHz 2 x 1.8GHz
| Mali-G52 MP4
| 2-4GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Orange Pi
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Orange Pi 3 LTS
| 2019
| Allwinner
| 28nm
| H6
| Quad-core: 4 x Cortex-A53
| 4 x 1.8GHz
| Mali-T720 MP2
| 1-2GB LPDDR3
| No
|-
| Orange Pi 4 LTS
| 2021
| Rockchip
| 28nm
| RK3399
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 2-4GB LPDDR4
| No
|-
| Orange Pi 800
| 2022
| Rockchip
| 28nm
| RK3399
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 2-4GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Pine64
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Rock64
| 2017
| Rockchip
| 28nm
| RK3328
| Quad-core: 4 x Cortex-A53
| 4 x 1.5GHz
| Mali-450 MP2
| 1-4GB LPDDR3
| No
|-
| RockPro64
| 2017
| Rockchip
| 28nm
| RK3399
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 2-4GB LPDDR4
| Yes
|-
| Pine H64
| 2019
| Allwinner
| 28nm
| H6
| Quad-core: 4 x Cortex-A53
| 4 x 1.8GHz
| Mali-T720 MP2
| 2-4GB LPDDR3
| Yes
|-
| Pinebook
| 2017
| Allwinner
| 40nm
| A64
| Quad-core: 4 x Cortex-A53
| 4 x 1.152GHz
| Mali-400 MP2
| 2GB LPDDR3
| Yes
|-
| Pinebook Pro
| 2019
| Rockchip
| 28nm
| RK3399
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 4GB LPDDR4
| Yes
|-
| Pinephone
| 2019
| Allwinner
| 40nm
| A64
| Quad-core: 4 x Cortex-A53
| 4 x 1.2GHz
| Mali-400 MP2
| 2-3GB LPDDR3
| No
|-
| Pinephone Pro
| 2022
| Rockchip
| 28nm
| RK3399
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| 2 x 1.5GHz 4 x 1.5GHz
| Mali-T860 MP4
| 4GB LPDDR4 @800 MHz
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Radxa
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Rock Pi 4B & 4C
| 2019
| Rockchip
| 28nm
| RK3399
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| 2 x 2.0GHz 4 x 1.5GHz
| Mali-T860 MP4
| 1–4GB LPDDR4
| Yes
|-
| Radxa Zero
| 2021
| Amlogic
| 12nm
| S905Y2
| Quad-core: 4 x Cortex-A53
| 4 x 1.8GHz
| Mali-G31 MP2
| 1-4GB LPDDR4
| No
|-
| Rock 3A
| 2022
| Rockchip
| 22nm
| RK3568
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G52 2EE
| 2-8GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Raspberry Pi
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Pi 3B
| 2016
| Broadcom
| 28nm
| BCM2837
| Quad-core: 4 x Cortex-A53
| 4 x 1.2GHz
| VideoCore IV
| 1GB LPDDR2
| No
|-
| Pi 3B+
| 2018
| Broadcom
| 28nm
| BCM2837B0
| Quad-core: 4 x Cortex-A53
| 4 x 1.4GHz
| VideoCore IV
| 1GB LPDDR2
| No
|-
| Pi 400
| 2020
| Broadcom
| 28nm
| BCM2711
| Quad-core: 4 x Cortex-A72
| 4 x 1.5GHz
| VideoCore VI
| 4GB LPDDR4
| No
|-
| Pi 4B
| 2019
| Broadcom
| 28nm
| BCM2711
| Quad-core: 4 x Cortex-A72
| 4 x 1.5GHz
| VideoCore VI
| 1-8GB LPDDR4
| No
|}
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Ugoos
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| AM6 Plus
| 2019?
| Amlogic
| 12nm
| S922XJ
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.2GHz 2 x 1.9GHZ
| Mali-G52 MP6
| 4GB LPDDR4
| No
|-
| Pi 3B+
| 2018
| Broadcom
| 28nm
| BCM2837B0
| Quad-core: 4 x Cortex-A53
| 4 x 1.4GHz
| VideoCore IV
| 1GB LPDDR2
| No
|-
| Pi 400
| 2020
| Broadcom
| 28nm
| BCM2711
| Quad-core: 4 x Cortex-A72
| 4 x 1.5GHz
| VideoCore VI
| 4GB LPDDR4
| No
|-
| Pi 4B
| 2019
| Broadcom
| 28nm
| BCM2711
| Quad-core: 4 x Cortex-A72
| 4 x 1.5GHz
| VideoCore VI
| 1-8GB LPDDR4
| No
|}

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

=Raspberry Pi Tips= 

==Sensors== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

==Overclocking== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

=Raspberry Pi Troubleshooting= 

==Pi 400 Power Button== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

==Blocked Update== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

==Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

=Unsupported Devices= 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-12-20T17:03:37Z

Strit: Move raspberry pi tips and troubleshooting to after supported devices lists

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 
Devices listed here are either supported by having device specific images, runs from the Generic images with board firmware on SPI or is still installable via the [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer Manjaro ARM Installer] script.

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Hardkernel
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Odroid C2
| 2016
| Amlogic
| 28nm
| S905
| Quad-core: 4 x Cortex-A53
| 4 x 1.5GHz
| Mali-450 MP3
| 2GB DDR3
| No
|-
| Odroid C4
| 2020
| Amlogic
| 12nm
| S905X3
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G31 MP2
| 4GB DDR4
| No
|-
| Odroid N2
| 2019
| Amlogic
| 12nm
| S922X
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.0GHz 2 x 1.8GHz
| Mali-G52 MP4
| 2-4GB DDR4
| Yes
|-
| Odroid N2+
| 2020
| Amlogic
| 12nm
| S922X
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.4GHz 2 x 1.9GHz
| Mali-G52 MP4
| 2-4GB DDR4
| Yes
|-
| Odroid M1
| 2021
| Rockchip
| 22nm
| RK3568B2
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G52 2EE MC2
| 4–8GB LPDDR4
| No
|}

==Khadas== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Orange Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Orange Pi
|-
| style="width: 12%"|
Model
| Orange Pi 3 LTS
| Orange Pi 4 LTS
| Orange Pi 800
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
|-
| CPU
| H6
| RK3399
| RK3399
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.8GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T720 MP2
| Mali-T860 MP4
| Mali-T860 MP4
|-
| Memory
| 1–2GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
|}

==Pine64== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
| Rock 3A
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 22nm
|-
| CPU
| RK3399
| S905Y2
| RK3568
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
| 2–8GB LPDDR4
|-
| Generic image support
| Yes
| No
| No
|}

==Raspberry Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry Pi
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>

==Ugoos== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="1" | Ugoos
|-
| style="width: 12%"|
Model
| AM6 Plus
|-
| Release Year
| 2019?
|-
| SoC Manufacturer
| Amlogic
|-
| Lithography
| 12nm
|-
| CPU
| S922XJ
|-
| CPU Topology
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 2.2GHz 2 x 1.9GHZ
|-
| GPU
| Mali-G52 MP6
|-
| Memory
| 4GB LPDDR4
|-
| Generic image support
| No
|}

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

=Raspberry Pi Tips= 

==Sensors== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

==Overclocking== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

=Raspberry Pi Troubleshooting= 

==Pi 400 Power Button== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

==Blocked Update== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

==Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

=Unsupported Devices= 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-12-20T16:55:11Z

Strit: */ Hardkernel */ Redo table to horizontal list

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 
Devices listed here are either supported by having device specific images, runs from the Generic images with board firmware on SPI or is still installable via the [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer Manjaro ARM Installer] script.

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="9" | Hardkernel
|-
| Model
| Release Year
| SoC Manufacturer
| Lithography
| CPU
| CPU Topology
| CPU Frequency
| GPU
| Memory
| Generic Image Support
|-
| Odroid C2
| 2016
| Amlogic
| 28nm
| S905
| Quad-core: 4 x Cortex-A53
| 4 x 1.5GHz
| Mali-450 MP3
| 2GB DDR3
| No
|-
| Odroid C4
| 2020
| Amlogic
| 12nm
| S905X3
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G31 MP2
| 4GB DDR4
| No
|-
| Odroid N2
| 2019
| Amlogic
| 12nm
| S922X
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.0GHz 2 x 1.8GHz
| Mali-G52 MP4
| 2-4GB DDR4
| Yes
|-
| Odroid N2+
| 2020
| Amlogic
| 12nm
| S922X
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| 4 x 2.4GHz 2 x 1.9GHz
| Mali-G52 MP4
| 2-4GB DDR4
| Yes
|-
| Odroid M1
| 2021
| Rockchip
| 22nm
| RK3568B2
| Quad-core: 4 x Cortex-A55
| 4 x 2.0GHz
| Mali-G52 2EE MC2
| 4–8GB LPDDR4
| No
|}

==Khadas== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Orange Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Orange Pi
|-
| style="width: 12%"|
Model
| Orange Pi 3 LTS
| Orange Pi 4 LTS
| Orange Pi 800
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
|-
| CPU
| H6
| RK3399
| RK3399
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.8GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T720 MP2
| Mali-T860 MP4
| Mali-T860 MP4
|-
| Memory
| 1–2GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
|}

==Pine64== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
| Rock 3A
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 22nm
|-
| CPU
| RK3399
| S905Y2
| RK3568
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
| 2–8GB LPDDR4
|-
| Generic image support
| Yes
| No
| No
|}

==Raspberry Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry Pi
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Ugoos== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="1" | Ugoos
|-
| style="width: 12%"|
Model
| AM6 Plus
|-
| Release Year
| 2019?
|-
| SoC Manufacturer
| Amlogic
|-
| Lithography
| 12nm
|-
| CPU
| S922XJ
|-
| CPU Topology
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 2.2GHz 2 x 1.9GHZ
|-
| GPU
| Mali-G52 MP6
|-
| Memory
| 4GB LPDDR4
|-
| Generic image support
| No
|}

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

=Unsupported Devices= 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T13:12:42Z

Strit: /* Supported Devices */ Add small description

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 
Devices listed here are either supported by having device specific images, runs from the Generic images with board firmware on SPI or is still installable via the [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer Manjaro ARM Installer] script.

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Orange Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Orange Pi
|-
| style="width: 12%"|
Model
| Orange Pi 3 LTS
| Orange Pi 4 LTS
| Orange Pi 800
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
|-
| CPU
| H6
| RK3399
| RK3399
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.8GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T720 MP2
| Mali-T860 MP4
| Mali-T860 MP4
|-
| Memory
| 1–2GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
|}

==Pine64== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
| Rock 3A
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 22nm
|-
| CPU
| RK3399
| S905Y2
| RK3568
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
| 2–8GB LPDDR4
|-
| Generic image support
| Yes
| No
| No
|}

==Raspberry Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry Pi
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Ugoos== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="1" | Ugoos
|-
| style="width: 12%"|
Model
| AM6 Plus
|-
| Release Year
| 2019?
|-
| SoC Manufacturer
| Amlogic
|-
| Lithography
| 12nm
|-
| CPU
| S922XJ
|-
| CPU Topology
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 2.2GHz 2 x 1.9GHZ
|-
| GPU
| Mali-G52 MP6
|-
| Memory
| 4GB LPDDR4
|-
| Generic image support
| No
|}

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

=Unsupported Devices= 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T13:08:04Z

Strit: Move Unsupported Devices out of Supported Devices and into it's own entry

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Orange Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Orange Pi
|-
| style="width: 12%"|
Model
| Orange Pi 3 LTS
| Orange Pi 4 LTS
| Orange Pi 800
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
|-
| CPU
| H6
| RK3399
| RK3399
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.8GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T720 MP2
| Mali-T860 MP4
| Mali-T860 MP4
|-
| Memory
| 1–2GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
|}

==Pine64== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
| Rock 3A
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 22nm
|-
| CPU
| RK3399
| S905Y2
| RK3568
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
| 2–8GB LPDDR4
|-
| Generic image support
| Yes
| No
| No
|}

==Raspberry Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry Pi
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Ugoos== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="1" | Ugoos
|-
| style="width: 12%"|
Model
| AM6 Plus
|-
| Release Year
| 2019?
|-
| SoC Manufacturer
| Amlogic
|-
| Lithography
| 12nm
|-
| CPU
| S922XJ
|-
| CPU Topology
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 2.2GHz 2 x 1.9GHZ
|-
| GPU
| Mali-G52 MP6
|-
| Memory
| 4GB LPDDR4
|-
| Generic image support
| No
|}

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

=Unsupported Devices= 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T13:06:10Z

Strit: Move the Raspberry Pi specific things back just below rpi device

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Orange Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Orange Pi
|-
| style="width: 12%"|
Model
| Orange Pi 3 LTS
| Orange Pi 4 LTS
| Orange Pi 800
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
|-
| CPU
| H6
| RK3399
| RK3399
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.8GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T720 MP2
| Mali-T860 MP4
| Mali-T860 MP4
|-
| Memory
| 1–2GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
|}

==Pine64== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
| Rock 3A
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 22nm
|-
| CPU
| RK3399
| S905Y2
| RK3568
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
| 2–8GB LPDDR4
|-
| Generic image support
| Yes
| No
| No
|}

==Raspberry Pi== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry Pi
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Ugoos== 

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="1" | Ugoos
|-
| style="width: 12%"|
Model
| AM6 Plus
|-
| Release Year
| 2019?
|-
| SoC Manufacturer
| Amlogic
|-
| Lithography
| 12nm
|-
| CPU
| S922XJ
|-
| CPU Topology
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 2.2GHz 2 x 1.9GHZ
|-
| GPU
| Mali-G52 MP6
|-
| Memory
| 4GB LPDDR4
|-
| Generic image support
| No
|}

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T12:57:45Z

Strit: Add Ugoos device

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Orange Pi==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Orange Pi
|-
| style="width: 12%"|
Model
| Orange Pi 3 LTS
| Orange Pi 4 LTS
| Orange Pi 800
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
|-
| CPU
| H6
| RK3399
| RK3399
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.8GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T720 MP2
| Mali-T860 MP4
| Mali-T860 MP4
|-
| Memory
| 1–2GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
| Rock 3A
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 22nm
|-
| CPU
| RK3399
| S905Y2
| RK3568
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
| 2–8GB LPDDR4
|-
| Generic image support
| Yes
| No
| No
|}

==Raspberry Pi==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry Pi
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Ugoos==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="1" | Ugoos
|-
| style="width: 12%"|
Model
| AM6 Plus
|-
| Release Year
| 2019?
|-
| SoC Manufacturer
| Amlogic
|-
| Lithography
| 12nm
|-
| CPU
| S922XJ
|-
| CPU Topology
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 2.2GHz 2 x 1.9GHZ
|-
| GPU
| Mali-G52 MP6
|-
| Memory
| 4GB LPDDR4
|-
| Generic image support
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T12:22:02Z

Strit: /* Radxa */ Add Rock 3A

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Orange Pi==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Orange Pi
|-
| style="width: 12%"|
Model
| Orange Pi 3 LTS
| Orange Pi 4 LTS
| Orange Pi 800
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
|-
| CPU
| H6
| RK3399
| RK3399
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.8GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T720 MP2
| Mali-T860 MP4
| Mali-T860 MP4
|-
| Memory
| 1–2GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
| Rock 3A
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 22nm
|-
| CPU
| RK3399
| S905Y2
| RK3568
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
| 2–8GB LPDDR4
|-
| Generic image support
| Yes
| No
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T12:15:20Z

Strit: /* Preparing the SPI (optional) */ Add EFI notes

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image] and our [https://github.com/manjaro-arm/generic-efi-images/releases generic EFI image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic (EFI) aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has).

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Orange Pi==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Orange Pi
|-
| style="width: 12%"|
Model
| Orange Pi 3 LTS
| Orange Pi 4 LTS
| Orange Pi 800
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
|-
| CPU
| H6
| RK3399
| RK3399
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.8GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T720 MP2
| Mali-T860 MP4
| Mali-T860 MP4
|-
| Memory
| 1–2GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|-
| Generic image support
| Yes
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T12:11:35Z

Strit: Add Orange Pi section

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Orange Pi==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="3" | Orange Pi
|-
| style="width: 12%"|
Model
| Orange Pi 3 LTS
| Orange Pi 4 LTS
| Orange Pi 800
|-
| Release Year
| 2019
| 2021
| 2022
|-
| SoC Manufacturer
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
|-
| CPU
| H6
| RK3399
| RK3399
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.8GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T720 MP2
| Mali-T860 MP4
| Mali-T860 MP4
|-
| Memory
| 1–2GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|-
| Generic image support
| Yes
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T11:55:29Z

Strit: /* Pine64 */ fix title column width

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="8" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|-
| Generic image support
| Yes
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T11:54:42Z

Strit: Fix title column width

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|-
| Generic image support
| Yes
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T11:53:25Z

Strit: /* Pine64 */ Add Quartz64

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
| Quartz64
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
| 2021
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
| 22nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
| RK3566
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-G52 2EE
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
| 4–8GB LPDDR4
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|-
| Generic image support
| Yes
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T11:46:53Z

Strit: /* Hardkernel */ Add Odroid M1

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
| Odroid-M1
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
| 2021
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
| Rockchip
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
| 22nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
| RK3568B2
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Quad-core: 4 x Cortex-A55
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
| 4 x 2.0GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
| Mali-G52 2EE MC2
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
| 4–8GB LPDDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
| No
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|-
| Generic image support
| Yes
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T11:41:11Z

Strit: /* Pine64 */ Pinebook does support Generic images

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
|-
| Generic image support
| No
| Yes
| Yes
| Yes
| Yes
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|-
| Generic image support
| Yes
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-11-14T11:40:07Z

Strit: /* Pine64 */ Add Pine H64

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.installer.img` file to a spare SD card. If the archive does not contain any spi.installer.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System. Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pine H64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
|-
| Release Year
| 2017
| 2017
| 2019
| 2017
| 2019
| 2019
| 2022
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Allwinner
| Rockchip
| Allwinner
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
|-
| CPU
| RK3328
| RK3399
| H6
| A64
| RK3399
| A64
| RK3399S
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-T720 MP2
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2–4GB LPDDR3
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
|-
| Generic image support
| No
| Yes
| Yes
| No
| Yes
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|-
| Generic image support
| Yes
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-06-20T15:13:12Z

Strit: Add Generic image support field to supported devices

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.imager.img` file to a spare SD card. If the archive does not contain any spi.imager.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
|-
| Generic image support
| No
| No
| Yes
| Yes
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
|-
| Release Year
| 2017
| 2017
| 2017
| 2019
| 2019
| 2022
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Rockchip
| Allwinner
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
|-
| CPU
| RK3328
| RK3399
| A64
| RK3399
| A64
| RK3399S
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
|-
| Generic image support
| No
| Yes
| No
| Yes
| No
| No
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|-
| Generic image support
| Yes
| No
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|-
| Generic image support
| No
| No
| No
| No
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-06-15T18:34:39Z

Strit: Add Radxa Zero to supported devices

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.imager.img` file to a spare SD card. If the archive does not contain any spi.imager.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
|-
| Release Year
| 2017
| 2017
| 2017
| 2019
| 2019
| 2022
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Rockchip
| Allwinner
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
|-
| CPU
| RK3328
| RK3399
| A64
| RK3399
| A64
| RK3399S
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="2" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
| Radxa Zero
|-
| Release Year
| 2019
| 2021
|-
| SoC Manufacturer
| Rockchip
| Amlogic
|-
| Lithography
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905Y2
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-G31 MP2
|-
| Memory
| 1–4GB LPDDR4
| 1–4GB LPDDR4
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-06-15T18:26:00Z

Strit: Add unsupported devices section

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.imager.img` file to a spare SD card. If the archive does not contain any spi.imager.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
|-
| Release Year
| 2017
| 2017
| 2017
| 2019
| 2019
| 2022
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Rockchip
| Allwinner
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
|-
| CPU
| RK3328
| RK3399
| A64
| RK3399
| A64
| RK3399S
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="1" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
|-
| Release Year
| 2019
|-
| SoC Manufacturer
| Rockchip
|-
| Lithography
| 28nm
|-
| CPU
| RK3399
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR4
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

==Unsupported Devices== 


In general, any device that does not have a device specific image or works with the Generic image, is considered unsupported. We may drop support for a device when the manufacturer no longer sells the device. The device is then considered EOL (End-Of-Life). Such a device might still work by updating and old image or running the Generic image, but we no longer work to keep it working.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-02-14T14:01:58Z

Strit: fix first link to generic image

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [https://github.com/manjaro-arm/generic-images/releases generic image]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.imager.img` file to a spare SD card. If the archive does not contain any spi.imager.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
|-
| Release Year
| 2017
| 2017
| 2017
| 2019
| 2019
| 2022
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Rockchip
| Allwinner
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
|-
| CPU
| RK3328
| RK3399
| A64
| RK3399
| A64
| RK3399S
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="1" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
|-
| Release Year
| 2019
|-
| SoC Manufacturer
| Rockchip
|-
| Lithography
| 28nm
|-
| CPU
| RK3399
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR4
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-02-14T14:00:57Z

Strit: Add instructions for SPI flashing

<languages/>
__TOC__

<translate>
=Overview= 


The Manjaro distribution, but for ARM devices.


Based on Arch Linux ARM, combined with Manjaro tools, themes and infrastructure to make install images for your ARM device, like the Pinebook and Raspberry Pi.


<div style="clear: both"></div>

=Installation= 

===Preparing the SPI (optional)===

Some boards have an SPI storage chip. This is a small storage device, usually 4-16 MB in size, that the board checks for firmware before proceeding to other devices. So we can utilize this chip, by preparing the board specific firmware on it, making it able to boot our [link generic images]. 
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.

# Go to the [https://github.com/Tow-Boot/Tow-Boot/releases latest release section] of Tow-Boot and download the file that matches your board. This is important.
#
# Unpack it and flash the `spi.imager.img` file to a spare SD card. If the archive does not contain any spi.imager.img file for your board, you should use one of our pre-built OS images instead, which has the Shared Storage version of U-boot installed.
#
# Insert the SD card into your device and boot from it. You will be presented with a short menu. One entry is "Flash Tow-Boot to SPI", second entry is "Erase SPI Flash" and the last option is "Reboot".
#
# Select the "Flash Tow-Boot to SPI" option and wait until it finishes successfully. It can take a couple of minutes as SPI storage is rather slow.
#
# When it's done, power off the device and take out the SD card. Now your device has the Tow-Boot board firmware in place and should now be capable of booting any generic aarch64 image that supports your board.

Our Generic Aarch64 image supports the Extlinux booting scheme so far.

===Downloading=== 


You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website]. 
Find the image that matches your target device and desired edition. 
Or if you have Board Firmware on your SPI, you can try our new [https://github.com/manjaro-arm/generic-images/releases Generic Aarch64 images].

===Writing the Installation Media=== 


The images are in a .xz file. These files can be burned directly to an SD card with Etcher or with dd directly. 
To manually install to your SD card with dd:


Extract the image.


unxz Manjaro-ARM-[Edition]-[Device]-[Version].xz


Get it on the SD card


sudo dd if=Manjaro-ARM-[Edition]-[Device]-[Version].img of=/dev/[device] bs=4M
Where ''[device]'' is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.

===Cleanup and First Boot=== 
Once you have the image on the SDCard, you should be able to put the card into your device and plug it in. If everything worked correctly, it should boot to the OEM setup. Here you define your username, passwords locales etc. Once that is done, the script will clean up after itself, resize the partition and reboot the device. After that reboot, it should boot to the Operating System Depending on the edition you have installed, this could be a simple TTY login or a graphical desktop environment.

===Resizing the partitions=== 
Since 18.09 this is now done automatically. The device will boot to OEM setup, which will handle the resizing, and then reboot before the login screen would appear. When it's booted to the login screen, the filesystem has been resized to fill out the remaining space on the SD card.

===Login=== 
Login depends on what you set up during the OEM setup.
There are 1 users by default on the image. root.
And by default it has no password and autologin enabled.
This gets changed when the OEM script is run, to disable the autologin and set the password defined during the setup.
</translate>
<translate>
=Supported Devices= 

==Hardkernel== 
</translate>
{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Hardkernel
|-
| style="width: 12%"|
Model
| Odroid-C2
| Odroid-C4
| Odroid-N2
| Odroid-N2+
|-
| Release Year
| 2016
| 2020
| 2019
| 2020
|-
| SoC Manufacturer
| Amlogic
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 12nm
| 12nm
| 12nm
|-
| CPU
| S905
| S905X3
| S922X
| S922X
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A55
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 4 x 2.0GHz
| 4 x 2.0GHz 2 x 1.8GHz
| 4 x 2.4GHz 2 x 1.9GHz
|-
| GPU
| Mali-450 MP3
| Mali-G31 MP2
| Mali-G52 MP4
| Mali-G52 MP4
|-
| Memory
| 2GB DDR3
| 4GB DDR4
| 2–4GB DDR4
| 2–4GB DDR4
|}

==Khadas==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Khadas
|-
| style="width: 12%"|
Model
| Edge-V
| Vim 1
| Vim 2
| Vim 3
|-
| Release Year
| 2018
| 2016
| 2017
| 2019
|-
| SoC Manufacturer
| Rockchip
| Amlogic
| Amlogic
| Amlogic
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 12nm
|-
| CPU
| RK3399
| S905X
| S912
| A311D
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Octa-core: 8 x Cortex-A53
| Hexa-core: 4 x Cortex-A73 2 x Cortex-A53
|-
| CPU Frequency
| 2 x 1.8GHz 4 x 1.5GHz
| 4 x 1.5GHz
| 8 x 1.5GHz
| 4 x 2.2GHz 2 x 1.8GHz
|-
| GPU
| Mali-T860 MP4
| Mali-450 MP3
| Mali-T820 MP3
| Mali-G52 MP4
|-
| Memory
| 2–4GB LPDDR4
| 2GB DDR3
| 2–3GB LPDDR4
| 2–4GB LPDDR4
|}

==Pine64==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="5" | Pine64
|-
| style="width: 12%"|
Model
| Rock64
| RockPro64
| Pinebook
| Pinebook Pro
| PinePhone
| PinePhone Pro
|-
| Release Year
| 2017
| 2017
| 2017
| 2019
| 2019
| 2022
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Rockchip
| Allwinner
| Rockchip
|-
| Lithography
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
| 28nm
|-
| CPU
| RK3328
| RK3399
| A64
| RK3399
| A64
| RK3399S
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 4 x 1.5GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.152GHz
| 2 x 2.0GHz 4 x 1.5GHz
| 4 x 1.2GHz
| 2 x 1.5GHz 4 x 1.5GHz
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
| 4GB LPDDR4 @800 MHz
|}

==Radxa==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="1" | Radxa
|-
| style="width: 12%"|
Model
| Rock Pi 4
|-
| Release Year
| 2019
|-
| SoC Manufacturer
| Rockchip
|-
| Lithography
| 28nm
|-
| CPU
| RK3399
|-
| CPU Topology
| Hexa-core: 2 x Cortex-A72 4 x Cortex-A53
|-
| CPU Frequency
| 2 x 2.0GHz 4 x 1.5GHz
|-
| GPU
| Mali-T860 MP4
|-
| Memory
| 1–4GB LPDDR4
|}

==Raspberry==

{| class="wikitable" style="text-align: center;width: 100%;"-- Header -->
!  
! colspan="4" | Raspberry
|-
| style="width: 12%"|
Model
| Pi 3B
| Pi 3B+
| Pi 4B
| Pi 400
|-
| Release Year
| 2016
| 2018
| 2019
| 2020
|-
| SoC Manufacturer
| Broadcom
| Broadcom
| Broadcom
| Broadcom
|-
| Lithography
| 28nm
| 28nm
| 28nm
| 28nm
|-
| CPU
| BCM2837
| BCM2837B0
| BCM2711
| BCM2711
|-
| CPU Topology
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A53
| Quad-core: 4 x Cortex-A72
| Quad-core: 4 x Cortex-A72
|-
| CPU Frequency
| 4 x 1.2GHz
| 4 x 1.4GHz
| 4 x 1.5GHz
| 4 x 1.5GHz
|-
| GPU
| VideoCore IV
| VideoCore IV
| VideoCore VI
| VideoCore VI
|-
| Memory
| 1GB LPDDR2
| 1GB LPDDR2
| 1–8GB LPDDR4
| 4GB LPDDR4
|}

<translate>
===Raspberry Pi=== 

====Sensors==== 


For temperature and humidity sensor see this tutorial on the forums: https://forum.manjaro.org/t/howto-raspberry-pi-temperature-and-humidity-sensor-dht22-dht11-am2302/34685

====Overclocking==== 


You can manage voltage and frequency settings in your <code>/boot/config.txt</code>. The following are the most common values for the Raspberry Pi:
<pre>
over_voltage=6
arm_freq=2100
gpu_freq=650
</pre>

===Troubleshooting=== 

====Pi 400 Power Button==== 


If you have trouble using the power button on your Pi 400 with the XFCE desktop (or xfce4-power-manager) then make sure logind is handling button events:
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true

====Blocked Update==== 


There are device-dependent workarounds if you experience an error similar to:
<pre>
error: failed to prepare transaction (conflicting dependencies)
:: brcm-patchram-plus and pi-bluetooth are in conflict
</pre>


For the '''Pi 3B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi3.service


For the '''Pi 3B+''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 4B''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi
sudo systemctl enable attach-bluetooth.service


For the '''Pi 400''':


sudo systemctl disable brcm43438.service
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi
sudo systemctl enable attach-bluetooth-pi400.service

====Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==== 


First, check whether the bootloader has been updated:
pacman -Ss raspberrypi-bootloader


Possible results:
core/raspberrypi-bootloader '''20210208-1''' [installed]
Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x '''20210208-1''' [installed]
Bootloader with extra codecs for Raspberry Pi


If it is the case, changing the occurrences of '''ttyAMA0''' in /boot/cmdline.txt to '''serial0''' may fix missing Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Source]).

==Android TV boxes== 


With a couple of small tweaks it is possible to boot and install the vim3 builds of Manjaro on some [[Amlogic TV boxes]]. Running Manjaro on TV boxes is not recommended for less experienced users of Linux nor serious production use.

=See also= 
https://wiki.archlinux.org/index.php/Category:ARM_architecture 
https://archlinuxarm.org/wiki 
https://osdn.net/projects/manjaro-arm/ 
 

</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:ARM{{#translation:}}]]

Manjaro-ARM

2022-02-01T15:45:18Z

Strit: remove osdn mention

Manjaro-ARM

2022-01-25T15:42:56Z

Strit: Add PinePhone Pro