No more sound after installing v. 4.1 in recalbox

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

[Substring]

@klubad ES is not very good at setting sound volume for anything other than the pi itself tonbe honnest. Alsamixer is a much better choice.

[klubad]

@Substring well, I tried to set the volume through alsamixer (and amixer too). No sound.

Any advice of what I could test next?

[grgohr]

hello @substring maybe an old topic but there is no sound in ES since 4.1 and thought it was a temp bug but not fixed with 1802 (XU4) (sound in videointro ok, sound in game ok)

here are the ES logs at first boot:

lvl0: Error loading sound "../sounds/scroll.ogg"!
Audio device hasn't been opened
lvl2: req music [system.bgsound]
lvl2: playing
lvl2: Mix_PlayMusic: Audio device hasn't been opened

Going in to the sound menu and validating a soundcard activates sound in ES (sound volume is always 0 but does not affect anything, can be ignored for XU4)

[Substring]

@grgohr hey !
The sou d card parameter is supposed to be saved. How do you turn off your recalbox ?

[grgohr]

@substring even after a proper menu>quit>shutdown or reboot I have the same behaviour and ES logs:

lvl0: VolumeControl::init() - Failed to find mixer elements!
lvl0: MUSIC Error - Unable to open SDLMixer audio: ALSA: Couldn't open audio device: Device or resource busy
lvl2: Mix_PlayMusic: Audio device hasn't been opened
lvl0: Error loading sound "../sounds/scroll.ogg"!
Audio device hasn't been opened

once I go to the menu>sound and change the device from auto>card or vice-versa (I hear a sound click), sound comes and back and ES logs shows:

lvl2: Shutting down SDL AUDIO
lvl0: VolumeControl::init() - Failed to find mixer elements!
lvl2: SDL AUDIO Initialized
lvl2: playing

also sound comes back after going into a game and chaning nothing in ES menu:
lvl2: Mix_PlayMusic: Audio device hasn't been opened
lvl2: Attempting to launch game...
lvl2: Shutting down SDL AUDIO
going back from game
lvl0: VolumeControl::init() - Failed to find mixer elements!
lvl2: SDL AUDIO Initialized
lvl2: playing

it seems that the following step is the key to have proper init of sound in ES
lvl2: Shutting down SDL AUDIO

[Substring]

@grgohr es may be trying to open the 1st sound card which must be the HDMI output (which hsmas no mixer available)