Posts by milhouse

    Yes, I could mount the second partition - use "sudo apt-get install kpartx" on Ubuntu to install kpartx:



    i don't have another SD this is a new SD and like i said when build x works and y, z doesn't i still think it might be the build not the SD otherwise it doesn't make any sense.


    Yes, that is strange, but I can't think of anything obvious that has changed that would cause this.



    I can write this to the device nand but won't that brick it if it's bad?


    Not familiar with the Wetek system so can't advise here.


    So I am starting to suspect LE has some issue with 16GB SD cards (or Kingston in particular) since Raspbian has no issues at all with it. Unfortunately I do not have any smaller sized SD cards to test with. Just 16GB's.


    Just to be clear, you have the same problem with OE? This question isn't about scoring points, it's just that the image creation/first boot process has diverged somewhat between OE and LE and if you have this same failure-to-resize problem with OE then it's unlikely to be caused by any LE changes...still not sure what could be causing this (all my available SD cards top out at 8GB).


    P.S. I also tried it with OpenELEC (I know, I know) but that has the same issue with add-ons (storage wise is is the same as with the LibeElec Jarvis situation shown above).


    So you say you've got a 16GB SD card, but neither OE or LE will expand the ext4 partition? Have you ever managed to install any release on to this SD card which has then gone on to use all the available 15-16GB of space?


    Since OE is also failing to resize the partition my suspicion would be that the SD card has failed, or the SD card is a fake and isn't really 16GB - see this article and consider testing the SD card with a tool such as h2testw on Windows.



    Not sure if the problem is caused by the storage being almost full or something else though.


    That's definitely the reason why you can't install any add-on, the question though is why you don't have the space... after a fresh install from disk image LE (and OE) will automatically resize the ext4 partition to use ALL available space which should in your case be slightly over 15GB. This is a relatively straight forward process and if this isn't working then there's possibly something wrong with the SD card...


    It seems with the Kodi 17 LibreELEC inputstream doesn't work for some reason (RPi2)? I installed it via: curl -Ls getwidevine.sh | bash
    It did say sucessfully installed ....


    getwidevine.sh isn't installing the inputstream.mpd add-on, it's only installing the libwidevine library which is needed by the inputstream.mpd add-on to decrypt encrypted content.


    With official LibreELEC Kodi 17 releases (alpha, beta, whatever) you'll need to install the inputstream.mpd add-on from the LibreELEC Add-ons repository.

    I've downloaded your img.gz and fsck'd both the FAT and ext4 partitions and they're both clean so there's nothing wrong with the image itself. Unfortunately I don't have Wetek hardware so can't write the image to an actual device, but the problem doesn't appear to be in the image creation process (we did have a problem with this, when creating the FAT partition, fixed on master on 9 June - see mtools: Fix creation of dot directories (. and ..) by MilhouseVH · Pull Request #435 · LibreELEC/LibreELEC.tv · GitHub).


    Can you try a different SD card?


    The default web server port has changed to 8080 in recent Kodi builds, so make sure Kore is trying to connect on the same port that your LE client is using.

    Thanks popcornmix. Just re-downloading the refreshed 7.0.1 file (tar or img.gz) and re-applying as an update (copy the tar/img.gz to the Update folder, reboot) should fix the issue and clear up the fsck files.


    Thanks everyone for notifying us about the issue, and apologies that this slipped through testing - unfortunately it was a semi-random problem (1-in-4 maybe 1-in-3 chance of it happening), and installing images isn't something you tend to repeat if you can help it, particularly when it worked previously and hasn't changed...


    I can use latest KODI git master and compile without errors, but only when i remove:


    - kodi-100.10-handle-SIGTERM.patch
    - kodi-999.10-aarch64-support.patch


    When using latest Kodi master you need to apply the following two patches on top of LE master:


    00_fix_k17_SIGTERM.txt #Fix SIGTERM patch after PR9748
    00_kodi_cmake.txt #Fix cmake after PR9750


    and remove the following file from LE:


    packages/mediacenter/kodi/patches/kodi-999.10-aarch64-support.patch #Merged upstream

    Maverick82 : presumably you're referring to this post? I've tested NTP with RPi3 built-in WiFi and didn't have a problem, which might suggest its a problem with certain access points rather than a widespread problem (otherwise there'd be a lot more noise around this issue).


    Unfortunately in that thread there seems to be a number of people saying there's a problem, yet no issue opened on github which is the correct way to progress towards a fix.

    To revert to 4.4.7 you need to revert all the kernel-related commits that have been added since 4.4.7, including those commits for packages (such as nvidia-drivers) needed for them to build against 4.6.x, as these additions may now mean those packages no longer build against 4.4.7. It's possible to go back to 4.4.7 with a bit of effort, but a lot of work just to fix auto-repeat.


    We'll switch to 4.7-rc once it becomes usable, currently there are some graphics issues.


    Side question: Is there an intentional reason why KODi itself did not get a update in libreELEC master since ~1 month? (Just curious)


    Yes, LE master will be updated when Kodi master bumps to 17alpha3 or 17beta1 or whatever their next tagged version is - LE is tracking only the tagged releases. If you want bleeding edge Kodi master in LE master you'll need to take matters into your own hands.