ycomp

I popped the sdcard back in (that has ubuntu w/mate), and it managed to boot up off that. Now I wonder if the script actually worked because lsblk doesn't seem to show any partitions for mmcblk0 I have working dtb.img and linux.img at /BOOT What I meant about my question before about the 64GB sdcard was that emmc is 32, ROOTFS partition on the SD card is almost twice that - could that cause problems? I re-ran the install script now, basically I have no error messages except for a bunch of var/lib/samba (sic) : socket ignored When I reboot it now it goes to the android robot screen. Is that supposed to happen? (I removed the sd card)

I ran the script as suggested, everything seemed to go fine - no error messages that I noticed (although I wasn't watching it the whole time). Then I removed my sd card and rebotted and it went to the android recovery screen. I chose reboot now and it booted back into the android recovery screen. So I chose boot to bootloader, and then the H96 logo just comes on and stays there. Anyone know what I should do now? p.s. was it a mistake to run the install script from a 64GB microsd card (it's the ubuntu mate armbian image installed on there)? I was thinking that wouldn't matter. But I'm not very good with linux. (BOOT 128MB, ROOTFS 59GB)

Could someone explain how to install ubuntu on the built in eMMC memory? I have tried both the mate and server 16.04 images from the freaktab thread, on sd card. And they work (except wifi) But I'd like to run the OS directly from the built in memory. I don't care about overwriting Android

has anyone been able to get ZFS to work on an S912 armbian? How can I get ethernet to work with OpenSUSE or Archlinux? (would ZFS work on those?) Does anyone know if ZFS works on other S9xx boxes?