Posts by trogggy


    If the add-ons is the biggest issue, You can just take a copy of ' /userdata/addon_data' folder to safe location.

    Re-install, copy folder above back to it's location, install back add-on's You need and You're done...

    You might have to restart after installing add-ons before those re-read configs but that works every time.


    I don't think that works if you've updated straight to krypton. You'd need to enable any addons copied directly into the .kodi/addons folder.
    If you move from OE to LE jarvis, then move addons in, restart then update to LE krypton it should work.

    I have to tell you on at least 20 posts in the past , members have named their Black UN BRANDED box
    Beelink MiniMx because the sellers sold it to them with that name.
    Google beelink minimx s905 and see my point.
    Asking the question Un Branded confirmed they had the Broadcom Chip Un Branded Box.
    Because it is Manufactured by Beelink , there's nothing wrong with that.
    Again it is Chinese Branding mixing up names with numerous boxes with different specs.


    I think we're talking at cross purposes here.

    If someone says they have a minimx there's doubt as to what they mean.
    If someone says they have a minimx iii then that's a specific box.
    No?
    I've not seen a generic box sold as a mini mxiii - but maybe they have been?

    My point is that a Member asking for help with MiniMx as their Box to seek help is what causes confusion for me.
    I never know which of the 2 boxes a member has when they post MiniMx as their Box.
    Both boxes are made by Beelink with Nexteon Boards but have minor differences in Hardware (wifi chip) AND DIFFERENT
    Firmware.


    Gotcha. But in this case he did say ' I have Beelink Mini MXIII ...'
    If someone says that I'm going to assume they have a Beelink Mini MXIII - if not it's their problem. :D

    So I just copy one "disk" partition to the other "disk" partition and that is enough? I dont need to worry about the old boot partition?

    THanks

    Pretty much. But you need to stop kodi first.
    SSH (putty) in and run
    SYSTEMCTL STOP KODI
    Rename the .kodi folder on your storage partition.
    Copy the .kodi folder from the old partition to the new one.
    Run
    SYSTEMCTL START KODI
    and stand clear.

    Obviously that's only copying kodi across - if you have stuff in eg the .config folder (or want to copy the whole card contents) copy that across and reboot when you're done (which is just REBOOT in putty).

    If your boot partitions are identical it should just work. If the one on the non-working card is older you might find the first thing kodi does is to try to update addons and databases when it starts.
    Backup first (ie image the cards) and you can't break anything.
    Obviously you can copy the boot partitions (if you want to) while the cards are running (you'd need to run 'mount -o remount,rw /flash') but sticking them in a pc also works.

    Btw the one thing I don't copy across from 1 card to another is the .cache folder. I've found eg SSH has stopped working in the past when I've done that.

    I have had this issue with identifying a MiniMx during the last 12 months with members not being specific as to
    what MiniMx they have.
    I never use Beelink MiniMx when posting and always use Un Branded MiniMx S905 along with the ram and memory size to make it clear.
    Looks like the Branded Box uses Realtek. ;)


    Identifying a minimxiii should be pretty straightforward - the box and device are clearly labelled (Beelink on the device, Beelink minimx iii on the packaging) and they have a Beelink splash screen (as opposed to that bear or whatever it is).
    It's the rest of 'em (minimx) that seem to be unclear.

    I have never used Realtek device trees for my MiniMx S905 2g/16g non branded on casing.

    Please SSH into your box and run

    Code
    udevadm info /sys/bus/sdio/devices/sdio*

    This is my result below. Broadcom Wifi.

    For comparison my minimxiii (ie branded) returned this:

    I tried that on box number 2 when it arrived. Left it on for a couple of days, then installed LE to internal.
    I guess it was better than stock, it's hard to tell when you're testing a couple of months apart.
    And tbh I spent a load of time setting up the first box on android - when the second arrived it was more or less 'I'll check that out but what I really want to see is how well LE runs from Nand.'


    I have a couple of minimxiiis, both running 8.0, and they run like a dream. I tried android (kodi jarvis and spmc) when I bought the first box, and LE has been a much better experience.


    One thing, I tried renaming with e2label, but its not found, so I need to install it, but the system isn't operational (sudo apt-get not found, apt-get not found etc)

    I'm pretty sure I remember renaming partitions with e2label.

    Just tried in putty on my Beelink:


    That's obviously telling me my storage partition has the right name (LIBREELEC_DISK). But if not I'd be running:

    Quote


    e2label /dev/sda2 LIBREELEC_DISK


    The problem with the above, of course, is that if it doesn't boot you can't SSH in.
    So what I'd do is boot from a fresh sd card / usb (or use another instance of libreelec if you have one), stick your sd card in a card reader and plug it in a usb port, open putty, run 'df' to find the relevant partition and then e2label (carefully) to rename it. And if I was bothered about what was on it I'd image the card with eg win32diskimager or usbit before I started.
    Disclaimer - I'm also a windows user who just mucks about with this linuxy stuff.


    Linux can be picky with mounting partitions when for example there are disk errors, or the drive was not unmounted properly, or the system that the drive was in was in hibernation mode.

    Please recheck.


    I've just been caught out by that - noticed that ntfs drives weren't mounting in LE if I'd previously run windows 10 then switched off. They mounted fine if coming from from windows 7 poweroff, and if from windows 10 on a reboot. It turned out to be the 'Fast Start' setting in windows 10 (on by default) - probably been like that for ages but I hadn't noticed.

    Yes that is what i mean. I do not press any key on the remote. It start direct in Libreelec. Is that standard?


    Yes. If you plug these boxes in they will try to boot. To whatever they're set to boot from.
    So if there's an sd card or usb stick with libreelec on inserted they'll boot to that.

    A 'stock' box will boot to android when you plug it in.