Posts by jmooremcc

    Thanks for your advice.

    Actually both systems were originally OE. I made a backup of the OE system, created a fresh install using your SD creator app and then restored from the backup.

    Is there a way to get rid of those unnecessary language resources? I assumed they were dependencies associated with other addons.

    My epg has been off by an hour since we switched back to standard time.

    I've tried uninstalling the nextPVR client and clearing the guide databases, rebooting and then installing nextPVR. The epg time is correct until I reboot Kodi and then it goes back to being one hour off.

    Here's a link to my log: Kodi log (epg issue) 11/12/17 -

    By the way, I am running Kodi on 2 Raspberry Pi systems and only one of them has the epg time problem.

    Their configurations are the same except one has more addons than the other and of course they are connected to different TVs.

    The one with the additional addons is the problem child.

    I'm in the U.S. eastern time zone and have never had this problem before. Any suggestions for resolving this issue will be greatly appreciated.

    Since upgrading to LE 8.01 Krypton 17.1, I've had the perception that WiFi under Krypton 17.1 was slower than under Jarvis 16.1. Jarvis is running under OpenElec while Krypton is running under LibreElec.
    What specifically got my attention was the amount of time during startup that Kodi takes to load nextPVR channel/recordings data. It took a lot longer under Krypton for the data to load.
    I used the WiFi Speed Test Android app to conduct my tests. Kodi is running on a Raspberry Pi and is 8 feet from my router. I also have each version of Kodi on separate SD Cards.
    As you can see from the attached screen shot, Jarvis/OE WiFi does appear to run faster than Krypton/LE. Has anyone else run a similar test and if so, what were your results?

    Sent from my GT-P3113 using Tapatalk

    Did you pay for the mpeg license for your RPi? If you didn't you'll be relying on a software decoder instead of the hardware decoder which doesn't work as well. The hardware decoder frees the cpu for other important tasks which makes the decoding process more efficient.

    Sent from my GT-P3113 using Tapatalk

    I have to walk back my earlier comment about Estuary not lagging on a RPi. I upgraded another RPi system to LE 8 Krypton that I use more intensively. I noticed the slowness immediately especially when I use the Super favorites addon. So I tried an experiment. I did the unthinkable and loaded Confluence. It was immediately obvious how much faster Kodi Kroton runs with Confluence as the skin.
    Yes, there are some features of Estuary I like but the painful slowness I cannot tolerate.

    Sent from my GT-P3113 using Tapatalk

    HooRaay! I finally got LE 8.0 to compile.
    Thanks vpeter for your advice that helped resolve my pronlem.
    Your advice to update the e2fsprogs package and the fonts package specifically helped resolve the issue. The update to populatefs was not required,.

    Sent from my GT-P3113 using Tapatalk

    Your method backs-up and then restores "all the crap" from OE into the new clean LE install. There is no cleaning benefit :)

    I acknowledge "some crap" but what's the alternative? Manually install every addon and every configuration setting?
    Compared to "updating" an existing image, the method I outlined and used delivered superior results because less baggage, I.e. crap was carried forward. [emoji4]

    Sent from my GT-P3113 using Tapatalk

    On the RPi create a backup of your OE configuration and copy it to your computer. Next put the LE 8 image on a new SD card using their usb creator app. Boot up your RPi using the LE 8 image and do a minimal configuration that will allow you to connect with your computer using samba. Copy your OE configuration backup to your RPi's download directory and perform a restore operation. You should also anticipate that your advancedsettings.xml file, if you have one, may need to be updated due to changes made in Kodi Krypton.

    A big advantage of the above method is that you will have a super clean image with minimal crap from the old system.
    Another advantage of this technique is that you will still have the old OE system available just in case.

    Sent from my GT-P3113 using Tapatalk

    I'm running LE 8 on a good ole RPi and have no problem with Estuary lagging at all. In fact I have it connected to a 1080p TV and Krypton is running very well. The RPi2 runs rings around an RPi so I'm surprised to hear your complaint about its performance.

    Sent from my GT-P3113 using Tapatalk

    For me it is

    1. build.LibreELEC-RPi.arm-8.0.0/toolchain/sbin/populatefs

    I think something is messed up with your system. This package should be build automatically.

    It's not in that directory on my system.
    I'm running the following system on a Dell computer:
    Distributor ID: Ubuntu
    Description: Ubuntu 16.10
    Release: 16.10
    Codename: yakkety

    what's the command to compile only populatefs?

    Not sure what happen but this should work.

    1. PROJECT=RPi ARCH=arm ./scripts/clean populatefs
    2. PROJECT=RPi ARCH=arm ./scripts/build populatefs:host
    3. PROJECT=RPi ARCH=arm make

    Unfortunately that didn't work. Got the same error. Where should populatefs be located?
    Is it a script file or executable?
    I did a search using the find command and find said the file does not exist.

    Sent from my EM756 using Tapatalk

    1. wget -O packages/x11/font/liberation-fonts-ttf/
    2. PROJECT=RPi ARCH=arm ./scripts/clean liberation-fonts-ttf
    3. rm sources/liberation-fonts-ttf/liberation-fonts-ttf-2.00.1.tar.gz*
    4. PROJECT=RPi ARCH=arm make

    I appreciate all the help you've given me and I feel like I'm almost there.
    I now have the following error:
    image: creating file LibreELEC-RPi.arm-8.0.0.img...
    image: creating partition table...
    image: creating part1...
    image: creating part2...
    image: creating filesystem on part1...
    image: creating bootloader configuration...
    image: copying files to part1...
    image: extracting part2 from image...
    image: creating filesystem on part2...
    image: populating filesystem on part2...
    image: error happen...

    scripts/mkimage: line 287: populatefs: command not found

    image: cleanup...
    I ran the following commands you gave me:
    wget -O packages/tools/populatefs/
    PROJECT=RPi ARCH=arm ./scripts/clean populatefs

    and then recompiled but I still get the same error dealing with populatefs.

    What should I do next?

    Full Log:LE8 Compile 3/6/17

    Then try to bump populatefs too:

    1. wget -O packages/tools/populatefs/
    2. PROJECT=RPi ARCH=arm ./scripts/clean populatefs
    3. PROJECT=RPi ARCH=arm make image

    I've implemented all of your suggestions to myself and others with similar problems compiling LE8.
    However, now I'm getting the following new error:
    You will probably need to make your busybox binary
    setuid root to ensure all configured applets will
    work properly.

    make[1]: Leaving directory '/home/john/'
    INSTALL busybox (target)
    INSTALL busybox (host)
    INSTALL hdparm (target)
    INSTALL e2fsprogs (target)
    INSTALL diskdev_cmds (target)
    INSTALL libressl (target)
    INSTALL zip (target)
    INSTALL bzip2 (target)
    INSTALL unzip (target)
    INSTALL usbutils (target)
    INSTALL libusb (target)
    INSTALL systemd (target)
    INSTALL libcap (target)
    INSTALL kmod (target)
    INSTALL entropy (target)
    INSTALL parted (target)
    INSTALL parted (host)
    INSTALL procps-ng (target)
    INSTALL netbsd-curses (target)
    INSTALL nano (target)
    INSTALL rpcbind (target)
    INSTALL libtirpc (target)
    UNPACK liberation-fonts-ttf
    Makefile:12: recipe for target 'image' failed
    Do you have any advice for resolving this issue?

    BTW, I wanted to use pastebin to post my entire log but unlike previous logs, the current log file is huge (36MB)

    You need to use newer e2fsprogs package. Run this:

    1. wget -O pr1154.patch
    2. patch -p1 <pr1154.patch
    3. PROJECT=RPi ARCH=arm ./scripts/clean e2fsprogs
    4. PROJECT=RPi ARCH=arm make image

    Thanks for your help.
    I followed your advice but encountered the following problem after the 2nd command:
    ========> patch -p1 <pr1154.patch
    patching file packages/sysutils/e2fsprogs/
    Hunk #1 FAILED at 17.
    1 out of 1 hunk FAILED -- saving rejects to file packages/sysutils/e2fsprogs/

    Sent from my GT-P3113 using Tapatalk