Turing Pi Update 2026
It’s Been Almost Two Year#
I decided to fire up Discord for getting my son’s Christmas list this morning. I couldn’t tell you the last time I had been on it. So I was pleasently surprised to see that the Turing Discord is still active. That’s what prompted this post.
Two years later since my last since my Turing Pi2 Update,
my TuringPi 2 Is still chugging along. Unfortuantely, Turing hasn’t provided much in the way of updates for
Board, BMC, or the RK1 Cards. With prices not showing any signs of stopping soon, even despite AI contracts
remaining unfulfilled; keeping this little ARM cluster running is as important as ever. AI is breathing life
into all sorts of projects. So it’s a weird feeling that the reason hardware prices are so absurd is also
helping keep what would otherwise be abandonware alive.
As I started scrolling through Firmware threads to see if there’s been anyone picking up and running with the BMC or if the Ubuntu Rockchip Github had gained any activity (Nope, instead it was archived.) I was pleased to see that on the Board BMC side Oleg Tsarev with some help of Claude has kept things going with a fork of the BMC Firmware. After scrolling through the threads, I decided to dig into the Turing Pi 2 BMC Site. A little searching through the Discord to see if anything new came up on the RK1 side, I found that Armbian now had some updated community images including an Ubuntu 26.04 Minimal image among others. So naturally, that meant time to try out some upgrades.

