Difference between revisions of "Manjaro-ARM"

Marked this version for translation
m (small fix)
(Marked this version for translation)
 
Line 16: Line 16:
=Installation= <!--T:5-->
=Installation= <!--T:5-->


===Preparing the SPI (optional)===
===Preparing the SPI (optional)=== <!--T:46-->


<!--T:47-->
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>
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.
We have currently tested [https://github.com/Tow-Boot/Tow-Boot Tow-Boot], so that's what this guide will use.


<!--T:48-->
# 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.
# 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.
#  
#  
Line 31: Line 33:
# 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.
# 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.


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


Line 79: Line 82:
==Device List== <!--T:18-->
==Device List== <!--T:18-->


<!--T:50-->
{|  class="wikitable" style="text-align: center;width: 100%;"-- Header -->  
{|  class="wikitable" style="text-align: center;width: 100%;"-- Header -->  
! &nbsp;
! &nbsp;
Line 548: Line 552:
For the '''Pi 400''':
For the '''Pi 400''':


<!--T:51-->
sudo systemctl disable brcm43438.service
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


==Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1==  
==Missing Bluetooth after raspberrypi-bootloader/-x update 20210208-1== <!--T:52-->


<!--T:43-->
<!--T:43-->
Line 568: Line 573:
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]).
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=  
=Unsupported Devices= <!--T:53-->


<!--T:54-->
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.
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=
=See also= <!--T:55-->
https://wiki.archlinux.org/index.php/Category:ARM_architecture<br />
https://wiki.archlinux.org/index.php/Category:ARM_architecture<br />
https://archlinuxarm.org/wiki<br />
https://archlinuxarm.org/wiki<br />
translator
10,704

edits