The testing build for USB/NMVe is not merged to the main Volumio OS yet.
At the top of this thread, there is a complete guide what steps are needed and which build you should choose. The relevant links are provided to the latest RC builds, hence why I am not posting direct links in the discussions, just to avoid a confusion. If you do not test upgrade process, head directly to the subsection with the links to the prototype (screenshot).
If you are not planing to use MicroSD then option 2 will try USB boot right away. In all test I am running with attached devices option 1 is my choice for debugging, fixing, etc.
Currently, the USB boot, amongst other boot options for Raspberry devices, is in the test phase. Change as such, is disruptive. Since all devices and community ports are sharing the same ecosystem base, newly introduced functions need to be thoroughly tested. Devs are already planning for the merge, no hard ETA yet. Once merge happens, this development build will became part of the main Volumio OS. The only caveat is that the OTA from test to main will not be offered.
With Volumio OS installed to USB with USB boot highest priority, the fix or changes would look like before, with MicroSD as only option. Nothing changes here.
This is interesting, taking that I am not offered firmware sentinel on first boot as there is no firmware upgrade pending.
Is it from fresh test image start on USB?
Yeah, after updating the bootloader, Boot from usb, i download and flash the Version 3.639 RC-Testing 29 using rpi imger.
Then mount it to rpi4 then that happen.
Hi dev! Itâs working now. I plug the ssd with prototype os instead. However, it seems that touch screen not working, even i successfully installed the plugin touch display, and another problem is i canât play network music such as webradio. It says failed to open alsa.
Hey,
You will need to provide more details about your hardware like touch/screen - connected using DSI, USB, etc. Play using what output device and how this device is configured.
I did have problem on that version. Itâs 4096 bytes which Raspberry Pi does not support for booting up. I returned it and got this one instead and itâs 512 bytes and working fine.
This one has a thumb reading for security which I intend to use for my important files in case it doesnât work with the Pi. The price difference is only $5.
Iâm going to make an assumption that some things are purportedly âwell known.â But in the interest of trying to make open source documentation not be terrible, can you get some references to the following:
Intermediate OTA After reboot completes, ensure that the âTestâ mode in /dev is set to false. Accept OTA upgrade to version v3.632 and perform upgrade in the usual manner. Your Raspberry Pi will reboot automatically.