NeeOder: Not sure how a fresh 8.2.4 image can fail to have working RPi3 WiFi unless there's a hardware issue, or additional configuration you've not mentioned.
djkidy123: What version of LibreELEC were you using before that had working RPi3 WiFi?
NeeOder & djkidy123: Can you both execute the following commands in LibreELEC 8.2.4 and post the links (you'll need a wired Ethernet connection):
cat /flash/config.txt | pastebinit
journalctl -a | pastebinitThe content cannot be displayed because it is no longer available. Hi,
is it possible to refresh "initramfs | initramfs.cpio" without rebuilding the whole project ?
it seems that rebuilding the "linux" isn't enough.
best regards
Yes. As initramfs is built during the build of the linux package you should clean both initramfs and linux if you want to rebuild initramfs.
Download the latest firmware: firmware/boot at master · raspberrypi/firmware · GitHub
Copy bootcode.bin to /flash/bootcode.bin
Copy fixup_x.dat to /flash/fixup.dat
Copy start_x.elf to /flash/start.elf
Check you haven't muted the audio in Kodi, or turned the volume in Kodi down to 0%.
If you're going to edit guisettings.xml then do so once Kodi has been shut down (as Kodi will overwrite guisettings.xml on shutdown, overwriting your changes). To be honest I'd just delete guisettings.xml and reconfigure your settings, but now without DSP (which, by the way has just been removed from Kodi 18 as DSP is no longer maintained).
same issue here on libreelec 8.2.4 (in my mind also 8.2.3), needed to go back to 8.0.2.
rpi3 analog output bad sound with TV/PVR streaming.
i can also confirm, deactivating deinterlace solves the issue so far on 8.2.4.
Can you test the latest firmware with 8.2.4 and confirm if that resolves the audio issue?
LibreELEC 8.2.4 ships with Samba 4.6.10 which already includes a fix for the "nt pipe" vulnerability.
It plays fine here (VLC for Windows).
VLC 2.2.6 on Windows 7 - all I get is one frozen frame of video but the audio plays normally.
With Windows Media Player it plays only the audio, no video at all.
Maybe I'm missing a codec or something.
The sample doesn't play at all in VLC for Windows (or Windows Media Player) so there may be some encoding issues.
On my Pi3+ system all seemed OK until the fat guy wearing #64 jumped on the other guys head at 20-21 seconds, at which point frames started to be dropped. Not sure why - the video is 1080@50 so maybe the bit rate is too much, or more encodiing errors.
For x86: edit syslinux.cfg in /flash - there's two, one in root (legacy BIOS) and a second in EFI/BOOT (UEFI boot) so edit whichever you are using. Add the word "textmode" (without quotes) to the end of the line that begins with APPEND.
For RPi: edit /flash/cmdline.
For everything else: dunno.
We accept PRs. 
The post you're replying to that contains the list is almost a year old. Things change. Old forum posts, don't.
You can see the latest packages in the system-tools meta package here: libreelec-8.2. htop is now present.
If the LibreELEC upgrade process continues to fail it would be worth posting a photograph of your TV so that we can see the errors - it shouldn't freeze or force you to reboot unless there's a hardware failure (run memtest86+ to test your RAM - two other users with similar upgrade errors had faulty DIMMs).
Are you overclocking in any way? The log garbage could be due to memory or file corruption.
There's still some rough edges with the RPi firmware following the Pi3B+ launch which are being addressed and will appear in a future LibreELEC update.
1) Check you really do have a Pi3+ - you wouldn't be the first that thought they had a Pi2 or Pi3 when in fact they had a Pi1, perhaps you've been shipped the wrong device? If the RPi is inside a case then open it up and visually confirm it is actually a Pi3+. Installing/booting the wrong image is the most common reason for the rainbow splash.
2) Try installing the latest firmware to your SD card (some devices have problems with the current 8.2.4 firmware). Extract the contents of new-firmware.zip into the root of the SD card, overwriting the three files of the same name.
3) You may have a faulty device - are you able to boot Raspbian?
Last night myself and a colleague both tried clean builds with LANG=pl_PL.UTF-8 in order to try and narrow down the cause of the failure, but our builds were successful (we were both building master, I built Odroid_C2, my colleague built RPi2).
In my case I built with the following patch on my Ubuntu 17.10 build system (which uses en_GB.UTF-8 by default): 12K6
Would you mind testing the following patch on your Docker container to see if it has any effect? 13e9
You should restore your system to the initial failure condition, ie. pl_PL.UTF-8 as the system default LANG, before the test.
This isn't necessarily a long term fix (although if it works then it could be), but it might also help shed more light on the issue.
Can you also confirm your command line when starting your build, and if you are building with any other patches?
You'll need to buy a heatsink. The FLIRC case is very good.
Kodi has a caching mechanism that will save slow queries to local storage for subsequent (in theory faster) re-use, which most likely explains why the initial query takes longer than subsequent queries. The cache folder is cleared when Kodi is restarted so the cache does not persist across restarts/reboots.
However there are problems with the FileItem cache - at least in latest Kodi 18, and probably 17.6 too - which may mean it doesn't quite work as intended, but this could be skin specific.
Also bear in mind that after booting the RPi1 will be busy for 1-2 minutes while it starts services in the background etc.
The PVR errors in your log ("Misplaced [") are most likely skin bugs and should be reported to the skin maintainer.
