References:
https://codingfield.com/blog/2024-01/install-armbian-and-proxmox-on-orangepi5plus/
https://docs.pxvirt.lierfang.com/en/installfromdebian.html
Download Armbian Releases
Keyword in image filename Turing_RK1 and minimal:
https://github.com/armbian/community/releases/download/26.2.0-trunk.100/Armbian_community_26.2.0-trunk.100_Turing-rk1_trixie_vendor_6.1.115_minimal.img.xz
Extract the image file and flash the turing Pi using the web interface on the correct Node:
[Info 22-12-2025]
The image is now installed on the mmc of the RK1
Login on the Turin Pi and open an an emulated TTY session to the node:
picocom /dev/ttyS2 -b 115200 # Connect to Node 2, pay attention to the version of your BMC firmware!!
Restart the node using the Turing Pi web interface.
Interrupt the boot in the emulated TTY session by entering any key when the interrups boot message appears.
Set the boot drive to mmc with the following commands:
setenv boot_targets mmc0
boot
Follow Armbian setup instructions during the first boot.
Change Hostname by adjusting the following files:
/etc/hostname
/etc/hosts
Reboot machine
Follow instructions on https://docs.pxvirt.lierfang.com/en/installfromdebian.html
Changed /etc/network/interfaces:
# interfaces(5) file used by ifup(8) and ifdown(8)auto loiface lo inet loopback
iface end0 inet manual
auto vmbr0iface vmbr0 inet static address 192.168.1.12/24 gateway 192.168.1.1 bridge-ports end0 bridge-stp off bridge-fd 0
1. Add the DNS servers to /etc/systemd/resolved.conf:
[Resolve] DNS=1.1.1.1 8.8.8.8
2. restartsystemd-resolved
systemctl restart systemd-resolved
3. Check your settings with resolvectl status:
$ resolvectl status
Global
Protocols: -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Current DNS Server: 1.1.1.1
DNS Servers: 1.1.1.1 8.8.8.8
DNS Domain: your.search.domain
Link 2 (ens3)
Download Armbian Releases
Keyword in image filename Turing_RK1 and minimal:
https://github.com/armbian/community/releases/download/26.2.0-trunk.100/Armbian_community_26.2.0-trunk.100_Turing-rk1_trixie_vendor_6.1.115_minimal.img.xz
Extract the image file and flash the turing Pi using the web interface on the correct Node:
[Info 22-12-2025]
The image is now installed on the mmc of the RK1
Login on the Turin Pi and open an an emulated TTY session to the node:
picocom /dev/ttyS2 -b 115200 # Connect to Node 2, pay attention to the version of your BMC firmware!!
Restart the node using the Turing Pi web interface.
Interrupt the boot in the emulated TTY session by entering any key when the interrups boot message appears.
Set the boot drive to mmc with the following commands:
setenv boot_targets mmc0
boot
Follow Armbian setup instructions during the first boot.
After the bash appears:
Download the minimal RK1 Armbian image to the mmc with the following command:wget https://github.com/armbian/community/releases/download/26.2.0-trunk.100/Armbian_community_26.2.0-trunk.100_Turing-rk1_trixie_vendor_6.1.115_minimal.img.xz
Unzip and copy the image to the nvme drive:
sudo xzcat /root/Armbian_community_26.2.0-trunk.100_Turing-rk1_trixie_vendor_6.1.115_minimal.img/ | sudo dd of=/dev/nvme0n1 bs=1M status=progress
Download the turing-rk1-uboot-only.zip from https://www.nico-maas.de/?p=2669
Unzip the image and use that file to flash the node again.
References:
https://forum.turingpi.com/t/26782959/talos-ubuntu-dual-boot-guide
https://docs.turingpi.com/docs/tpi-uart
https://docs.radxa.com/en/rock3/rock3b/getting-started/install-os/nvme
https://www.nico-maas.de/?p=2669
https://codingfield.com/blog/2024-01/install-armbian-and-proxmox-on-orangepi5plus/
https://github.com/jiangcuo/pxvirt
https://docs.pxvirt.lierfang.com/en/README.html
As per inststructions:
Adjusted /etc/hosts
/etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)auto loiface lo inet loopback
iface end0 inet manual
auto vmbr0iface vmbr0 inet static address 192.168.1.12/24 gateway 192.168.1.1 bridge-ports end0 bridge-stp off bridge-fd 0
/etc/resolv.conf
Change to point to the correct nameserver, default it was pointing to 127.0.0.54
Problem: after install their was no Proxmox webui.
Investigate: checking if the proxmox service was up and running with the following command:
systemctl status pveproxy.service
Result: Service was running, but the following error was shown:
/etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2148.
Continue investigation:
The following two commands gave the same error:
pvenode cert info
pvecm status
Error message:
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused
2 Issues:
1. the hostname was different in /etc/hostname (turing-rk1 instead of pxvirt02)
2. There was still a reference in /etc/hosts to turing-rk1 behind the line starting with "::1"
Rebooted the machine and waited a minute or so. It took some time before the pveproxy.service was started.
Now I could access the Proxmox Web UI.
To Test:
https://docs.pxvirt.lierfang.com/en/setup/Linux-on-port.html
https://www.openeuler.org/en/download/archive/detail/?version=openEuler%2024.03%20LTS%20SP2
VM wouldn't start, showing the following message:
Solution: Define CPU Affinity "0-3" under Proxmox VM Processors [Advanced Settings]
Cause: "To sum up, the problem with booting kvm VMs only happens when a mix of A55 and A76 are enabled. I confirmed that by disabling [0,1,4,5].
With only A76 cores or only A55 cores, booting a kvm VM works." Source: https://github.com/Joshua-Riek/ubuntu-rockchip/issues/731
https://forum.proxmox.com/threads/how-to-convert-raspberry-pi-os-images-and-import-to-proxmox.146837/
https://digisden.com/posts/installing-proxmox-on-a-turing-pi-rk1/
apt-get install qemu-utils
wget https://github.com/armbian/community/releases/download/26.2.0-trunk.100/Armbian_community_26.2.0-trunk.100_Turing-rk1_trixie_vendor_6.1.115_minimal.img.xz
https://gitlab.collabora.com/hardware-enablement/rockchip-3588/debian-image-recipes
Dozze: Direct access to console/logs of other containers
Watchtower: Automated update docker containers
Pulse: Monitoring Proxmox and Docker hosts (including alerts and notifications)
Komodo: All in one tool for Container Management
Netdata: Full Monitoring Dashboard (Realtime visability using netdata agent container)
Uptime Kuma: Uptime Monitor
Bitwarden: Local Password Management
Homer: Create Startpage
Mailrise: Translate SMTP to Modern Notification Service (e.g. Discord, Telegram)
Netbox: Network Automation & Documentation
Nginx Proxy Manager: Routing Traffic with Proper SSL termination
phpIPAM: Keep Track of Network Info
Duplicati: Backup Docker Volumes
Pi-Hole: DNS Level Ad-blocking Telemetry
Gitea: Self-hosted Git Service