@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.
@dragu No it's an uppercase one, not a lowercase. It's to force the dest filename
@Substring
Ok, I will proceed again with fresh card.
just updated my post to add a chmod
@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.
@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 ...
@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
@Substring
To compare, I shot the screen lsmod from march 4.1u
Thanks anyway for your help and not urgent.
@Dragu @Substring I will try it out as well with the old config.sh and report as soon as I am home.
@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
@Substring https://file.ac/drgmKFzTWo0/
dtparam=audio=ondtoverlay=hifiberry-dacplusdtdebug=1Not even the green indication light on the hifiberry dacplus is on 
Anything else I can test?
@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
@Substring I have attached one above 
@Substring Did you already have time to have a look at the support archive?
@lackyluuk sorry, this got out of my mind ...
Well, nope, nothing special, as if the pi wouldn't load the overlay or god knows what
@Substring
Yes, I understand,
the x(86) compatibility is a killer.
@Substring okay, thank you for checking. I ran out of ideas Just let me know when you have some new ideas to check
Thanks mate
@dragu someone's making fun at me here, uh ? 
@lackyluuk the only thing i understand is that kernel modules aren't loaded. So i guess the device is not found by the kernel.
@Dragu do you think you can check in your march version if dmesg finds the hifiberry ?
@Substring
Hi,
Yes I see it on the list. How can I send you the result of dmesg ?
@dragu you can create a support file. The easiest way is to let it be created by the recalbox manager. There you also get directly a link to the file which you can share
@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
