No more sound after installing v. 4.1 in recalbox

[lackyluuk]

@Dragu The guy from hifiberry thinks that it could be a hardware failure. I really don't know.
Is there the possibility of having a 4.0.0 installation of recalbox? There it worked for sure.

[Dragu]

@lackyluuk
I just checked, previous release are again disponible for download
https://github.com/recalbox/recalbox-os/releases
In 4.0.0 is a driver version with 1378 length.

[lackyluuk]

@Dragu Then I will try this one for a next test

[lackyluuk]

@Dragu @Substring Thank you very much for all your help.
I think my card had a sudden death after the update to 4.1 stable

I just tried with 4.0.1 stable where it worked perfect. And now it's not even recognized there.
I am going to buy a new one and try again

[Substring]

@lackyluuk my DAC+ with RCA output worked straight out of the box

[Dragu]

@Substring
Really good for you. But is'nt it afraying that with new driver release from this company, former versions of the card are not working anymore ? This should not, never be. And who knows, perhaps next version driver just will work with cards from 3.0 on....

[lackyluuk]

@Dragu According to their support the EEPROM has nothing to do with it. It's just for pre-configuring so that you don't have to change config.txt anymore.

[Dragu]

@lackyluuk
For me all this looks as if there is a system behind. You know that some asian clones of Hifiberry DAC circulates that use this driver. I think, they wanted to eliminate the imitations and on the way also eliminate some of own cards, not at last version number. I bought my card in 2016, from them. So nothing good here.

[Dragu]

@Substring
@lackyluuk
I am asking me that if there is not a small chance, but too less knowledge for an answer on my own.
So, for this one time working DAC+ 1.0, should it not only be necessary to copy the driver from 4.0.0 but also the codec that has another version "snd-soc-pcm512x.ko" 27744 ?

[Substring]

that's our mistake to include odtbo compiled with 4.9 kernel whereas we're still on 4.4

[lackyluuk]

Wait what? Please an explanation for dummys

[Substring]

@lackyluuk i'm saying that we , recalbox dev team, should have stayed at a 4.4 kernel + compatible overlays. We're probably out of sync. That's something that never caused any harm so far ...

[clappique]

Hello, I have the same trouble since I've upgrade to 4.1.
Is there an issue or should I have to buy a new hifiberry board ?

[lackyluuk]

@clappique I dont know what your issue is exactly. I am going to buy a new one since mine is not even recognized by the hifiberry test images.

Have you already tried our whole discussion?
(Using an older hifiberry.dtb, using test images etc)?

[clappique]

@Dragu i didn't see the last posts about the driver available on github.
Everything is actually OK after some hours trying to get the sound back.
Many thanks to this precious post and to the community !

[Dragu]

@clappique
Très bien, mais c'est @Substring qui a eu l'idée. je ne suis qu'un humble serviteur

[wegen]

bonjour,

plus beaucoup de news avec ce sujet. Est-ce que la compatibilité en recalbox et HiFiBerry a été corrigée ?

Merci d'avance

[klubad]

Hi @Substring

I also have a rpi3 with a hifiberry dacplus. I have no sound either.

I followed the instructions found here. With the old hifiberry-dacplus.dtbo file, the card now shows up in reacalbox UI and alsamixer. (I got the device tree file here https://github.com/raspberrypi/firmware/tree/b4b1f641ba1290bdf275b99922e16c0194a8e54b/boot/overlays)

But I can't have any sound. I tried to move up every sliders in alsamixer, but still no sound. Am I missing something?

[Substring]

@klubad have you selected the device in ES and rebooted ?

[klubad]

@substring yes, multiple times

As much as I understood, it seems that we can't set volume through ES. So if I change the volume in ES, close the sound panel and reopen, volume is set back to 0. It is the expected behavior with hifiberry card, right?

I can provide you dmesg output and other stuff tonight.