No more sound after installing v. 4.1 in recalbox

[Dragu]

@Substring
From Hifiberry Website
"
The DAC+ Light uses a different DAC chip (from ESS instead of a Burr-Brown model), which allows us to offer you an even more affordable DAC for your Raspberry Pi. It lacks some features of the DAC+: It has no integrated EEPROM (which is no problem at all) or integrated volume control. To control the volume, you need to connect it to an amplifier with integrated volume control or use so-called software volume control. The latter option is supported in many—but not all—applications.
"
For me it seems as a driver was at a certain moment renamed and perhaps the driver for DACPLUS use the wrong chipset. Like both are different.
That could be a plausible explication.

[lackyluuk]

it becomes even more strange
With Dragu's image I can see with lsmod the DAC+. But the led is not working and I can also not access amixer or alsa settings...thus it does not really work...

dmesg tells me this (Image of Dragu):
[ 3.434116] snd-rpi-hifiberry-dacplus soc ASoC: CODEC DAI pcm512x-hifi not registered
[ 3.434130] snd-rpi-hifiberry-dacplus soc snd_soc_register_card() failed: -517
[ 3.515429] snd-rpi-hifiberry-dacplus soc ASoC: CODEC DAI pcm512x-hifi not registered
[ 3.515452] snd-rpi-hifiberry-dacplus soc snd_soc_register_card() failed: -517
[ 3.519463] usbcore: registered new interface driver brcmfmac
[ 3.519487] snd-rpi-hifiberry-dacplus soc ASoC: CODEC DAI pcm512x-hifi not registered
[ 3.519496] snd-rpi-hifiberry-dacplus soc snd_soc_register_card() failed: -517

[Substring]

@lackyluuk mmhhhh ... Should try with an older version of the firmware then

[Dragu]

@lackyluuk
@Substring

I have exactly the same dmesg as you can see on my screenshot with march version, but try some more sound-test.
Because, when you enter ES, led is green! and sound working in ES, Kodi, Games.
When I go to the root, led goes out and it gives me the following dmesg :
But you really tried out the sound in ES ? Because this is working for me and @benj008 also.....
In line 10 he makes some mapping.

[Substring]

@dragu please select text in putty, it's automatically copied to clipboard, then paste it here surrounded by 3 back quotes, it's easier to read and manipulate

[lackyluuk]

@Dragu What do you mean by "going to the root"? You mean go to the terminal?
My led is off when I turn of my recalbox. No sound in ES.

[Dragu]

@Substring
ok, first time I use putty for Recalbox. Difference, the led stays green as I must not quit it. But result the same, always in working march version 4.1u

[    2.754525] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CPU DAI (null) not registered
[    2.754540] snd-rpi-hifiberry-dacplus soc:sound: snd_soc_register_card() failed: -517
[    2.757516] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered
[    2.757529] snd-rpi-hifiberry-dacplus soc:sound: snd_soc_register_card() failed: -517
[    2.813147] usb 1-1.2: New USB device found, idVendor=0079, idProduct=0006
[    2.813165] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.813172] usb 1-1.2: Product: Generic   USB  Joystick
[    2.813178] usb 1-1.2: Manufacturer: DragonRise Inc.
[    2.817897] usbcore: registered new interface driver brcmfmac
[    2.822122] snd-rpi-hifiberry-dacplus soc:sound: pcm512x-hifi <-> 3f203000.i2s mapping ok

@lackyluuk
I mean, when I leave to ssh with F4. Otherway, when I start Recalbox, led directly on and sound working.
You made also the usual modifications in this march version, config.txt, asound.conf.

[Dragu]

@lackyluuk
@Substring
Between 4.1u march and 4.1s all codec drivers were also updated (03.17 - 10.17) and here interesting question on the hifiberry page, with same error 517 :
https://support.hifiberry.com/hc/en-us/community/posts/207236915-Dac-pro-error-in-dmesg
even more interesting
https://support.hifiberry.com/hc/en-us/community/posts/207234405-RPi3-and-DAC-Pro-Linux-not-working-Working-on-a-fix-

[Dragu]

@Substring
I think I found something, just follow the second link.
They were having an issue with PI3,DAC+ and internal bluetooth. They proposed at this moment to disable it by the following lines :

dtoverlay=pi3-disable-bt
dtoverlay=hifiberry-dacplus

I wanted to try it out on 4.1 stable, but pi3-disable-bt not working.
Perhaps the codec version is from this time.

[Substring]

@dragu ok i'll give a go on a pi3
Anyway, this looks really wierd as it used to work some time ago with bt enabled

[Substring]

@lackyluuk @Dragu give a try to the last 4.4 commit on firmware + dtbo files : https://github.com/raspberrypi/firmware/tree/b4b1f641ba1290bdf275b99922e16c0194a8e54b/boot

[Dragu]

@Substring
And how to proceed, Master ?

[lackyluuk]

@Dragu This is what I tried out the last 20 min lol
there is a directory in /boot where to add the .dtb files?

[Substring]

@lackyluuk @Dragu in fact just get the iverlays for a starter, we'll see if it's worth a total rollback with the firmware after

[Dragu]

@Substring
Github is not my world, so how to download all overlays without taking one by one. ?

[Substring]

@dragu you just need the overlay for your DAC

[Dragu]

WE HAVE A WINNER !
It's working. So as I understand, this is an older version from the driver. Not the fault of Codec but Switzerland? Bye, bye, Raclette, I cannot stand the smell anymore

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

[lackyluuk]

@Dragu Great! Can you please explain what & how you did this? I still don't get it how to change the overlay

[Dragu]

@lackyluuk
I just download the overlay : hifiberry-dacplus.dtbo from the github after @Substring told about. Just this unique file and replaced the old one in the 4.1stable overlays. Size 1436 against 1693.

[Dragu]

The version from kernel 4.9.11 the last in build was the not working version. The actuel working is from 4.4.
Bulls**t that this company dont offer very simple download from their website. Time to shake them.