06-05-22, 21:49 -
Hi Besibesi,
I assume that you started your actions because you don't have sound now.
Some remarks:
If samplerbox is started, the audio device is busy, because it's in use by samplerbox.
There was no need to install extra software. Samplerbox is reported to run hifiberry out of the box, after making two changes in the config.txt.
One change is adding the appropriate overlay, which you (or the install) did.
I noticed you (or the install) also commented the dtparam line in the config (the second config change), which should rule out any conflicts there, but the comments state you should set it to off.
You also added force_eeprom_read=0, but I doubt this has influence here and I understood this has to be used from some hifiberry models..
In other words: config looks OK apart from that dtparam line.
As it happens I also use a hifiberry: debugging info gives similar results, apart from model differences
Looking OK too except for one line that I see, but is missing in your log:
So I checked my config.txt and saw I use explicit dtparam=audio=off
It's also useful to start the debugging actions as explained on the Build it page.
The messages during startup and play when running manually may reveal more.
And when samplerbox is inactive, you can also test with speakertest.
Hope this helps, Noek.
I assume that you started your actions because you don't have sound now.
Some remarks:
If samplerbox is started, the audio device is busy, because it's in use by samplerbox.
There was no need to install extra software. Samplerbox is reported to run hifiberry out of the box, after making two changes in the config.txt.
One change is adding the appropriate overlay, which you (or the install) did.
I noticed you (or the install) also commented the dtparam line in the config (the second config change), which should rule out any conflicts there, but the comments state you should set it to off.
You also added force_eeprom_read=0, but I doubt this has influence here and I understood this has to be used from some hifiberry models..
In other words: config looks OK apart from that dtparam line.
As it happens I also use a hifiberry: debugging info gives similar results, apart from model differences
Looking OK too except for one line that I see, but is missing in your log:
Code:
002023.147: dtparam: audio=offIt's also useful to start the debugging actions as explained on the Build it page.
The messages during startup and play when running manually may reveal more.
And when samplerbox is inactive, you can also test with speakertest.
Hope this helps, Noek.