No more sound after installing v. 4.1 in recalbox

[Dragu]

@Substring
@lackyluuk

I have also now the card appearing as choice in the ES soundmenu

But, still one problem.
If I switch to the existing share folder on INTENSO SSD, the sound disappear some trace perhaps in the background with alot of noise. @Substring , I am sure you know the answer.

[lackyluuk]

@Dragu i will try this and report then
Didn't know that hifiberry is a swiss company..i should blame them to put my country to a bad light, lol
ps. fondue is better

[Substring]

@dragu still on a pi3 ?

[Dragu]

@Substring
Yes, I just have running big transfert backup from my bartop share folders to the server.

[Substring]

@dragu does dmesg show anything ?

[Dragu]

@Substring
Yes, driver seems ok.

  2.142276] snd-rpi-hifiberry-dacplus soc:sound: pcm512x-hifi <-> 3f203000.i2s mapping ok

I suppose I have an error in recalbox.conf. I will compare both.

[Dragu]

@Substring
I just compared recalbox.conf 4.1stable from origin to my share recalbox.conf. Nothing that could cut off sound.

[Dragu]

@Substring
@lackyluuk

This becomes totaly crazy now.
To resume :

1. Before today I used version 4.1u (march) with my shared files on INTENSO Disk.------> Sound working, Bluetooth + Wlan also.
2. The link from github with older overlays and hifiberry-dacplus.dtbo makes actual version 4.1stable functional with working sound.
   To remember, this driver is exactly the same from 4.1u (march) version.
3. As long as I use internal storage (with internal share), sound working,
   but after selecting Intenso and using my existing share folders, sound is dead again. Ok, not completely dead because you hear some trace of sound, the card exist, the driver is loaded, the same as on the internal share, but no sound.
   If I switch in ES system back to internal storage, sound comes back again.
   Crazy, or ?

[Substring]

@dragu you probably have a ~/configs/asound.state on your SSD that you should remove + set the DAC in ES + fool around with TERM=xterm alsamixer to raise volumes

[Dragu]

@Substring
TERM=xterm alsamixer was exactly the solution, now I am arrived on 4.1 stable and thanks alot.
I put volume on 100%, as anyway I have volume regulation on amplifier.

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