Ah, and testing with the latest LE11 nightly build (on a separate SD card) would also be interesting.
so long,
Hias
Ah, and testing with the latest LE11 nightly build (on a separate SD card) would also be interesting.
so long,
Hias
You could try increasing cma size further to 448 or 512 (the latter is used on RPi4 by default, but it could be problematic with only 1GB RAM).
It might also be worth to try a full clean installation on a separate SD card (without any further addons, skins etc) - it could also be related to some addon or setting you changed.
We'll need a full pastecrash log to give further advice (non-debug log might already help and cut size down, but debug log would be preferred of course).
so long,
Hias
Do you have an advancedsettings.xml file and have changed imageres , fanartres or other settings? If yes, remove your advancedsettings.xml file and test again.
so long,
Hias
Please try with stock config.txt (i.e gpu_mem=76 and no cma dtoverlay) - the log indicates you are running out of CMA memory, so 394 isn't enough.
Please post another log with stock settings if it fails.
so long,
Hias
It's a bit more involved:
in LE10 you need to change CONFIG_SND_SOC_TLV320AIC3X in projects/RPi/devices/RPi4/linux/linux.aarch64.conf to 'm', in LE10 you need to set CONFIG_SND_SOC_TLV320AIC3X_I2C to m
But the soundcard also needs a soundcard driver (dacberry400.ko) in addition to the device tree overlay.
The source code for the driver is in the src directory, but as the provided Makefile is a bit of a mess you'd need to adapt it before you can add a separate driver package for it to LE and include it in the LE build (see packages/linux-drivers/ for various out-of-tree driver packages).
Certainly doable, but a bit of a PITA.
As you payed good money to the manufacturer I'd prod him a bit more to get the sound card driver included in the official RPi kernel - or try to get a refund and buy a card with better support.
so long,
Hias
Keep gpu_mem at 76, setting it higher only wastes memory.
You could try reducing cma to 384 (as you did), but the problem seems to be that kodi is caching too many pictures and if they are large it runs out of memory at some point...
so long,
Hias
Just contact the manufacturer and ask them to PR the driver in the official RPi kernel source https://github.com/raspberrypi/linux then we can enable it when it's been added.
We won't be adding any out-of-tree drivers as they've been causing a lot of pain in the past (they need constant maintenance and tend to break on every other kernel update - and we do lots of them on a regular basis).
so long,
Hias
Thanks for reporting back!
The current LE10 nightly should be safe to use, we've been rather conservative and careful when updating the LE10 branch. But OFC we can't be 100% sure that something slipped through or will slip through in the future so always do it at your own risk.
I'm not sure if (auto-)updating LE10 nightly works as we've recently restructured the directory layout on the test server.
If in doubt just stick to the current nightly build, manually update it if you want or just update to the next official release when it's out (should be soon-ish, we're just waiting for Kodi 19.5 release).
so long,
Hias
Please test with the latest LE10 nightly build from here https://test.libreelec.tv/10.0/RPi/ this should contain a fix for your issue.
so long,
Hias
Just use arithmetic expansion https://pubs.opengroup.org/onlinepubs/969…ml#tag_18_06_04
so long,
Hias
imforumman and others affected by the issue:
The workaround is now included in official LE10 nightly builds (starting with today's 20220610 build)
Add vc4.force_hotplug=3 to /flash/cmdline.txt to activate the workaround on both HDMI ports.
Also please try with 1 and 2 instead of 3 to activate it only on the first or second HDMI port and report back which values work for you.
so long,
Hias
The logs show you plugged in the HDMI cable to the wrong HDMI port (HDMI1 instead of HDMI0), please try the other one.
so long,
Hias
Start by providing logs, our crystal balls are all still on repair.
ssh in, run pastekodi and modetest | pastebinit and post the URLs you got.
so long,
Hias
Yes, you can use the SD card in the other RPi.
so long,
Hias
I've uploaded RPi4 builds with the latest version of popcornmix's patch https://github.com/raspberrypi/linux/pull/5052
LE10: https://www.horus.com/~hias/tmp/libr…054-eb85a9e.tar
LE11: https://www.horus.com/~hias/tmp/libr…608-bbb7ee2.tar
Please test with vc4.force_hotplug=3 added to the end of cmdline.txt and report back if this works.
The value 3 forces HDMI hotplug on both HDMI ports, you can also use 1 to force it only on the first HDMI port or 2 for only the second one.
so long,
Hias
You can just plug in ethernet after a wifi issue, it should connect automatically. Ethernet takes precedence over wifi so if you have ethernet plugged in wifi won't be tried at all.
so long,
Hias
hmm, that log looks like you freshly booted with ethernet cable plugged in - I don't see any failed wifi connection attempts here
so long,
Hias
Just run "pastekodi" and post the URL you got. We can't provide any more help if you don't provide full, unredacted logs.
so long,
Hias