rampagepi

Members
  • Content Count

    4
  • Joined

  1. Cool. The first floor in this topic mentioned both universal multi-boot is required and uEnv.ini, it's a bit confusing. Maybe this part should be removed or commented out? I read your topic about activate universal multi-boot again, However my tv box's Android is corrupted, it won't boot or restored or recovered. So option A is not for me. Tried option B, but it won't boot with the new build on the MicroSD card.
  2. Actually I've tried both FDT=/dtb/amlogic/meson-gxm-khadas-vim2.dtb and dtb_name=/dtb/amlogic/meson-gxm-khadas-vim2.dtb in uEnv.ini with the new build, but it won't boot. So what should it be?
  3. How do I config this build to run from MicroSD card on H96 Pro Plus? The old version I had runs fine, but this new build won't boot by default. Old version uEnv.ini dtb_name=/dtb/meson-gxm-khadas-vim2.dtb bootargs=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 Old version extlinux.conf LABEL Armbian LINUX /zImage INITRD /uInitrd FDTDIR /dtb # FDT /dtb/meson-gxm-khadas-vim2.dtb APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 With this new build, for the uEnv.ini it is # aml s9xxx FDT=/dtb/amlogic/meson-g12b-odroid-n2.dtb APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
  4. Hi, How do I flash this image to a MicroSD card? With previous armbian image, after flashing I have a BOOT partition for me to edit the uEnv.ini but with this image Armbian_20.02.0-rc1.037_Aml-s9xxx_bionic_current_5.5.0-rc6_20200205.img.xz after flashing using balenaEtcher or Rufus, I can't seem to find the BOOT partition? Thanks. Edit: Ok, the image needs to be unpacked first and use Rufus. balenaEtcher doesn't work