LTS

    Innovation Version

      Installation Modes

      NOTE

      • The hardware supports only Raspberry Pi 3B/3B+/4B/400.
      • The installation is performed by writing images to the SD card. This section describes how to write images on Windows, Linux, and Mac.
      • The image used in this section is the Raspberry Pi image of openEuler. For details about how to obtain the image, see Installation Preparations.

      Writing Images on Windows

      This section uses Windows 10 as an example to describe how to write images to the SD card in the Windows environment.

      Formatting the SD Card

      To format the SD card, perform the following procedures:

      1. Download and install a SD card formatting tool. The following operations use SD Card Formatter as an example.

      2. Start SD Card Formatter. In Select card, select the drive letter of the SD card to be formatted.

        If no image has been installed in the SD card, only one drive letter exists. In Select card, select the drive letter of the SD card to be formatted.

        If an image has been installed in the SD card, one or more drive letters exist. For example, the SD card corresponds to three drive letters: E, G, and H. In Select card, you can select the drive letter E of the boot partition.

      3. In Formatting options, select a formatting mode. The default mode is Quick format.

      4. Click Format to start formatting. A progress bar is displayed to show the formatting progress.

      5. After the formatting is completed, the message "Formatting was successfully completed" is displayed. Click OK.

      Writing Images to the SD Card

      NOTE If the compressed image file openEuler-22.03-LTS-SP2-raspi-aarch64.img.xz is obtained, decompress the file to obtain the openEuler-22.03-LTS-SP2-raspi-aarch64.img image file.

      To write the openEuler-22.03-LTS-SP2-raspi-aarch64.img image file to the SD card, perform the following procedures:

      1. Download and install a tool for writing images. The following operations use Win32 Disk Imager as an example.
      2. Start Win32 Disk Imager and right-click Run as administrator.
      3. Select the path of the image file in IMG format from the Image File drop-down list box.
      4. In Device, select the drive letter of the SD card to which the image is written.
      5. Click Write. A progress bar is displayed to show the progress of writing the image to the SD card.
      6. After the write operation is completed, a dialog box is displayed, indicating that the write operation is successfully completed. Click OK.

      Writing Images on Linux

      This section describes how to write images to the SD card in the Linux environment.

      Checking Drive Partition Information

      Run the fdisk -l command as the root user to obtain the drive information of the SD card. For example, the drive partition corresponding to the SD card can be /dev/sdb.

      Unmounting the SD Card

      1. Run the df -lh command to check the mounted volumes.

      2. If the partitions corresponding to the SD card are not mounted, skip this step. If the partitions (for example, /dev/sdb1 and /dev/sdb3) are mounted, run the following commands as the root user to unmount them:

        umount /dev/sdb1

        umount /dev/sdb3

      Writing Images to the SD Card

      1. If the image obtained is compressed, run the xz -d openEuler-22.03-LTS-SP2-raspi-aarch64.img.xz command to decompress the compressed file to obtain the openEuler-22.03-LTS-SP2-raspi-aarch64.img image file. Otherwise, skip this step.

      2. Run the following command as the root user to write the openEuler-22.03-LTS-SP2-raspi-aarch64.img image to the SD card:

        dd bs=4M if=openEuler-22.03-LTS-SP2-raspi-aarch64.img of=/dev/sdb

        NOTE Generally, the block size is set to 4 MB. If the write operation fails or the written image cannot be used, you can set the block size to 1 MB and try again. However, the write operation is time-consuming when the block size is set to 1 MB.

      Writing Images on Mac

      This section describes how to flash images to the SD card in the Mac environment.

      Checking Drive Partition Information

      Run the diskutil list command as the root user to obtain the drive information of the SD card. For example, the drive partition corresponding to the SD card can be /dev/disk3.

      Unmounting the SD Card

      1. Run the df -lh command to check the mounted volumes.

      2. If the partitions corresponding to the SD card are not mounted, skip this step. If the partitions (for example, dev/disk3s1 and /dev/disk3s3) are mounted, run the following commands as the root user to unmount them:

        diskutil umount /dev/disk3s1

        diskutil umount /dev/disk3s3

      Writing Images to the SD Card

      1. If the image obtained is compressed, run the xz -d openEuler-22.03-LTS-SP2-raspi-aarch64.img.xz command to decompress the compressed file to obtain the openEuler-22.03-LTS-SP2-raspi-aarch64.img image file. Otherwise, skip this step.

      2. Run the following command as the root user to write the image openEuler-22.03-LTS-SP2-raspi-aarch64.img to the SD card:

        dd bs=4m if=openEuler-22.03-LTS-SP2-raspi-aarch64.img of=/dev/sdb

        NOTE

        Generally, the block size is set to 4 MB. If the write operation fails or the written image cannot be used, you can set the block size to 1 MB and try again. However, the write operation is time-consuming when the block size is set to 1 MB.

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.

      PR

      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.

      Usability

      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.

      Correctness

      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Submit
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份