Volumio 2 on PINE64/ PINE A64-LTS / SOPINE Compute Module

It is OK. I have tried in private navigation and it is OK. I see the Tidal et Qobuz options.

Thanks @gkkpch

thanks for reporting back, saves me from investigating.

@gkkpch: I just upgraded my sopine-a64 to .861 with wifi module, ESS9023 DAC and eMMC and it works PERFECTLY! Thank you very much for all your efforts on this platform.

Hi Guys,

new member and hopefully soon to be new user. I wish to use a rockpro64 as the basis for a digital speaker crossover and streamer, running camilladsp and outputting i2s to a multichannel dac PCB iā€™m designing, using ES9038PRO. see that you have gotten the i2s working properly, over the course of this thread. at least it says the rock64 is supported, so I hope the rockpro64 is. Can you please confirm that it is not just 2 channel i2s supported? ie, are all 8 channels i2s output available? (all 4 x sdata pins). thanks for your time

rock64 and rockpro64 are two different pairs of shoes.
rock64 works fine, rock64pro never got ported, due to lack of demand, no plans either.
and, Volumio will never have >2 channel i2s support for any board.

Hello,
I had volumio running on plain Pine64 with 512M and it worked awesome. At some point I decided to upgrade it with new image, and I couldnā€™t make it working. Builds 863 and 857 both have issues with wifi on my device (with wifi-bt hat on rtl8723bs). It reported ā€œincorrect passwordā€ with volumio2 and failed to initialize eth0 on the board. Unfortunately, I couldnā€™t fallback to any working version as I got no backup of my sd card. Links with previous version volumio-2.528-2019-01-12-pine64 and volumio-2.383-2018-03-17-pine64 are broken on the page. I would really appreciate if someone share any working solution for old vanilla pine64, with wifi, please. Thank you

I think I know what the issue is, the 512Mb version has another ethernet NIC. This is specified in the device tree for the pine64, but with the latest versions it might be that the one for pine64+ is loaded.
I canā€™t verify this as I only have a Pine64+ available for testing.
A separate image version for pine64 and pine64+ was already done for the Volumio 3 buster version, but this is not ready for release or beta yet.
Volumio 3 will get beta versions for Pine64 in the coming few weeks.

As I there are only very small number of Pine64 users (mostly Pine64+), I do not intend to start modifications for building a separate version for Volumio 2, sorry about that.

Edit: Perhaps we can fix it with a small modification of the boot configuration, you will need some linux file editing skills, please let me know if that is OK.

rtl8323bs (the one from the Pine64 store) appears to works fine, I see no issue with passwords or whatever.
Please submit a volumio log if you continue to have issues with wifi.
Howto: Send a log

Just downloaded volumio-2.775-2020-05-07-pine64 and volumio-2.715-2020-03-04-pine64, they should still work

Hi gkkpch,
thanks for your quick response and for promising news about volumio3, indeed.
Youā€™re right, it seems the pine64plus image is being loaded by default, and my updating it to pine64 in the uEnv.txt makes no sense, I suspect it uses pine64+ despite my changes.
About logs, If I only could make my board accessible over ssh, I would easily grab them, but at the moment I can login there using usb keyboard and hdmi, and yes, Iā€™m able to run linux commands and edit configs. Please, give me a hand, Iā€™ll try figure out.

Please edit uEnv.txt this way:

verbosity=8
console=serial
kernel_filename=Image
initrd_filename=uInitrd
fdtfile=allwinner/sun50i-a64-pine64.dtb
squashfile-arg=imgfile=/volumio_current.sqsh
bootpart-sd=rebootmode=normal bootdev=mmcblk0 bootpart=/dev/mmcblk0p1 imgpart=/dev/mmcblk0p2 datapart=/dev/mmcblk0p3
hwdevice=hwdevice=pine64
overlay_prefix=sun50i-a64

Note the new fdtfile and modified hwdevice line.

1 Like

Works like a charm, thanks a lot! As I understood, directive fdtfile overrode default plus dtb. On first boot I plugged in wired eth0, then went to the UI and set up the wifi and switched off wired connection. You saved me hours, I can listen to my music again!
With respect,
Sergei

Yes, anything configured in uEnv.txt will override the standard settings from uboot.
Obviously the new uboot canā€™t differ between pine64 and pine64+ anymore.
Glad to be able to help, knew it couldnā€™t be anything big.
So, with Volumio 3 you will have a separate image, should work ootb.

Please read this IMPORTANT notice!

Iā€™m working on an update for all supported Pine64 devices.
They should be available sometime tonight.

New updates are available, either use OTA (System Menu ā†’ System ā†’ Check Updates) or reflash.
Of course, many other changes flowed into this version.
Refer to the changelog on the download page for a detailed list since your last update.

volumio-2.916-2021-10-01-pine64plus
volumio-2.916-2021-10-01-pine64solts

I unsuccessfully tried the OTA and reflash for the PIne64plus. On the reflash the password of volumio2 did not work for the hotspot and the ethernet failed to work. I was successful in reflashing my RPI3 using the hotspot with volumio2 as the password.

for OTA, Pine64 needs test mode to be set.
Are you sure, you took the correct image for your board?

Thanks for your reply. For the OTA update, I put my Pine64 plus in test mode to update to v2.916 but after system restart it did not boot into the new v2.916 version. It remained at v2.715 with a unworkable Spotify Application.

In regards to a re-flash, I took the volumio-2.916-2021-10-1-pine64plus.img image because I have the first version of the Pine64 Plus 2G board.

Thanks, I have to load the image on my pine64plus and see what happens.
Can take a few days though as weā€™re busy with volumio 3.

Thanks for all your support on these Pine modules and I will patiently await your advice.

Upgraded sopine-a64 OTA with wifi module, ESS9023 DAC and eMMC to .916 after setting test mode (http://<ip.addr>/dev). Works great.

Again, thanks for your continued support of this platform!