Posts by chewitt

You need to create two partitions ~ 512MB and 8GB are good sizes if media is stored somewhere else. Format both as ext4 and put the boot files (KERNEL and SYSTEM from an installer USB) in the first partition. Then configure your bootloader along the lines of the syslinux.conf file you'll find on the bootable USB. Do not install from the USB as this will nuke the contents of whatever device you point it to ~ it assumes LE is the only OS and it does not support installation to a blank partition like some general purpose distros do.

mount -o remount,rw /flash
cp /storage/yoursplash.png /flash/oemsplash.png
mount -o remount,ro /flash

I forget how to do the Kodi one, but ^ that does the LE boot splash.

I've updated the thread name so people are more likely to find it.

You need two partitions, one for the boot files and a second for the persistent /storage area.

distributions/LibreELEC/splash

Make a backup from the LE settings add-on inside Kodi then copy it off box for safe keeping ~ in most cases the backup file will be smaller (and thus quicker to create) than imaging the entire SD card. It also doesn't require any extra software and a future restore will be quicker too.

You'd need to go patching Kodi to add it into one of the on-screen displays. Adding GPU/CPU temp should be relatively simple as code exists for them in the system info screen that's part of Kodi settings, but HDD temp is not so you'd have to add more code for that. If you're competent at C++ go have a crack at it. If not, a cron job that exports values to a text file in /storage once per minute will be considerably easier.

The PR should be sent here: GitHub - raspberrypi/linux: Kernel source tree for Raspberry Pi Foundation-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://www.raspberrypi.org/forum then it benefits all RPi users, not just LE, and becomes something we pick up in the RPi backports patch we rebase as part of minor kernel bumps. The folks who maintain that repo will also evaluate and judge whether it's something that should go further upstream to the mainline kernel.

It's completely unclear what you're trying to do and which end (server, client, etc.) you're talking about.

If whatever change you're thinking up is worthwhile it should be submitted to the linux kernel. Then we'll pick up the change in a future kernel release. Patches and hacks are out of fashion around here

Kodi uses smbclient to talk to devices and the version we currently use (3.6.25) only supports NT1 (SMB1) connections and LANMAN auth so if your Xubuntu box does not support SMB1 or old auth methods Kodi will not connect to the shares. There is some cleanup planned for future releases both in Kodi (dropping dumb configuration) and with newer Samba versions in LE, but for now you probably need to tweak the Xubuntu config.

There is no power management hardware on a Pi so it will never shutdown and turn off. If you've done shutdown from the GUI and the OS has halted ~ it's time to pull the power cord to turn it off.

MacOS would ignore the ext4 partition and mount the two FAT32 ones, but as Windows doesn't understand multiple partitions on USB/SD media there isn't much point. Request denied

S912 is disqualified for having no proper Linux drivers (forcing use of Android drivers in a compatibility fudge). S905X is technically the best chipset, but all boxes are crippled with 100-BaseT Ethernet. S905 is thus the best real-world option as it has 95% of S905X features and 1000-BaseT Ethernet on most (not all, but most) boxes. If you purchase a $cheap box from various far-east websites expect a more complex install process, zero support from the vendors, lower quality internal chip choices, and frequently shitty firmware and manufacturing practices. Caveat emptor..

No tapatalk support unless someone writes a plugin for tapatalk. Stats show there are typically 35-40 active users of tapatalk (max) in a week so it's something we'll continue to track but it's not a high priority.

We have to balance the importance of the security update against the ignorance of our userbase. The breakage issues with 17.2 that result in 17.3 mostly don't concern us so we could ship something quickly, but then there are tens of thousands of users who will whine and moan like crazy if we give them 17.2 once 17.3 is available. So for the sake of waiting 12h while Kodi fix the 17.2 issues, we'll wait. Meanwhile it's 4.40am here and I'll get back to building test releases so we can move quickly once things are merged upstream so that "but you're not treating it seriously" whiny folk can get off our case and go back to polishing their tin foil hats.