Posts by dtech

    Start reading from this post or few posts above as well RE: LE-9.2.8 builds for some Amlogic S905x, S802/S812 and S805 devices

    I didn't try ethernet but will try it today as we are using the same image on similar box.

    Your boxes are quite different. For example, your box was equipped with Gigabit Ethernet (Realtek RTL8211F), not 10/100 Mbps.

    On the other hand, your box has an S812 SoC and ochentay4 's box has an S802 only.

    But nonetheless, I am happy to accept the result from both. ;)

    Ok, image seems to work nicely on Netxeon M82_V4.0_20141106 device (Tronsmart MXIII 2G/8GB Wifi 6330). Wifi worked correctly, funny enough, ethernet did not, cant get ip from DHCP (triple checked connections). Ethernet chip is H1601NL (1502-XG). Any fix you can think of?

    I also managed to installtointernal, I like it. If I could get ethernet working Im golden.

    H1601NL -> It's just a transformer, your Ethernet chip is actually an IC+ IP101GR.

    It is located under the quartz behind your lower USB port. :)

    I need a dmesg.

    jim_p

    It's good that you're asking me these, but I'm reassuring you, I didn't eat the free space. :angel:

    The schema of the partitions on the internal NAND/eMMC follows Android, which splits the flash into quite a few pieces.

    There are a lot of partitons on it that are unnecessary for LE, or have no file system, just raw data (eg. kernel -> /dev/boot).

    But the same is true for bootloader, dtb, recovery, cache, etc.

    For example: /dev/system also varies in size for some boxes, in your case ~1GB, but here it usually only contains the SYSTEM (squashfs) file, which is 120-150 MB in size and is basically a non-writable partition.

    But on a USB flash drive or an SD card, it’s completely different, so it’s like comparing an apple to a pear.

    There are two partitions, one for boot files (kernel, squashfs) and one for data. And that's the story. :shy:

    Honestly if that would be slowly the end of does devices i would be still more then happy by what you achieved and what i have now installed on my box. While i was running kodi 15 for last few years i might as well run kodi 18.9 for another 3 years(as only using it for playing 1080p files and now maybe even x256 (maybe even in 4k). So i'm good with that. And then i will buy a newer box or something else to use LE.

    THANK YOU.

    No, I would like to thank you and wish you enjoyable and trouble-free use. ;)

    Hi, love this project. Is Tronsmart MXIII 2GB/8GB (K200) going to be supported anytime soon?

    Experience shows that the n200 image is also perfect for k200 devices. Do you know what kind of wifi chip is in your box?

    I can't get ffmpeg to work with this addon,

    it works on CE, Windows, Linux,

    i tried
    and,

    possibly the builds are incompatible with the kernel of this system

    I don't know much about it, but since it works on S905 + processors
    then I have to look for some very old version of ffmpeg 

    The problem is, I don’t even know if it worked with earlier versions under 3.10/3.14 kernel or not.

    Unfortunately, the addon problems are in the same hat as the docker. I have neither the time nor the opportunity to investigate very much.

    In the background, I'm also trying to bring back amcodec support to the Kodi Matrix version so that older devices can be used with the older kernel for at least some time. But I can't really move forward with that either.

    Apparently, I was left alone for this, because the previous developers had already got out of this "suffering" since LE version 8.2 or 9.0 (kszaq, Demetris, datrh, etc.). Unfortunately, I’m starting to realize that the Amlogic v3.10/3.14 kernels are slowly no longer compatible with anything new. :(

    To my surprise this time it booted instantly from flash:)

    But... there is always but when external hdd not connected - otherwise is a long boot.

    Unfortunately, if a storage device is connected to an external USB (external HDD, flash drive, etc.), it would try to boot from there first.

    If you need to ignore startfromext, you need to set this:

    Code
    fw_setenv bootcmd run storeboot

    And then reboot. If all goes well, it will no longer try to boot from an exernal device (not even an SD card).

    please help libreelec for this m8s working box.

    Next time please use a translator because the only accepted language on the forum is English.

    dtech
    February 7, 2021 at 2:33 PM

    Unfortunately, I don’t see exactly the type of wifi chip on your photo, but basically one of two images can be good:

    • Universal n200: Ampak AP6330 or Realtek wifi,
    • OTT M8S+ (n200C): multiple broadcom/ampak wifi.

    Please try them out and report back in the linked topic.

    I need some enterprising Minix X8 / X8-H / X8-H Plus testers in this topic:

    dtech
    September 13, 2021 at 8:58 AM

    You are right. How to check flash size then?

    Well, the easiest way to really do this is to type the ID at the top of the chip into a search engine. ^^

    This really matters if you run from there. (E.g. if it is installed to the internal memory with installtointernal script.)

    This is my M8S (n200C), LE runs from the internal NAND:

    Code: df -h
    Filesystem                Size      Used Available Use% Mounted on
    devtmpfs                766.4M      4.0K    766.4M   0% /dev
    /dev/system             975.9M    124.1M    835.8M  13% /flash
    /dev/loop0              122.0M    122.0M         0 100% /
    /dev/data                 5.3G      1.3G      3.9G  25% /storage
    tmpfs                   768.4M         0    768.4M   0% /dev/shm
    tmpfs                   768.4M      9.1M    759.2M   1% /run
    tmpfs                   768.4M         0    768.4M   0% /sys/fs/cgroup
    tmpfs                   768.4M      2.2M    766.2M   0% /var
    tmpfs                   768.4M         0    768.4M   0% /tmp

    Can't access this file (repository.libreelec.tv-9.2.1.zip) on your server.

    Sorry, the link has been link fixed. There is no SSL certificate for this subdomain on my server, so the HTTPS is not valid in the URL.

    But this stupid Crome found it funny to add that idiot s to http. No comment... :P

    BTW That's my box mainboard in attachment - it shows tronsmart on sticker and 8gb but it is 16gb.

    NCEFAT28-08G -> It is interesting because this is a 8GB eMMC on your PCB.

    Okay, the manual workaround is here for the "repo bug after update":

    (However, as a new installation, everything will work immediately, and there is no need for manual intervention.)

    IMPORTANT!

    If you installed it as an update and you have a problem installing addons, you will need to manually update the LE repository addon:

    repository.libreelec.tv-9.2.1.zip

    For v9.2.8.1 and earlier versions I also replaced the old repo, and the only package included is this:

    After that you just need to update and point to the location of the new repo (S8X2):

    I wouldn't bother with that bug too much(tbh i downloaded only one add-on from repo and it is a skin;) - just add in first post that "users have to do a fresh install every time new build is released" and wait for LE to fix it.

    This is a "catch-22" situation: If LE fix this bug, how do you install it if you don't reach the repo itself?

    I'm trying to find a bridging solution...

    Install failure. It looks like LE can't see files from this repo as it is not showing size. I did update from old snapshot(the one from 10th). Will check with new installation as well.


    Yes - it is upgrade related as fresh installation is working ok.

    Okay, I investigated and all new images in the S8X2 project are affected: M8S+, MXIII*, Uni-n200.

    The cause of the error is probably not in my own build, but rather in Kodi or LE.

    It is a fact: The repository link for the devices has changed.

    Old: http://libreelec.dtech.hu/packages/9.2.0/M8S-Plus/arm

    New: http://libreelec.dtech.hu/packages/9.2.0/S8X2/arm

    But that's still not the real reason, because both paths work and point to the same target (symlink).

    Code
    2021-09-14 06:37:34.376 T:3010805760 WARNING: Repository add-on repository.libreelec.tv uses plain HTTP for add-on downloads in path http://libreelec.dtech.hu/packages/9.2.0/S8X2/arm - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!
    2021-09-14 06:38:04.143 T:2901406592 WARNING: Previous line repeats 32 times.
    2021-09-14 06:38:04.143 T:2901406592   ERROR: Requested path http://libreelec.dtech.hu/packages/9.2.0/M8S-Plus/arm/virtual.dvb-tools/virtual.dvb-tools-9.2.0.105.zip not found in known repository directories

    The repository link is good, the download link is working, it's just from the old index file.

    Somehow the index would have to be updated to point to the new location, but I have no idea where LE stores this. ?(

    Update #1:

    It doesn't work either: https://wiki.libreelec.tv/how-to/force-add-on-update

    It can be updated, but it will still use the old URL when downloading add-ons. What a stupid bug is this?

    Update #2: The Kodi backup/restore solution does not work either.

    MXIII-G 4K 2GB/16GB

    LibreELEC-n200-AP6330_2G.arm-9.2.8.2 - some glitches at boot(when you see "linux things" - same with last snapshot but not important). Wifi no problem(connects with kodi repo straight away and is downloading skin without any issues), movie freeze gone. If there were no more changes from previous snapshot then i was testing it for hours and it is working flawless.

    No volume/mute osd but i think it might be related to my avr/panasonic 4k tv but my older openelec build works without that glitch - will try to track it down with debug..

    LibreELEC-MXIII-Plus.arm-9.2.8.2.img - no wifi for me so didn't test it more. Glitches at boot.

    That glitch is normal, also present in M8S+, due to the framebuffer reset (by platform_init script).

    However, this is necessary to correct the freezing error, but I think we can live with that. :)

    Since you have a clone with the AP6330, the universal n200 image is basically the best (and perhaps the only working) choice.

    I enabled the image as stable, thanks for your feedback. ;)