• Content Count

  • Joined

  • Last visited

  1. you can try . 3.14 with /root/ command, 4.18 with 1. Execute script “/boot/” 2. Execute script “/root/” and see if that works
  2. according to balbes150 who creates those beautiful images, the installation to emmc on the kernel 4.xx looks like this: 1. Execute script “/boot/” 2. install Armbian on eMMC execute script “/root/”. I did this and it worked just fine
  3. install something like stress-ng and check if all 4 cores are working for instance with htop - or just run htop and wait, usually the load is distributed among all cores randomly even if system is idle - if they do work, who cares what system information is showing P. S. or just save your time - you do have 4 cores. I just looked at my s912 that has 8 cores and armbian shows the load for only 3 of them after login
  4. how do you know, that you have only 3? what the command lscpu shows?
  5. it is s905x, it should have gxl and/or p212 in name and 2gb as ram amount if there multiple dtb files for gxl_p212
  6. Oh no pal, of course it is not ok. You should always rename it to dtb.img - that explains why 3.14 worked. It just took dtb from android on emmc and it did work because android on this box has same 3.14 kernel
  7. connect via ethernet, find out the ip on your router - they usually have device list, connect from different machine via ssh and do what you want to do (first registration, wifi setup, etc)
  8. 100% because I could not find working dtb for 3.14 . But, now after googling a bit, I think we have different models - I have H96 Pro without + and in spite of same specs it looks slightly different than yours, so maybe that's why. Does yours have 1000M Ethernet or 100M? As far as I know all s912 with 1000M fall under gxm-q200 category, and all 100M should be gxm-q201
  9. that is the hardest of them all - normally you don't need this, but congratulations anyway
  10. many boxes get recognized only when you plug usb cable to specific usb port and some only as soon as you press reset button (it is often hidden in AV-output or just looks like a hole in the case). it is very hard (or almost impossible) to kill s905/s912 so just keep trying
  11. meson-gxm-q200.dtb works for me, but only with ubuntu xenial headless. I could not boot ubuntu bionic headless with it. I also didn't try distributions with desktop
  12. I'm experiencing problem installing Armbian 5.59 / 4.18 based on Ubuntu Bionic on my H96 Pro (s912 3/16) using (presumably correct) gxm_q200 dtb from image - amlogic logo goes away after some time and then appears again in endless loop. Strange thing is that the same 5.59 / 4.18 based on xenial with the same dtb boots just fine. Not a big deal since xenial is also ok for me too
  13. that did the job, besides that I noticed that my box seems to boot from usb only on usb-port 1 but I didn't investigate further. regarding installation to emmc I used older deb files from yandex disc to downgrade and used one of older dtbs - that did help
  14. I could, but the problem is that I've already installed, configured and tested everything on a usb stick, hoping to move the system to emmc after that - repeating all of this would be really a last resort for me...unless there is an easy way to downgrade to 3.14.29
  15. thank you, I'll give it a try. I also have a problem installing the system to the emmc - /dev/boot and /dev/data do not exist (I did flash a fresh android rom to emmc before trying this) /usr/sbin/fw_setenv initargs "root=/dev/data rootflags=data=writeback rw console=ttyS0,115200n8 console=tty0 no_console_suspend consoleblank=0 net.ifnames=0 mac=\${mac}" fails as well with message Cannot parse config file '/etc/fw_env.config': Invalid argument Can this be a problem with dtb-s for the last 905 ubuntu build with kernel 3.14.79? Installation to the emmc DID work on the previous ubuntu and debian builds with kernel 3.14.29 - so it is not about my box having some exotic emmc structure (actually it is a full clone of vega s95 pro)