Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
    Gran Canaria, Spain
  • Interests
    Computers, tinkering, TV-series, movies...

Recent Profile Visitors

1313 profile views
  1. No. The Snapdragon 7c is different from the RK3318/RK3328. You'd have to find an image for the Snapdragon 7c.
  2. Wouldn't some paths be wrong? Like, the kernel is expected to be in eMMC and not SD card.
  3. Correct me if I'm wrong. But you want to run the system from a USB3 SSD? If so, I think the easiest would be to just have the boot on eMMC or SD-card, and the rest of the system on the SSD, then "almost" everything would be running from the fast SSD.
  4. It seems to be an SP6330 wifi chip, if you look at the chip with the most dust on it.
  5. Wouldn't it be easier to modify Armbian as you want it before installing it in the first place? I don't know how to do it, but example. Download @jock's Armbian, or compile your own. Modify the files on the .iso. write it to the SD card and install it on box 1 without the need to modify it later. Then do it on box 2, box 3, etc.
  6. If it's a similar problem as I had with my H96 Max Plus (RK3328) @jock gave me a few good hints Here,
  7. curse


  8. Late response. In theory. I think you're on te right track. The backup in multitool does a raw copy, sector by sector, of the eMMC, so... theoretically. Install Armbian to eMMC and configure it to your liking Take a backup of the eMMC with multitool. Start the next box with multitool and "restore" the backup from the first box. It could work. The problem with TV-boxes though, is that sometimes(or even often), even if they are named the same and look the same, there can be different hardware in them. Probably what was cheapest at the time of production. Other potential issue I see, even if they are 100% identical, would be the hostname. That might be needed to set manually on all boxes. For example "RK3228-Box"(if that was the original hostname) had to be set to "RK3228-Box-1","RK3228-Box-2", etc. Otherwise the network might get confused. Then again, if you have hundreds of them. You could experiment a bit. It wouldn't be a total loss if a few of them died during experimentation.
  9. I noticed the same when I was trying to restore my backup. It got stuck at around 20-25 percent and I thought it might work better if I uncompress it first. Oups, I have a 64GB eMMC, and the SD card I had at the time was only 16 or 32 GB. The backup is a raw disk image of the eMMC, and it will always be the same size as the eMMC until it's compressed, and "removing the blank data" is part of the compression process.
  10. My French is not the best but for me it seems like the folders named "/boot/dtb-5.14.13-rockchip64/rockchip", "/boot/dtb-5.14.13-rockchip64/rockchip/overlay" and "/var/lib/initramfs-tools" are missing and the packages "bison" and "flex" needs to be installed.
  11. So, it should have the new Paragon additions for NTFS, right? I usually have an external NTFS drive connected to my box, and I'm currently using the NTFS-3G driver. It's said that the new stuff is supposed to be better. Pretty cool, my Arch Linux x86_64 desktop computer still has 5.14.**.
  12. Current: APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0gs=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 Fix after quick look: APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 It seems like you had everything after "APPEND root=LABEL=ROOTFS rootfla" copied and pasted after "net.ifnames=0" Is this the S905x3 version? I've been looking at one, but still not decided on it.
  13. And perhaps try with different SD cards. I first used some expensive recommended 64GB SanDisk card and nothing worked then I tried a "no-name" cheap 8GB card and it worked perfectly. I think it's up to luck when it comes to the SD cards. The recommended expensive cards might work more often than the cheap ones, but sometimes it's the other way around.
  14. Just one question. How did you "burn" the iso to the SD-card? did you use dd, rufus, etc? Just in case the error is there and not with the box or the iso?
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines