Posts by shippy

    LE uses connman to provide the tethered hotspot. Apart from clarifying that all I can see lots of talk about IPs and a/b/c that doesn't make any sense and doesn't actually ask a question; thus I cannot provide any more answers.

    You provided a partial answer, viz connman for tether. And good enough ,:P

    Question: Is there a way to update packages that already are a part of LE, e.g., Connman ( new version 1.34 Aug 2017) ?


    The other questions might not make sense if you are not familiar with networking- viz, NAT, iptables, hostapd and DHCP packages that will make up a router install.

    Here is some explanation for OSMC, from where I believe LE is derived from:

    Unable to route internet traffic from wifi to ethernet ready TV [SOLVED!] - Raspberry Pi - OSMC Forums

    So apparently, Connman has built in DHCP, and also DNSproxy (from another reference.) Thus Connman seems like a complete package that can replace DNS/DHCP features from dnsmasq and tether feature from hostapd !

    Btw, Connman does not allow change of SSID or the settings will mess up.

    So I managed to recover my Windows 7 on my laptop, but Clonezilla still doesn't seem to do the data imaging job...

    I am getting piecemeal info and doesn't look like LE is interested in a full single image vs their backup tool. ( LE or CE look the same problem to me. Using both.)

    Right now it has become a mini challenge to do a LE/CE single image data only clone. Sure I can always do a backup.

    *So what exact steps and settings do I need?* I have a laptop with Windows 7, and an SD card reader + 3 USB slots. Couple USB sticks too. And my Clonezilla live USB works in one USB stick.

    1. Here it says it does only copy data not entire disk unless instructed otherwise:

    [SOLVED] Clonezilla make image of size of data not size of disk - Data Backup - Spiceworks

    So is this done under defaults with Beginner mode?

    2. Also I copied my CE SD card to a USB drive, but the size looks 157MB. I know the original 140MB gzip expands to 559 MB, so there must be either hidden partitions on SD card, and/or data gets copied to the S905 eMMC.

    So what is the case? I don't think I can copy above to a fresh SD card and boot a S905 box??!!

    3. Here is I what I wrote back to [email protected] after he suggested a recovery on my laptop ( yes I had used defaults on the tuxboot live USB way and got Clonezilla installed over my Windows 7 instead of a USB !)

    Any suggestions ?

    I am trying to clone the LE/CE image as a single image (about 1GB or less with a couple addons and settings), not whole 8GB SD card, via Clonezilla live USB attached to a Windows 7 laptop along with one USB stick as destination, and an SD card reader (or a 3rd USB stick) as source.

    ----------

    Steven

    I fixed my Windows via recovery.

    Now I noticed that Clonezilla doesn't recognize my SD card reader on my laptop- I am using Beginner mode throughput.

    So then I just copied the contents of myCoreElec.org distribution including device tree folder (containing several *.dtb files) and System files.

    However Clonezilla first only showed the device tree folder, not the actual root directory at directory selection; then for source shower the HDD on laptop and the destination USB drive.

    But when I try selecting USB the red square doesn't stay: it moves with the ok or cancel button !

    How do I image data on my SD card/ USB stick then (don't want the entire disk copied)?

    ----------

    harpmaster

    I will still appreciate any links.

    My aim here is just to img (complete backup) from an LE SD card once add-ons and settings etc have been customized. Then transfer (restore) this new img (minimum possible for boot) to another similar S905 box later, plus archive it in case of loss. No wish to run this img on Windows !

    Sure we all know balbes150 great work. But my task is simple enough :P

    I'm not quite following that. CloneZilla does do compression, thus it can create small(er) images of large partitions that also have large empty spaces. Data is compressed by default, unless you don't want that and prefer bit-by-bit images. It's an advanced settings thing. You can also do Clonezilla images where you backup/restore partitions seperately but still into one image file. Perhaps you need to dive into Clonezilla's options and capabilities a bit more.

    That is part of the read-only system partition. Which should be easy enough to manually reinstall: creating partitions and copying the 4 files to that system partition. How many times are you planning to restore your LE system files anyway? Remember, LibreELEC uses only 2 system blob files (KERNEL + SYSTEM) in its installation.

    Klojum

    Yes I finally did realize Clonezilla does it right- too much smoke and mirrors online !

    But now here is what happened- Emailed to [email protected]

    -------------

    Steven,

    Saw your name online re:bug fixes.

    Have an old Win7 home premium Acer 255E netbook.


    I downloaded Clonezilla live USB via tuxboot following all site instructions via online and also downloaded the ISO.


    I proceeded to boot from the USB and apparently was able to copy a Linux distro image from the SD card reader to a second USB stick. All seemed fine.


    Then I tried booting from the laptop and have realized that it always boots Clonezilla. I briefly saw Acer eRecovery after pressing various F buttons, Alt and Esc etc, before I read about eRecovery.


    The Alt + F10 combo doesn't work to bring up eRecovery ( there is no CD drive.) I keep getting Clonezilla screen no matter what. Acer online forums are nice help.


    Kindly suggest a solution ! This likely is a bug as I noticed mention of a big fix earlier re: Acer One boot.


    -------------

    Klojum

    bubblegum57

    Guys I appreciate your quick responses.

    So the problem remains- backup vs cloning, with pros and cons.

    It's painful to see Clonezilla not being able to take out empty spaces while doing the .img thing. And DD is fraught even with a Linux laptop.

    Question: Is the /storage folder the only one physically on the SD card?

    How about /flash? I am assuming all LE folders are on SD card, or Clonezilla etc wouldn't be able to backup a complete image?

    This is what I did on my windows pc, download Yumi YUMI - Multiboot USB Creator | USB Pen Drive Linux then follow the instruction to create the clonezilla boot option, gparted is another useful program.

    Then boot this from your pc, insert original usb stick, (source) insert, another usb stick, (target) at least the same size or bigger than the source.

    As Klojum says, just follow the default settings, just make sure you select the correct source & target. This will make an exact clone of the source, it won't reduce the size.

    I do not know how to clone eMMC, but if you do, I'd be interested to know how.

    bubblegum57

    Klojum

    1. So what I understand is that the Clonezilla backup process above doesn't solve my real issue: backing up *only* the used portions of the original SD card with the LE distro+ add-ons+ settings?

    Otherwise Win32DiskImager is far easier to use.

    With the LE backup tool I need only one USB stick; with Clonezilla 3- bootable USB + source + target. And effort.

    2. Another way: Will the usual LE backup also include any custom splash images from /flash?

    Will LE backup contain all custom items? That is, whatever customization I do they will be LE backed up and simply be restorable on top of the respective original LE .img build that is burned via, say, Win32DiskImager, on the SD card?

    Personally, I have never had much luck with the backup program.

    I used to run my nuc from usb, & cloned the usb, to another usb using clonezilla. This worked very well.

    So, I suppose if you get a bootable version of clonezilla, you could do this.

    bubblegum57

    It's an old thread but a living conversation...

    1. Can you kindly give me instructions on how to clone the LE SD card as .img on PC disk (or USB stick) via Clonezilla, on Windows?

    I am more interested in a shrunk image, which Win32DiskImager doesn't do- produces a 7.44 GB .img on my PC HD !

    2. Also, is there a way to clone the LE image after installtointernal to the eMMC on an S905 box?

    With cloning you deal with one .img as opposed to doing it twice with backup + original .img.

    The problem with cross-platform backup/restore is that Win/Mac/Linux/Android share ~90% of their configuration, but ~10% is platform specific and may cause Kodi to choke on things during startup. Kodi doesn't claim to support it; neither do we. The additional issue with Win > Linux is Windows\paths\are\like\this and Linux/paths/are/like/that, so all media in DB files has an invalid path. It's not technically impossible to correct things, but it's not particularly simple either (and we don't provide guides for things we don't support).

    The LE backup function will capture any Docker containers installed via our addon repo. It won't capture anything stored elsewhere on /storage as the backup script only archives /storage/.kodi, /storage/.config and /storage/.cache. To backup/restore with our files, use our backup/restore function (in the settings addon). We don't test restore of our backup files with other Kodi addons so YMMV. At the end of the day LE backups are just a tar file, so doing things manually just requires you to run tar commands.

    Ok, appreciate the details.

    So I will assume that using LE settings backup/restore will work fine with all Kodi, Docker and LE add-ons and configurations.

    Of course you can't speak for Kodi Backup tool that has cloud backup/restore :P

    I think I understand .kodi folder backup /restore, but how about backup/restore with LE updates including add-ons/Docker?

    So here is what I want:

    1. Have Leia beta2 installed on my Win7 laptop, with add-ons and settings. No library items, just online streaming for now.

    2. I can use the Kodi Backup add-on to backup the updated .Kodi from Windows to GDrive or USB stick.

    Then I can restore on LE S905 box that already has Kodi Backup add on installed.

    Question: Is there an SSH way to update .Kodi from Windows PC to S905 LE?

    3. Now I further update LE with installation and configuration of LE (and Kodi) add-ons plus LE Docker add-ons.

    Questions:

    A. This means I can backup up Kodi + LE via the LE > System >System and Kodi Backup & Restore menu as a date.tar file?

    B. Also that the Kodi Backup will only backup the . Kodi folder with Kodi add-ons updates and settings in a zip file?

    4. I should then be able to use the respective 3A .kodi.zip and 3B date.tar files and restore to another S905 LE box (with fresh LE Leia installed) via respective Kodi Backup add-on and LE System and Kodi Backup&Restore menus?

    balbes150

    Good to see you making major LE contributions as well ! 👻👻

    1. Great ideas both, since they eliminate a lot of manual work.

    Is it possible for you to just look at the LibreElec remote.conf and mxq repo for many such files?

    remote.conf repository

    http://mxqproject.com/files/remote-config-file/

    2. Does installtointernal (to eMMC) eliminate remote.conf incompatibility for IR remotes with your generic S905/X/W Kodi 18alpha builds?

    Updated image Libreelec_s905_aarch64_20180425.

    Other options for s912 and arm will be added later as build and test.

    Major change.

    1. The shared dtb file (dtb.img) is excluded from the image. The startup script will attempt to use dtb data from internal memory. If the system fails to start in this mode, you must manually copy the correct file from the /device_trees directory to the root and rename it to "dtb.img " (this principle is exactly the same as it has long been used in all Armbian images). You can try all the files in a row, until you have selected an option with full support for all iron TV box.

    2. Added the ability to easily connect the settings file for the remote. It must be copied to the directory /storage/.config/rc_keymaps named remote-ir.conf. Additional manipulations are not required. Now already have one settings file for Khadas VIM\VIM2. If someone wants to add their own choices in the images - to send it to me indicating the model of the TV box.

    I am confused by kszaq red WARNING note under S805 generic TIPS & TRICKS re: remote.conf problems, which should apply equally to S905/912 builds too:

    [8.2.3.1] LibreELEC 8.0 for S805

    " WARNING

    Unless you have Android installed on internal, you might have remote.conf issues..."

    1. Does this (typo?) by any chance mean that with LE installtointernal, there should be no IR remote mismatch problems?

    That these problems arise only with dual boot SD install?

    *Below I refer to kszaq LE 805/905/905X 8.2.3.1 latest builds available.*

    2. How about the case with SD LE boot with internal data install?

    Would one still run into remote.conf problems?

    3. Is it enough to copy the Android /system/etc/remote.conf file to your SD card root containing your img and dtb files required to boot from SD card?

    I copied remote.conf from Android /system/etc to SD card root as above but without luck for my Yuntab MXV S805.

    My Nexbox A95X box with S905X Android 6.1 works fine including remote from SD card boot.

    The Yuntab MXV S805 Android 4.4.2 boots LE from SD; however none of the remote.conf files on kszaq 805 site work (I keep overwriting new trial files over existing ones in SD card root folder.)

    Strangely with the bottom side recovery button pressed and power cord then inserted, MXV box never entered recovery-just booted from Android 4.4.2 normally. But then I am able to boot LE from SD card anyway with the button pressed !

    ( The 3rd box, Richino S905 boots fine from Android 5.1.1, but the full SD card slot doesn't seem to do anything with various SD cards inserted.)

    Maybe I should try the #1,2,3 remote.conf files at http://mxqproject.com/files ?

    4. According to chewitt installtointernal is now deprecated... ( March 26, 2018 thread.)

    Does this mean kszaq 805/905 8.2.3.1 builds will continue having this feature, but newer builds won't?

    Is the installtointernal script part of autostart.sh ?

    5. As alternative, is it possible to take kszaq builds and use some program like TWRP to install to internal memory, and also backup/restore LE system and data and boot etc files?

    Thanks !:cool: