Perhaps label partitions and use boot=LABEL= and disk=LABEL= instead of GUIDs in extlinux.conf
Sorry I have little real-world knowledge of RK boot stuff ..
Perhaps label partitions and use boot=LABEL= and disk=LABEL= instead of GUIDs in extlinux.conf
Sorry I have little real-world knowledge of RK boot stuff ..
LE installs to a wide range of inexpensive hardware that attaches to TV's, e.g. a Raspberry Pi or Intel NUC, but we do not support direct installation to actual TV's (and no plans to add it). That's the bit you're missing.
LE is currently built around the assumption of being installed on an IPv4 device behind a NAT gateway in a domestic/home network. As a result you should assume there is only partial support for IPv6 in the OS. In fact i'm surprised there is any, as last time I actually looked it was mostly disabled everywhere. You are welcome to make suggestions on improvements, but AFAIK none of the core team have access to IPv6 networks to validate any suggestions that are made. Things that appear (or not) in the settings GUI could simply be things that didn't exist in connman when the settings add-on was originally written in 2012/2013 so it's worthwhile cross-referencing with connman documentation and the "connmanctl" utility. If you make changes via connmanctl they will be persistent.
Just FYR, this Shippy in comments below is *not* me !
Looks like our "fork" ex-colleagues stooping to new lows .. which is nothing newsworthy
is there any option to install LibreElec on specific partition without wiping whole HDD?
Technically no because LE requires TWO partitions (boot and storage) although it may be possible to use the current main partition for storage as long as it's Linux formatted, e.g. EXT4 (not possible if NTFS or FAT32 formatted). The wiki has some high level details of the manual install process. All of our installers are written for "nuke and pave" installs.
Okay, remote is working, thnks
What about sound and hw davlin codecs?
Work in progress.
Display MoreTried this https://yadi.sk/d/dhepyyrcterlf/leia-18/kernel_5.x/20190404/s905x2
for X96 Max
Boot - OK
Interfaice sound - NO
HW video support - NO
IR support - NO
Sound play - NO
Ethernet - OK
Bluetooth - NO
^ an exact match for balbes150 description of the image in post #470
How exactly do I move the backup file off-box? Secondly, how do I do a clean install without using the backup itself while the existing OS is already on there? I guess I'm asking, could you dumb it down a bit for me please.
The backup file is in /storage/backup so use WinSCP to transfer over the network, or if a USB drive is locally connected (and mounted) you can copy the file using 'cp' from the SSH console or the Kodi FileManager in Kodi settings.
Or if you don't care about any of the existing data. Create an install USB using the USB/SD Creator app and boot/install. The install process will nuke everything on whatever device you install to.
Count to somewhere between 3 and 8 seconds (depending on the box) before releasing the reset button. If you power on and release the button at the same time, u-boot hasn't reached the point in the boot process where the button release is seen; so it will just continue to boot normally.
Use Raspbian if you need a browser. It's a desktop OS with desktop features.
Google started to roll out a change to Widevine DRM that adds additional browser (environment) checking to more strictly enforce the browsers that can be used and Kodi fakes being a browser to obtain an L3 certificate. Several Kodi add-ons are impacted by the change and authors are aware and are likely researching how to work around it. Assuming something is possible (which is not guaranteed) it will likely take some time.
AFAIK it should work.
On what hardware? .. and what version of OS? .. we are not mind readers
Take the updated lima drivers?
Yes, using lima not the closed-source blob.
If it's in the Kodi repo it's device agnostic and should just work. If it doesn't, flag the issue to the add-on author via Kodi forums.
Everyone should always buy non-realtek USB dongles .. until they get the message that sloppy old crap code is not acceptable anymore!
LE settings will need a major overhaul for LE10 due to Kodi finally shifting from Python2 to Python3 and our current aspiration is to completely redesign it rather than convert the code which is now 7+ years old and a little dated in overall approach. Until that effort starts "it is what it is" and users will need to configure in Estuary and then switch to other skins. Some skins do support it .. but not Confluence.
I'm guessing it's an older OE install that was cross-graded to LE at some point. OE used a 235MB boot partition and LE 7.x/8.x are around 230MB so fit within that partition size constraint. The LE 9.0 image has grown a little due to drivers and such and the 235MB boot partition is now too small to host the files so the upgrade aborts. To fix this you have two choices:
a) Backup the LE 8.2.5 install and move the backup file off-box, then clean install LE 8.2.5 (which gives you a 512MB boot partition) and then restore the backup; then update to LE9.0. This is normally the fastest option as most LE installs only have 1-4GB of actual Kodi data on the /storage partition that needs to be backed-up and moved and the reinstall/restore process is quick.
b) Boot an Ubuntu (or similar) LiveUSB and use gparted to shrink and then relocate the /storage partition to create space for the boot partition to be size expanded to 512MB or 1GB (whatever you fancy). This is normally the slower of the two options as you end up moving 31GB of data on disk.