No more sound after installing v. 4.1 in recalbox

[benj008]

@dragu thanks, i was careless, i didn't have a backup of previous 4.0.1

[Dragu]

@benj008
build 11603320 is an 4.1 unstable version, that I use (for me very stable, never had a problem).
I have still the image, but if I link it here, I will be in death row.

[lackyluuk]

@benj008 @Dragu @Substring

I have just installed 4.1 and my HifiBerry DAC+ is not working at all. In the settings I can only choose between AUTO, JACK and HDMI.

The dtoverlay in /boot/conig.txt is still dtoverlay=hifiberry-dacplus and the green LED on the card is on.
But somehow in alsamixer the card is not showing up. The only soundcard is the internal.

With cat /proc/asound/cards i get the following:

0 [ALSA           ]: bcm2835 - bcm2835 ALSA
                     bcm2835 ALSA

If I remove this driver I cannot access alsa or amixer anymore

Still try to figure out some other ways to check the soundcard implementation...

[benj008]

same for me..

[Dragu]

In build 15156473 the problem was appearing for me.

[Substring]

@benj008 @lackyluuk @Dragu The only things that changed regarding sound are how the volumes are set/forced at boot, so I have an idea where to look BUT as I can't test by myself, I need you guyz.
So first remount / as read-write : mount -o remount, rw / then edit /recalbox/scripts/recalbox-configure.sh and comment line 409 by adding a # at the start of it and report back If it worked, remove the #, and set the volume to 100% in ES, reboot and report back.

[benj008]

@substring salut
Tipping /recalbox/scripts/recalbox-configure.sh path in putty seems to bring me to an empty file

[lackyluuk]

@Substring I will test it tonight when I am home. Thanks for the approach!

[Dragu]

@Substring
You sleep sometimes ?
The file name is in my installation recalbox-config.sh, I think you mean the same.
I made the comment out, it had no effect. I also changed in ES the sound to 100%. But the animal put it back directly to 0%, no way.

I have some other issues with 4.1s, dont want to kill you.

[Substring]

@dragu I guess I spend about 4 to 6h a day on support for 4.1 since Friday, and it's becoming exhausting ... So many people who just can't read or report false bugs ... Have to find the truth in all forum topics

But the hifiberry IS a real regression bug that sadly I can't test at home

Now can you make that line 409 look like :

for param in `amixer controls | cut -d ',' -f 1` ; do recallog "Setting volume for $param" ; amixer -q cset ${param} 100% ; done

reboot, and report ?

[Dragu]

@Substring

No, it has no effect. In ES the sound level is put back to 0% after leaving the sound menu.
But in my beloved version from march, this is the same, anyway as the volume for this card is not regulable and always at max.
I see the problem from the driver side, the hifiberry driver is not loaded. If you have the tools to run a compare between versions. If you compare build 11603320 with the stable release, somewhere shoud be the answer, I think.

[benj008]

@substring same for me the 409 line looks line the one you propose already and even with the # changes, no sound again.
But my ES seems to save volume after reboot or leavong dound menu unlike dragu..

[Substring]

@dragu said in No more sound after installing v. 4.1 in recalbox:

11603320

ok that's the runner ID.

Have you followed https://support.hifiberry.com/hc/en-us/articles/205377651-Configuring-Linux-4-x-or-higher ? looks like it's not "compatible" with our default config.txt

[Dragu]

@Substring
Yes, the modifications in the config.txt are made this way. Would also be interesting if aplay was in the package.

[Substring]

@dragu aplay is not on the pi, but aplay is not useful in that case.

Try this :

cat > ~/.asoundrc << EOF
pcm.!default  {
 type hw card 0
}
ctl.!default {
 type hw card 0
}
EOF

reboot, report

[Dragu]

@Substring
No change.
But I have no directory /proc/asound/ as lackyluuk has.

[lackyluuk]

@Dragu Don't know if it's relevant for this, but have you created a asound.conf file?

I also noticed that if I remove the internal sound card, it is added back after every reboot into /boot/config.txt

[Dragu]

@lackyluuk
@Substring

Yes, /etc/asound.conf I created, is there that I made the modifications from
before, (cat >..) I expect it was the right place, or should this block be in /boot/config.txt ?

[Substring]

@dragu WTF ? no /proc/asound ??? i guess lackyluuk hasn't removed the dtparm=audio=on from the config.txt. But still ... I'll look at changes since March

[lackyluuk]

If I remove dtparam=audio=on in the config.txt it is automatically re-added after a reboot. Only commenting it out helps. But then I cannot access amixer, alsamixer etc anymore. And no soundcard at all is loaded