No more sound after installing v. 4.1 in recalbox

[benj008]

tu fais comment? j'ai pas trop l'habitude sorry

[Substring]

@benj008 ah ok

mount -o remount, rw /
rm /etc/asound.conf

Ensuite tu rebootes et tu me dis

[benj008]

merci!
mais je n'ai toujours pas de son...

[Substring]

@benj008 donne moi la ref exacte de ton hifiberry stp + archive de support en allant sur http://recalbox/help

[benj008]

c'est un hifiberry DAC+ standard RCA (n° modele 4260439550057)

voici pour le lien:
https://file.ac/H7idCNRf1ZE/

[lackyluuk]

@benj008 @Substring
I will test it tonight since I didn't have the chance yet to try 4.1.
I'll give a feedback then

[benj008]

@lackyluuk ok thank you very much ! hope i don't bother you too much...

[lackyluuk]

@benj008 Not at all. Actually I cannot wait any longer to try it out because I was away the whole weekend and couldnt install it. Lol

[benj008]

@substring je ne sais pas si mon dernier message est passé desolé...le voici

c'est un hifiberry DAC+ standard RCA (n° modele 4260439550057)

voici pour le lien:
https://file.ac/H7idCNRf1ZE/

[Dragu]

@benj008
@lackyluuk

I have also the issue with my hifiberry DAC+ not working with 4.1 stable.
Just for history, I was having the same problem with 4.1 unstable from april and switched back to 4.1 unstable from march, where the sound was working. Issue that I didnt followed. So it seems to me that something important changed between this 2 versions that was important for the DAC story.
What I changed so far on 4.1 stable (just today jumped in )

/boot/config.sys
comment out
#dtparam=audio=on

and put missing section

# uncomment for hifiberry
dtoverlay=hifiberry-dacplus

/etc/asound.conf create

pcm.!default {
type hw card 0
}
ctl.!default {
type hw card 0
}

etc/modules.conf
comment out

# snd_bcm2835
uinput
usbhid

for the moment, silence is golden.....

[Dragu]

There is a very simple way to find out if the hifiberry-dacplus card is adressed.
On the board is a green led, when the card is in contact with a driver, it is lit. When it has no connection with software, is dark.
I changed again the cards and on 4.1 stable, led is not on. With my unstable from march, led and sound.

[benj008]

@dragu so is it possible to get back and reinstall 4.1 from march? maybe it's one of the solutions for my issue

[Dragu]

@benj008
I think, they should have a chance to look into this.
I have the system on another card, so easy for me to change, till they find a solution.
But if you have no image anymore from build 11603320, I have no idea.

[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