No more sound after installing v. 4.1 in recalbox

[lackyluuk]

@Dragu great that it works fine for you now
I still don't know what to do else..not even the test image of hifiberry detected my DAC+. Thats weird.

Since recalbox is detecting my card i think its not dead..

@Substring Does it make sense to start from scratch, with a clean installed version?

[Substring]

@lackyluuk which hat do you have ? same as me or Dragu ?

[lackyluuk]

@substring I have DAC+ HW 1.0 with RCA connectors soldered

[Substring]

@lackyluuk ok mine is rev 2.6
So, step by step :

• does the module appear in ES as a sound output ?
• have you tried doing like dragu (get an old dtbo) ?

[lackyluuk]

@Substring

• No, I only have Auto, Jack and HDMI as sound outputs
• Yes, I tried the same .dtb as Dragu. No luck.

As you can see some posts before, I am somehow missing the "i2c mapping ok" line in the dmesg output

[Dragu]

@lackyluuk
You can find even an older version, from 4.0 time, where it was still working ? I guess it was not yet device tree driver. If you cannot find, like you are in the country, I would speak to them and they should be able to adapt your version.
I just looked and compared, the version from hifiberry-dacplus.dtbo in 4.0.1 was the same as my working now with 1436 length.

[lackyluuk]

@Dragu okay, thank you! What do you mean with 'adapt' the version?
I wrote them now since my card is not even recognized on a different RPi 3 with their test images.

[Dragu]

@lackyluuk
I hope the company can burn you the eeprom to an newer version,
but you tried to go back to a stage where your card still working and using a driver from this version ?
Anyway, its not normal, the bullsh.. that they have with the drivers. No download on the website, no version following...
Very strange, the last (not working) version is not integrated in their Raspian lite distribution. I unpacked it and inside the same with 1436 length. Insane that newer driver disable previous version cards.

[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 ...