Manjaro - User contributions [en]

Manjaro-ARM

2022-08-19T17:47:10Z

Sevens: /* Preparing the SPI (optional) */ Fix installer image name

<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
| 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-08-11T01:43:52Z

Sevens: Missing dot.

<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:}}]]

Pamac

2022-04-28T18:35:39Z

Sevens: Add missing word

<languages/>
__TOC__

<translate>
=Overview= 


Pamac (Add/Remove Software) is Manjaro's Package Manager. It is based on libalpm with AUR and Appstream support. It focuses on providing an easy to use interface while still providing a powerful set of features.


[[File:Pamac-gtk-main.png|center|800px]]

=Installing Pamac= 


Pamac is pre-installed on many Manjaro Editions but if your system does not have it it can be easily installed. Pamac comes in several different packages:
* {{ic|pamac-gtk}} - The GTK version of pamac. Includes a tray icon for many desktops.
* {{ic|pamac-cli}} - The command line version of pamac.
* {{ic|pamac-tray-icon-plasma}} - A tray icon for KDE plasma


These packages can be installed using pacman. For example, to install the GTK version, you can use the command:
sudo pacman -Syu pamac-gtk


{{tip|Both the GTK and Qt Pamac packages will automatically install the CLI version as well}}

=Using the Pamac GUI= 

==Installing Software== 


[[File:Pamac-gtk-optional-deps.png|left|thumb|400px]]


To install packages simply check check the box next to the packages. Once you have selected all the packages all the packages you want to install, click the Apply button at the bottom of the page.


If any of the packages have optional dependencies(packages that enable additional functionality) you will see a window like the one to the left which allows to select the ones you would like to install.
<div style="clear: both"></div>
[[File:Pamac-gtk-transaction-summary.png|left|thumb|400px]]


After you have selected optional dependencies, you should see a windows similar to the one pictured on the left. This lists all the packages that will be installed, upgraded or removed by the action. Once you have reviewed the list, press the Apply button to install the packages.


You may notice this list has more packages than you selected in the GUI. This is because many packages also have dependencies which are packages that must be installed in order for the software you selected to function properly. You may also notice that packages are being removed even though you didn't select any packages to remove. This is happening in the example to the left where you can see {{ic|clutter}} and {{ic|cogl}} are being removed. They are being removed because they conflict with {{ic|deepin-clutter}} and {{ic|deepin-cogl}} which provide the same functionality.
<div style="clear: both"></div>

==Removing Software== 


[[File:Pamac-gtk-remove-summary.png|left|thumb|400px]]


Removing software is as simple as unchecking the packages you want to remove and clicking the Apply button at the bottom of the page.


Once you do you should see a screen similar to the one on the left which lists all the packages that are about to be removed. You may notice this list contains more packages than you selected. This is because when you remove a package that other packages depend on, those packages are also removed.


