There's basically no difference between the RPi2(3) and RPi4 images. Note that installed paths in LE and OSMC will be different so if you've copied a config file that points to some kind of playlist? (I've never used IPTVSimple so no idea of that's a requirement) the path could need tweaking.
Posts by chewitt
-
-
RPi4 is hardware capable of HDR and HBR audio, but neither are implemented in current software. There is active effort to implement HDR on several platforms for Kodi v19, mostt advanced in the quest is recent Intel devices, but that's still in a pre-alpha state and for RPi4 some other essential code plumbing needs to come first.
-
Cron should be enabled and running by default.
-
If you mount to the local filesystem all the paths change, so media is seen as new media and will need to be re-scraped. Read the wiki sections on exporting watched status first, so that it can be reimported again.
-
Pastebin a debug log at the start, and after restarting Kodi, e.g.
cat /storage/.kodi/temp/kodi.log | paste <= share the URL generated
wait 30 secons
systemctl restart kodi
cat /storage/.kodi/temp/kodi.log | paste <= share the URL generated
i'm wondering if it's something to do with drivers/loading.
-
LE 9.2.2 is here: GitHub - LibreELEC/LibreELEC.tv at 9.2.2
Unless you posted in the Amlogic section deliberately? in which case no 9.2.x version exists and the latest sources are:
LE 9.0.2: GitHub - LibreELEC/LibreELEC.tv at 9.0.2
LE 10 (future, in a pre-Alpha state): GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI
-
This is resolved in master branch (will be LE10) image: add /etc/environment by MilhouseVH · Pull Request #4065 · LibreELEC/LibreELEC.tv · GitHub
-
"/usr/bin/sh" not "sh" ?
-
Sorry.. I kind of stopped caring about Realtek chips several years ago and no longer have a clue about what we support or don't support.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
It's not possible to set codec-specific configurations. It sounds like bad encoding, so best option would be to re-rip the content from original media. NUCs are quite speedy for ripping - even the low-spec ones.
-
It's upstream, so torvalds/master would always be a starting point.
-
LE 9.2.3 will have GUI options for setting wireless regulatory domain which appears to be more important on RPi WiFi hardware than other devices for setting the correct radio properties and getting good (or better) performance. Until the release you can force the same with this:
Codeecho "options cfg80211 ieee80211_regdom=US” > /storage/.config/modprobe.d/cfg80211.confreplace "US" with other country codes if required.
-
Linux 5.7 doesn't really fix anything - it's just another incremental step in the journey. I've been working with it for a month now and need to rework audio support as the upstream maintainers rejected yet-another idea that I had to simplify adding new devices - so I need to revert back to a previous approach (aka doing it the hard way). Once that's done I'll push some device support upstream and then think about making a general 5.7 update to LE master. There are still some known glitches for audio support on GX hardware and while there has been some effort with ffmpeg V4L2m2m we still have issues with draining which impacts end of stream and seeking. No public code for HEVC yet either. Apart from that, things are stable.
-
Browsing only works with SMBv1, which is best avoided in the Windows world due to numerous security issues, but that should be marginally less of an issue running on MacOS. If it works, it works.
-
miwenka ahh, that explains why boot fails, the u-boot.ext file is for G12 devices. It's odd that you have this behaviour though, as it's normally only seen with very recent u-boot on boxes. Anyway.. download u-boot.bin.wetek-play2 and rename to u-boot.exe and see if that works, it's mainline u-boot from another S905 device. No guarantees..
-
Code
cat /storage/.kodi/temp/kodi.log | paste^ show me your Kodi boot log
-
I am very sorry for misunderstanding. I copied this file to root USB key ( STORAGE and LIBREELEC) , but OS stop loading. After that I try to copy this file to OS:
What hardware are you trying to boot?
