Manjaro - User contributions [en]

Manjaro-ARM

2021-07-27T18:31:34Z

Haymaker: /* Tips and Tricks */ Remove empty section

__TOC__

=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=

===Downloading===

You can find installation images in the downloads section of the [https://manjaro.org/download/#ARM Manjaro Website] or at [https://osdn.net/projects/manjaro-arm/ OSDN] 
Find the image that matches your target device and desired edition.

===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.

=Supported Devices=

==Hardkernel==

{| 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
|-
| Release Year
| 2017
| 2017
| 2017
| 2019
| 2019
|-
| SoC Manufacturer
| Rockchip
| Rockchip
| Allwinner
| Rockchip
| Allwinner
|-
| Lithography
| 28nm
| 28nm
| 40nm
| 28nm
| 40nm
|-
| CPU
| RK3328
| RK3399
| A64
| RK3399
| A64
|-
| 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
|-
| 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
|-
| GPU
| Mali-450 MP2
| Mali-T860 MP4
| Mali-400 MP2
| Mali-T860 MP4
| Mali-400 MP2
|-
| Memory
| 1–4GB LPDDR3
| 2–4GB LPDDR4
| 2GB LPDDR3
| 4GB LPDDR4
| 2–3GB LPDDR3
|}

==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
|}

===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/ 
 

[[Category:Contents Page]]

Openbox

2021-07-25T18:07:38Z

Haymaker: /* Adjusting keybindings */ Change subheadings to make clear these are just examples

__TOC__

=Overview=

The [http://openbox.org/wiki/Main_Page Openbox Window Manager] is designed to be highly configurable and customisable with extensive standards support.

[[File: Openbox-wm-18.jpg|left|600px]]
<div style="clear: both"></div>

=Installing Openbox=

For information on how to install a basic Openbox environment please review the [[Install_Desktop_Environments#Openbox|Openbox installation instructions]].

=Adjusting keybindings=

Openbox is built to be customized, and this includes the ability to create your own custom '''keybindings'''. These are combinations of key presses that may be used to undertake virtually any action, usually much faster and more directly than other means, such as by sifting through a menu. Although the Manjaro Openbox Edition provides a user-friendly graphical interface that may be used to alter or create custom keybindings, some combinations of special keys are not easily managed through this interface.

In this instance it will be necessary to manually edit the Openbox {{ic|rc.xml}} file. One of the many functions of this file is to store and enable keybindings in the Openbox environment. This file is located at {{ic|~/.config/openbox/rc.xml}} and you can edit it with a standard [[Viewing_and_editing_configuration_files|text editor]].

==Example: screen brightness==
Once the file has been opened, you will be presented with a substantial amount of commands contained within it. Don't worry about this, as you will only need to add a new block of code, rather than amend anything that is there. The code that must be added to enable full manual control over the screen brightness is as follows:

<keybind key="XF86MonBrightnessUp">
<action name="Execute">
<command>xbacklight +10</command>
</action>
</keybind>
<keybind key="XF86MonBrightnessDown">
<action name="Execute">
<command>xbacklight -10</command>
</action>
</keybind>

{{warning|This code cannot just be placed anywhere in the file. It must be placed in a particular section in order to work. Please follow the instructions below to do so.}}

To find the correct place to insert the above commands, it is recommended to use the '''Find''' or '''Search''' functions provided by your editor. If your text editor does not have the ability to search, it will be necessary to manually scroll down to about the mid-way point (perhaps using the '''Page Down''' key) to locate the following code:

</keyboard>

The overall section of the code should look like this:

</keybind>
</keyboard>
<mouse>

Once located, the new code above can be inserted between the </keybind> and </keyboard> codes. Press <enter> after the </keybind> code to provide a space to do so. Below is an example where this has taken place. The new code inserted has been '''highlighted in green''' for illustrative purposes:

</keybind>
 <keybind key="XF86MonBrightnessUp">
 <action name="Execute">
 <command>xbacklight +10</command>
 </action>
 </keybind>
 <keybind key="XF86MonBrightnessDown">
 <action name="Execute">
 <command>xbacklight -10</command>
 </action>
 </keybind>
</keyboard>
<mouse>

If the command "xbacklight +10" does nothing, find out the minimum value to put instead of 10 by trying to set the brightness to 20, then 40. You can use the following commands:

* `xbacklight =X` to change the brightness, and
* `xbacklight -get` to see if the minimum value has been reached.

Once you have made the necessary amendments to the file, save the changes and close it.

Now logout and back in again for the changes to take effect.

==Example: volume keys (ALSA)==

Once the file has been opened, you will be presented with a substantial amount of commands contained within it. Don't worry about this, as you will only need to add a new block of code, rather than amend anything that is there. The code that must be added to enable full manual control over the volume (i.e. to raise, lower, and mute it) is as follows:

<keybind key="XF86AudioRaiseVolume">
<action name="Execute">
<command>amixer set Master 10%+</command>
</action>
</keybind>
<keybind key="XF86AudioLowerVolume">
<action name="Execute">
<command>amixer set Master 10%-</command>
</action>
</keybind>
<keybind key="XF86AudioMute">
<action name="Execute">
<command>amixer set Master toggle</command>
</action>
</keybind>

{{warning|This code cannot just be placed anywhere in the file. It must be placed in a particular section in order to work. Please follow the instructions below to do so.}}

To find the correct place to insert the above commands, it is recommended to use the '''Find''' or '''Search''' functions provided by your editor. If your text editor does not have the ability to search, it will be necessary to manually scroll down to about the mid-way point (perhaps using the '''Page Down''' key) to locate the following code:
</keyboard>

The overall section of the code should look like this:

</keybind>
</keyboard>
<mouse>

Once located, the new code above can be inserted between the </keybind> and </keyboard> codes. Press <enter> after the </keybind> code to provide a space to do so. Below is an example where this has taken place. The new code inserted has been '''highlighted in green''' for illustrative purposes:

</keybind>
 <keybind key="XF86AudioRaiseVolume">
 <action name="Execute"> 
 <command>amixer set Master 10%+</command>
 </action>
 </keybind>
 <keybind key="XF86AudioLowerVolume">
 <action name="Execute">
 <command>amixer set Master 10%-</command>
 </action>
 </keybind>
 <keybind key="XF86AudioMute">
 <action name="Execute"> 
 <command>amixer set Master toggle</command>
 </action>
 </keybind>
</keyboard>
<mouse>

Once you have made the necessary amendments to the file, save the changes and close it.

[[Category:Contents Page]]
[[Category:Desktop]]