Jump to content

FrizzleFry

Validating
  • Posts

    2
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Looks like i was lucky and my bootloader ist still functional. With the suggested dtb, i was getting stuck on "starting kernel" I assume this dtb is no good for regular x96 (without suffix) ? However meson-gxl-s905x-p212.dtb seemed to work so far, thernet and wifi both work out of the box, so i assumed its good to use. I followed your link and followed balbes150's advice on how to start the mmc script su - ./install-aml.sh The part that still confuses me is "u-boot.sd" So far, what i did was to rename the u-boot-s905x-912, that i found on my SD card after burning the image, to u-boot.ext (follwing OP from this post) Where is u-boot.sdsupposed to come from? Anyways, i reburned the image to my SD card, sucessfully booted from that, installed to eMMC (without any Errors) but boooting wirthout SD still looks like in my first post.
  2. Hello there! after some tinkering i finally managed to boot Armbian_20.09_Arm-64_buster_current_5.8.10 from SD on my X96 box, using meson-gxl-s905x-p212.dtb Now i want to install to eMMC and i learned that sudo /root/install-aml.sh should take care of that. From what i understand i also need to copy u-boot.ext and name it u-boot.sd (although im not sure if that applies to my situation) After doing those steps and booting with sd card removed, i am getting the following: I tried to search for answers, but i'm completely lost. I dont have a lot of linux experience, let alone armbian. If someone could point me in the right direction, that would be very much appreciated. Cheers!
×
×
  • Create New...