My $0.02 is that the /boot partition is equally susceptible to card corruption as the /storage partition. Script/automate a nightly backup and just accept that things die once in a while instead of using fragile netboot workarounds over unreliable wifi.
Posts by chewitt
-
-
There is no maximum on the number of movies. Just get a disk .. it really doesn't matter about the brand or type.
-
The last official i386 image was OpenELEC 5.0.8 about 3.5 years ago. We dropped support to save on resources after measuring the active installed base of i386 users and finding it to be tiny. It is technically possible to still create an i386 image if you self-build with changes to re-add i386 support to the build-system. Have a look at GitHub - maideii/LibreELEC.tv-Intel-i386: Just enough OS for KODI for hints.
-
Use zomboided's OpenVPN add-on.
-
If we have to guess the GPU model any further support will require a long wait.
-
Read the lirc section of the release notes
-
We aren't fans of realtek drivers that sit outside the kernel because they are usually poor quality and problematic to maintain. It's probably not hard to build the driver, but it's debatable whether we really want more realtek crap in our builds.
-
Windows network browsing in Kodi stops working when the Kodi SMB client is set to SMB2 or higher as this is an SMB1 protocol function. We now default to SMB2 hence something changed. Zeroconf browsing only works for devices that advertise their shares over Zeroconf .. which is normally fine for NAS devices with Samba that use Zeroconf and will not work for Windows because Windows does not use Zeroconf. My honest advice .. get familiar with SSH, nano and the contents of /storage/.kodi/userdata/sources.xml and just add sources manually.
-
Our stance on support for people with banned add-ons is not negotiable. As someone with a regular presence here you should know that.
-
Intel released new firmware update for this audio problem, however its relevant for windows only
Download HDMI 2.0 Firmware Update Tool for Intel® NUC Kit NUC7i3BN, NUC7i5BN, NUC7i7BN, NUC6CAY
Hope it will be part of next LE version....
Intel firmware flashing functions will never be part of LE .. because the fcukwits at Intel only have a Windows (not Linux) flashing tool.
-
The current Samba version in Ubuntu 16.04 defaults to making NT1 (SMB1) connections even though it supports SMB2 and SMB3 - hence it works when you specify the client version from the command line. The default is scheduled to change to SMB3 in Samba 4.7 (due for release soon) and already does this in LE because we backported the change to Samba 4.6 for our codebase. You have two options:
a) Configure the system smb.conf in Ubuntu to have "client min protocol = smb2" and "client max protocol = smb3" so that smbclient connections are forced to use something higher than NT1 .. then you don't need to specify the protocol version manually.
b) Configure the Samba server in LE to allow SMB1 connections. This can be done in the LE settings GUI.
-
It's a terrible idea because compatibility lists are never maintained and are thus instantly out of date. I also strongly doubt your current box is incompatible, it's just not configured right.
-
In the absence of any pastebin'd debug logs or sample configuration our best guess is "user error"
-
"journalctl -b 0 --no-pager | paste" and share the URL generated
-
Someone PR the required changes to GitHub pls.
-
Use English please.
-
Make sure the BIOS is current, see MrChromebox.tech - and if things continue submit a Kodi debug log. If Kodi is in debug mode the events that lead up to the crash should be in /storage/.kodi/temp/kodi.old.log
-
Skins are a very personal choice .. which is why Kodi ships with a simple and well-maintained default skin and an add-on repo where more exotic skins can be found if people feel the need for them. There's nothing to stop us from creating an official LE skin, apart from low enthusiasm among the team for the long and skilled task of actually making one.
