one more thing: can you copy & paste here the complete config.txt file content?
In particular, have you set dtparam=i2c_arm=on?
Updated first post with new redirection service which should work better.
This requires up-to-date Berryboot binaries (v 2018-09-29 or later).
Please report any problem here.
I’ve been trying to get Volumio set up under Berryboot in my spare time over the last week and have encountered behaviour that I’m not sure is normal. I’ve got two questions:
-
After setting bootdev=/dev/mmcblk0p1 is it normal that on the next restart, berryboot is unable to mount the system partitian? Consequently I can no longer view or edit cmdline.txt or config.txt from the berryboot gui. If I don’t include /dev/ in front of mmcblk0p1 then berryboot wont boot at all.
-
Volumio boots to ssh rather than the gui. Is this normal? I was definitely expecting it to launch to the gui just as it does when I flash a copy to a dedicated sd card. Can I launch the gui from ssh? I’ve looked through the documentation but must have my blinders on.
Any suggestions for what I’m doing wrong? My Pi is a brand new 3B+ and my SD card is 32GB. I only started playing this week so as far as I know I’ve been using all the latest versions of berryboot etc.
Hi,
Thanks for trying.
re 1: It is an issue with latest berryboot-20190612: I noticed some change in boot sequence just happened, and there’s some inconsistent treatment of bootdev argument. Until this is resolved, can you try with previous berryboot-20181211 version?
re2: this is intended Volumio behavior: Pi is a headless server, remote UI is served via Web interface to connecting device (PC, phone, tablet: connect to volumio.local or whatever IP you Pi has). You may install additional plugin to also have UI on the Pi, but you need to access via Web first to do it…
All this is in the user doc (check link in my signature below).
Scripts updated: now also support berryboot-20190612 & later.
Note for earlier users: bootdev parameter tweaking is NOT necessary anymore, and cmdline.txt should be cleaned-up removing bootdev=mmcblk0p1 if using standard SD setup.
Parameter definition is only needed if booting from USB.
I wonder if it’s possible to install a custom Volumio image as the one here: nanomesher.com/nanosound-cd-support/ ans maintain installed plugins
The image link is here nanomesher.com/?smd_process_dow … ad_id=4031
Thanks in advanced
Hi,
sorry just saw your message now, as notifications were not working with earlier forum.
Install & updates are only supported with stock Volumio distribution.
However, it you replicate that image install from stock image (with plugins & al), then everything will smoothly update through Volumio releases.
Is the version of Volumio on Berryboot still relatable? Im not even able to finish the config on volumio.local its so laggy. On SD card with normal image no problem tho…
Is it new Volumio install or upgrade? (assuming original install done through github script)
Which device?
Which Berryboot release date(i.e kernel)?
It’s true Berryboot is unfortunately not frequently updated with kernel releases, and maxnet does not seem to be willing to support non armv8 Pi devices anymore…
Original install done through github script with Raspbian.
Raspberry Pi 4B 2GB model
Berryboot-20200612-pi4
I am able to boot it, but the config wizard on volumio.local don’t register change and loading time are way too slow its un-usable
I do not have Pi4 to test unfortunately, but there have been some earlier success reports.
Can you install an earlier Volumio version (like 2.779 which was reported OK), set-it up & test.
And then do an update with Volumio UI?
How do i install earlier version of volumio? I can only find the 2.8xx version not the 2.799
my install scripts give you the option to type in desired Volumio version.
Unfortunately, berryboot has now abandoned support for Pi 0/1/2, and focuses exclusively on 64bit architecture Pi3/Pi4.
While berryboot-scripts may still happen to work for some time, I don’t think I’ll be supporting/fixing them in the future, and I’ll probably move Github project to archive mode.
Anyone motivated can eventually fork/take it from here.
The script to install Volumio generates the following error as the version defined within the bash script is too old (current version is 2.907).
curl -Ls --output installVolumio2 https://bit.ly/InstVolumio2; chmod u+x installVolumio2; ./installVolumio2
*** Performing self-update
*** Relaunching after update
######################################################
########### Volumio2 install on Berryboot ###########
########### version 1.2 by macmpi ###########
This script prepares and installs Volumio2 image for use under berryboot on
Raspberry Pi
It MUST be run under a Debian Linux OS (like Raspbian-lite) and with
internet access.
At first run, it may install missing Debian packages: this can take time...
(sudo rights are needed for Debian installs, mounts and image copy)
If run under Pi with berryboot (recommended), it will try to install image into
final location (SD/USB disk encrypted or not, iSCSI).
If not run under berryboot (Pi, PC,...), it will try to copy image to
any connected media eventually containing a berryboot partition.
If no berryboot data partition is detected, image file may be produced in
working directory, for later-on use...
Hit any key to continue, or "q" to quit j
Found berryboot partition at /dev/mmcblk0p2 : do you want to use this one? [Y/n] Y
Could not identify latest version, falling-back to version 2.296
Please input desired Volumio2 version (format: 2.xxx 2.185 minimum advised)
List of available versions here https://volumio.org/forum/changelog-t1575.html
For default version 2.296, just hit [ENTER] :
Please input name for the image (no space or special characters)
For default name Volumio2, just hit [ENTER] :
Downloading original image from Volumio2 repo, this may take a bit of time...
failed on url http://updates.volumio.org/pi/volumio/2.296/volumio_current.sqsh.zsync
could not read control file from URL http://updates.volumio.org/pi/volumio/2.296/volumio_current.sqsh.zsync
Volumio2 image download failed, or wrong version.
cleaning-up...2.296 has probably been pulled – try a more recent version…
Hi.
Is this still applicable to the current Volumio version?
With x86 and uefi boot you could modify the grub configuration, done it once, but needs corresponding grub configuration knowhow. Not for the faint-hearted, a mistake in the config can render the whole install not bootable.