If you're comfortable at the command-line and know what Kodi files are important and where they live it's pretty simple to do a manual update from 9.2.x to 10.0.x .. the only problem thing is add-ons (so move them out of the way before updating). I'd guesstimate that 85% of our userbase is not comfortable, and staff don't want to be drowned in "but my add-ons broke" support work, which is why the clean-install advice is pushed.
Posts by chewitt
-
-
-
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 a known issue but nobody submitted a fix yet. Use "bluetoothctl" to make the pairing .. this works from the CLI.
-
Crazycat and similar are a pain in the arse once you start bumping kernels. Just disable them.
See Generic: disable dvb add-ons by CvH · Pull Request #5600 · LibreELEC/LibreELEC.tv · GitHub
-
I've tried most everything to get to the grub prompt, no luck.
What am I missing?
You're missing grub, since we don't use it. Put the same thing on the APPEND line in syslinux.conf in the first partition on the USB.
-
Get a Flirc Kodi case .. temps will be in the 50-55ºC range in normal LE use but this is passive cooling (no fans) and it looks fab. RPi4 was designed to run happily at much higher thermal temps than most users are mentally comfortable with. You need to have some cooling but active cooling cases with noisy fans are not required.
-
It's hard to understand what you're trying to do now
-
It's just a hunch .. I'm fairly clueless about compiling stuff
-
In LE /etc/fstab exists inside a read-only squashfs file so you cannot edit it (and there is no need to). The location of KERNEL/SYSTEM and the filesystem for /storage are specified in boot configuration boot= and disk= .. and everything else will be automounted to /var/media by udevil and will be named according to disk-labels.
-
why do they use FA16 instead of ext4 or some other native linux system for the system?
because some users will need to tweak/edit boot config files (e.g. config.txt on Raspberry Pi boards) and users need to mount the first partition of the USB/SD media on their desktop OS .. and Windows/macOS cannot mount native Linux filesystems like EXT4. Using FAT16 allows editing anywhere and causes no harm or loss of performance.
-
It must be caching in your browser, because when I check it the data is showing updated/current for me.
-
My suggestion is to drop into the #connman IRC channel on OFTC (OFTC - Home has a webchat option) and ping "wagi" for help. He's loosely familiar with LE packaging and is the main developer lead for ConnMan. People around here have little/no experience with WPA-EAP so we're not going to be that helpful.
-
It appeared in 9.2, but not many folks noticed.
-
You might try a 64-bit version. Even when we had 32-bit support we built in a 64-bit environment.
-
Are there any plans to release this version in NOOBS / PINN format?
Latest version for NOOBS right now (for Rpi4) is 9.2.6.
Done / Updated.
-
Are you building on a 32-bit or 64-bit version of Ubuntu 16.04?
-
I'd stick with the current headend arrangement and only swap the client device. Kodi flirc cases are nice
