damienq

Members
  • Content Count

    4
  • Joined

  • Last visited

  1. Only different versions of Ubuntu Server. On kernel 4.16, it can't see the emmc at all, but from a Balbes150 post I read, I think emmc install doesn't work on 4.16. On kernel 3.x, it all works fine, including emmc install.
  2. Sorry about that. Here is the output of "parted print list,all" (It's ubuntu server so there is no gui) Model: SanDisk Cruzer (scsi) Disk /dev/sda: 125GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 4194kB 138MB 134MB primary fat16 lba 2 138MB 124GB 124GB primary ext4 Error: /dev/mmcblk0rpmb: unrecognised disk label Warning: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error Retry/Ignore? ignore Model: Generic SD/MMC Storage Card (sd/mmc) Disk /dev/mmcblk0rpmb: 4194kB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags: Error: /dev/mmcblk0boot0: unrecognised disk label Model: Generic SD/MMC Storage Card (sd/mmc) Disk /dev/mmcblk0boot0: 4194kB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags: Error: /dev/mmcblk0boot1: unrecognised disk label Model: Generic SD/MMC Storage Card (sd/mmc) Disk /dev/mmcblk0boot1: 4194kB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags: Error: /dev/mmcblk0: unrecognised disk label Model: MMC AWPD3R (sd/mmc) Disk /dev/mmcblk0: 15.6GB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags:
  3. If by internal partition you mean the the emmc blocks, then yes. This is the output of "fdisk -l" Disk /dev/sda: 116.9 GiB, 125460021248 bytes, 245039104 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: 0x2bba5da7 Device Boot Start End Sectors Size Id Type /dev/sda1 8192 270335 262144 128M e W95 FAT16 (LBA) //// This is the usb stick used to boot /dev/sda2 270336 242588703 242318368 115.6G 83 Linux Disk /dev/mmcblk0: 14.6 GiB, 15634268160 bytes, 30535680 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 Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 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 Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 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
  4. Greetings. I have two issues, and I would be equally grateful if either could be solved: 1) I have a T95Z Plus with an s912. I'm running Balbes150's Ubuntu Server 16.04 kernel 4.9. After boot, the system is able to recognize the emmc, and /dev/data exists, but when I run the install.sh script, when it gets to "copy USR", it starts to hit a bunch of segmentation faults and a few bus errors, and eventually the system freezes up and I have to reboot. I'm using the gml_q200_2g.dtb from the dtb folder. 2) I have an X96 Mini with an s905W, running the same image as above. The system cannot at all recognize the emmc, and /dev/data does not exist. The output of "fdisk -l", "lsblk", and "ls -al /dev/block" all only recognize the boot device (my usb drive). I'm using gmx_231_1g.dtb from the dtb folder. I'm aware that it isn't the correct dtb file, but strangely it is the only one that will boot. I have extracted the dtb from firmware but it didn't work. Bonus Issue) On the T95Z Plus (the first one), right from boot, the video output stops, and does not come back. I used an hdmi to dvi adapter on my monitor. It isn't a big issue because I'm able to ssh to it, but if anyone has a solution it would be appreciated.