Leap on a Turing RK1
Hey people, I finally managed to get Leap 15.6 installed on the eMMC of a Turing RK1. 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. 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
Hi Felix, Thanks for your report and detailed steps.
-----Original Message----- From: Felix Niederwanger <phoenix@feldspaten.org> Sent: Thursday, April 18, 2024 8:38 PM To: arm@lists.opensuse.org Subject: Leap on a Turing RK1
Hey people,
I finally managed to get Leap 15.6 installed on the eMMC of a Turing RK1.
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.
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 :-)
You could create a page for this board on the openSUSE wiki, if you want to. That's usually where we point people for arm board support information. Cheers, Guillaume IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 19/04/24 10:42, Guillaume Gardet wrote:
You could create a page for this board on the openSUSE wiki, if you want to. That's usually where we point people for arm board support information.
And here we go: https://en.opensuse.org/HCL:Turing-RK1 Best, phoenix :-)
Cheers, Guillaume
-- phoenix@feldspaten.org, gpg: 0x6E77A590E3F6D71C Consider using plain text | email is not SMS https://email.is-not-s.ms/
Quick follow-up on the Turing RK1 because I ran into some issues lately: Virtualization shows some weird behaviour, namely two: 1. A migrated VM runs into instruction errors when booting 2. Starting the installation of Leap 15.6 is stuck at the "Hardware detection" step. Working hypothesis: I'm still using the uboot from the Ubuntu image that something with the device-tree-binary is causing those issues. Anyone a better guess or some suggestions on how to fix/debug this issue? Best, phoenix On 4/23/24 21:02, Felix Niederwanger wrote:
On 19/04/24 10:42, Guillaume Gardet wrote:
You could create a page for this board on the openSUSE wiki, if you want to. That's usually where we point people for arm board support information.
And here we go: https://en.opensuse.org/HCL:Turing-RK1
Best, phoenix :-)
Cheers, Guillaume
participants (2)
-
Felix Niederwanger -
Guillaume Gardet