Manjaro-ARM
简介
用于 ARM 设备的 Manjaro 发行版。
基于Arch Linux ARM版，就像Pinebook和树莓派上的一样，打包了 Manjaro工具、主题和为您ARM设备制作安装镜像的基础工具。
安装
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 generic image and our generic EFI image.
We have currently tested Tow-Boot, so that's what this guide will use.
- Go to the 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).
下载
你可以在 Manjaro 网站 的下载区 或 OSDN 找到安装镜像。
找到你想要的，符合你的设备的版本。
写入安装媒介
镜像文件在用 .xz 结尾的文件中。 这种文件可以直接用 Etcher 或者 dd 写入到 SD 卡中。
如何用 dd 命令手动安装到你的 SD 卡：
提取镜像。
unxz Manjaro-ARM-[发行版本]-[设备]-[版本号].xz
将其导入 SD 卡
sudo dd if=Manjaro-ARM-[发行版本]-[设备]-[版本号].img of=/dev/[device] bs=4M
Where [device] is your SD card's device, as seen by lsblk. Usually mmcblk0 or sdb.
第一次启动和清理工作
一旦把镜像写入到 SD 卡上，你就应该可以把卡插到设备上启动了。 如果一切正常，设备会被引导到 OEM 设置。 在这里，你可以设置你的用户名、密码和区域等。 设置完成后，脚本会自动清理、调整分区大小并重启。重启后，根据你安装的版本进入操作系统（可能是简单的 TTY 登录或桌面环境登录）。
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 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.
支持的设备
Hardkernel
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
| 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 |
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 |
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 |
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 |
RaspberryPi
| 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 |
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 电视盒子
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.
故障排除
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
阻止更新
There are device-dependent workarounds if you experience an error similar to:
error: failed to prepare transaction (conflicting dependencies) :: brcm-patchram-plus and pi-bluetooth are in conflict
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
首先，检查引导程序是否已经更新：
pacman -Ss raspberrypi-bootloader
可能会出现的结果：
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 (Source).
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
另见
https://wiki.archlinux.org/index.php/Category:ARM_architecture
https://archlinuxarm.org/wiki
https://osdn.net/projects/manjaro-arm/
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 (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.