Libreelec for Kodi 17.4 Download Android Libreelec for Kodi 17.4 Download Android

Libreelec for Kodi 17.4 Download Android Libreelec for Kodi 17.4 Download Android

libreelec for kodi 17.4 download android Libreelec for kodi 17.4 download android. Hi all, I currently have a Raspberry Pi 2 connecting to my NAS drive. It's a WD World Edition (early model) 3TB NAS hard drive. This lets me plug it into the network and have all my files accessible over the network. I filled it up some time ago so now have a 2Tb WD Passport plugged into the USB drive on it which has also now filled. Sadly it only has 1 USB drive so I am now out of options to add more storage to it. I really like using just 2.5" external hard drives for the storage as it means I can simply unplug it and take it with me when I go travelling. I'm just looking for suggestions really as to what recommended options are for a cheap/small NAS solution. I dont need RAID at all and just literally want my drives accessible over the network - would happily just buy another 2Tb Passport to increase capacity. Is the Raspberry Pi (1 or 2) able to have a external drive connected to it and share it? I have an old Raspberry Pi 1 that I could happily use for a NAS if it'd work. LibreELEC (Krypton) 8.2.0 RELEASE. LibreELEC 8.2.0 provides a mid-year bump to improve hardware support on Intel and Raspberry Pi hardware. It also resolves minor support issues on a range of devices and fixes a number of important security issues affecting the core OS reported in recent months. Kodi is bumped to 17.5, and Samba bumps to 4.6 which brings support for SMB2/3 to LibreELEC for the first time. PLEASE READ THE RELEASE NOTES below before posting an issue in the forums as there are disruptive changes to Samba, Lirc and Tvheadend. NB: An issue with HEVC playback on Raspberry Pi and Slice hardware was reported during the initial canary period and replacement 8.2.0.1 images with a fix (for those devices only) have now been published. Changes since LibreELEC 8.0.2 include: Fix boot-time overwrite of samba.conf.sample to ensure v4 template exists Fix Samba startup failures by detecting/disabling old (v3) samba.conf files Fix NAND install on WeTek Hub/Play 2 after Android Marshmallow updates Fix VMware OVF template, drop OVA .img suffix and force ‘installer’ mode Fix an issue in the embedded getedid script Fix Kodi to support 352KHz and 384KHz audio over S/PDIF Fix clearing of core files from /storage/.cache during Kodi startup Fix vulnerability (CVE-2017-1000250 aka Blueborne pt.1) in BlueZ Fix vulnerability (CVE-2017- 1000251 aka Blueborne pt.2) in all kernels except Amlogic 3.10 Fix a Python /dev/random issue that caused some Python crypto functions to error Fix to prevent boot-loops when a failed update leaves valid files in /storage/.update Update Amlogic 3.14 kernel to use kernel wireless- regdb on all reference devices Update RPi firmware to solve minor CEC button press issues Update RPi wifi firmware to resolve CVE-2017- 9417 (Broadpwn) Update wpa_supplicant to resolve multiple CVE’s (KRACK) Update linux-firmware and misc-firmware packages Update nvidia-legacy driver to 340.104 Update nvidia main driver to 384.90 Update RTL8192EU driver Update RTL8188EU driver Update RPi kernel to 4.9.59 Update Generic kernel to 4.11.8 Update from LibreSSL to OpenSSL Update Samba to 4.6.8 Update to lirc 0.9.4d Update Kodi to 17.5 (the 17.5.1 release is for Android only) Update kernel to enable SMB2 support (default) and where possible SMB3 Update LibreELEC settings add-on to expose more Samba config options Revert Hauppauge DualHD tuner support (back to single-tuner, which works) Add Slice and Slice3 projects Add (merge) Virtual project into Generic Add buildsystem changes to make backports from master easier Add support for the Xiaomi Mi Box Bluetooth remote Add support for Xbox ONE (DVB-C/T/T2) USB tuner (excluding Amlogic devices) Add alsa configuration for the IQAudIO Digi+ on Raspberry Pi devices Add dummy Tvheadend 4.0 add-on to ensure 4.0 is disabled on upgrade. SAMBA / SMB CHANGES . Samba = server software embedded into LibreELEC images. SMB = client protocol used for connecting to Windows Server and Samba shares. LibreELEC 8.2.0 includes changes that allow the Kodi SMB client and our embedded Samba server to support SMB2/3 connections; deprecating SMB1 to improve security and performance. This is necessary to cope with changes Microsoft introduced in the Windows 10 ‘Fall Creators Update’ to resolve SMB1 security issues. Please see Microsoft notes here and here and here for an explanation. LibreELEC changes are summarised below: The Kodi SMB client now defaults to SMB3 connections but can fail to negotiate SMB3 with old Samba (NAS) versions. A new option in Kodi Settings > Services > SMB client > allows SMB2 or SMB1 to be forced for compatibility with legacy SMB servers. Some router and NAS devices have proprietary SMB1 implementations that do not support NTLMv2 and forcing SMB1 still results in a refused connection. This is normally resolved by adding client NTLMv2 auth = no and client use spnego = no to /storage/.kodi/.smb/user.conf before rebooting. In a future LibreELEC release we will make this configurable within the Kodi settings GUI. The embedded Samba server defaults to and supports only SMB2/SMB3 connections. The LibreELEC Settings add-on allows the minimum protocol version to be changed, e.g. to enable SMB1 for compatibility with legacy SMB clients. It also supports GUI configuration of WORKGROUP name. In other Linux distros Samba clients default to SMB1 for all Samba versions up to v4.7 when the Samba default changes to SMB2. If the installed Samba version is between v4.1 and v4.6 you can force SMB2/3 connections by adding client min protocol = SMB2 and client max protocol = SMB3 to smb.conf. Samba versions older than v4.1 do not support SMB2/3 and require the LibreELEC Samba server to be configured for SMB1 support. Samba detects v3 /storage/.config/samba.conf configurations and ignores them to avoid the Samba service failing on startup. If this happens Samba starts with a default v4 configuration. Custom Samba configurations must be updated to use the new Samba 4.x base template (samba.conf.sample). Kodi “Windows network browsing” needs the Kodi SMB client to support SMB1 and we now default to SMB2/3 connections so browsing no longer works. Windows SMB share sources must be added using the full server/share path. SMB sources from Samba/NAS devices can normally be browsed via the “ZeroConf network browsing” alternative. Connection failures to anonymous and guest shares on a Windows server are normally solved by creating a local machine user account and password credential on the server for Kodi to use, then setting read or read-write permissions for that credential to the shares Kodi will access. Connection failures from a Windows client to the embedded Samba server are probably the result of Win10 changes that remove support for guest/anonymous access. Enabling password authentication in the LibreELEC settings add-on and setting username/password credentials should restore access. Local filesystem mounts of a remote SMB filesystem via systemd or autostart.sh now default to SMB2 so connections to SMB1 shares fail unless vers=1.0 is added into the mount command to force SMB1. SAMBA / SMB CONFIGURATION FILES. Kodi forum posts commonly refer to Samba configuration files in. /.smb/smb.conf which is common in other Linux distros but is not correct for LibreELEC and Kodi 17.4 or newer. The embedded Samba server obtains the runtime config from /etc/samba/smb.conf unless /storage/.config/samba.conf custom config is present. The Kodi SMB client configuration is stored in /storage/.kodi/.smb/smb.conf which can be extended with changes in /storage/.kodi/.smb/user.conf if required. nb: Changes to smb.conf in the same location will be overwritten by GUI client changes. If you experience issues with SMB shares (client or server) please post in the forums sharing details of the Windows and Samba versions and a Kodi debug log. !! LIRC CHANGES !! In LibreELEC 8.0 the Lirc service is enabled when an IR receiver is detected in the system, but it is not started unless used with the lirc_rpi or lirc_xbox drivers or a personal lircd.conf. In LibreELEC 8.2 the Lirc service is enabled and supports all drivers which can result in the service starting and interfering with normal IR operations. If you experience “double button presses” after updating the Lirc service can be disabled in the ‘Services’ tab of the LibreELEC settings add-on. The Lirc service is disabled in new installations and must be manually enabled. Thanks to @HiasoffT changes the Lirc service is now configurable using a combination of /storage/.config/lirc_options.conf and lircd.conf – the same approach used in desktop Linux distributions and most howto instructions users find via Google searches. !! TVHEADEND CHANGES !! LibreELEC 8.2 does not provide Tvheadend (Server) 4.0 so the add-on repo has been populated with a dummy 4.0 add-on that Kodi will download then mark as broken. It has been discontinued because it is no longer maintained upstream. Tvheadend 4.2 has been available for some time and has proven to be more stable with better features and hardware support. Unfortunately Tvheadend does not provide an automatic upgrade or configuration export/import process so 4.0 users must perform a new installation of Tvheadend 4.2.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    8 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us