BMC Upgrades#
Now I’ll be the first to say, AI writing style is still pretty detectible by default (At least as of now, none of my posts have been authored with it.) And the forked Turing Pi 2 BMC Site has all the hallmarks of that. And the navigation was a bit confusing. But I mean no shade at Oleg. This is a huge step in the right direction after Turing seemingly abandoning the product. And website and content is a lot of extra work on top of an already big uplift.
I started with the Upgrade from stock page thinking that’s
where I needed to be. I was wrong. Install still applied. The page
mentioned that v2.4, v2.5, v2.5.1, or v2.5.2 were needed. So I logged into my bmc and ran
cat /etc/os-release | grep VERSION. My board was reporting version=2024.05.1 which appears to be a
Buildroot verion which is an upstream bug according to the docs and that it’s an even older version still. I
assume this is due to having the original KickStarter board (Without the CMOS battery and all.) The notes for
v2.4 said it ran against the factory 2024.05.1 image in NAND. So I figured my board was probably on an
acceptable image at this point. Let’s give it a download and a try!
So I followed on to the release for v2.48.0 and said, “Why not?” I figured worst case, I’ll spend some time
trying to recover. If that fails, I guess it’s time to sell the RK1s.
I downloaded the tp2-bmc-firmware-ota-v2.48.0.tpu artifact. From my Downloads folder ran a
sha256sum tp2-bmc-firmware-ota-v2.48.0.tpu got a result of
22971b679d29992ea27a3ef835d79c8748f50eac1066594d6c5aaefdf4e3031c matched it up to that of the artifact, and
decided good to go.
I debated trying to do it CLI. But decided just as easy to log on to the BMC web server and try there.
I Navigated over to the Firmware Upgrade tab. selected the .tpu file. Pasted in the SHA256, and
hit upgrade. A few minutes later (less than 10, didn’t time exactly though) I had a prompt to reboot. I went
ahead and said yes. Started up a ping against the IP the BMC had been reporting on previously, and a couple of
minutes later it started responding. I hit refresh on the page, and was greated with the new login screen.
One thing I did notice right away, trying to use my credentials was not working. I thought this odd. I Went back to my terminal, tried to SSH into it, and was successful. Thinking I was going to be filing a bug report, I went back to the web page to try again; this time it worked. So I guess there’s some amount of delay between the BMC coming up and being ready for login. Not overly surprising. But a note for anyone else following along.
Since I was logged in to the CLI, I decided I’d validate the version, and sure enough, running
cat /etc/os-release | grep VERSION returned VERSION=v2.48.0 and BUILDROOT_VERSION=2025.02.17. So that was
great succss in my mind.
A few minutes clicking around the new dashboard, contemplating enabling VLANs at this point (ultimately, I did not yet.) I have to give Oleg a lot of credit. The streamlined interface is much easier to navigate. I especially appreciated the new serial console interface and how responsive it is.
All this in mind, I decided, “Let’s give the Ubuntu 26.04 image a shot next.”
Armbian Ubuntu 26.04#
I spent more than a few minutes scrolling through Armbian and getting excited about
finding images for other unfinished projects like my StarFIVE VisionFive2.
I got to business. I pulled down the Ubuntu 26.04 Minimal image from the Direct Download
link. I unzipped the
Armbian_community_26.11.0-trunk.130_Turing-rk1_resolute_vendor_6.1.172_minimal.img.xz. And then navigated
to my newly upgraded BMC web page again. Navigated to Flash Node. Clicked on the File upload selected the
freshly unzipped Armbian_community_26.11.0-trunk.130_Turing-rk1_resolute_vendor_6.1.172_minimal.img image
and selected Install OS. To my extremely pleasent surprise, this did not take an hour like it did
previously. The 1.88GB image took right around 5 minutes.
Once the install prompted in the lower right of the modal that it was completed successfully. Image flashed successfully to the node I went over to Power Control and Powered on the node. After a few more minutes I
was a little concerned that the web console was showing Starting Kernel ... as the last line with no more
scrolling. I used the Reboot command again thinking maybe something went wrong. It did this again. So I
looked through my DHCP leases, and found there was now a turing-rk1 entry. I thought, “let’s give that a
shot.” I tried to SSH, and to my surprise was prompted for a password. I tried ubuntu/ubuntu with no
success. So I hopped over to the Armbian Docs. Clicked through a bit, got to
Getting Started / First boot and login. I
noticed right away that the username is root and the password 1234. Went back to try again, and I was in.
I was immediately prompted with:
Welcome to Armbian_community!
Documentation: https://docs.armbian.com | Community support: https://community.armbian.com/
IP address: x.x.x.x
Create root password:
A quick “ew” over setting the root password, I continued.
Developer Preview Build
This Armbian image was generated automatically for development and testing purpose.
It may include unfinished features or unstable components.
If you are not here to report issues or just test it, please do not use this image in production.
Expect things to change — or even break — as improvements are made.
Creating a new user account. Press <Ctrl-C> to abort
Please provide a username (eg. your first name):
I finished up setting my name, confirming the timezone, and locale. After, a pleasent surprise, I was then greeted with:
_ _ _ _ _
/_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _
/ _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || |
/_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, |
|__/
v26.11 rolling for Turing RK1 running Armbian Linux 6.1.172-vendor-rk35xx
Packages: Ubuntu stable (resolute)
Updates: Kernel upgrade enabled and 5 packages available for upgrade
Support: for advanced users (rolling release)
IPv4: (LAN) x.x.x.x (WAN) y.y.y.y
Performance:
Load: 2% Uptime: 3m Local users: 4
Memory usage: 1% of 31.03G
CPU temp: 50°C Usage of /: 6% of 29G
Featured:
Thanks to Dominic for sponsoring Armbian
https://github.com/sponsors/armbian
Commands:
Configuration: armbian-config
Upgrade : armbian-upgrade
Monitoring : htop
root@turing-rk1:~#
From here I ran a reboot to make sure eMMC was written to and persistent.
I opted not to install onto my NVMe drive to keep that available for storage only.
A quick mkdir .ssh and pasting my public key with an ever lazy nano .ssh/authorized_keys
Followed by a logout and login confirming the key was good.
_ _ _ _ _
/_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _
/ _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || |
/_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, |
|__/
v26.11 rolling for Turing RK1 running Armbian Linux 6.1.172-vendor-rk35xx
Packages: Ubuntu stable (resolute)
Updates: Kernel upgrade enabled and 5 packages available for upgrade
Support: for advanced users (rolling release)
IPv4: (LAN) x.x.x.x (WAN) y.y.y.y
Performance:
Load: 1% Uptime: 2m
Memory usage: 1% of 31.03G
CPU temp: 49°C Usage of /: 6% of 29G
Featured:
Blog: Armbian 26.11 – Testing begins
https://blog.armbian.com/armbian-26-11-testing-begins/
Commands:
Configuration: armbian-config
Upgrade : armbian-upgrade
Monitoring : htop
Last login: Sat Nov 14 15:37:24 2026 from x.x.x.x
USER@turing-rk1:~$
Wrap It Up#
So with all that done, I’ve got a bit of fresh life into both the BMC and RK1 modules. I went ahead and finished up the second module. Ran my fresh install Ansible playbook to finish some of the initial setup. For anyone wondering what the basics of that role are:
- Ensure the user is there
- Ensure the pubkey is there
- Enable sudo without password
- Set the timezone
- Update apt
- Apt Upgrade
- Autoremove unused packages
- Autoclean unused packages
- Ensure root login is disabled via SSH
- Check for reboot flag
Finally, I wanted to re-initialize my storage drive on both these devices so grabbing from my
Automated Baremetal Ubuntu post I ran:
sudo parted /dev/nvme0n1 mklabel gpt
sudo parted -a opt /dev/nvme0n1 mkpart primary ext4 0% 100%
sudo mkfs.ext4 -L storage /dev/nvme0n1p1
sudo lsblk --fs
sudo mkdir -p /mnt/storage
sudo nano /etc/fstab
sudo systemctl daemon-reload
sudo mount -a
df -h /mnt/storage
Ensuring that I took the UUID from lsblk --fs nvme0n1p1 ext4 1.0 storage UUID-HERE and that the /etc/fstab had a line of /dev/disk/by-uuid/UUID-HERE /mnt/storage ext4 defaults 0 2
Making sure that the correct UUID for each node was in the respective fstab.
As always with drive management commands, be sure you’re validating that the drive is what you’re expecting. I’m not responsible if you just blindly copy and paste commands without checking.
With that, everything is ready to setup and configure for some containers and virtualization again.