dxs1

Members
  • Content Count

    12
  • Joined

  • Last visited

About dxs1

  • Rank
    Member

Recent Profile Visitors

571 profile views
  1. Hello, Here are my 2 cents related to installation of image version xenial_3.14.29_mate dated 23 March 2017 Found here: https://yadi.sk/d/pHxaRAs-tZiei INSTALLATION TO eMMC: I have installed image "Armbian_5.27_S9xxx_Ubuntu_xenial_3.14.29_mate_20170323.img" on SD card. I was able to boot successfully without modifying anything. As root, I have run /root/install.sh and system was installed to eMMC. I was able to boot from eMMC with Mate successfully. Video Hardware Acceleration: My understanding is that there is no driver available for the GPU to get hardware acceleration. I guess this means that Kodi cannot be built and installed to provide proper video rendering. T95Z Plus hardware specifics: Also, there are 2 additional features which could be nice to add: - Control colored light around device - Control LCD display located at the front of device Do you know how I could control them ? Is there any test I can perform to provide any further help ? Thank you
  2. PREPARATION: 1/ I have downloaded following image from https://yadi.sk/d/5_32km_EsCV2A : S9xxx_4G_ICEWM_MATE_XFCE_LXDE_LXQT_20170129.img.xz 2/ unzipped downloaded file and installed on usb stick (M:\) with Win32DiskImager 3/ dowloaded gxm_q201_2g.dtb file from https://forum.armbian.com/index.php/topic/2138-armbian-for-amlogic-s912/?p=17682 and extracted dtb.img file from gxm_q201_2g.zip to M:\dtb.img BOOT TEST: - Insert USB stick - Turn TZ95Plus device on - Wait some time - Have a coffee - Wait some more time RESULT: Black screen.
  3. Hi Balbes, Thank you for your message. 1. My entry in the post #11 above was a typo (now corrected). I did copy vega_s96.dtb ​from dtb directory and renamed it to dtb.img 2. I will wait for a final version to be installed on the eMMC. 3. Is there a procedure to enable GPU hardware acceleration ?
  4. Reboot from USB and connect with ssh ┌root@t95zplus: [23:02] ~ └ lsblk -o name,mountpoint,label,size,uuid,model NAME MOUNTPOINT LABEL SIZE UUID MODEL sda 14.9G SD Transcend ├─sda1 /boot BOOT 96M 0866-6F26 └─sda2 / ROOTFS 14.7G efbd7497-b0c0-416d-9e37-eaad1e6c6585 mmcblk0rpmb 4M mmcblk0boot0 4M mmcblk0boot1 4M mmcblk0 14.6G hum... ┌root@t95zplus: [23:08] ~ └ fdisk -l /dev/data Disk /dev/data: 11.7 GiB, 12551454720 bytes, 24514560 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 ┌root@t95zplus: [23:11] ~ └ mount -o rw /dev/data /mnt/data mount: /dev/data is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/data, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. ┌root@t95zplus: [23:23] ~ └ dmesg @qualcomm.com>@linux.it> ┌root@t95zplus: [23:24] ~ └ mount -o rw /dev/data /mnt/data mount: /dev/data is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/data, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. ┌root@t95zplus: [23:24] ~ └ dmesg | tail -5 [ 105.933418] dhd_open: Exit ret=0 [ 106.090216] P2P interface registered [ 106.171043] P2P interface started [ 641.098175] UDF-fs: warning (device mmcblk0p14): udf_fill_super: No partition found (2) [ 829.274512] UDF-fs: warning (device mmcblk0p14): udf_fill_super: No partition found (2) ┌root@t95zplus: [23:46] ~ └ lsmod Module Size Used by fuse 77241 3 dhd 709627 0 brcmfmac 167978 0 brcmutil 4979 1 brcmfmac cfg80211 402427 2 dhd,brcmfmac joydev 10328 0 rtc_hym8563 5856 0 aml_nftl_dev 82724 0 wifi_dummy 814 0 autofs4 24757 2 ┌root@t95zplus: [23:50] ~ └ cpufreq-info ┌root@t95zplus: [23:53] ~ └ ./aml_cpu.sh performance --2017-02-06 23:56:13-- http://www.phoronix-test-suite.com/benchmark-files/c-ray-1.1.tar.gz Resolving www.phoronix-test-suite.com (www.phoronix-test-suite.com)... 23.111.154.110 Connecting to www.phoronix-test-suite.com (www.phoronix-test-suite.com)|23.111.154.110|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 231074 (226K) [application/x-gzip] Saving to: ‘c-ray-1.1.tar.gz.1’ c-ray-1.1.tar.gz.1 100%[============================================================>] 225.66K 403KB/s in 0.6s 2017-02-06 23:56:14 (403 KB/s) - ‘c-ray-1.1.tar.gz.1’ saved [231074/231074] c-ray-mt v1.1 Rendering took: 4 seconds (4884 milliseconds)
  5. Hi balbes150, Because I am crazy, my first move after renaming the device to tz95plus was to install to eMMC: this took something like 5 minutes: root@t95zplus:~# ./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:24 2015 e2fsck 1.42.13 (17-May-2015) /dev/data: clean, 11/799680 files, 90770/3195392 blocks done. Copying ROOTFS. Copy BIN Create BOOT Copy DEV Copy ETC Copy HOME Copy LIB Copy MEDIA Copy MNT Copy OPT Create PROC Copy ROOT Create RUN Copy SBIN Copy SRV Create SYS Create TMP Copy USR Copy VAR Copy fstab amlogics905x_init.sh ******************************************* Done copy ROOTFS ******************************************* Writing kernel image... done. Writing device tree image... done. Write env bootargs ******************************************* Complete copy OS to eMMC parted DATA ******************************************* root@t95zplus:~# shutdown now removed usb stick unplug/plug power Boot messages appear then stuck at "Begin: Running /scripts/local-block done ...": I hit Enter several time and accessed BuzyBox v1.22.1 Begin: Waiting for root file system done ... Begin: Running /scripts/local-block done ... Begin: Running /scripts/local-block done ... (...) Begin: Running /scripts/local-block done ... Begin: Running /scripts/local-block done ... Begin: Running /scripts/local-block done ...Begin: Running /scripts/local-block done ... Gave up wating for root device. Common problems: -Boot args (cat /proc/cmdline) -Check rootdelay= (did the system wait long enough?) -Check root= (did the system wait for right device?) -Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/data does not exist. Dropping to a shell! However, /dev/data does exist: (initramfs) ls -l /dev/data brw------- 1 179, 14 /dev/data
  6. Hi Stoman, As suggested, I have installed Armbian_5.24_S9xxx_mate_Ubuntu_xenial_3.14.29_desktop_20170205.img on micro sd card. Copied vega_s96.dtb ​from dtb directory and renamed it to boot.img dtb.img Booted from USB stick with micro sd card. Waited a bit... Yes! I confirm I am able to boot from USB: Hurray !
  7. You mean: you want this result from the Mini m8s II running LibreElec ? minis8ii:/lib/firmware/RTL8192E # fw_printenv EnableSelinux=enforcing aml_dt=gxl_p212_2g baudrate=115200 bootcmd=run start_autoscript;run storeboot; bootdelay=1 bootfromnand=0 bootfromrecovery=0 cmdline_keys=if keyman init 0x1234; then if keyman read usid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;if keyman read mac ${loadaddr} str; then setenv bootargs ${bootargs} mac=${mac} androidboot.mac=${mac};fi;if keyman read deviceid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.deviceid=${deviceid};fi;fi; cvbs_drv=0 cvbsmode=576cvbs display_bpp=24 display_color_bg=0 display_color_fg=0xffff display_color_index=24 display_height=1080 display_layer=osd1 display_width=1920 dtb_mem_addr=0x1000000 ethaddr=00:15:18:01:81:31 factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; if test ${wipe_cache} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; fb_addr=0x3d800000 fb_height=1080 fb_width=1920 fdt_high=0x20000000 firstboot=1 gatewayip=10.18.9.1 hdmimode=1080p60hz hostname=arm_gxbb init_display=osd open;osd clear;imgread pic logo bootup $loadaddr;bmp display $bootup_offset;bmp scale initargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 ipaddr=10.18.9.97 jtag=apee loadaddr=1080000 netmask=255.255.255.0 outputmode=1080p60hz preboot=run factory_reset_poweroff_protect;run upgrade_check;run init_display;run storeargs;run upgrade_key;run switch_bootmode; recovery_from_flash=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if imgread kernel ${recovery_part} ${loadaddr} ${recovery_offset}; then wipeisb; bootm ${loadaddr}; fi recovery_from_sdcard=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload mmc 0 ${loadaddr} recovery.img; then if fatload mmc 0 ${dtb_mem_addr} dtb.img; then echo sd dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi; recovery_from_udisk=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if fatload usb 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload usb 0 ${loadaddr} recovery.img; then if fatload usb 0 ${dtb_mem_addr} dtb.img; then echo udisk dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi; recovery_offset=0 recovery_part=recovery sdc_burning=sdc_burn ${sdcburncfg} sdcburncfg=aml_sdc_burn.ini serverip=10.18.9.113 start_autoscript=if usb start ; then run start_usb_autoscript;fi;if mmcinfo; then run start_mmc_autoscript;fi; start_mmc_autoscript=if fatload mmc 0 1020000 s905_autoscript; then autoscr 1020000; fi start_usb_autoscript=if fatload usb 0 1020000 s905_autoscript; then autoscr 1020000; fi storeargs=setenv bootargs ${initargs} androidboot.selinux=${EnableSelinux} logo=${display_layer},loaded,${fb_addr},${outputmode} maxcpus=${maxcpus} vout=${outputmode},enable hdmimode=${hdmimode} cvbsmode=${cvbsmode} hdmitx=${cecconfig} cvbsdrv=${cvbs_drv} androidboot.firstboot=${firstboot} jtag=${jtag}; setenv bootargs ${bootargs} androidboot.hardware=amlogic;run cmdline_keys; storeboot=if imgread kernel boot ${loadaddr}; then bootm ${loadaddr}; fi;run update; switch_bootmode=get_rebootmode;if test ${reboot_mode} = factory_reset; then run recovery_from_flash;else if test ${reboot_mode} = update; then run update;else if test ${reboot_mode} = cold_boot; then fi;fi;fi; try_auto_burn=update 700 750; update=run usb_burning; run sdc_burning; if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash; upgrade_check=echo upgrade_step=${upgrade_step}; if itest ${upgrade_step} == 3; then run init_display; run storeargs; run update;else fi; upgrade_key=saradc open 0; if saradc get_in_range 0x0 0x50; then echo detect upgrade key; run update; fi; upgrade_step=2 usb_burning=update 1000 wipe_cache=successful wipe_data=successful
  8. Hi Balbes, I accidently made the following test: - exrtact /lib/firmware/RTL8192E/boot.img from libreelec runing from another device: Mini m8s II - Renamed this file to dtb.img (zipped and attached to this post as "dtb_LibreElec_MiniM8sII.zip") - Use this attached dtb.img with your Armbian image RESULTS: T95Z boot logo appears and then black screen ... Then "boot" appears on LCD... and then mouse icon which I can move appears on HDMI. Also, I can ping the device (but no ssh) ssh rrot@192.168.10.95 ssh: connect to host 192.168.10.95 port 22: Connection refused Any idea what to try next ? Thanks. dtb_LibreElec_MiniM8sII.zip
  9. Same behavior: T95Z boot logo appears and then black screen.
  10. Hi balbes, - I have downloaded your attached file "t95zplus.dtb" tz95plus.dtb: Device Tree Blob version 17, size=41699, boot CPU=0, string block size=3307, DT structure block size=38336 - I have renamed "tz95plus.dtb" to "dtb.img" Test 1: Armbian_5.24_Amlogic-s905x_Ubuntu_xenial_3.14.29_desktop_20170127 image - I have copied this "dtb.img" to the FAT partition ( named 'BOOT' ) of sdcard image - Inserted SD Card and plug power cord to boot the TZ95Plus device RESULTS: T95Z boot logo appears and then black screen. (waited 7min) Test 2: S9xxx_4G_ICEWM_MATE_XFCE_LXDE_LXQT_20170122 image - I have copied this "dtb.img" to the FAT partition ( named 'BOOT' ) of sdcard image - Inserted SD Card and plug power cord to boot the TZ95Plus device: RESULTS: T95Z boot logo appears and then black screen. (waited 7min) Test 3: Armbian_5.24_Amlogic-s905x_Ubuntu_xenial_3.14.29_desktop_20170118.img image - I have copied this "dtb.img" to the FAT partition ( named 'BOOT' ) of sdcard image - Inserted SD Card and plug power cord to boot the TZ95Plus device RESULTS: T95Z boot logo appears and then black screen. (waited 7min) Are my steps correct ? Is there any more test/action I can perform ? Thanks for your help.
  11. I have tried to boot following images from SD Card - Armbian_5.24_Amlogic-s905x_Ubuntu_xenial_3.14.29_desktop_20170127 - S9xxx_4G_ICEWM_MATE_XFCE_LXDE_LXQT_20170122 Result: HDMI screen remains black. My understanding is that a dtb.img specific to T95Z Plus device must be copied to the FAT partition. I have managed to copy /dev/block/boot from T95Z Plus Android directory and renamed it to boot.img (zipped and attached to this post as boot.img.tz95plus.zip) Then I have downloaded split_bootimg.pl and used it with this boot.img ./split_bootimg.pl boot.img Page size: 2048 (0x00000800) Kernel size: 7419928 (0x00713818) Ramdisk size: 917780 (0x000e0114) Second size: 41699 (0x0000a2e3) Board name: Command line: Writing boot.img-kernel ... complete. Writing boot.img-ramdisk.gz ... complete. Writing boot.img-second.gz ... complete. I got these files: boot.img: Android bootimg, kernel (0x1080000), ramdisk (0x1000000), second stage (0xf00000), page size: 2048 boot.img-kernel: gzip compressed data, max compression, from Unix boot.img-ramdisk.gz: gzip compressed data, from Unix boot.img-second.gz: Device Tree Blob version 17, size=41699, boot CPU=0, string block size=3307, DT structure block size=38336 Then, result of hexdump -C -v boot.img-second.gz | grep "d0 0d fe ed" is 00000000 d0 0d fe ed 00 00 a2 e3 00 00 00 38 00 00 95 f8 |...........8....| How can I get the dtb.img from this point ? Also, I ran dtc -I dtb boot.img-second.gz -O dts -o tz95plus.dtd I got this file: tz95plus.dtd: ASCII text (zipped and attached to this post as tz95plus.dtd.zip) boot.img.tz95plus.zip tz95plus.dtd.zip
  12. Hi , My device is a "MINI M8S II" and I am using "Armbian_5.24_Amlogic-s905x_Ubuntu_xenial_3.14.29_desktop_20170118.img". I have no audio output on HDMI. I am open to use "Armbian_5.24_Amlogic-s905x_Debian_jessie_3.14.29_20170118.img" if the issue can be solved By any chance, can you share your new kernel for download with the modules enabled for this device ? Thank you.