Jump to content

Erario

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Another excellent method that works perfectly is this. The advantage of this script is that it succeeds in copying the entire filesystem to SD or USB drives without performing a mirror clone as with dd, so even if the destination is smaller than the source as long as it has the space needed for the actual space occupied. I had been using it for years on RPI, I didn't think it was compatible with Armbian as well, instead it works great. And by taking the correct version from here is already compatible with Armbian, also acts on correcting UUID on the target device to make it boot correctly after the clone. If it works on my tvbox it will also work on any official Armbian distribution, so on any device... absolutely must have! Booted disk: mmcblk2 63.7GB Destination disk: mmcblk0 31.4GB --------------------------------------------------------------------------- Part Size FS Label Part Size FS Label 1 root 58.7G ext4 -- 1 29.3G ext4 -- --------------------------------------------------------------------------- == Initialize: IMAGE partition table - forced by option == 1 root (6.7G used) : RESIZE MKFS SYNC to mmcblk0p1 --------------------------------------------------------------------------- -e clone fstab edit : edit mmcblk2p device entries to mmcblk0p. Run setup script : no. Verbose mode : no. -----------------------: ** WARNING ** : All destination disk mmcblk0 data will be overwritten! -----------------------: Initialize and clone to the destination disk mmcblk0? (yes/no): y Optional destination ext type file system label (16 chars max): Initializing Imaging past partition 1 start. => dd if=/dev/mmcblk2 of=/dev/mmcblk0 bs=1M count=8 ... Resizing destination disk last partition ... Resize success. Changing destination Disk ID ... => mkfs -t ext4 /dev/mmcblk0p1 ... Syncing file systems (can take a long time) Syncing mounted partitions: Mounting /dev/mmcblk0p1 on /mnt/clone => rsync // /mnt/clone with-root-excludes ... Editing /boot/armbianEnv.txt UUID to use 08477615-e9ee-4faa-8574-d58796f838ad for partition 1 Editing /etc/fstab UUID to use 08477615-e9ee-4faa-8574-d58796f838ad for partition 1 =============================== Done with clone to /dev/mmcblk0 Start - 14:56:29 End - 14:57:55 Elapsed Time - 1:26
  2. I managed to extract the correct dtb for this tvbox from Android, I converted it the DTS and it is all well readable but now I am stuck in doubts. I use Armbian with the dtb "sun50i-h6-tanix-tx6.dtb" for the Tanix TX6, but unfortunately it is not fully compatible with this tvbox. I have exaggeratedly high SoC temperature measurements compared to what I thermally detect on the cpu, and only two USB ports out of the existing four work. By compiling the image with these patches I was able to get the four usb ports and also the dual color LEDs working, but unfortunately they are stopped at an outdated kernel version inside Buster, and I would like to stay more up to date with Jammy. Now I would like to try to create a proper Armbian DTB for this tvbox starting from that of the Tanix TX6 for Android where everything works, even the wifi (XR819), but I can't find any documentation to be able to do it right. But the important thing now is to understand whether the thermal sensor is correct in the DTB of the Tanix TX6 for this tvbox, with the heat gun I detect a temperature of the SoC not over 40° but Armbian reports me over 80°. What puts me off is the high and shutdown temperatures, which are totally different, much less conservative in the Android version (85/100 VS 110/115). The two files I attach are the DTS extracted from Android for my tvbox and the one from the Buster image with kernel 5.7 patched that I currently use, I thank in advance those who will get me on the right track before I think about kernel patching. mx10pro.dts sun50i-h6-generic.dts
  3. I solved with two scripts, the first one creates a dump to img in mounted Windows filesystem (to be executed only once), the second one keeps the image aligned via rsync as needed.
  4. Since this link is down does anyone have an image of the latest published for S812?
  5. I couldn't find anything on the web, I looked everywhere. With the dd command I can of course create a complete image of the eMMC anywhere, even on a network path, but I can't find anything that allows me to do what the "nand-sata-install.sh" script does, which formats the eMMC and populates it with all the contents of the MicroSD, appropriately adapting some files needed for booting. It would be many useful to be able to do the exact opposite as well, i.e. clone eMMC to MicroSD, which would be useful to have a bootable backup with all the customizations performed on the eMMC, without having to go through the process of creating an image file. I tried modifying the script to do this but could not do it, there is actually an option already there to do this but it doesn't work for me. Surely there is someone better than me, I hope, who maybe has already done this. nand-sata-install.sh
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines