koakh

Members
  • Content Count

    45
  • Joined

  • Last visited

Posts posted by koakh

  1. hello try to flash to eMMC without success
    it is bricked, only boots from sdcard, the risk is minimal :)

    I keep play with it with sdcard....

     

    version used : Armbian_5.88_Aml-s905_Ubuntu_bionic_default_5.1.0_20190530

     

    log

     

    ```

    root@s905w-1:~# ./install.sh 
    Start script create MBR and filesystem
    Start backup u-boot default
    dd: failed to open '/dev/mmcblk1': No such file or directory
    Start create MBR and partittion
    Error: Could not stat device /dev/mmcblk1 - No such file or directory.
    Error: Could not stat device /dev/mmcblk1 - No such file or directory.
    Error: Could not stat device /dev/mmcblk1 - No such file or directory.
    Start restore u-boot
    dd: failed to open '/boot/u-boot-default.img': No such file or directory
    dd: failed to open '/boot/u-boot-default.img': No such file or directory
    Done
    Start copy system for eMMC.
    Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24)
    mkfs.vfat: unable to open /dev/mmcblk1p1: No such file or directory
    done.
    mount: /ddbr/install: special device /dev/mmcblk1p1 does not exist.
    Cppying BOOT...done.
    Edit init config...done.
    umount: /ddbr/install: not mounted.
    Formatting ROOT partition...
    The file /dev/mmcblk1p2 does not exist and no size was specified.
    e2fsck 1.44.1 (24-Mar-2018)
    e2fsck: No such file or directory while trying to open /dev/mmcblk1p2
    Possibly non-existent device?
    done.
    Copying ROOTFS.
    mount: /ddbr/install: special device /dev/mmcblk1p2 does not exist.
    Copy BIN
    Create DEV
    Copy ETC
    Copy HOME
    Copy LIB
    Create MEDIA
    Create MNT
    Copy OPT
    Create PROC
    Copy ROOT
    Create RUN
    Copy SBIN
    Copy SELINUX
    Copy SRV
    Create SYS
    Create TMP
    Copy USR
    Copy VAR
    Copy fstab
    umount: /ddbr/install: not mounted.
    *******************************************
    Complete copy OS to eMMC 
    *******************************************
    ```

     

    thanks to all :)

    IMG_20191215_180718.jpg

    IMG_20191215_180727.jpg

  2. Hello again

     

    I try to extract dtb file following this post, and other posts on net

    https://www.cnx-software.com/2014/05/12/how-to-extract-a-device-tree-file-from-android-firmware-files/

     

    the only way I can get the dtb file (meson1.dtb) is with a tool Amlogic Customization Tool that someone comments about in above post

     

    but I try boot it in my box without success, it try to boots, jump to black screen after a 1 or 2 seconds 

     

    meson1.dtb

     

    Update: I uses the above command to extract dtb, I extract dtb.img, and test it to boot, but some error ir won't boot, black screen after 1sec

     

    dd if=/dev/dtb | gzip > /storage/emulated/0/Download/dtb.img.gz

     

    can someone help me to extract a bootable dtb for my A95X max Box, help me to get access to usb to sata bridge module, to mount sata disk

     

    Thanks on advance

  3. You are right this is a A95X Max!

    And not a x96 Max, sorry but I forget the post title and forget to say my box modelo, and this create some confusion.

     

    Now I understand why eMMC backup and restore works in your box and not um mine. And why you say that "On X96 max there are no SATA devices."

     

    Is this One FreakTab Link

     

    I'm posting on wrong topic.

    Maybe I Open another topic for this box

     

    Thanks @balbes150

    hwX9jWM.jpg

  4. Photos has requested...

     

    About eMMC backup and restore, it works using nand-sata-install, but armbian never boots....

     

    I post a lots of related info about boot problems, and partition problems above....please scroll up, and view one image that shows the Crash on boot, related with bad partition (added to. This post)

     

    Ir we try to mount the restored Partition, ir inspect it, we sure check that we can mount it

     

    root@aml:~# sudo mount /dev/mmcblk1p2 /mnt/mmcblk1p2 mount: /mnt/mmcblk1p2: can't read superblock

     

    Thanks for your support @balbes150

     

    IMG_20190422_231749.jpg

    IMG_20190422_231715.jpg

    IMG_20190422_231655.jpg

    IMG_20190422_231728.jpg

    IMG_20190407_121332.jpg

  5. Hi, any news about X96 MAX eMMC and sata drive?

     

    This is the ONLY things that is missing to close/finish my new post about create a server with X96 Max with eMMC and SataDisk.

     

    Maybe someone help me to use USB bridge with sata disk, and flash it INTO eMMC....

     

    I post relevant info and problems above

     

    Thanks

  6. hello

    another problem 
    I installed one 1tb sata disk and It appears in android OS but is not detected in armbian,

    has anyone have any idea why the internal sata disk (it uses usb) is not detected with fdisk, parted, usb-devices etc?
    maybe is not supported in this kernel yet....

    $ sudo fdisk -l
    
    Disk /dev/mmcblk0: 7.3 GiB, 7850688512 bytes, 15333376 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0xb2ee51e1
    
    Device         Boot  Start      End  Sectors  Size Id Type
    /dev/mmcblk0p1        8192   270335   262144  128M  e W95 FAT16 (LBA)
    /dev/mmcblk0p2      270336 15026687 14756352    7G 83 Linux
    
    Disk /dev/mmcblk1: 58.2 GiB, 62537072640 bytes, 122142720 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    $ sudo dmesg | grep usb-storage
    
    [    2.486462] usbcore: registered new interface driver usb-storage
    
    $ sudo lsusb
    
    Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. 
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    
    $ usb-devices 
    
    T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
    D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=1d6b ProdID=0002 Rev=05.01
    S:  Manufacturer=Linux 5.1.0-rc1-aml-s905 xhci-hcd
    S:  Product=xHCI Host Controller
    S:  SerialNumber=xhci-hcd.3.auto
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    
    T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 4
    D:  Ver= 2.10 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
    P:  Vendor=05e3 ProdID=0610 Rev=93.03
    S:  Manufacturer=GenesysLogic
    S:  Product=USB2.1 Hub
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
    I:  If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub
    
    T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
    D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
    P:  Vendor=1d6b ProdID=0003 Rev=05.01
    S:  Manufacturer=Linux 5.1.0-rc1-aml-s905 xhci-hcd
    S:  Product=xHCI Host Controller
    S:  SerialNumber=xhci-hcd.3.auto
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    
    T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=5000 MxCh= 4
    D:  Ver= 3.10 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
    P:  Vendor=05e3 ProdID=0620 Rev=93.03
    S:  Manufacturer=GenesysLogic
    S:  Product=USB3.1 Hub
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    
    (parted) print devices                                                    
    /dev/mmcblk1boot0 (4194kB)
    /dev/mmcblk0 (7851MB)
    /dev/mmcblk1boot1 (4194kB)
    /dev/mmcblk1 (62.5GB)

    if I connect it via usb with external case it is detected

    [   39.169476] usb 2-1.3: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd
    [   39.192093] usb-storage 2-1.3:1.0: USB Mass Storage device detected
    [   39.192756] scsi host0: usb-storage 2-1.3:1.0
    [   40.193953] scsi 0:0:0:0: Direct-Access     TO Exter nal USB 3.0      0204 PQ: 0 ANSI: 6
    [   40.194680] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
    [   40.194988] sd 0:0:0:0: [sda] Write Protect is off
    [   40.194994] sd 0:0:0:0: [sda] Mode Sense: 47 00 00 08
    [   40.195284] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [   40.195300] sd 0:0:0:0: [sda] Optimal transfer size 0 bytes < PAGE_SIZE (4096 bytes)
    [   40.301541]  sda: sda1
    [   40.302993] sd 0:0:0:0: [sda] Attached SCSI disk
                                                                              
    $ sudo fdisk -l                                                                          
    Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0xb87cc500
    
    Device     Boot Start        End    Sectors   Size Id Type
    /dev/sda1        2048 1953523711 1953521664 931.5G 83 Linux

    thanks

  7. current progress, finished docker, builded neo4j and mongodb armv8 containers, nodejs, openjdk11,  and other development related stuff......
    eMMC flashed, boots but still have problems with system partition.........
    reserved space for next update with eMMC and installed HardDisk installation notes....

    UPDATE: I have problems with nand-sata-install and system partition
    in /dev/mmcblk1p1 everything is work has expected, I can't mount it, it boot but /dev/mmcblk1p2 is giving a lots of problems flashing from USB to eMMC
    and after flash I can't mount the partitiion, I have a lot's of problems like
     

    sudo mount /dev/mmcblk1p2 /mnt/tmp
    mount: /mnt/tmp: can't read superblock on /dev/mmcblk1p2.

    and

    Calling ioctl() to re-read partition table.
    /dev/mmcblk1: close device failed: Input/output error

    full nand-sata-install log

    $ sudo nand-sata-install
    Start script create MBR and filesystem
    Start backup u-boot default
    4+0 records in
    4+0 records out
    4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.0545877 s, 76.8 MB/s
    Start create MBR and partittion
    Error: Input/output error during write on /dev/mmcblk1
    Error: You requested a partition from 700MB to 828MB (sectors 1367187..1617187).
    The closest location we can manage is 700MB to 700MB (sectors 1368063..1368063).
    Error: You requested a partition from 829MB to 62.5GB (sectors 1619140..122142719).
    The closest location we can manage is 829MB to 829MB (sectors 1619967..1619967).
    Start restore u-boot
    dd: fsync failed for '/dev/mmcblk1': Input/output error
    442+0 records in
    442+0 records out
    442 bytes copied, 0.00497615 s, 88.8 kB/s
    dd: fsync failed for '/dev/mmcblk1': Input/output error
    8191+0 records in
    8191+0 records out
    4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.376217 s, 11.1 MB/s
    Done
    Start copy system for eMMC.
    Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24)
    done.
    Cppying BOOT...done.
    Edit init config...done.
    rm: cannot remove '/ddbr/install/s9*': No such file or directory
    rm: cannot remove '/ddbr/install/aml*': No such file or directory
    Formatting ROOT partition...
    /dev/mmcblk1p2 contains a ext4 file system labelled 'ROOT_EMMC'
    	last mounted on /ddbr/install on Sat Apr  6 22:07:17 2019
    
    Warning, had trouble writing out superblocks.
    e2fsck 1.44.1 (24-Mar-2018)
    ROOT_EMMC: clean, 80766/3768320 files, 1360921/15065344 blocks
    done.
    Copying ROOTFS.
    mount: /ddbr/install: can't read superblock on /dev/mmcblk1p2.
    Copy BIN
    Create DEV
    Copy ETC
    Copy HOME
    Copy LIB
    Create MEDIA
    Create MNT
    Copy OPT
    Create PROC
    Copy ROOT
    Create RUN
    Copy SBIN
    Copy SELINUX
    Copy SRV
    Create SYS
    Create TMP
    Copy USR
    Copy VAR
    tar: var/lib/samba/private/msg.sock/1333: socket ignored
    tar: var/lib/samba/private/msg.sock/1607: socket ignored
    tar: var/lib/samba/private/msg.sock/1522: socket ignored
    tar: var/lib/samba/private/msg.sock/1482: socket ignored
    tar: var/lib/samba/private/msg.sock/10057: socket ignored
    tar: var/lib/samba/private/msg.sock/1498: socket ignored
    tar: var/lib/samba/private/msg.sock/1497: socket ignored
    tar: var/lib/samba/private/msg.sock/1355: socket ignored
    tar: var/lib/samba/private/msg.sock/1483: socket ignored
    tar: var/lib/samba/private/msg.sock/1363: socket ignored
    tar: var/lib/samba/private/msg.sock/1611: socket ignored
    tar: var/lib/samba/private/msg.sock/1448: socket ignored
    tar: var/lib/samba/private/msg.sock/10058: socket ignored
    tar: var/lib/samba/private/msg.sock/9771: socket ignored
    tar: var/lib/samba/private/msg.sock/1447: socket ignored
    tar: var/lib/samba/private/msg.sock/1610: socket ignored
    tar: var/lib/samba/private/msg.sock/1376: socket ignored
    tar: var/lib/samba/private/msg.sock/1609: socket ignored
    Copy fstab
    umount: /ddbr/install: not mounted.
    *******************************************
    Complete copy OS to eMMC 
    *******************************************

    resume: the device boots but stops boot when try to access / system partition, with a lots of errors

     

    eMMCBoot.Crash.thumb.jpg.4e8b1045f330a5349133d96a89251374.jpg

    any help will be appreciated, thanks

    UPDATE: try nand-sata-install with sdcard but same errors occurs....

    I try to dd/copy partition from /dev/mmcblk0 to /dev/mmcblk1 but it won't boot either

    root@aml:~# dd if=/dev/mmcblk0 of=/dev/mmcblk1 bs=1024k status=progress
    7844397056 bytes (7.8 GB, 7.3 GiB) copied, 335 s, 23.4 MB/s
    7487+0 records in
    7487+0 records out
    7850688512 bytes (7.9 GB, 7.3 GiB) copied, 337.959 s, 23.2 MB/s
    
    # try to mount fails on /dev/mmcblk1p2, but not on /dev/mmcblk1p1
    
    root@aml:~# sudo mount /dev/mmcblk1p1 /mnt/mmcblk1p1
    root@aml:~# sudo mount /dev/mmcblk1p2 /mnt/mmcblk1p2
    mount: /mnt/mmcblk1p2: can't read superblock on /dev/mmcblk1p2.

    some info about eMMC

    sudo mmc extcsd read /dev/mmcblk1
    =============================================
      Extended CSD rev 1.8 (MMC 5.1)
    =============================================
    
    Card Supported Command sets [S_CMD_SET: 0x01]
    HPI Features [HPI_FEATURE: 0x01]: implementation based on CMD13
    Background operations support [BKOPS_SUPPORT: 0x01]
    Max Packet Read Cmd [MAX_PACKED_READS: 0x3f]
    Max Packet Write Cmd [MAX_PACKED_WRITES: 0x3f]
    Data TAG support [DATA_TAG_SUPPORT: 0x01]
    Data TAG Unit Size [TAG_UNIT_SIZE: 0x02]
    Tag Resources Size [TAG_RES_SIZE: 0x00]
    Context Management Capabilities [CONTEXT_CAPABILITIES: 0x05]
    Large Unit Size [LARGE_UNIT_SIZE_M1: 0x07]
    Extended partition attribute support [EXT_SUPPORT: 0x03]
    Generic CMD6 Timer [GENERIC_CMD6_TIME: 0x0a]
    Power off notification [POWER_OFF_LONG_TIME: 0x3c]
    Cache Size [CACHE_SIZE] is 65536 KiB
    Background operations status [BKOPS_STATUS: 0x00]
    1st Initialisation Time after programmed sector [INI_TIMEOUT_AP: 0x1e]
    Power class for 52MHz, DDR at 3.6V [PWR_CL_DDR_52_360: 0x00]
    Power class for 52MHz, DDR at 1.95V [PWR_CL_DDR_52_195: 0x00]
    Power class for 200MHz at 3.6V [PWR_CL_200_360: 0x00]
    Power class for 200MHz, at 1.95V [PWR_CL_200_195: 0x00]
    Minimum Performance for 8bit at 52MHz in DDR mode:
     [MIN_PERF_DDR_W_8_52: 0x00]
     [MIN_PERF_DDR_R_8_52: 0x00]
    TRIM Multiplier [TRIM_MULT: 0x02]
    Secure Feature support [SEC_FEATURE_SUPPORT: 0x55]
    Boot Information [BOOT_INFO: 0x07]
     Device supports alternative boot method
     Device supports dual data rate during boot
     Device supports high speed timing during boot
    Boot partition size [BOOT_SIZE_MULTI: 0x20]
    Access size [ACC_SIZE: 0x07]
    High-capacity erase unit size [HC_ERASE_GRP_SIZE: 0x01]
     i.e. 512 KiB
    High-capacity erase timeout [ERASE_TIMEOUT_MULT: 0x01]
    Reliable write sector count [REL_WR_SEC_C: 0x01]
    High-capacity W protect group size [HC_WP_GRP_SIZE: 0x10]
     i.e. 8192 KiB
    Sleep current (VCC) [S_C_VCC: 0x07]
    Sleep current (VCCQ) [S_C_VCCQ: 0x07]
    Sleep/awake timeout [S_A_TIMEOUT: 0x11]
    Sector Count [SEC_COUNT: 0x0747c000]
     Device is block-addressed
    Minimum Write Performance for 8bit:
     [MIN_PERF_W_8_52: 0x00]
     [MIN_PERF_R_8_52: 0x00]
     [MIN_PERF_W_8_26_4_52: 0x00]
     [MIN_PERF_R_8_26_4_52: 0x00]
    Minimum Write Performance for 4bit:
     [MIN_PERF_W_4_26: 0x00]
     [MIN_PERF_R_4_26: 0x00]
    Power classes registers:
     [PWR_CL_26_360: 0x00]
     [PWR_CL_52_360: 0x00]
     [PWR_CL_26_195: 0x00]
     [PWR_CL_52_195: 0x00]
    Partition switching timing [PARTITION_SWITCH_TIME: 0x01]
    Out-of-interrupt busy timing [OUT_OF_INTERRUPT_TIME: 0x05]
    I/O Driver Strength [DRIVER_STRENGTH: 0x1f]
    Card Type [CARD_TYPE: 0x57]
     HS200 Single Data Rate eMMC @200MHz 1.8VI/O
     HS Dual Data Rate eMMC @52MHz 1.8V or 3VI/O
     HS eMMC @52MHz - at rated device voltage(s)
     HS eMMC @26MHz - at rated device voltage(s)
    CSD structure version [CSD_STRUCTURE: 0x02]
    Command set [CMD_SET: 0x00]
    Command set revision [CMD_SET_REV: 0x00]
    Power class [POWER_CLASS: 0x00]
    High-speed interface timing [HS_TIMING: 0x02]
    Erased memory content [ERASED_MEM_CONT: 0x00]
    Boot configuration bytes [PARTITION_CONFIG: 0x00]
     Not boot enable
     No access to boot partition
    Boot config protection [BOOT_CONFIG_PROT: 0x00]
    Boot bus Conditions [BOOT_BUS_CONDITIONS: 0x01]
    High-density erase group definition [ERASE_GROUP_DEF: 0x01]
    Boot write protection status registers [BOOT_WP_STATUS]: 0x00
    Boot Area Write protection [BOOT_WP]: 0x00
     Power ro locking: possible
     Permanent ro locking: possible
     ro lock status: not locked
    User area write protection register [USER_WP]: 0x00
    FW configuration [FW_CONFIG]: 0x00
    RPMB Size [RPMB_SIZE_MULT]: 0x20
    Write reliability setting register [WR_REL_SET]: 0x1f
     user area: the device protects existing data if a power failure occurs during a write operation
     partition 1: the device protects existing data if a power failure occurs during a write operation
     partition 2: the device protects existing data if a power failure occurs during a write operation
     partition 3: the device protects existing data if a power failure occurs during a write operation
     partition 4: the device protects existing data if a power failure occurs during a write operation
    Write reliability parameter register [WR_REL_PARAM]: 0x14
     Device supports the enhanced def. of reliable write
    Enable background operations handshake [BKOPS_EN]: 0x00
    H/W reset function [RST_N_FUNCTION]: 0x01
    HPI management [HPI_MGMT]: 0x01
    Partitioning Support [PARTITIONING_SUPPORT]: 0x07
     Device support partitioning feature
     Device can have enhanced tech.
    Max Enhanced Area Size [MAX_ENH_SIZE_MULT]: 0x000e8f
     i.e. 30531584 KiB
    Partitions attribute [PARTITIONS_ATTRIBUTE]: 0x00
    Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
     Device partition setting NOT complete
    General Purpose Partition Size
     [GP_SIZE_MULT_4]: 0x000000
     [GP_SIZE_MULT_3]: 0x000000
     [GP_SIZE_MULT_2]: 0x000000
     [GP_SIZE_MULT_1]: 0x000000
    Enhanced User Data Area Size [ENH_SIZE_MULT]: 0x000000
     i.e. 0 KiB
    Enhanced User Data Start Address [ENH_START_ADDR]: 0x000000
     i.e. 0 bytes offset
    Bad Block Management mode [SEC_BAD_BLK_MGMNT]: 0x00
    Periodic Wake-up [PERIODIC_WAKEUP]: 0x00
    Program CID/CSD in DDR mode support [PROGRAM_CID_CSD_DDR_SUPPORT]: 0x01
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[127]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[126]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[125]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[124]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[123]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[122]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[121]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[120]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[119]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[118]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[117]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[116]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[115]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[114]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[113]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[112]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[111]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[110]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[109]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[108]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[107]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[106]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[105]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[104]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[103]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[102]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[101]]: 0x05
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[100]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[99]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[98]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[97]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[96]]: 0x01
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[95]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[94]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[93]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[92]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[91]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[90]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[89]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[88]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[87]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[86]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[85]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[84]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[83]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[82]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[81]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[80]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[79]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[78]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[77]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[76]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[75]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[74]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[73]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[72]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[71]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[70]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[69]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[68]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[67]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[66]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[65]]: 0x00
    Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[64]]: 0x0f
    Native sector size [NATIVE_SECTOR_SIZE]: 0x00
    Sector size emulation [USE_NATIVE_SECTOR]: 0x00
    Sector size [DATA_SECTOR_SIZE]: 0x00
    1st initialization after disabling sector size emulation [INI_TIMEOUT_EMU]: 0x00
    Class 6 commands control [CLASS_6_CTRL]: 0x00
    Number of addressed group to be Released[DYNCAP_NEEDED]: 0x00
    Exception events control [EXCEPTION_EVENTS_CTRL]: 0x0000
    Exception events status[EXCEPTION_EVENTS_STATUS]: 0x0000
    Extended Partitions Attribute [EXT_PARTITIONS_ATTRIBUTE]: 0x0000
    Context configuration [CONTEXT_CONF[51]]: 0x00
    Context configuration [CONTEXT_CONF[50]]: 0x00
    Context configuration [CONTEXT_CONF[49]]: 0x00
    Context configuration [CONTEXT_CONF[48]]: 0x00
    Context configuration [CONTEXT_CONF[47]]: 0x00
    Context configuration [CONTEXT_CONF[46]]: 0x00
    Context configuration [CONTEXT_CONF[45]]: 0x00
    Context configuration [CONTEXT_CONF[44]]: 0x00
    Context configuration [CONTEXT_CONF[43]]: 0x00
    Context configuration [CONTEXT_CONF[42]]: 0x00
    Context configuration [CONTEXT_CONF[41]]: 0x00
    Context configuration [CONTEXT_CONF[40]]: 0x00
    Context configuration [CONTEXT_CONF[39]]: 0x00
    Context configuration [CONTEXT_CONF[38]]: 0x00
    Context configuration [CONTEXT_CONF[37]]: 0x00
    Packed command status [PACKED_COMMAND_STATUS]: 0x00
    Packed command failure index [PACKED_FAILURE_INDEX]: 0x00
    Power Off Notification [POWER_OFF_NOTIFICATION]: 0x01
    Control to turn the Cache ON/OFF [CACHE_CTRL]: 0x01
    eMMC Firmware Version:
    eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x01
    eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x01
    eMMC Pre EOL information [EXT_CSD_PRE_EOL_INFO]: 0x01
    Command Queue Support [CMDQ_SUPPORT]: 0x01
    Command Queue Depth [CMDQ_DEPTH]: 16
    Command Enabled [CMDQ_MODE_EN]: 0x00

     

  8. thanks @balbes150 for the fastest repply

    but I already found it (I think so),
    I update my post above, it seems the link is

    https://yadi.sk/d/pHxaRAs-tZiei/5.77/S905X2

    I'm flashing my pen disk right now with Armbian_5.77_Aml-s905_Ubuntu_bionic_dev_5.1.0-rc1_20190406
    I post my feedback ASAP
    thanks :)

    update: disk flashed, booting armbian, and ssh right now.........
    awesome work, at last, our great armbian distro working on S905X2 :)

    uname -a 
    Linux aml 5.1.0-rc1-aml-s905 #5.77 SMP PREEMPT Sat Apr 6 14:53:09 MSK 2019 aarch64 aarch64 aarch64 GNU/Linux
    docker -v
    Docker version 18.09.2, build 6247962
    docker-compose -v
    docker-compose version 1.17.1, build unknown
    

     

  9. Great news.....today I Will try it on my  S905X2

     

    I leave feedback here.....

     

    Thanks @balbes150

     

    update: confirm it boots LibreELEC

    uname --all
    Linux LibreELEC 5.1.0-rc1 #1 SMP PREEMPT Fri Apr 5 13:37:17 MSK 2019 aarch64 GNU/Linux

    but this is far from useful for a linux server, that is my purpose.
    LibreELEC is not based on any debian distro or other distro with a good package manager
    ......but it have docker, I give it a try :)
     

    docker --version
    Docker version 18.09.1, build 18.09.1

    but its a start :)

    a question is possible to use this boot kernel with armbian distro? 

    thanks

  10. For reference - no longer uses the copy file mode dtb to the "dtb.img". To select which dtb to use, edit the file "uEnv.ini".

     

    Nice tip.....and I tested All dtb's with copy method......eheheh....last time I installed armbian this is the method I used....

     

    today I Will try All dtb's with @balbes150 tip :) one by One, and post

    my findings. I just want the Shell to setup another Linux Sever :).....

     

     

     

  11. @pcconsult first thing after opening the box would be installing Linux

     

    Lol

     

    Is what I do with mine today, when it arrives

    awesome hardware

     

    I connect my tested S912/S905x USB stick in first boot with clip just for fun.....but it won't boot (it's to soon yet)

    Ir keeps on boot screen....I try some diferent ports, but I'm on work, and dont have time to play with it

     

    Tomorrow or next weekend I Will try some dtb's (startup in first to last) with above sugestted image.....and I post my finds, if it boot we are in good track, if not I wait for a new kernel, but never give up, this box is too great for a server to give up)

     

    If someone has some stuff to test, send it, its a pleasure :)

    UPDATED: 2019/02/03

    Tested all dtb.img in sugested image 
    https://yadi.sk/d/pHxaRAs-tZiei/5.72/S905, but won't boot, stays in boot logo forever with all dtb.img's

    - [X] dtb-4.20.2-aml-s905/meson-axg-s400.dtb
    - [x] dtb-4.20.2-aml-s905/meson-g12a-u200.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-nanopi-k2.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-nexbox-a95x.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-odroidc2.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-p200.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-p201.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-vega-s95-meta.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-vega-s95-pro.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-vega-s95-telos.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-wetek-hub.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxbb-wetek-play2.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s805x-p241.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s905d-p230.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s905d-p231.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s905w-p281.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s905w-tx3-mini.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s905x-hwacom-amazetv.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s905x-khadas-vim.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s905x-libretech-cc.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s905x-nexbox-a95x.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxl-s905x-p212.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxm-khadas-vim2.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxm-nexbox-a1.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxm-q200.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxm-q201.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxm-rbox-pro.dtb
    - [x] dtb-4.20.2-aml-s905/meson-gxm-vega-s96.dtb

    It seems that I'm arrived to the end of line....I will wait for a news, or advices for next weeks/months....no problem


    if someone has any advice/tips on out to boot armbian on this SOC/S905X2, I will appreciate it...

     

    PS: my objective is only boot in linux console mode to install a server with the gigabit or wifi network card


    I don't need any acelarated video, graphics chipset stuff etc, only the console/ssh version


    thanks

     

    Keep the good working

  12. 39 minutes ago, fatugazuhati said:

    Did you noticed that also in a clean install at system in idle we always have a system load that never goes under 1 caused by vdec-core in uninterruptible sleep?

    This is a kernel related problem appeared in last versions and I have reported it here. Do you have some idea about what do to?

    I dont know about this idle problem. But when I push system and use more resources, like push docker containers for eg, I have all cores and CPU at higher levels. But I will watch this idle for higher values.....

  13. 36 minutes ago, Jeycop said:

    Nice to read you made it.

     

    PS: Awesome Thread for setup, thanks !!!

    hm docker, didn't hear about it, I start reading about it now^^

    Did you do a wifi speedtest?Now I try mumble server and a website with apache and mysql.

    and dont know docker! welcome 

     

    docker is the best thing that appens to IT after Linux (my humble opinion)
    you have many containers already setup waiting.........with mysql, php, lamp etc just choose :)
    install docker from my post and follow some good tutorials, and you are learning good stuff man (again my opinion)

     

    thanks to all

  14. This is a quick notes post for people that want to setup Armbian on AlfaWise H96 Pro+ eMMC and use it as a Headless Server for Docker Microservices

     

    Thanks to @balbes150 @guidol and @Jeycop and all the awsome people of this forum

     

    Tech stack used

     

    Armbian

    - Java 8

    - Docker

    - Spring Framework/Boot 2.0

    - Node Js

    - Aurelia Freamework

     

    Download Files

     

    - Android firmware (Optional, required in case of revert from eMMC flash)

     

    - New H96 Pro Plus 7.1.2 firmware download By EBox

     

    - Armbian Version

     

    Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_server_20180305.img

     

    Flash SDCard or USBDisk

     

    1) use rufus with dd, or linux disks, or dd command to flash above image

     

    2) plug SDcard/Usb into Box

     

    4) Plug power cable into Box while holding reset button pressed


    Note:This step is only required if is the first time boot armbian after flash android firmware.....

     

    5) See Armbian booting up

     

    8) login with `un:root`, `pw:1234` and configure it

     

    7) reboot

     

    8) login with root

     

    9) start "./install.sh" and wait for finish (5-7 minutes)

     

    (WARNING above command flash eMMC, You Lost ANDROID, dont do that if you dont know how to recovery android firmware, or dont want to use eMMC, SKIP to step 14 for the setup with SdCard/Usb Only)

     

    10) shutdown with `halt` and remove power cable

     

    11) remove SDcard/Usb

     

    12) plug power cable in Box, now you should see Armbian booting up without SDCard/Usb

     

    13) login to catch ip or scan it with `sudo nmap -sS -p 22 192.168.1.0/24 | grep -a4 -b2 00:80:0F:96:E3:01`. Change to your mac and ip

     

    14) SSH To it, and get some info

    $ uname -a
    Linux amlogic 3.14.29 #114 SMP PREEMPT Mon Mar 5 12:57:46 MSK 2018 aarch64 aarch64 aarch64 GNU/Linux
    
    $ lscpu
    lscpu
    Architecture: aarch64
    Byte Order: Little Endian
    CPU(s): 8
    On-line CPU(s) list: 0-7
    Thread(s) per core: 1
    Core(s) per socket: 4
    Socket(s): 2
    CPU max MHz: 1512.0000
    CPU min MHz: 100.0000
    Hypervisor vendor: (null)
    Virtualization type: full

    Setup WiFi with 3.14 Mali-6 Image Only (The Version that works with Wifi)

     

    this required some hacked script to put it to work, lost a few hours to figure it, its not pretty but works after boot and its stable

     

    First remove all modules from `/etc/modules` to leave it initialization for `init.d` script

    $ cat /etc/modules
    #aml_nftl_dev

    Next Create a `init.d` hacked script, with some magic and optimized sleeps, without that sleep times or with lower times it wont work, Its very strange that I must load and unload module, and reload again, but its seems the only way to put this working, I know its too strange, and hard to find, maybe someone has a better ways, I belive with some knowledge its easy,

     

    Why its working only that way, dont ask me why, I dont care, for me its not pretty, but its hugly and working, Im happy with it, who cares LOL, I dont waste more time for an elegant and pretty solution......

     

    move on.....the `init.d` script

    $ sudo nano /etc/init.d/wlan

    paste

    #! /bin/sh
    # /etc/init.d/wlan
    #
    ### BEGIN INIT INFO
    # Provides:          wlan
    # Required-Start:    $remote_fs $syslog
    # Required-Stop:     $remote_fs $syslog
    # Default-Start:     2 3 4 5
    # Default-Stop:      0 1 6
    # Short-Description: AlfaWise H96 Pro+ Wireless Boot Script
    # Description:       This file should be used to construct scripts to be
    #                    placed in /etc/init.d.  This example start a
    #                    single forking daemon capable of writing a pid
    #                    file.  To get other behavoirs, implemend
    #                    do_start(), do_stop() or other functions to
    #                    override the defaults in /lib/init/init-d-script.
    ### END INIT INFO
    
    # Some things that run always
    touch /var/lock/wlan
    
    # Carry out specific functions when asked to by the system
    case "$1" in
      start)
        echo "Starting Wlan Script"
        echo "modprobe wlan"
        /sbin/modprobe wlan
        echo "modprobe wlan -r in 28sec..."
        sleep 28
        /sbin/modprobe wlan -r
        echo "modprobe lan in 28sec..."
        sleep 28
        echo "modprobe wlan..."
        /sbin/modprobe wlan
        ;;
      stop)
        echo "Stopping script wlan"
        /sbin/modprobe wlan -r
        ;;
      *)
        echo "Usage: /etc/init.d/wlan {start|stop}"
        exit 1
        ;;
    esac
    
    exit 0

    Install systemd service

    $ sudo chmod 755 /etc/init.d/wlan
    $ sudo systemctl enable wlan

    Reboot

    $ sudo reboot

    Configure wireless with nmtui

    $ sudo nmtui
    
    $ ifconfig wlan
    wlan0 Link encap:Ethernet HWaddr 84:5d:d7:??:??:??
    inet addr:192.168.1.177 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::865d:d7ff:fe4a:3202/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:15 errors:0 dropped:0 overruns:0 frame:0
    TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:3246 (3.2 KB) TX bytes:1556 (1.5 KB)

    check configs saved from nmtui

    $ ls /etc/NetworkManager/system-connections/ -la
    total 12
    drwxr-xr-x 2 root root 4096 Mar 29 18:42 .
    drwxr-xr-x 8 root root 4096 Mar 5 10:24 ..
    -rw------- 1 root root 419 Mar 29 18:42 scWF_WDS1
    
    $ sudo cat /etc/NetworkManager/system-connections/scWF_WDS1

    > Note: If Problems arrise using WiFi, with/without eth0 cable, try disable eth0 with `sudo ifdown eth0`, sometimes the connection is linked somehow to ethernet to prevent this kinds of problems disable ethernet or boot without cable connected

    $ sudo reboot

    After reboot inspect unload/load driver with

    $ sudo tail -f /var/log/syslog | grep wlan
    Mar 29 18:42:25 localhost dnsmasq[4152]: using nameserver 192.168.1.10#53(via wlan0)
    Mar 29 18:42:25 localhost nm-dispatcher: req:1 'up' [wlan0]: new request (1 scripts)
    Mar 29 18:42:25 localhost nm-dispatcher: req:1 'up' [wlan0]: start running ordered scripts...
    Mar 29 18:42:28 localhost ntpd[3533]: Listen normally on 8 wlan0 192.168.1.177:123

    In other PC ping the wifi IP and wait it responds without do anything, here it starts respond after 2:18 (with usb stick) minutes:seconds, not bad since reboot, shutdown and boot, and with time delays for wifi 

     

    some info after login

    $ cat /etc/modules
    #aml_nftl_dev
    
    $ lsmod
    Module Size Used by
    wlan 3435325 0
    zram 8953 8
    cfg80211 415017 1 wlan

    Update and Install Stuff

    $ sudo apt update && sudo apt upgrade
    $ sudo apt install docker.io docker-compose samba openvpn lshw hwinfo
    
    $ docker -v
    Docker version 1.13.1, build 092cba3
    
    $ docker-compose -v
    docker-compose version 1.8.0, build unknown

    Configure Samba

    sudo cp /etc/samba/smb.conf /etc/samba/smb.conf_ORG
    sudo nano /etc/samba/smb.conf

    paste above

    [users]
    comment = All users
    path = /home
    read only = No
    inherit acls = Yes
    veto files = /aquota.user/groups/shares/
    
    [root]
    comment = Root
    path = /
    writable = yes
    printable = no
    write list = root
    browseable = no

    add a user

    $ sudo smbpasswd -a USERNAME
    # start service
    $ sudo systemctl restart smbd
    # enable service
    $ sudo systemctl enable smbd.service

    Install Java 8 (Optional currently using Docker Containers, but it may be usefull for running quick prototype protects)

    $ sudo -i
    $ sudo echo "deb http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main" | tee /etc/apt/sources.list.d/webupd8team-java.list
    $ sudo echo "deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main" | tee -a /etc/apt/sources.list.d/webupd8team-java.list
    $ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys EEA14886
    $ sudo apt-get update
    $ sudo apt-get install oracle-java8-installer
    
    #####Important########
    To set Oracle JDK8 as default, install the "oracle-java8-set-default" package.
    E.g.: sudo apt install oracle-java8-set-default
    On Ubuntu systems, oracle-java8-set-default is most probably installed
    automatically with this package
    
    $ sudo apt install oracle-java8-set-default
    
    $ java -version
    java version "1.8.0_161"
    
    Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
    Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)

    Create docker-compose.yml to run and test my Spring-Boot IoT Project in Arm64v8 Arquitecture

     

    Note: this step is ommited, it simply is a docker-compose file to test my IOT project, with four docker arm64v8 container microservices,

     

    - Spring Boot Rest Api /Arm64V8

    - Spring Boot Moquette/Mqtt Mongo Server with Auth and ACL

    - Aurelia Framework / NodeJS WebApp / Mqtt.js Client / Chart.js

    - Mongo DB

     

    if someone like to test it with a ESP8266 tell me and paste here the docker-composer.yml 

     

    move on

     

    Backup Image

     

    Use the DD command to create image of `/dev/boot` and `/dev/system`

      

    Create a mount point to house images, using a samba share here to //192.168.1.1/root, one can use a spare disk or other media

    $ sudo nano fstab

    add //192.168.1.1/root /mnt/koakhserver cifs username=${USER},password=${PASSWORD},_netdev,noauto 0 0 to the bottom

    #/var/swap none swap sw 0 0
    #/dev/root / auto noatime,errors=remount-ro 0 1
    #proc /proc proc defaults 0 0
    /dev/root / ext4 defaults,noatime,errors=remount-ro 0 1
    tmpfs /tmp tmpfs defaults,nosuid 0 0
    
    //192.168.1.1/root /mnt/koakhserver cifs username=${USER},password=${PASSWORD},_netdev,noauto 0 0

    Backup eMMC

    $ sudo mkdir /mnt/koakhserver -p
    $ sudo mount /mnt/koakhserver
    
    $ sudo dd if=/dev/boot of=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/boot.img bs=1024k status=progress
    32+0 records in
    32+0 records out
    33554432 bytes (34 MB, 32 MiB) copied, 3.3319 s, 10.1 MB/s
    
    $ sudo dd if=/dev/system of=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/system.img bs=1024k status=progress
    2146435072 bytes (2.1 GB, 2.0 GiB) copied, 150.027 s, 14.3 MB/s
    2048+0 records in
    2048+0 records out
    2147483648 bytes (2.1 GB, 2.0 GiB) copied, 197.892 s, 10.9 MB/s

    when we need to restore use the reverse process

    $ sudo mount /mnt/koakhserver/
    $ sudo dd if=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/boot.img of=/dev/boot bs=1024k status=progress
    $ dd if=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/system.img of=/dev/system bs=1024k status=progress
    

    Done......I Think I dont forget nothing.....................

     

    Thanks to all

  15. 13 hours ago, Jeycop said:

     

    Thank you.

    I got it to work on my internal.

    (H96 Pro+ (Plus) green mainboard with LDDR3 produced in 2017)

     

    I used this version "Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_server_20180305.img.xz" LINK

    Installed it directly over original Firmware with "./install.sh" -script without any problems.

    Important for me was to use Rufus to burn the image to a sdcard and to run it without any dtb-file in main directory on the sdcard.

    To start from sdcard I pressed the reset-button for few seconds right after I plugged in the power cable.

     

    I was just wondering about the download, because it's under "5.41_KODI-17.6" but I don't need any kodi on this box.

    So do I have to clean it up at first, so no storage and performance waste on these additional installations?

     

    Flashed in eMMC at first with Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_server_20180305.img.xz but without backup and restore like sugested.........
    Damn why I not try that LOL

    Thanks @Jeycop

     

    Its lightning fast running eMMC :) and a lots more space :) 25GB Free is more than enough :) simply awsome

    I setup the whole setup, that contains 4 docker microservice containers, webapi. mqttserver, mongo, and nodejs/aurelia spa running and with a load average of 1.06

    top - 19:32:17 up 15 min,  2 users,  load average: 1.09, 1.50, 1.26
    Tasks: 162 total,   2 running, 160 sleeping,   0 stopped,   0 zombie
    %Cpu(s):  0.5 us,  0.1 sy,  0.0 ni, 99.5 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
    KiB Mem :  2815116 total,   846868 free,   989084 used,   979164 buff/cache
    KiB Swap:  1407520 total,  1319976 free,    87544 used.  1758744 avail Mem 
    
      PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                                                               
     4377 999       20   0  936044  49136  12252 S   1.3  1.7   0:17.40 mongod                                                                                                                
     5411 mario     20   0    7484   1764   1192 R   1.0  0.1   0:00.19 top                                                                                                                   
     4378 root      20   0 4624736 445216  12608 S   0.7 15.8   4:10.79 java                                                                                                                  
     2600 root      20   0       0      0      0 S   0.3  0.0   0:02.63 kworker/3:2                                                                                                           
     3461 root      20   0 1029888  28788  15004 S   0.3  1.0   0:09.37 dockerd                                                                                                               
     3680 root      20   0  946616   8888   4592 S   0.3  0.3   0:04.32 containerd                                                                                                            
     4420 root      20   0 4761960 375840  12632 S   0.3 13.4   3:43.67 java                                                                                                                  
     4975 root      -2   0       0      0      0 S   0.3  0.0   0:00.69 ksdioirqd/sdio                                                                                                        
        1 root      20   0  155872   5712   2408 S   0.0  0.2   0:10.92 systemd                                                                                                               
        2 root      20   0       0      0      0 S   0.0  0.0   0:00.00 kthreadd                                                                                                              
        3 root      20   0       0      0      0 S   0.0  0.0   0:00.23 ksoftirqd/0                                                                                                           
        5 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/0:0H                                                                                                          
        7 root      20   0       0      0      0 S   0.0  0.0   0:00.73 rcu_preempt                                                                                                           
        8 root      20   0       0      0      0 S   0.0  0.0   0:00.00 rcu_sched                                                                                                             
        9 root      20   0       0      0      0 S   0.0  0.0   0:00.00 rcu_bh                                                                                                                
       10 root      rt   0       0      0      0 S   0.0  0.0   0:00.00 migration/0                                                                                                           
       11 root      rt   0       0      0      0 S   0.0  0.0   0:00.12 migration/1                                                                                                           
       12 root      20   0       0      0      0 S   0.0  0.0   0:00.02 ksoftirqd/1                                                                                                           
       14 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/1:0H                                                                                                          
       15 root      rt   0       0      0      0 S   0.0  0.0   0:00.00 migration/2                                                                                                           
  16. I note that you dont backup/restore your partitions! You just use install.sh and nothing more!

     

    I read and have some guide tips from @balbes150 (I think so) to 

     

    1) install.sh

    2) dont reboot, and backup partitions

    3) boot from SD and restore partitions (Fail here)

    4) boot from emmc

     

    I never try boot after install.sh like you do, maybe it works without steps 2,3, and 4 too

     

    I note that you comment about remove kody, why you dont flash headless server. I burn headless server and its awsome,very clean :)

  17. 27 minutes ago, Jeycop said:

    Yes, for me it was very easy ^^

     

    H96Pro+ has 2 different versions. One with LDDR3 and one with DDR4, maybe thats the difference. 

    I opened the case and there are 2 USB extra inside but no hole in case. Now I have 4x USB ;P

     

    1.) if you changed something on internal EMMC storage -> flash official Firmware   (mine was from 12-2017) // I think it's important, so Armbian can read the correct DeviceTree?

    2.) Burn image "Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_server_20180305.img" with Rufus to SDCard (LINK)

    3.) Plug SDcard into Box

    4.) Plug power cable into Box while holding reset button pressed

    5.) See Armbian booting up

    6.) Set username and password

    7.) reboot

    8.) login

    9.) start "./install.sh" and wait for finish (5-7 minutes)

    10.) shutdown and remove power cable

    11.) remove SDcard

    12.) plug power cable in Box, now you should see Armbian booting up without SDCard -> finished

     

    I think the trick is related with the firmware

     

    1.) if you changed something on internal EMMC storage -> flash official Firmware   (mine was from 12-2017) // I think it's important, so Armbian can read the correct DeviceTree?

     

    In the past I lost original my firmware,  and after a few hours try and failling and searching for a firmware/tools that works I found and use this one

     

    New H96 Pro Plus 7.1.2 firmware download By EBox
    https://www.entertainmentbox.com/new-h96-pro-plus-tv-box-android-7-1-2-custom-firmware-download/
    
    AlfaWise H96 PRO+ 3 32Gb LPDDR3
    
    Download SCV4 BLUE (LPDDR3) PCB IMG:
    DOWNLOAD HERE BLUE PCB SCV4 IMG 7.1.2
    MD5: 67D22C782DDCA083F297B98DA406ADE3
    

    This is the version I used NOW, can you confirm that is the same as yours from above pictures...
    I post other pics too like boot faillure on boot with half restored /system from eMMC  and my blue board version

    It seems your firmware is diferent from mine

    Can you confirm please, and the board is the same?

    thanks @Jeycop

    PS: I only have time to do something tomorrow, currently Im working and dont have alfawise box here only access to my laptop/notes

    IMG_20180303_215137.jpg

    IMG_20180303_214612.jpg

    IMG_20180303_223310.jpg

    IMG_20180306_142405.jpg

  18. 4 hours ago, Jeycop said:

     

    Thank you.

    I got it to work on my internal.

    (H96 Pro+ (Plus) green mainboard with LDDR3 produced in 2017)

     

    I used this version "Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_server_20180305.img.xz" LINK

    Installed it directly over original Firmware with "./install.sh" -script without any problems.

    Important for me was to use Rufus to burn the image to a sdcard and to run it without any dtb-file in main directory on the sdcard.

    To start from sdcard I pressed the reset-button for few seconds right after I plugged in the power cable.

     

    I was just wondering about the download, because it's under "5.41_KODI-17.6" but I don't need any kodi on this box.

    So do I have to clean it up at first, so no storage and performance waste on these additional installations?

     

    Hello @Jeycop

     

    First Sorry I forget that you request something in the past, 
    and I forget what is it, 
    I think is related with my notes, 
    only today I received the mail from forum and I remember that

    When I repply I was on phone and far from my laptop/notes

     

    move on....

     

    Note: I Note here your version is 20180305 and mine is 20180225

     

    Glad to know you flashed your eMMC with Armbian, great achievement,

    I try it in past but always I have this error 

     

    dd: error writing '/dev/system': No space left on device

     

    it seeems that it requires a 2.0 GiB partion and mine is 1.0 GiB :(


    I try to repartition the partition to increase size but without success

     

    Maybe I try with the same image 20180305 and using rufus, 
    I use "disks" or "dd" in linux to flash the image not rufus

     

    I belive is more about with that image that you flashed that is diferent
    maybe that image has diferent partition sizes or a diferent install.sh script (maybe)


    I will try for sure :)
    and I will check the size of partitions and install.sh script to check diferences
     

    My Notes from the PAST TRY to use eMMC Using Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_server_20180225.img.xz

     

    > Not its diferent from youre like I note in above Notes

     

    ```shell
    $ ./install.sh
    Start copy system for DATA partition.
    Formatting DATA partition...
    umount: /dev/data: not mounted
    /dev/data contains a ext4 file system
        last mounted on /data on Thu Jan  1 00:00:14 2015
    e2fsck 1.42.13 (17-May-2015)
    /dev/data: clean, 11/1721760 files, 152081/6883328 blocks
    done.
    Copying ROOTFS.
    Copy BIN
    Copy BOOT
    Create DEV
    Copy ETC
    Copy HOME
    Copy LIB
    Create MEDIA
    Create MNT
    Copy OPT
    Create PROC
    Copy ROOT
    Create RUN
    Copy SBIN
    Copy SELINUX
    Copy SRV
    Create SYS
    Create TMP
    Copy USR
    Copy VAR
    Copy fstab
    *******************************************
    Done copy ROOTFS
    *******************************************
    Writing new kernel image...
    65536+0 records in
    65536+0 records out
    33554432 bytes (34 MB, 32 MiB) copied, 0.621699 s, 54.0 MB/s
    writing boot image config in bootimg.cfg
    extracting kernel in zImage
    extracting ramdisk in initrd.img
    reading kernel from /boot/zImage
    Writing Boot Image /dev/boot
    reading ramdisk from /boot/initrd.img-3.14.29
    Writing Boot Image /dev/boot
    done.
    Writing new dtb ...
    done.
    Write env bootargs
    *******************************************
    Complete copy OS to eMMC parted DATA
    *******************************************
    ```
    
    Used the DD command to create image of `/dev/boot` and `/dev/system`
        
    Create a mount point to house images
    
    ```shell
    $ sudo nano fstab
    //192.168.1.1/root      /mnt/koakhserver        cifs    username=${USER},password=${PASSWORD},_netdev,noauto   0 0
    
    sudo mkdir /mnt/koakhserver
    sudo mount /mnt/koakhserver 
    ```
    
    ```shell
    $ sudo dd if=/dev/boot of=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/boot.img bs=1024k status=progress
    65536+0 records in
    65536+0 records out
    33554432 bytes (34 MB, 32 MiB) copied, 4.60886 s, 7.3 MB/s    
    
    $ sudo dd if=/dev/system of=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/system.img bs=1024k status=progress
    2124414976 bytes (2.1 GB, 2.0 GiB) copied, 51.0174 s, 41.6 MB/s 
    2048+0 records in
    2048+0 records out
    2147483648 bytes (2.1 GB, 2.0 GiB) copied, 52.4382 s, 41.0 MB/s
    ```
    
    Restart the system from the SD card and restore the `/dev/boot` and `/dev/system` partitions from the created copies
    
    ```shell
    $ sudo mount /mnt/koakhserver/
    $ sudo dd if=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/boot.img of=/dev/boot bs=1024k status=progress
    
    $ dd if=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/system.img of=/dev/system bs=1024k status=progress
    $ dd if=/mnt/trekstor/system.img of=/dev/system bs=1024k status=progress
    1073741824 bytes (1.1 GB, 1.0 GiB) copied, 112.024 s, 9.6 MB/s 
    dd: error writing '/dev/system': No space left on device
    1025+0 records in
    1024+0 records out
    1073741824 bytes (1.1 GB, 1.0 GiB) copied, 113.171 s, 9.5 MB/s
    ```

    Thanks for yout feedback @jeycop

     

    It seems that was "easy" for you, you just

    1) Flash image with Rufus
    2) Boot and flash eMMC with install.sh 

    3) Backup Partitions before reboot

    4) Reboot with SdCard

    5) Restore Backup Partitions

    6) Remove SDCard and it boots from eMMC 

     

    can you confirm the aboves steps :) (thanks in advance)
     

  19. 3 hours ago, Jeycop said:

    Hi koakh,

    my goal is to replace my raspb3 (webserver and other services)with the same box as you (H96 Pro+)

     

    Could you please post a (if possible) short version what you did to run Armbian on your H96 box? (DTB and Armbian version)

    (Wifi is not so important for me)

     

    Did you manage to install armbian on the internal storage?

    I think the sd-reader is slower than the raspb3 one. (tested with samsung evo) So I wanted to get armbian running on the internal storage.

     

    thanks for your time

    Hello

     

    First I must tell that I stopped at my last requirement step, that is using the eMMC, I started but when I used the scripts it gives problems, like restore the Partitions to a lower size partition (1gb),

     

    I use the sdcard version, until I have spare time or any help, I lost a few hours with this setup now.

    Right now I dont have my notes, I'm on phone, but I answear your questions ASAP

     

    About version and dtb I already post here in this topic, please scroll...and how to boot armbian too, use the reset when boot first time. After first armbian boot is not need to use the reset anymore.

     

    If I can help, just ask....no problem its a pleasure ;)