libre-computer OS Tool (LOST) is a firmware designed to deploy operating system distributions quickly over the internet. Our newer boards have it built-in and it supports booting from all storage mediums (MicroSD, eMMC, USB, NVMe).
Boards with onboard LOST
AML-S805X-AC
ROC-RK3399-PC - cannot deploy yet
Boards without onboard LOST
ALL-H3-CC-H3
ALL-H3-CC-H5
AML-S905X-CC
ROC-RK3328-CC
These boards can still boot from non-native storage mediums by having a blank MicroSD or eMMC flashed with the bootloader. You can use the following tool to install board-specific bootloaders on a MicroSD card. Leave it plugged in your board and it will be able to boot from non=native storage mediums like USB.
Should USB boot work without any modifications to usb image? Iâve tried HA image for rasp and Proxmox7 but they wonât even try to boot. Error message âCannoât find valid erofs superblockâ
What board do you have? Raspberry Pi Raspbian images donât work without running libretech-raspbian-portability first on the Raspberry Pi. If youâre just finding random images off the internet that might not be Raspbian or based on an old version of NOOBS, it most likely wonât work.
I just bought the AML-S905X-CC for HomeAssistant. First problem was that, HA OS will not boot on this board. Is there any tricks to get HA OS to boot on Le Potato? This would solve all problems at once.
Other problems Iâve encountered:
-Iâve been debugging HA Supervised install now for 10 hours and I canât get it to work on âlibre-computer-aml-s905x-cc-debian-stretch-headless-mali-4.19.55â image (âPreparing Home Assistantâ gets stuck on â[supervisor.plugins.base] Watchdog found audio plugin failed, restartingâ and error [supervisor.utils.dbus] D-Bus method org.freedesktop.DBus.Properties.call_get_all not exists!".
-I also tried to install KVM and VirtualBox to run HA OS in VM. But CPU doesnât support KVM and atleast âubuntu-22.04.1-preinstalled-desktop-arm64+aml-s905x-ccâ image canât install VirtualBox.
The image you are using is obsolete and 3+ years old. It will be replaced soon. I recommend starting off with Ubuntu or Raspbian from our site. Thatâs why youâre probably spending a ton of time and not having anything work.
I also tried to install KVM and VirtualBox to run HA OS in VM. But CPU doesnât support KVM and atleast âubuntu-22.04.1-preinstalled-desktop-arm64+aml-s905x-ccâ image canât install VirtualBox.
HomeAssistant and Klipper are two OSes on our todo list. KVM should work on Ubuntu 22.04.1 and 20.04.5 images. If it doesnât work, send us the logs and we will fix it.
What is the timetable with that HA in your todo list? Weeks or months?
KVM did work on raspbian, but CPU does not support virtualization:
âegrep -c â(vmx|svm)â /proc/cpuinfoâ outputs â0â. Quoting: " As long as it doesnât return 0 , then youâre good" from HomeAssistant Community.
Next I will try to install Debian 11 with your instructions (Debian11/Debian12) and try HA supervised installation again (HA Supervised).
Depending on the complexity. We have a lot of engineering tasks mostly to support commercial customers. It could be weeks or months. Currently a lot of users have gotten those things to work by just following standard Ubuntu instructions.
vmx and svm are x86 virtualization flags. They do not apply to ARM devices. Our kernel has virtualization enabled.
Recommend trying with Ubuntu as Debian install is cumbersome right now. We will have Debian images released in weeks.
Thanks for the great guide! However, you should post this as a new thread title so that people can find it. eg. âHow to install HomeAssistant Supervised on USBâ
I successfully used these instructions to copy an existing microsd to an SSD (with SATA to USB) and then boot from the SSD from there on out. This method requires a dedicated, empty, microsd card that just has the bootloader applied from the libretech-flash-tool. Before you swap the microsd you need to copy the data from your existing, working microsd to the SSD. On a linux machine that has both drives connected, do the following:
sudo su
cat /dev/mmcblk1 > /dev/sdc
The mmcblk1 is the source microsd (your device name may differ) and the destination SSD is sdc (same). This will take quite a while and thereâs no status. Just let it run (and if youâre on ssh, make sure your device has something to prevent it from disconnecting).
Hello! Can I ask how you created a dedicated, empty microsd card that has the bootloader installed? I get to the point where I have used the âcatâ command and the system transfers correctly, but then I am lost with how to install the bootloader on the card that I have to boot up to access the git command, etc. Do I have to do this from a separate computer? Do I use a sdcard to usb stick and install the bootloader on that one?
This tool is used to flash the bootloader. I havenât used it, but there appear to be clear instructions for it.
You can use a usb adapter or a separate computer as far as I know. As long as the sd card is connected to a Linux computer with the flash tool, you should be good.
I may be a bit late to the conversation, but I have been having a related boot issue.
I am using a renegade elite (ROC-RK3399-PC-Plus). The box doesnât say -Plus, but the board layout is equivalent to the Plus, including the 4 tall SPI pins. That being said, I believe that I am unable to get it to boot off of a USB drive after flashing a boot loader to a micro SD as described above. The red and green LED illuminate and stay illuminated without ever flashing or changing.
I tried putting Debian, Ubuntu, the custom version of Raspbian/RaspberryOS, and Armbian with no luck (both headless and desktop environments were tried when available).
When flashing the OS to an SD card, the LEDâs underwent the normal booting process (though I havenât been able to get a display output yet. I havenât tried multiple USB C docks so thatâs a separate issue that I have yet to debug).
boot loader flashing â
outputs received and commands issued:
**bash lft.sh dev-list**
loop26
vma
vmb
sda
**sudo bash lft.sh bl-flash roc-rk3399-pc sda**
1850+0 records in
1850+0 records out
947200 bytes (947 kB, 925 KiB) copied, 0.222271 s, 4.3 MB/s
BOOTLOADER_flash: bootloader written to sda successfully.
Do you have a picture of the board and can you let us know where you got it? ROC-RK3399-PC-Plus is an entirely different board that we did not design and our software will not support.
