Preliminary LE12 PR is here: https://github.com/LibreELEC/LibreELEC.tv/pull/8175, I'm now looking at adding support to LE11 as well.
so long,
Hias
Preliminary LE12 PR is here: https://github.com/LibreELEC/LibreELEC.tv/pull/8175, I'm now looking at adding support to LE11 as well.
so long,
Hias
Will LE 11.0.3 run with a raspberry Pi 5 ?
LE 11.0.3 pre-dates the RPi5 release, so no
We are still thinking about if or how we include RPi5 support in LE 11 (eg 11.0.4).
Background info: we've been testing with LE12, which runs entirely 64bit code and can take advantage of several nice optimizations (eg accelerated deinterlace) which are only available on 64bit.
LE11 on RPi is entirely 32bit userspace code though. Adding 64bit support to it would open a can of worms (lots of the addons would need updates etc) so likely I'll have a look at doing a 32bit LE11 RPi5 build as this should be easier to achieve (fingers crossed).
so long,
Hias
The first one is Kodi's SMB Client configuration and the latter is LE's Samba server configuration.
so long,
Hias
Which LE version are you using?
I did a quick test on LE12 nightly and oddly kodi showed it under the name of my soundcard but with empty parenthesis after them (usually they have he name of the soundcard, again). Certainly some kodi oddity but I saw it in the log, too:
2023-09-25 18:58:05.085 T:1120 info <general>: Device 3
2023-09-25 18:58:05.085 T:1120 info <general>: m_deviceName : both
2023-09-25 18:58:05.085 T:1120 info <general>: m_displayName : RPi-Cirrus ()
2023-09-25 18:58:05.085 T:1120 info <general>: m_displayNameExtra: WM5102 AiFi wm5102-aif1-0
2023-09-25 18:58:05.085 T:1120 info <general>: m_deviceType : AE_DEVTYPE_PCM
2023-09-25 18:58:05.085 T:1120 info <general>: m_channels : FL, FR, BL, BR, FC, LFE, SL, SR, UNKNOWN1, UNKNOWN2, UNKNOWN3, UNKNOWN4, UNKNOWN5, UNKNOWN6, UNKNOWN7, UNKNOWN8
2023-09-25 18:58:05.085 T:1120 info <general>: m_sampleRates : 32000,44100,48000
2023-09-25 18:58:05.085 T:1120 info <general>: m_dataFormats : AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE
2023-09-25 18:58:05.085 T:1120 info <general>: m_streamTypes : No passthrough capabilities
If you can't get it working please provide a debug log (enabled debug logging in settings, reboot, ssh in and run "pastekodi").
If you play multichannel content and have the number of channels set to 2 in kodi audio config then kodi will downmix to 2ch automatically.
OFC you could also configure more channels, like you did before (also increase the number of channels in the multi pcm accordingly) and eg map 6 channels to HDMI and only FL and FR to the soundcard - but then you'll loose the center channel at the soundcard when playing 5.1 contents.
You could play around with ttable and down-mix more channels into left and right of the soundcard but that could have negative effects if you only output stereo content.
It's tricky, you have to play around a bit what you prefer.
so long,
Hias
It's best to refer to the various cards by name (eg CARD=vc4hdmi), not by number - the numbers can change. see the output of aplay -L
For hdmi output you need to use the hdmi PCM (i.e. hdmi:CARD=vc4hdmi,DEV=0) or the default pcm - the vc4 hw pcm supports only iec958 format (not S16LE etc) which pretty much no software supports (the hdmi pcm will do the necessary conversion).
It seems it's necessary to specify the number of slave channels (eg 4 if you want to output 2+2 channels via the multi pcm) in the route pcm.
And, if you want aplay -L to show the "both" pcm you need to add a description hint.
Please test with this asound.conf file:
pcm.both {
type route
slave.pcm {
type multi
slaves.a.pcm "hw:CARD=sndrpihifiberry"
slaves.a.channels 2
slaves.b.pcm "hdmi:CARD=vc4hdmi,DEV=0"
slaves.b.channels 2
bindings.0.slave a
bindings.0.channel 0
bindings.1.slave a
bindings.1.channel 1
bindings.2.slave b
bindings.2.channel 0
bindings.3.slave b
bindings.3.channel 1
}
slave.channels 4
ttable.0.0 1
ttable.1.1 1
ttable.0.2 1 # front left
ttable.1.3 1 # front right
hint.description "Output to HDMI and Soundcard"
}
Display More
so long,
Hias
It looks like your 500GB drive is dying
Sep 24 17:24:51.239391 LibreELEC kernel: sd 3:0:1:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=1s
Sep 24 17:24:51.239860 LibreELEC kernel: sd 3:0:1:0: [sdb] tag#0 Sense Key : 0x3 [current]
Sep 24 17:24:51.240185 LibreELEC kernel: sd 3:0:1:0: [sdb] tag#0 ASC=0x11 ASCQ=0x4
Sep 24 17:24:51.240507 LibreELEC kernel: sd 3:0:1:0: [sdb] tag#0 CDB: opcode=0x28 28 00 15 17 16 90 00 00 08 00
Sep 24 17:24:51.240824 LibreELEC kernel: I/O error, dev sdb, sector 353834640 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
so long,
Hias
Next try, I found a rather easy way to fix this at least on GBM (i.e. all devices except Generic Legacy/X11)
Solution: let logind handle the system/case power buttons (performing a shutdown) and let kodi handle all other input devices which might have a power button on them as well (and show the shutdown menu).
so long,
Hias
Power off via systemd-logind can be configured in /storage/.config/logind.conf.d
This will only work on Generic Legacy where kodi doesn't grab the input device. On Gerneric with Kodi GBM logind won't see the power button as kodi has grabbed the input devices.
Currently the best way to do it (which will work on all variants) is to create a simple /storage/.kodi/userdata/keymaps/keyboard.xml file with the following content:
BTW: I've changed the PR I've linked and it won't fix that issue because it turned out to be very tricky - the change (and the keymap above) also affects USB / BT / Wireless / ... remotes that kodi sees as "keyboards" and thus kodi would shut down immediately if you (accidentally) hit the power button on such remotes (which can happen quite easily and may be fatal as often it's not possible to power up the PC / RPi / other devices via the remote again).
so long,
Hias
FYI: This should be fixed in LE12 nightlies when this PR https://github.com/LibreELEC/LibreELEC.tv/pull/8161 is merged
so long,
Hias
Thanks for analyzing this!
Could you please report that on the youtube addon issue tracker https://github.com/anxdpanic/plugin.video.youtube/issues ?
It could also be some kodi API change, something with inputstream.adaptive or something other - the addon devs should certainly know more about that than we do.
so long,
Hias
ssh in (eg with Putty on windows or ssh on Linux then enter the following command:
This will produce kodi stacktraces, upload it to ix.io and output the URL of the uploaded backtrace (eg http://ix.io/4GFw)
so long,
Hias
Might be worth testing with a clean kodi installation without addons.
See here: RE: possible memory leak in nightly builds
so long,
Hias
This seems to be a bug in inputstream.adaptive, probably this one https://github.com/xbmc/inputstream.adaptive/issues/1362
No solution yet, we have to wait until i.a is fixed.
so long,
Hias
The last line in the kodi log is from the jellyfin addon. Try disabling that and see if that improves things.
BTW: you seem to have quite a lot of addons, scripts and skins installed. It might be worth disabling them one by one (or start with a clean kodi and install addons one after the other). ISTR script.embuary.helper has caused crashes in the past and there are also error log messages from script.lazytv.
so long,
Hias
hmm, according to the logs mmcblk0 should be a 128GB SD card. However the storage partition seems to contain only a 1GB filesystem - that should have been about 127GB instead. 1GB isn't enough for kodi plus addons...
so long,
Hias
You can either use 11.0.1 and wait for 11.0.4 (no ETA on it though yet) or install the latest LE11 test build from here: https://test.libreelec.tv/11.0/RPi/RPi4/
The official 11.0.3 version has not been changed.
so long,
Hias
Drop the "=1" after systemd.debug_shell (that would set the serial device), console=serial0,115200 systemd.debug_shell is working fine here.
I also have dtoverlay=disable-bt here in config.txt so that the AMA0 UART is used for the console.
so long,
Hias
Yes, that repo is certainly banned and you might have got other crap from it that's not flagged by kodi's pastebin site / banned list.
As we don't know if it's the banned crap, some other addon, or kodi (latter is not too likely since I don't see the issue here) you need to do a clean install anyway to narrow it down. Start with clean LE kodi, add one addon after the other and see if things change.
so long,
Hias