No more sound after installing v. 4.1 in recalbox

[Dragu]

Non, non.
Sur ta console tu ouvre le menu configuration controlleurs et alors tu vas sur Recalbox Manager la ligne "screenshot" pour faire une image écran de ta console.

[benj008]

@dragu je suis désolé je capte pas ce que tu demandes : Sur ta console tu ouvre le menu configuration controlleurs

[NeeeeB]

console = pi
dans EmulationStation il veut dire.

[benj008]

dans option manette sur ES, qd je configure en laissant un bouton appuyé, mon matos s'appelle tht 2p arcade controler tht 2p arcade controler (deux fois...) que j'appuie sur le set joystick + boutons à gauche ou celui à droite.
je peux faire un screenshot mais je vois pas trop en quoi ca va vous aider

[benj008]

j'ai édité cmdline.txt et ajouté:
usbhid.quirks=0x16c0:0x75e1:0x040 et les deux sticks sont reconnus pour les 2 joueurs
quel bazar...

[Substring]

@dragu @lackyluuk
The whole changelog between the 2 builds that Dragu reported working/non working is here

What is written as "+" is what has been added since the working version. What is "-" has been removed from the working version. One tric could be to test the recalbox-consig.sh from the working commit by doing

mount -o remount, rw /
cp /recalbox/scripts/recalbox-config.sh /recalbox/scripts/recalbox-config.sh.backup
wget -O /recalbox/scripts/recalbox-config.sh https://gitlab.com/recalbox/recalbox/raw/443dd09ba56305fa6ebf2afff5fc9be376f7c987/board/recalbox/fsoverlay/recalbox/scripts/recalbox-config.sh
chmod u+x /recalbox/scripts/recalbox-config.sh
reboot

Test and report, with a lsmod please

[Dragu]

@Substring
I suppose that wget -o is from small (o)ctave. ok ?
I entered it like this on a fresh 4.1s card. So, when you select after mods the sound menu in ES, there are nomore device to select and ES sayed goodbye.
After reboot, also Wlan dead, and not possible to restart. So, lsmod just with screen-photo from camera possible. If you want, I will make it.

[Substring]

@dragu No it's an uppercase one, not a lowercase. It's to force the dest filename

[Dragu]

@Substring
Ok, I will proceed again with fresh card.

[Substring]

just updated my post to add a chmod

[Dragu]

@Substring
This time, seems it was working. But still no sound, just for the feedback.
Like it was a fresh install, just need some time to configurate the network.
And for your info, I also did the hifiberry line in config.txt, and comment dtparam.

[Substring]

@dragu So this is definitely not a recalbox config itself problem, but a kernel modules loading ...

You should try to manually modprobe all the missing modules from your previous screenshot. What I don't understand is why the kernel doesn't detect your hifiberry and load the drivers accordingly ...

[Dragu]

@Substring
You should try to manually modprobe all the missing modules from your previous screenshot. What I don't understand is why the kernel doesn't detect your hifiberry and load the drivers accordingly ...

I am just a simple man...I am not inside this stuff.

Concerning my config.txt

[Dragu]

@Substring
To compare, I shot the screen lsmod from march 4.1u
Thanks anyway for your help and not urgent.

[lackyluuk]

@Dragu @Substring I will try it out as well with the old config.sh and report as soon as I am home.

[Substring]

@dragu I prefer support archives
Hifiberry doc suggests to add dtdebug=1 in config.txt to eventually debug. could you add it ? (see "Device not recognised?" at https://www.hifiberry.com/build/documentation/configuring-linux-3-18-x/) and make a support archive ? I'd like to check what dmesg reports

[lackyluuk]

@Substring https://file.ac/drgmKFzTWo0/

• Added your "old" config.sh
• Commented out dtparam=audio=on
• Added dtoverlay=hifiberry-dacplus
• Added dtdebug=1

Not even the green indication light on the hifiberry dacplus is on

Anything else I can test?

[Substring]

@lackyluuk i need the output of dmesg since dtdebu=1 should make device trees verbose. You can make a support archive, that would be even better

[lackyluuk]

@Substring I have attached one above

[lackyluuk]

@Substring Did you already have time to have a look at the support archive?