Posts by chewitt

    Code
    19:36:28  40.400620 T:1777333152 WARNING: No information found for item '/media/TV Shows 2Tb/', it won't be added to the library.
    19:36:28  40.404320 T:1777333152   DEBUG: VideoInfoScanner: No (new) information was found in dir /media/TV Shows 2Tb/

    Kodi uses hashing to detect changes in the media folders and cannot see anything "new" in the folders so skips scraping. If things didn't originally scrape it's probably issues with the folder/file naming structure you're using. Fix that and then "scan for new content" and it will appear. Naming is the main issue that people have with scraping.

    change PKG_VERSION in packages/x11/driver/xf86-video-nvidia-legacy/package.mk

    If the driver throws an error on compilation it's probably missing a patch to build 304.131 against a Linux 4.7 kernel. The solution is to use Google to find the patch. I normally look at the driver packages for Arch linux, as Arch runs a current kernel and will need the same patch.

    The command "xrandr" will list the adapters, resolutions and rates they support, e.g.

    Code
    LibreELEC:~ # xrandr
    Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
    DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
    HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 160mm x 90mm
       1920x1080     60.00 +  59.94*   50.00    29.97    25.00    24.00    23.98  
    DVI-I-1 disconnected (normal left inverted right x axis y axis)

    Then you can change the Xorg display using:

    Code
    xrandr --output HDMI-0 --mode 1920x1080 --rate 60.00

    However, this setting is not persistent over a reboot. There are two options; hacky and good. If you add commands to /storage/.config/autostart.sh (which does not exist by default) they will be re-run on each boot:

    Code
    (
    sleep 10
    xrandr --output HDMI-0 --mode 1920x1080 --rate 60.00
    )&

    but the better way is to set the in system settings. In normal LE this can be done in Kodi settings. I'd guess there is a similar function in PMP, but having never used it I cannot say - you're posting in the wrong forum for Plex/PMP expertise :)

    If you are selecting a local file in Step 2 you are not downloading anything so Step 1 is (correctly) blanked. If you reselect something in Step 1 you are no longer using a local file so the previously selected item in Step 2 is (correctly) blanked.

    No bug here to be fixed :)


    I don't want to leave Hide.me, now I'm using it without problems with LibreELEC version 7.0.2. For the future? May be I will compile OpenSSL and overwrite to LibreSSL ;)

    It will fix your VPN, but will also break binary compatibility with everything else that uses SSL (and expects LibreSSL). Not impossible, but not a quick change either. You energies would be more productive figuring out the patch/hack for LibreSSL ..

    Just SCP things to /storage and they should run. You can always bind-mount things to other locations if they really need to exist in other location. If they are static build they should just work. If not static, we may have the deps, or not..

    NB: Are these binaries that we build but don't copy into the image .. or binaries from another package that we don't have in our build system?

    The OS boots into RAM if there is >=1GB so it's possible to remove boot media and the system will continue to run, but this will make the persistent /storage area unavailable and when it reappears after unclean dismount the kernel will consider the partition to be dirty and remounts it read-only to prevent data corruption issues. This prevents Emby from making ad-hoc saves, and Kodi (Jarvis) only saves it's settings on shutdown, so when you reboot to solve the issue any changes since previous boot are lost.

    If it was 1/2 boxes I'd guess dodgy USB ports or USB sticks, but if it's 2/2 and you've already swapped the USB sticks it's either something in hardware like a BIOS or PSU issue that results in interrupted power to the USB ports, or it's software. If it's something in software, it's some kind of kernel level bug that probably doesn't leave much trace: "journalctl --no-pager -b -1" will show the previous boot journal including the diconnect/reconnect, but i'd be surprised if anything is revealed; and I'd be surprised if really was a software issue.

    As general advice: I worked for several companies who released products that boot from USB/SD media and a myriad of issues have been miraculously resolved the second they reverted to using old-fashioned spinning rust or SSD's. We don't advocate long-term use of removable media, as while it can be done, the underlying media is not designed for it. I personally consider all USB/SD installations to be temporary. It's never about if things will go wrong, only a matter of when it takes place.

    There are changes in Kodi Krypton to save settings as you change things rather than on "everything saved on shutdown" which has been seen to cause problems on multiple OS platforms, it's not LE specific. If you have repeated issues you can access via SSH and "systemctl restart kodi.service" to ensure settings are saved outside of the normal shutdown process, or you can update to the current Alpha builds, which despite the "Alpha" name are solid on x86 kit; I've been running them for months (albeit on an nVidia GPU box).


    Does anything happen with the registered bug reports here?

    They languish unloved until sometime replies

    I've no idea what the issue is but the first step is updating to the current Alpha release. If the problem still exists it can be investigated, while all development on our Jarvis/7.0 build ceased months ago.