Leap on a Turing RK1

[Felix Niederwanger]

Hey people,

I finally managed to get Leap 15.6 installed on the eMMC of a Turing RK1.









Here's how the partitions of the installed system look like:

vela-rk:~ # parted /dev/mmcblk0
GNU Parted 3.2
Using /dev/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: MMC BJTD4R (sd/mmc)
Disk /dev/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name     Flags
 1      16.8MB  554MB   537MB   fat32        primary
 2      554MB   688MB   134MB   fat16                 boot, esp
 3      688MB   31.3GB  30.6GB  btrfs


Have a lot of fun :-)

[1] https://docs.turingpi.com/docs/turing-rk1-flashing-os

TLDR: Flash the official Firmware image to the eMMC, delete all partitions but the first one (bootloader) and then boot from USB Stick. My solution was to use the provided bootloader from the official image, and then install the main OS alongside it on the eMMC. This works flawlessly. My main confusion point was to recognize, that the bootloader needs to be on the eMMC. This is actually documented in [1]. Without it, there is no output or anything when booting, it simply won't do anything. I installed my RK1 within my Turing Pi cluster. I used Node 4, so I could just plug in a USB Stick with Leap 15.6 into the USB3 ports and boot from there. The boot order of the firmware bootloader is NVMe > SATA > USB > eMMC [1]. The typical YaST installation works without any issues.

OpenPGP_0x6E77A590E3F6D71C.asc
Description: OpenPGP public key

OpenPGP_signature.asc
Description: OpenPGP digital signature