No more sound after installing v. 4.1 in recalbox
-
I have the HifiBerry DAC+, HW 1.0.
It should be the same as @Dragu but not with the Jack but with the RCA connectors soldered to it.Here you can see my card: https://forum.recalbox.com/topic/8031/recal-cardboard-box
@Substring
have you created aasound.conf
file or was it not needed? -
@dragu I'll give it a go on a pi3, but still, it does work for me
my (filtered) lsmod reports :
Module Size Used by Not tainted snd_soc_hifiberry_dacplus 4100 1 snd_soc_pcm512x_i2c 2243 1 snd_soc_hifiberry_dac 2511 0 snd_soc_bcm2835_i2s 6354 2 snd_soc_pcm512x 17268 1 snd_soc_pcm512x_i2c snd_soc_core 125885 4 snd_soc_hifiberry_dacplus,snd_soc_hifiberry_dac,snd_soc_bcm2835_i2s,snd_soc_pcm512x regmap_i2c 3393 1 snd_soc_pcm512x_i2c snd_pcm_dmaengine 3391 1 snd_soc_core snd_pcm 75698 7 snd_bcm2835,snd_soc_hifiberry_dacplus,snd_soc_hifiberry_dac,snd_soc_pcm512x,snd_soc_core,snd_pcm_dmaengine snd_timer 19156 1 snd_pcm snd 51908 5 snd_bcm2835,snd_soc_core,snd_pcm,snd_timer clk_hifiberry_dacpro 2278 1 uio 8000 1 uio_pdrv_genirq
-
@Substring Okay, I tested with another RPi3.
- downloaded latest recalbox build -> installed
- mounted Hifiberry DAC+
- Removed dtparam=audio=on from config.txt
- Added dtoverlay=hifiberry-dacplus to config.txt
- rebooted
Nothing happens! No LED is on, no card is visible in ES..maybe the card is kaput?
-
@lackyluuk
Kaput twice no
Or voodoo or some code that changed bad in PI3 system. -
I tried now my hifiberry DAC+ Light card..and tada..recognized by recalbox....LOL
but i need my DAC+ standard...it looks really like its not working anymore.. -
@lackyluuk
Try onetime with
http://www.zclub.eu/recalbox_11603320.img.xz
It will recover from death.
Anyway, the DAC+ light is just the simple DAC, so you must declare it as
hifiberry-dac, not hifiberry-dacplus. -
@dragu thanks, I will try it out now.
yes, this I am aware of. the DAC+ light was recognized, but not the DAC+ standard -
@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. -
it becomes even more strange
With Dragu's image I can see withlsmod
the DAC+. But the led is not working and I can also not accessamixer
oralsa
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 -
@lackyluuk mmhhhh ... Should try with an older version of the firmware then
-
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. -
@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
-
@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. -
@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. -
@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- -
@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. -
@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 -
@lackyluuk @Dragu give a try to the last 4.4 commit on firmware + dtbo files : https://github.com/raspberrypi/firmware/tree/b4b1f641ba1290bdf275b99922e16c0194a8e54b/boot
-
@Substring
And how to proceed, Master ? -
@Dragu This is what I tried out the last 20 min lol
there is a directory in /boot where to add the .dtb files?