8,560
edits
(Created page with "=Смотрите также= https://wiki.archlinux.org/index.php/Category:ARM_architecture<br /> https://archlinuxarm.org/wiki<br /> https://osdn.net/projects/manjaro-arm/<b...") |
(Updating to match new version of source page) |
||
Line 11: | Line 11: | ||
=Установка= | =Установка= | ||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
===Preparing the SPI (optional)=== | |||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
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].<br> | |||
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use. | |||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
# 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. | |||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
Our Generic Aarch64 image supports the Extlinux booting scheme, while our Generic EFI Aarch64 uses EFI enabled firmware (which tow-boot has). | |||
</div> | |||
===Загрузка=== | ===Загрузка=== | ||
<div class="mw-translate-fuzzy"> | |||
Установочные образы можно найти в разделе загрузок на [https://manjaro.org/download/#ARM сайте Manjaro] или на [https://osdn.net/projects/manjaro-arm/ OSDN]<br>. | Установочные образы можно найти в разделе загрузок на [https://manjaro.org/download/#ARM сайте Manjaro] или на [https://osdn.net/projects/manjaro-arm/ OSDN]<br>. | ||
Найдите образ, который соответствует вашему целевому устройству и желаемой редакции. | Найдите образ, который соответствует вашему целевому устройству и желаемой редакции. | ||
</div> | |||
===Запись установочного носителя=== | ===Запись установочного носителя=== | ||
Line 33: | Line 59: | ||
<div class="mw-translate-fuzzy"> | |||
===Очистка и первая загрузка=== | ===Очистка и первая загрузка=== | ||
После того, как вы получили образ на SDCard, вы должны поместить карту в устройство и подключить его. Если все сработало правильно - она должна загрузиться с OEM-установкой. Здесь вы определяете имя пользователя, пароли, локали и т.д. После этого сценарий выполнит очистку, изменит размер раздела и перезагрузит устройство. После перезагрузки устройство должно загрузиться в операционную систему. В зависимости от установленной редакции это может быть простой вход в TTY или графическая среда рабочего стола. | После того, как вы получили образ на SDCard, вы должны поместить карту в устройство и подключить его. Если все сработало правильно - она должна загрузиться с OEM-установкой. Здесь вы определяете имя пользователя, пароли, локали и т.д. После этого сценарий выполнит очистку, изменит размер раздела и перезагрузит устройство. После перезагрузки устройство должно загрузиться в операционную систему. В зависимости от установленной редакции это может быть простой вход в TTY или графическая среда рабочего стола. | ||
</div> | |||
===Изменение размеров разделов=== | ===Изменение размеров разделов=== | ||
Line 46: | Line 73: | ||
По умолчанию у него нет пароля и включен автологин. | По умолчанию у него нет пароля и включен автологин. | ||
Это изменяется при запуске OEM-скрипта, чтобы отключить автологин и установить пароль, заданный при настройке. | Это изменяется при запуске OEM-скрипта, чтобы отключить автологин и установить пароль, заданный при настройке. | ||
<div class="mw-translate-fuzzy"> | |||
=Поддерживаемые устройства= | =Поддерживаемые устройства= | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
==Жесткое ядро== | ==Жесткое ядро== | ||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
{| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | {| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | ||
! | ! | ||
! colspan=" | ! colspan="9" | Hardkernel | ||
|- | |||
| Model | |||
| Release Year | |||
| SoC Manufacturer | |||
| Lithography | |||
| CPU | |||
| CPU Topology | |||
| CPU Frequency | |||
| GPU | |||
| Memory | |||
| Generic Image Support | |||
|- | |- | ||
| | | <strong>Odroid C2</strong> | ||
<strong> | | 2016 | ||
| | | Amlogic | ||
| | | 28nm | ||
| | | S905 | ||
| | | Quad-core: <br>4 x Cortex-A53 | ||
| 4 x 1.5GHz | |||
| Mali-450 MP3 | |||
| 2GB DDR3 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Odroid C4</strong> | ||
| | | 2020 | ||
| | | Amlogic | ||
| 12nm | |||
| S905X3 | |||
| Quad-core: <br>4 x Cortex-A55 | |||
| 4 x 2.0GHz | |||
| Mali-G31 MP2 | |||
| 4GB DDR4 | |||
| No | |||
|- | |||
| <strong>Odroid N2</strong> | |||
| 2019 | | 2019 | ||
| | | Amlogic | ||
| 12nm | |||
| S922X | |||
| Hexa-core: <br>4 x Cortex-A73 <br>2 x Cortex-A53 | |||
| 4 x 2.0GHz <br>2 x 1.8GHz | |||
| Mali-G52 MP4 | |||
| 2-4GB DDR4 | |||
| Yes | |||
|- | |- | ||
| <strong> | | <strong>Odroid N2+</strong> | ||
| Amlogic | | 2020 | ||
| | | Amlogic | ||
| | | 12nm | ||
| | | S922X | ||
| Hexa-core: <br>4 x Cortex-A73 <br>2 x Cortex-A53 | |||
| 4 x 2.4GHz <br>2 x 1.9GHz | |||
| Mali-G52 MP4 | |||
| 2-4GB DDR4 | |||
| Yes | |||
|- | |- | ||
| <strong> | | <strong>Odroid M1</strong> | ||
| | | 2021 | ||
| | | Rockchip | ||
| | | 22nm | ||
| | | RK3568B2 | ||
| Quad-core: <br>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 | |||
|- | |- | ||
| <strong> | | <strong>Edge-V</strong> | ||
| | | 2018 | ||
| | | Rockchip | ||
| | | 28nm | ||
| | | RK3399 | ||
| Hexa-core: <br>2 x Cortex-A72 <br>4 x Cortex-A53 | |||
| 2 x 1.8GHz <br>4 x 1.5GHz | |||
| Mali-T860 MP4 | |||
| 2-4GB LPDDR4 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Vim 1</strong> | ||
| Quad-core:<br>4 x Cortex-A53 | | 2016 | ||
| | | Amlogic | ||
| | | 28nm | ||
| | | S905X | ||
| Quad-core: <br>4 x Cortex-A53 | |||
| 4 x 1.5GHz | |||
| Mali-450 MP3 | |||
| 2GB DDR3 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Vim 2</strong> | ||
| | | 2017 | ||
| | | Amlogic | ||
| | | 28nm | ||
| | | S912 | ||
| Octa-core: <br>8 x Cortex-A53 | |||
| 8 x 1.5GHz | |||
| Mali-T820 MP3 | |||
| 2-3GB LPDDR4 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Vim 3</strong> | ||
| | | 2019 | ||
| | | Amlogic | ||
| | | 12nm | ||
| | | A311D | ||
|- | | Hexa-core: <br>4 x Cortex-A73 <br>2 x Cortex-A53 | ||
| 4 x 2.2GHz <br>2 x 1.8GHz | |||
| | | Mali-G52 MP4 | ||
| | | 2-4GB LPDDR4 | ||
| 2 | | No | ||
| | |||
|} | |} | ||
{| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | {| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | ||
! | ! | ||
! colspan=" | ! colspan="9" | Orange Pi | ||
|- | |- | ||
| | | Model | ||
| | | Release Year | ||
| | | SoC Manufacturer | ||
| | | Lithography | ||
| | | CPU | ||
| CPU Topology | |||
| CPU Frequency | |||
| GPU | |||
| Memory | |||
| Generic Image Support | |||
|- | |- | ||
| <strong> | | <strong>Orange Pi 3 LTS</strong> | ||
| | | 2019 | ||
| | | Allwinner | ||
| | | 28nm | ||
| | | H6 | ||
| Quad-core: <br>4 x Cortex-A53 | |||
| 4 x 1.8GHz | |||
| Mali-T720 MP2 | |||
| 1-2GB LPDDR3 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Orange Pi 4 LTS</strong> | ||
| 2 x | | 2021 | ||
| | | Rockchip | ||
| | | 28nm | ||
| | | RK3399 | ||
| Hexa-core: <br>4 x Cortex-A73 <br>2 x Cortex-A53 | |||
| 2 x 2.0GHz <br>4 x 1.5GHz | |||
| Mali-T860 MP4 | |||
| 2-4GB LPDDR4 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Orange Pi 800</strong> | ||
| | | 2022 | ||
| | | Rockchip | ||
| | | 28nm | ||
| | | RK3399 | ||
|- | | Hexa-core: <br>4 x Cortex-A73 <br>2 x Cortex-A53 | ||
| 2 x 2.0GHz <br>4 x 1.5GHz | |||
| 2 | | Mali-T860 MP4 | ||
| | | 2-4GB LPDDR4 | ||
| 2 | | No | ||
| | |||
|} | |} | ||
{| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | {| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | ||
! | ! | ||
! colspan=" | ! colspan="9" | Pine64 | ||
|- | |- | ||
| | | Model | ||
| Release Year | |||
| | | SoC Manufacturer | ||
| Lithography | |||
| | | CPU | ||
| | | CPU Topology | ||
| | | CPU Frequency | ||
| GPU | |||
| Memory | |||
| | | Generic Image Support | ||
| | |||
| | |||
| | |||
| | |||
|- | |- | ||
| <strong> | | <strong>Rock64</strong> | ||
| Rockchip | | 2017 | ||
| | | Rockchip | ||
| | | 28nm | ||
| | | RK3328 | ||
| | | Quad-core: <br>4 x Cortex-A53 | ||
| 4 x 1.5GHz | |||
| Mali-450 MP2 | |||
| 1-4GB LPDDR3 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>RockPro64</strong> | ||
| 28nm | | 2017 | ||
| | | Rockchip | ||
| | | 28nm | ||
| | | RK3399 | ||
| | | Hexa-core: <br>4 x Cortex-A73 <br>2 x Cortex-A53 | ||
| 2 x 2.0GHz <br>4 x 1.5GHz | |||
| Mali-T860 MP4 | |||
| 2-4GB LPDDR4 | |||
| Yes | |||
|- | |- | ||
| <strong> | | <strong>Pine H64</strong> | ||
| | | 2019 | ||
| | | Allwinner | ||
| | | 28nm | ||
| | | H6 | ||
| | | Quad-core: <br>4 x Cortex-A53 | ||
| 4 x 1.8GHz | |||
| Mali-T720 MP2 | |||
| 2-4GB LPDDR3 | |||
| Yes | |||
|- | |- | ||
| <strong> | | <strong>Pinebook</strong> | ||
| Quad-core:<br>4 x Cortex-A53 | | 2017 | ||
| | | Allwinner | ||
| | | 40nm | ||
| | | A64 | ||
| | | Quad-core: <br>4 x Cortex-A53 | ||
| 4 x 1.152GHz | |||
| Mali-400 MP2 | |||
| 2GB LPDDR3 | |||
| Yes | |||
|- | |- | ||
| <strong> | | <strong>Pinebook Pro</strong> | ||
| | | 2019 | ||
| 2 x | | Rockchip | ||
| 28nm | |||
| 2 x 2.0GHz<br>4 x 1.5GHz | | RK3399 | ||
| | | Hexa-core: <br>2 x Cortex-A72 <br>4 x Cortex-A53 | ||
| 2 x 2.0GHz <br>4 x 1.5GHz | |||
| Mali-T860 MP4 | |||
| 4GB LPDDR4 | |||
| Yes | |||
|- | |- | ||
| <strong> | | <strong>Pinephone</strong> | ||
| | | 2019 | ||
| | | Allwinner | ||
| Mali-400 MP2 | | 40nm | ||
| | | A64 | ||
| | | Quad-core: <br>4 x Cortex-A53 | ||
| 4 x 1.2GHz | |||
| Mali-400 MP2 | |||
| 2-3GB LPDDR3 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Pinephone Pro</strong> | ||
| | | 2022 | ||
| Rockchip | |||
| | | 28nm | ||
| 4GB | | RK3399 | ||
| | | Hexa-core: <br>2 x Cortex-A72 <br>4 x Cortex-A53 | ||
| 2 x 1.5GHz <br>4 x 1.5GHz | |||
| Mali-T860 MP4 | |||
| 4GB LPDDR4 @800 MHz | |||
| No | |||
|} | |} | ||
{| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | {| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | ||
! | ! | ||
! colspan=" | ! colspan="9" | Radxa | ||
|- | |||
| Model | |||
| Release Year | |||
| SoC Manufacturer | |||
| Lithography | |||
| CPU | |||
| CPU Topology | |||
| CPU Frequency | |||
| GPU | |||
| Memory | |||
| Generic Image Support | |||
|- | |- | ||
| | | <strong>Rock Pi 4B & 4C</strong> | ||
<strong> | | 2019 | ||
| | | Rockchip | ||
| 28nm | |||
| RK3399 | |||
| Hexa-core: <br>2 x Cortex-A72 <br>4 x Cortex-A53 | |||
| 2 x 2.0GHz <br>4 x 1.5GHz | |||
| Mali-T860 MP4 | |||
| 1–4GB LPDDR4 | |||
| Yes | |||
|- | |- | ||
| <strong> | | <strong>Radxa Zero</strong> | ||
| | | 2021 | ||
| Amlogic | |||
| 12nm | |||
| S905Y2 | |||
| Quad-core: <br>4 x Cortex-A53 | |||
| 4 x 1.8GHz | |||
| Mali-G31 MP2 | |||
| 1-4GB LPDDR4 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Rock 3A</strong> | ||
| Rockchip | | 2022 | ||
| Rockchip | |||
| 22nm | |||
| RK3568 | |||
| Quad-core: <br>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 | |||
|- | |- | ||
| <strong> | | <strong>Pi 3B</strong> | ||
| 28nm | | 2016 | ||
| Broadcom | |||
| 28nm | |||
| BCM2837 | |||
| Quad-core: <br>4 x Cortex-A53 | |||
| 4 x 1.2GHz | |||
| VideoCore IV | |||
| 1GB LPDDR2 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Pi 3B+</strong> | ||
| | | 2018 | ||
| Broadcom | |||
| 28nm | |||
| BCM2837B0 | |||
| Quad-core: <br>4 x Cortex-A53 | |||
| 4 x 1.4GHz | |||
| VideoCore IV | |||
| 1GB LPDDR2 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Pi 400</strong> | ||
| | | 2020 | ||
| Broadcom | |||
| 28nm | |||
| BCM2711 | |||
| Quad-core: <br>4 x Cortex-A72 | |||
| 4 x 1.5GHz | |||
| VideoCore VI | |||
| 4GB LPDDR4 | |||
| No | |||
|- | |- | ||
| <strong> | | <strong>Pi 4B</strong> | ||
| | | 2019 | ||
| | | Broadcom | ||
| | | 28nm | ||
| BCM2711 | |||
| Quad-core: <br>4 x Cortex-A72 | |||
| 4 x 1.5GHz | |||
| | | VideoCore VI | ||
| 1-8GB LPDDR4 | |||
| No | |||
|} | |} | ||
{| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | {| class="wikitable" style="text-align: center;width: 100%;"-- Header --> | ||
! | ! | ||
! colspan=" | ! colspan="9" | Ugoos | ||
|- | |- | ||
| | | Model | ||
| Release Year | |||
| SoC Manufacturer | |||
| Lithography | |||
| CPU | |||
| CPU Topology | |||
| CPU Frequency | |||
| | | GPU | ||
| Memory | |||
| Generic Image Support | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
|- | |- | ||
| <strong> | | <strong>AM6 Plus</strong> | ||
| | | 2019? | ||
| Amlogic | |||
| | | 12nm | ||
| 4GB | | S922XJ | ||
| Hexa-core: <br>4 x Cortex-A73 <br>2 x Cortex-A53 | |||
| 4 x 2.2GHz <br>2 x 1.9GHZ | |||
| Mali-G52 MP6 | |||
| 4GB LPDDR4 | |||
| No | |||
|} | |} | ||
</div> | |||
== | ==ТВ-приставки Android== | ||
С помощью пары небольших настроек можно загрузить и установить сборку vim3 Manjaro на некоторые [[Amlogic TV box]]. Запуск Manjaro на ТВ-боксах не рекомендуется для неопытных пользователей Linux и для серьезного продакшена. | |||
<div class="mw-translate-fuzzy"> | |||
===Устранение неисправностей=== | ===Устранение неисправностей=== | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
====Кнопка питания Pi 400==== | ====Кнопка питания Pi 400==== | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
Если у вас возникли проблемы с использованием кнопки питания на Pi 400 с рабочим столом XFCE (или xfce4-power-manager), убедитесь, что logind обрабатывает события кнопки: | Если у вас возникли проблемы с использованием кнопки питания на Pi 400 с рабочим столом XFCE (или xfce4-power-manager), убедитесь, что logind обрабатывает события кнопки: | ||
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true | xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-power-key -n -t bool -s true | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
====Блокировка обновления==== | ====Блокировка обновления==== | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
Существуют обходные пути, зависящие от устройства, если вы столкнулись с ошибкой, подобной этой: | Существуют обходные пути, зависящие от устройства, если вы столкнулись с ошибкой, подобной этой: | ||
<pre> | <pre> | ||
Line 372: | Line 513: | ||
:: brcm-patchram-plus and pi-bluetooth are in conflict | :: brcm-patchram-plus and pi-bluetooth are in conflict | ||
</pre> | </pre> | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
Для '''Pi 3B''': | Для '''Pi 3B''': | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
sudo systemctl disable brcm43438.service | |||
sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi | sudo pacman -S -dd brcm-patchram-plus-pi3b firmware-raspberrypi | ||
sudo systemctl enable attach-bluetooth-pi3.service | sudo systemctl enable attach-bluetooth-pi3.service | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
Для '''Pi 3B+''': | Для '''Pi 3B+''': | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
sudo systemctl disable brcm43438.service | |||
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi | sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi | ||
sudo systemctl enable attach-bluetooth.service | sudo systemctl enable attach-bluetooth.service | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
Для '''Pi 4B''': | Для '''Pi 4B''': | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
sudo systemctl disable brcm43438.service | |||
sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi | sudo pacman -S -dd brcm-patchram-plus firmware-raspberrypi | ||
sudo systemctl enable attach-bluetooth.service | sudo systemctl enable attach-bluetooth.service | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
Для '''Pi 400''': | Для '''Pi 400''': | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
sudo systemctl disable brcm43438.service | |||
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi | sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi | ||
sudo systemctl enable attach-bluetooth-pi400.service | sudo systemctl enable attach-bluetooth-pi400.service | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
====Отсутствие Bluetooth после обновления raspberrypi-bootloader/-x 20210208-1==== | ====Отсутствие Bluetooth после обновления raspberrypi-bootloader/-x 20210208-1==== | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
Сначала проверьте, был ли обновлен загрузчик: | Сначала проверьте, был ли обновлен загрузчик: | ||
pacman -Ss raspberrypi-bootloader | pacman -Ss raspberrypi-bootloader | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
Возможные результаты: | Возможные результаты: | ||
core/raspberrypi-bootloader '''20210208-1''' [installed] | core/raspberrypi-bootloader '''20210208-1''' [installed] | ||
Line 407: | Line 570: | ||
core/raspberrypi-bootloader-x '''20210208-1''' [installed] | core/raspberrypi-bootloader-x '''20210208-1''' [installed] | ||
Bootloader with extra codecs for Raspberry Pi | Bootloader with extra codecs for Raspberry Pi | ||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
Если это так, то замена '''ttyAMA0''' в /boot/cmdline.txt на '''serial0''' может исправить пропажу Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Источник]). | Если это так, то замена '''ttyAMA0''' в /boot/cmdline.txt на '''serial0''' может исправить пропажу Bluetooth ([https://forum.manjaro.org/t/new-raspberry-pi-kernels-related-packages/4721/344 Источник]). | ||
</div> | |||
== | <div lang="en" dir="ltr" class="mw-content-ltr"> | ||
sudo systemctl disable brcm43438.service | |||
sudo pacman -S -dd brcm-patchram-plus-pi400 firmware-raspberrypi | |||
sudo systemctl enable attach-bluetooth-pi400.service | |||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
==Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1== | |||
</div> | |||
<div class="mw-translate-fuzzy"> | |||
=Смотрите также= | =Смотрите также= | ||
https://wiki.archlinux.org/index.php/Category:ARM_architecture<br /> | https://wiki.archlinux.org/index.php/Category:ARM_architecture<br /> | ||
Line 419: | Line 592: | ||
https://osdn.net/projects/manjaro-arm/<br /> | https://osdn.net/projects/manjaro-arm/<br /> | ||
<br /> | <br /> | ||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
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 | |||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
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]). | |||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
=Unsupported Devices= | |||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
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. | |||
</div> | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | |||
=See also= | |||
https://wiki.archlinux.org/index.php/Category:ARM_architecture<br /> | |||
https://archlinuxarm.org/wiki<br /> | |||
https://osdn.net/projects/manjaro-arm/<br /> | |||
<br /> | |||
</div> | |||
[[Category:Contents Page{{#translation:}}]] | [[Category:Contents Page{{#translation:}}]] | ||
[[Category:ARM{{#translation:}}]] | [[Category:ARM{{#translation:}}]] |