{{warning|It is extremely important to carefully review the Transaction Summary before accepting the package removal. Some packages have many packages which depend on them and you don't want to inadvertently remove your whole Desktop Environment}}
<div style="clear: both"></div>

==Preferences== 


You can access the preferences by clicking on the three dots in the upper right corner and selecting preferences.


[[File:Pamac-gtk-preferences-general.png|left|thumb|400px]]


The General tab of preferences contains several settings, most of which are self explanatory.


* Remove unrequired dependencies - This removes dependencies which are no longer required by any package
* Check available disk space - Checks to ensure you have sufficient disk space available before downloading and installing packages
* Maximum parallel downloads - The number of concurrent downloads allowed
* Enable downgrade - This allows packages to be downgraded as well as upgraded. This is important when [[Switching_Branches|switching branches]].
* Check for updates - Disabling this will stop Pamac from looking for updates. In most cases, turning this off on a [[The Rolling Release Development Model|rolling release]] distro like Manjaro is a bad idea.
* Ignore updates for - This is a list of packages that you don't want to be upgraded. This is inherently dangerous practice and should only be used by advanced users.


{{warning|Ignoring updates for individual packages will leave you in an unsupported "partial upgrade" state. It is common for innocuous looking ignored packages to leave your system unbootable}}
<div style="clear: both"></div>


{{warning|'''DISCLAIMER:''' AUR scripts are created for Arch Linux by Arch Linux Users. AUR packages are user-produced content. These PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.}}


[[File:Pamac-gtk-preferences-aur.png|left|thumb|400px]]


Pamac is also capable of using scripts from the [[Arch User Repository|Arch User Repository(AUR)]] to install or update packages. Please carefully read the considerations in the [[Arch User Repository|linked page]] prior to enabling support for AUR.


If you enable AUR support, you may also select, "Check for updates from AUR" so software you install from AUR won't become outdated. An alternative is creating an account on AURweb and subscribe to notifications for the scripts you are using on a permanent basis.


Checking for "development package" updates will allow updates on *-git packages which are built from the latest source code to also be updated.


The "Build directory" is where AUR packages will be built. Using "tmp" usually will provide the best performance but very large packages may fail to build. In this case, select somewhere with more available space.
<div style="clear: both"></div>
[[File:Pamac-gtk-preferences-cache.png|left|thumb|400px]]


When Pamac installs packages, it keeps a copy of all the old packages you have downloaded. This cache can be very useful if you have to download packages in an emergency. However, left unchecked, this cache will grow very large over time. These preferences allow your cache to be automatically managed based on your preferences.


The first option allows you to set a number for how many copies of each package are retained. In other words, if you have downloaded 25 versions of firefox over the life of your install and you set this number to "3", only the most recent 3 versions will be retained. Unless you are very short on disk space, it is recommended to set this to at least 2.


By selecting "Remove only the versions of uninstalled packages" pamac will retain all versions of packages you still have installed.
<div style="clear: both"></div>

=Using the Pamac CLI= 


Pamac also includes a fully functional CLI for when you don't have a functional GUI or for those that prefer to manager packages that way.

==Locating and Installing Packages== 


To search for available packages you can use the command {{ic|pamac search}}. For example, to search the repos for packages containing the word smplayer:
<pre>pamac search smplayer
smplayer [Installed] 19.5.0-1 community
Media player with built-in codecs that can play virtually all video and audio formats
smplayer-skins [Installed] 1:15.2.0-2 community
Skins for SMPlayer
smplayer-themes [Installed] 1:18.6.0-1 community
Themes for SMPlayer</pre>


As you can see, this will also show you which packages are already installed. If you would like to search both the repos and [[Arch_User_Repository|AUR]] you add {{ic|-a}} like this:
<pre>pamac search -a smplayer
smplayer [Installed] 19.5.0-1 community
Media player with built-in codecs that can play virtually all video and audio formats
smplayer-skins [Installed] 1:15.2.0-2 community
Skins for SMPlayer
smplayer-themes [Installed] 1:18.6.0-1 community
Themes for SMPlayer
papirus-smplayer-theme-git 20181024-2 AUR
Papirus theme for SMPlayer (git version)
smplayer-svn 17.12.0.r8852-1 AUR
Advanced front-end for MPlayer/MPV
smplayer-svn-notitlebar 18.3.0.r8982M-1 AUR
Advanced front-end for MPlayer/MPV + Patch to disable titlebar in compact mode
smplayer-skins-svn 15.2.0.r8852-1 AUR
Skins for SMPlayer
smplayer-themes-svn 17.3.0.r8852-1 AUR
Themes for SMPlayer
smplayer-qt4 18.5.0-1 AUR
Complete front-end for MPlayer/MPV (Qt4)
rosa-media-player-plugin 1.0-2 AUR
The new multimedia player(based on SMPlayer) with clean and elegant UI (mozilla plugin only).
smplayer-theme-faenza (Out of Date: 09/15/2017) 2-2 AUR
Normal, dark and silver faenza theme for smplayer.
umplayer 0.98.2-2 AUR
An alternative to SMPlayer</pre>


Once you have identified the packages you wish to install you can install them with command {{ic|pamac install}}. For example, if we wanted to install {{ic|smplayer}} and {{ic|smplayer-themes}} we could use the command:
pamac install smplayer smplayer-themes


{{tip|When using install pamac will check to see if packages are installed and only install the ones not already installed}}


If you want to install packages from [[Arch_User_Repository|AUR]] you use the command {{ic|pamac build}}. Sticking with the above example, if you decided you wanted to install {{ic|umplayer}} instead you could use the command:
pamac build umplayer

==Removing Packages== 


The command {{ic|pamac remove}} can be used to uninstall packages installed from the repos or [[Arch_User_Repository|AUR]]. For example if you wanted to remove all the packages installed above you could use the command:
pamac remove smplayer smplayer-themes umplayer


{{warning|It is extremely important to carefully review the list of packages pamac presents before confirming. Some packages have many packages which depend on them and you don't want to inadvertently remove your whole Desktop Environment}}

==Identifying Installed Packages== 


To display a list of all installed packages you can use the command:
pamac list -i

==Displaying Detailed Package Information== 


To display detailed information on a package that is in the repos or installed on your system use the command {{ic|pamac info}}. Keeping with our example:
pamac info smplayer


If you also would like to check packages in [[Arch_User_Repository|AUR]] you could use:
pamac info -a smplayer

==Updating the System== 


To check if updates are available you can use the command:
pamac checkupdates -a


To update all installed packages installed from the repos or [[Arch_User_Repository|AUR]] you can use the command:
pamac upgrade -a


{{tip|pamac update and pamac upgrade are exactly the same. You can use them interchangably.}}

==Dealing with Orphaned Packages== 


To check to see if there any orphaned packages(packages which are no longer needed) installed you can use:
pamac list -o


To remove all orphans use the command:
pamac remove -o

==Cleaning the Cache== 


When pamac installs packages, it keeps a copy of all the old packages you have downloaded. This cache can be very useful if you have to install older packages in an emergency. However, left unchecked, this cache will grow very large over time.


Otherwise, to clear the cache completely, enter the following command (and use with care):
pamac clean


A safer way to remove old package cache files is to remove all packages except for the latest three package versions using:
pamac clean --keep 3

==Other Useful Pamac Functions== 


To see which package owns a certain file on your system, use the command {{ic|pamac search -f}}. For example:
pamac search -f /usr/bin/smplayer


To force a package to be installed even if it is already installed use {{ic|pamac reinstall}}. For example:
pamac reinstall smplayer

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