Hey @Itolo,
Yes please, this will help the community.
Kind Regards,
hi @nerd
after 15 reboot the ALSA error appeared
Volumio OS 3.735
http://logs.volumio.org/volumio/8z5nyKd.html
volumio@volumio:~$ cat /boot/config.txt
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
dtparam=i2c_arm=on,i2c_arm_baudrate=1000000
include volumioconfig.txt
include userconfig.txt
#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-dacplushd
volumio@volumio:~$ cat /boot/volumioconfig.txt
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
[cm4]
dtoverlay=dwc2,dr_mode=host
otg_mode=1
[pi5]
dtoverlay=vc4-kms-v3d-pi5
# dtparam=uart0_console # Disabled by default
dtparam=nvme
dtparam=pciex1_gen=2
[all]
arm_64bit=0
dtparam=audio=on
audio_pwm_mode=2
# dtparam=i2c_arm=on
disable_splash=1
hdmi_force_hotplug=1
force_eeprom_read=0
Thank you
1 Like
@nerd, I was happy to see the update notification for 3.742; unfortunately it has not straightened out my undefined-after-reboot DAC2HD.
http://logs.volumio.org/volumio/zYmKS86.html
I did the same settings dance that I’ve been having to do [1) disable I2S, 2) reboot, 3) enable I2S (select DAC2 HD), 4) reboot]. That got the player working, but it then became unresponsive (black screen in browser) after starting playback. I had to hard reset and functioning DAC settings were lost.
Hi @eduardo,
I am truly sorry responding this late.
For the benefit of the community
Edit /boot/userconfig.txt and add:
dtparam=i2c_arm_baudrate=1000000
This way, the configuration customization will prevail during upgrade.
Kind Regards,
I must concur with @eduardo, As from reading here the issue had been resolved, I kicked back and waited for the latest release, which I installed today. And, unfortunately, no go, still not working 
That appears to have solved it. Normal playback after the first reboot. 
http://logs.volumio.org/volumio/Jy74shC.html
Hi @nerd this is a fresh install of 3.742 on a Pi 5.
I have not yet tried editing the /bot/userconfig.txt file, nor the “[1) disable I2S, 2) reboot, 3) enable I2S (select DAC2 HD), 4) reboot” procedure. I will try those as soon a s I have time and get back to you.
I do hope these are temporary workarounds.
Please take a note of:
1 Like
Thanks, clear summary of the situation.
p.s. I believe VolumioOS 7.742 should be 3.742 
Thank you, corrected 
Hi @nerd ,
I have good and (possibly) not so good news.
After editing the /boot/userconfig.txt file and going trough the little I2S dance I finally got sound 
The euphoria was still high after a couple of reboots where sound was still loud and clear.
But when I fully shut down the Pi and powered it up again… No dice …
I had to go through the little dance again to get things working.
any advice/tips?
Please let me know if I can do any further testing, simulate any scenarios and send logs to help.
Hey @quintino,
Pi 5 from cold start works for me. Please generate logs from cold start that we can inspect your configuration.
Kind Regards,
hi @nerd ,
Here’s the link to the logfile, please note that I have a dsp add-on board installed as well.
http://logs.volumio.org/volumio/BjX9vSg.html
I started with a cold boot, did the disable/reboot/enable/reboot sequence and it was working.
Then I powered off the PI (did NOT disconnect the power) and, once it was “off” (as in power light was red) I pressed the power button. After that cold start the issue returned.
Let me know if I can run any tests that may help.
Hey @quintino,
Leaving obvious difference aside - do not have the DSP add-on;
On my Pi 5 i have in the config.txt:
#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-dacplushd,slave
Worth the test.
Kind Regards,
Hi @nerd ,
I added ,slave to thr dtoverlay, that made no difference.
Next I removed the DSP add-on, still, no dice.
Here’s the related logfile:
http://logs.volumio.org/volumio/frCVLrS.html
Please advise on any tests I can perform to help.
Hey @quintino,
Actually there are couple tests:
Test 1:
Shutdown and disconnecting from power source then start. The line of thought is that the GPIO is left active with no clock.
Test 2:
Since you are on Pi 5 - test with 64bit kernel - change /boot/volumioconfig.txt
arm_64bit=1
Please compare clocks from tests:
sudo cat /sys/kernel/debug/clk/clk_summary
Kind Regards,
Hi @nerd It’s evening here in Amsterdam and I’ll be off to dinner with friends, but I will perform the tests tomorrow and keep you posted.
Good morning/evening (depending on what part of this blue marble you live on) @nerd ,
I tried both tests 1 and 2 with the following results:
Test 1
Disconnect did not help, although your line of thought seems correct, as I could still measure 5V and 3.3V over the respective power GPIO pins.
Test 2
Switching from arm_64bit=0 to arm_64bit=1 did not help either.
Results of sudo cat /sys/kernel/debug/clk/clk_summary
When I compare the results of a bad state with those of a good state the only difference is:
GOOD state:
fw-clk-arm 0 0 0 1700000000 0 0 50000
BAD state:
fw-clk-arm 0 0 0 1700000000 0 0 50000
All other clock values are the same
That’s as far as I got, please let me know if I can do any further testing to help out.
Aw crap… Dirsegard the previous tests… I still had an IQaudIO DAC plugged into the PI 
I’ll run a new set of tests with the proper DAC and keep you updated…