3 3
pcconsult

X96 MAX (S905X2) with Armbian-ubuntu

Recommended Posts

Hello! I am a novice on this forum. My device is the new (so far) X96 MAX. Now I am preparing to install on it the latest Armbian-ubuntu. My X96 MAX is with S905X2 chip, 4GB of RAM, 64GB of storage, gigabyte ethernet, dual-band wifi adapter. Please help me with some tips for this operation!

Share this post


Link to post
Share on other sites
3 hours ago, pcconsult said:

Hello! I am a novice on this forum. My device is the new (so far) X96 MAX. Now I am preparing to install on it the latest Armbian-ubuntu. My X96 MAX is with S905X2 chip, 4GB of RAM, 64GB of storage, gigabyte ethernet, dual-band wifi adapter. Please help me with some tips for this operation!

Wait... when mainline kernel will be support you soc. Or commit patches to meson project)

Share this post


Link to post
Share on other sites
On 12/17/2018 at 3:26 PM, talraash said:

Wait... when mainline kernel will be support you soc. Or commit patches to meson project)

 

Any idea regarding when the mainline kernel would support the s902x2 soc ? 

Or, could you please explain how to commit to meson project ?

Share this post


Link to post
Share on other sites
On 12/17/2018 at 10:50 AM, pcconsult said:

Hello! I am a novice on this forum. My device is the new (so far) X96 MAX. Now I am preparing to install on it the latest Armbian-ubuntu. My X96 MAX is with S905X2 chip, 4GB of RAM, 64GB of storage, gigabyte ethernet, dual-band wifi adapter. Please help me with some tips for this operation!

Have you tired the @balbes150 images?

https://yadi.sk/d/pHxaRAs-tZiei/5.72/S905

Try with meson-g12a-u200.dtb, it might boot but it looks pretty basic at the moment.

I would be interested to know whether they work on the S905X2

Share this post


Link to post
Share on other sites
(edited)

@pcconsult please keep us posted about youe progress. X96 Max is also on my radar and the first thing after opening the box would be installing Linux 😆. Thanks and good luck! Jarda

 

PS: it's not looking very promising "

IMHO these devices should stick to Android until mainline kernels are viable ..." https://forum.libreelec.tv/thread/13669-amlogic-s905x2-box-support/

Edited by Jaroslav Lhotak
Added a link to another forum

Share this post


Link to post
Share on other sites
(edited)

@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

Edited by koakh

Share this post


Link to post
Share on other sites

I also own a X96 Max and was hoping to get a Armbian image for it, Right now I have a mouse and keyboard connected to android, The keyboard enter key does not work , the right click on the mouse acts like a go backwards button on a browser and that's it. I wanted to use it as a desktop PC, but at this point its pretty crippled without using the on screen keyboard. Hence looking for a Armbian image that works. Also being Android there is no window dressings, like min,max,fullscreen in upper right corner of the screen, nor is there a taskbar to sort open windows, another reason for a Armbian image.  Please someone make an image for this. This is the one I purchased https://www.gearbest.com/tv-box/pp_009258424656.html?wid=1433363 

Share this post


Link to post
Share on other sites
On 1/29/2019 at 10:54 PM, koakh said:


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 

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".

 

47 minutes ago, Jeff Dewe said:

Please someone make an image for this. This is the one I purchased

There is a time for everything... wait for results. .. :)

Share this post


Link to post
Share on other sites

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 :).....

 

 

 

Share this post


Link to post
Share on other sites
48 minutes ago, balbes150 said:

So now my images no DTB for S905x2.

ok thanks, I will try in a near future :)

I wait, no problem.....

Share this post


Link to post
Share on other sites

Now I am waiting and I am tempted by the cute HYSTOU mini pc's in Gearbest. Some mini computer, not cheapest - up to $300 with 8GB RAM and 256GB SSD... and may be with I5 or I3 CPU... with big promo discount!

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

See the specified theme, there is a link to the site yandexdisk, it has a directory with version 5.77 with the corresponding subdirectories for S905X2.

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Yes it seem that is a USB <> sata bridge

 

Its what I try to find, a way to use it on armbian, it works on android 

 

Thanks @balbes150

 

TH4uB2M.png

Share this post


Link to post
Share on other sites

Show photos of your model and SATA connector. I just checked image 20190412 on my X96Max (S905X2) 4\32. eMMC without problems visible, works utility DDBR (allows you to create and restore full backup eMMc) and installation works Armbian in eMMC.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

All DTBS from Android are designed strictly for the old kernel. They will not work directly on core 5. From your files, you can only get the primary information to create an option for your model. But this is not an easy task that requires a lot of manual work.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
3 3