Good morning,
I'm having a problem with my Vivid Unit, which I purchased on January 9, 2026.
With some difficulty, I installed Debian 12 Bookworm ( https://www.vividunit.com/download-system-image), and everything works perfectly with GPRSDR++.
Now I wanted to upgrade my Vivid Unit, thanks to the M.2 slot, but I inserted a Samsung 970 Evo Plus 512GB (100% working, tested on another device), and when I tried sudo lsblk, it doesn't show up (it's perfectly connected to the NVMe slot).
How can I fix this?
Thanks in advance
We have confirmed that this is a bug in the device tree configuration included with the current VUOS Debian 12 image. The PCIe reset signal polarity was configured incorrectly, which prevents NVMe devices from being detected.
The <&gpio4 RK_PD3 GPIO_ACTIVE_LOW> should be <&gpio4 RK_PD3 GPIO_ACTIVE_HIGH> instead.
The issue has now been fixed and the correction will be included in the next VUOS system image.
In the meantime, we can provide a corrected rk3399-vivid-unit_20260713.dtb file, which can be used to update the existing installation without reinstalling the complete system.
After downloading the file to the Downloads directory, please run:
cd ~/Downloads sudo mkdir -p /mnt/vuos-boot sudo mount /dev/mmcblk0p2 /mnt/vuos-boot sudo cp /mnt/vuos-boot/dtbs/rk3399-vivid-unit.dtb \ /mnt/vuos-boot/dtbs/rk3399-vivid-unit.dtb.bak sudo cp rk3399-vivid-unit_20260713.dtb \ /mnt/vuos-boot/dtbs/rk3399-vivid-unit.dtb sync sudo umount /mnt/vuos-boot sudo poweroff
After the Vivid Unit has shut down, please disconnect the power completely for a few seconds and then power it on again.
You can verify that the SSD is detected by running:
lsblk
The SSD should appear as a device such as nvme0n1.