Search the Community

I am Running Armbian_5.67_Aml-s9xxx_Ubuntu_bionic_default_4.19.7_desktop_20181218 on an MAGICSEE N4 TV Box (meson-gxl-s905x-p212.dtb) The box runs quite fine, i am very impressed. Thanks a lot for your work. I am struggling to change the resolution of the HDMI out. on my full HD screen it runs fine, but i want tu run it on my 1024x768 screen via an DVI Adapter. Can't find the hdmi.sh script mentioned on the first page. Thanks a lot Johannes

Hello I am new at the forum. My english is not good but i can understand all :) I have a Magicsse n5 android box (S905X) and i like to install Armbian on it (on a micro sd card) I have done everything in the manual but I'm only assigned to the user and assigned root and then linux should start. But it does not do it, it only flashes in the top left of an arrow. I tried it with this file "meson-gxl-s905x-p212.dtb" but it does not work .... Do you have any idea why it is not working? Thank you :)

Hi Balbes150 and All, Thank you very much for your hard work and what you are providing for free to the community! It's my first post and I have a question. Have been running the latest build (Armbian_20.10_Arm-64_bionic_current_5.9.0.img) from eMMC, on couple of my boxes here (AMlogic S905X meson-gxl-s905x-p212.dtb) and it is very stable. LAN, WiFi, IR, HDMI with audio, all work great without any additional work! THANKS :-) But there is one feature that I need badly that doesn't work for me: Sound from the analog AV port. For now I have a cheap audio USB dongle plugged in but I'd rather use the onboard audio card if I can (I am making a battery operated internet radio). I run sound.sh but that did not solve the problem. Any help very much appreciated! Best regards, franck

Hi SteeMan. Unfortunately I could not answer before than 24h from my last message because of the forum restrictions. About your question: I just followed the thread I mentioned before. It means: I downloaded armbian bionic 20.10 from the repository linked in the thread I flashed it through balenaEtcher on my 64GB sd card. I renamed the correct e-boot-S905xxx file to e-boot.ext I edited /extlinux/extlinux.conf commented all the lines but FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb and APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0... Then I started the android box and manually update its firmware by selecting aml_autoscript.zip from the sd card The box restarted a couple of times, then I set the root password and that's all. After a couple of failed attempts to start a desktop manager I accidentaly run the install-am.sh script which might have overridden the MBR and now I no longer can access android even with sd card removed. Regards.

Hi, don't know if it might help, because I have a TX3 Mini with a 1.2 board, but if yours can dualboot stock Android (Alice UX) and LibreELEC, like mine does, then perhaps they are similar enough. On mine, pressing the reset button does nothing either, in order to boot from SD card I have to: -boot on the stock Android first; -open the upgrade & backup app; -press on select an upgrade package; At this point a menu will pop-up and after a brief search the app should find, on the SD card, an "aml_autoscript.zip" file, which I guess is a package the image creator has made in order to trick the upgrade app into thinking that the Armbian image is an upgrade package, but anyway, select it; -press the upgrade button; The app ask if you're sure, would you like to make a backup first, yada yada, click ok and it should reboot for the firmware upgrade; On reboot, instead of the firmware upgrade that Android expected, you should have Armian booting, no need to press buttons or anything, just click reboot and wait to be prompted to input a username and password. Since I have no wi-fi (my TX3 has the dreaded SV6051P SDiO Wi-Fi and BT chip) and since many around the forums claim that they fixed it by changing their dtb, I have tested several dtbs: meson-gxl-s905w-tx3-mini.dtb meson-gxl-s905x-p212.dtb meson-gxl-s905w-p281.dtb meson-gxl-s905x-nexbox-a95x.dtb All of them worked, meaning that I could boot into Armbian no matter which one of them I used, but I noticed that audio through HDMI works on the s905w ones and not on the s905x ones (sometimes I had no HDMI audio on s905w either, just try reflashing the SD card if that happens). None of them fixed the Wi-Fi, none of them had hw acceleration for videos (meaning that video playback relies on CPU and it sucks), no IR remote, no VFD, no audio from the AV jack, but that was to be expected. Since we're on the subject, I wanted to ask SteeMan (the man who owns 4 TX3s, with different board revisions) if he managed to get the Wi-Fi to work on any of them and if yes, on which ones. But anyway, yeah, let me know if that works.

Hi All, I've been trying to run Armbian on Minix for the past 2 days with no luck. I did the following: - dowloaded the image Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz and unpacked it - copied it to SDCARD using dd - modified extlinux.conf uncommenting this line: #FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb - I uncommented #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 - I renamed u-boot-s905x2-s922 to u-boot.ext - run the update selecting aml_autoscript.zip After reboot the dreadful image of Android opened show up with massively verbose message: Error I tried toothpick method, with the same luck. I was able to run Coreelec from SD card without any issues for the past few months now so my SD card seems to be fine. Any help is appreciated

Are there any other changes besides the different dtb method? On my mecool m8s pro +, these do not boot with /dtb-4.19.0-rc7-aml-s9xxx/meson-gxl-s905x-p212.dtb . The old 3.14 kernel versions do work, but no amcodec support. How to get HW playback? Any suggestions?

I got 3.14 Armbian, I Installed it on sdcard and it boot with the gxl-s905x-p212.dtb file rename in dtb.img. after password change , I run ./install.sh without any strange message but when I reboot without the sdcard the screen is frozen on the boot logo. Any ideas of what could be wrong ? It reboot correctly from the sdcard. thanks for help gérard

Hi, Armbian_5.44_S9xxx_Debian_stretch_4.16.1_server doesn't want to boot (stuck in the MeCool logo.) no matter what .dtb renamed (dtb.img) i use... gxl_p212_2g.dtb : NOK meson-gxl-s905x-p212.dtb : NOK Board : MeCool S905x(p212). Does anyone could have a solution please ?

@SteeMan Thanks for your quick response! In the past i had a armbian ubuntu running wich was at some point no longer maintained. I then made an attempt to replace it with a newer armbian image but i didnt succeed and put my efforts on hold until now, because now i have a more pressing reason to have an armbian box to run things on. From reading through your comments and balbes original instruction i understand that its recommended to start from the X96 Max stock image thus i installed "X96 MAX 20181219.img" via amlogic usb burn tool , i found the image via googling for "x96 max stock firmware" but the site i downloaded it from wasnt the official manufacturers support site or something. I understand that @balbes150 builds do not support S905x2 (thus X96 Max) from any release newer that 14. Okt. 2020 (thus i tested 2 images: Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz and Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img.xz wich is dated as released on 14. Okt. ) After writing the image on a microsd via USBImager.exe i did the following modifications: 1. rename "u-boot-s905x2-s922" into "u-boot-s905x2-s922.ext" 2. go to extlinux/extlinux.conf and remove the "#" from "#FDT /dtb/amlogic/meson-g12a-x96-max.dtb" and the "#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" [edit] sorry i missed to add # in front of the unwanted dbt line but it still doesnt work extlinux.conf now looks like this: LABEL Armbian LINUX /zImage INITRD /uInitrd # rk-3399 #FDT /dtb/rockchip/rk3399-rock-pi-4.dtb #FDT /dtb/rockchip/rk3399-nanopc-t4.dtb #FDT /dtb/rockchip/rk3399-roc-pc-mezzanine.dtb #APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 # rk-3328 #FDT /dtb/rockchip/rk3328-roc-pc.dtb #FDT /dtb/rockchip/rk3328-box-trn9.dtb #FDT /dtb/rockchip/rk3328-box.dtb #APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 # aw h6 #FDT /dtb/allwinner/sun50i-h6-tanix-tx6.dtb #APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 video=HDMI-A-1:e #APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 mem=2048M video=HDMI-A-1:e # aml s9xxx #FDT /dtb/amlogic/meson-gxbb-p200.dtb #FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb #FDT /dtb/amlogic/meson-gxm-q200.dtb FDT /dtb/amlogic/meson-g12a-x96-max.dtb #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 unfortunately it still doesnt work either via android updater or toothpick. Am i missing something or do i maybe need another x96 max stock firmware to start off with? OK I FOUND THE ERROR (sorry for stealing your time i have adhd and a gazillion tabs open wich caused me missing something) Instead of renaming "u-boot-s905x2-s922" into "u-boot.ext" i renamed it into "u-boot-s905x2-s922.ext" not i renamed it into "u-boot.ext" and its installing armbian ubuntu!

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.

Issue solved (primitively but effectively) I have simply replaced the Armbian_23.11.1 meson-gxl-s905x-p212.dtb file in boot/dtb/amlogic with the same file from Armbian_20.10. A new "Built-in audio stereo" soundcard has appeared in the Volume Control window. Its port is labeled "Analog Output" but, in fact, it works on HDMI. I believe that the old and new dtb files are very similar but the Armbian_23.11.1 has dropped support for whatever version of the soundcard I have. This is not so surprising given that my YUNDOO Y6 was probably made in 2014-2015.

Thanks for the quick answer The box is a MXQ PRO + which has a S905X 1.5ghz mira-450-GPU 10/100 mb/s ethernet wifi 2.4/5 ghz 2Gb RAm and 16 Gb emmc. 4 USB , 1SD card port HDMI and sound port. WiFi chip is a strange hs.... unknown I used this code : Armbian_5.44_S9xxx_Debian_stretch_4.16.1_server_20180515.img.xz and a DTB file : meson-gxl-s905x-p212.dtb Gérard

Great @thielj - USB "extlinux" folder: Update extlinux.conf: "FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb" - USB root folder: Copy "u-boot-s905x-s912" to "u-boot.ext" - Create in USB device a zero byte file called "vazio.zip" ("empty" in portuguese) - In tv-box Android, open Update App and select above zip file and "update" On next boot, Armbian (bookworm) will start at USB device succesfully. THANK YOU

Hi, After running armbian-install on S905x device it stopped booting. USB Burning Tool doesn't recognize the device, nothing. After connecting to UART it looks like install script has overwritten the original u-boot. That's the boot log from UART connection without sd card: GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 104174 BL2 Built : 11:58:42, May 27 2017. gxl gc3c9a84 - xiaobo.gu@droid05 set vcck to 1120 mv set vddee to 1000 mv Board ID = 1 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 912MHz - PASS Rank0: 1024MB(auto)-2T-13 Rank1: 1024MB(auto)-2T-13 DataBus test pass! AddrBus test pass! -s Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000 New fip structure! Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600 Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400 Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x000af000 NOTICE: BL3-1: v1.0(release):3348978 NOTICE: BL3-1: Built : 15:44:01, May 12 2017 [BL31]: GXL CPU setup! mpu_config_enable:ok [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07] OPS=0x82 8f bb f0 da ba 22 d2 cf 1 b0 31 f4 [0.359461 Inits done] secure task start! high task start! low task start! ERROR: Error initializing runtime service opteed_fast <debug_uart> U-Boot 2022.07-armbian (Nov 25 2023 - 12:50:42 +0000) libretech-cc Model: Libre Computer AML-S905X-CC SoC: Amlogic Meson GXL (S905X) Revision 21:b (82:2) DRAM: 2 GiB Core: 169 devices, 27 uclasses, devicetree: separate MMC: mmc@72000: 0, mmc@74000: 1 Loading Environment from nowhere... OK In: serial Out: serial Err: serial [BL31]: tee size: 0 [BL31]: tee size: 0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1: Armbian Retrieving file: /uInitrd ** File not found /uInitrd ** Skipping Armbian for failure retrieving initrd SCRIPT FAILED: continuing... Found U-Boot script /boot/boot.scr 8147 bytes read in 1 ms (7.8 MiB/s) ## Executing script at 08000000 U-boot default fdtfile: amlogic/meson-gxl-s905x-libretech-cc.dtb Current variant: Current fdtfile after armbianEnv: amlogic/meson-gxl-s905x-libretech-cc.dtb Mainline bootargs: root=/dev/mmcblk1p1 rootwait rootfstype=ext4 splash=verbose c onsole=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ub ootpart=d27dbd06-01 libata.force=noncq usb-storage.quirks= cgroup_enable=memo ry swapaccount=1 22783841 bytes read in 500 ms (43.5 MiB/s) 27433472 bytes read in 601 ms (43.5 MiB/s) 40228 bytes read in 4 ms (9.6 MiB/s) Failed to load '/boot/dtb/amlogic/overlay/-fixup.scr' ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 22783777 Bytes = 21.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7a982000, end 7bf3c721 ... OK Loading Device Tree to 000000007a90f000, end 000000007a981fff ... OK "Synchronous Abort" handler, esr 0x96000004 elr: 00000000010656ec lr : 0000000001055038 (reloc) elr: 000000007dfb46ec lr : 000000007dfa4038 x0 : e14b4287a666c25d x1 : 000000007dfbc290 x2 : 0000000000000010 x3 : 000000007bf54e10 x4 : 0000000000000000 x5 : e14b4287a666c25d x6 : 0000000001000000 x7 : 0000000000000000 x8 : 0000000000000007 x9 : 0000000000000000 x10: 0000000000000178 x11: 000000007bf40eec x12: 00000000000000a4 x13: 000000007bf40ea8 x14: 000000007a90f000 x15: 0000000000000020 x16: 000000007df5946c x17: 0000000000000000 x18: 000000007bf4cdb0 x19: 000000007af41040 x20: 000000007df4fb18 x21: 000000007dfbc290 x22: 0000000000001000 x23: 000000007bf54d60 x24: 000000007dfdacb8 x25: 0000000001000000 x26: 0000000000000000 x27: 0000000001000000 x28: 0000000000001000 x29: 000000007bf40ea0 Code: eb04005f 54000061 52800000 14000006 (386468a3) Resetting CPU ... resetting ... bl31 reboot reason: 0xd bl31 reboot reason: 0x0 system cmd 1. And with sd card GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 103545 BL2 Built : 11:58:42, May 27 2017. gxl gc3c9a84 - xiaobo.gu@droid05 set vcck to 1120 mv set vddee to 1000 mv Board ID = 1 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 912MHz - PASS Rank0: 1024MB(auto)-2T-13 Rank1: 1024MB(auto)-2T-13 DataBus test pass! AddrBus test pass! -s Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000 New fip structure! Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600 Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400 Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x000af000 NOTICE: BL3-1: v1.0(release):3348978 NOTICE: BL3-1: Built : 15:44:01, May 12 2017 [BL31]: GXL CPU setup! mpu_config_enable:ok [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07] OPS=0x82 8f bb f0 da ba 22 d2 cf 1 b0 31 f4 [0.358822 Inits done] secure task start! high task start! low task start! ERROR: Error initializing runtime service opteed_fast <debug_uart> U-Boot 2022.07-armbian (Nov 25 2023 - 12:50:42 +0000) libretech-cc Model: Libre Computer AML-S905X-CC SoC: Amlogic Meson GXL (S905X) Revision 21:b (82:2) DRAM: 2 GiB Core: 169 devices, 27 uclasses, devicetree: separate MMC: mmc@72000: 0, mmc@74000: 1 Loading Environment from nowhere... OK In: serial Out: serial Err: serial [BL31]: tee size: 0 [BL31]: tee size: 0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1: Armbian Retrieving file: /uInitrd Retrieving file: /Image append: root=UUID=a6cf29bd-49ae-4d3b-bf22-800408ae1fba rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles Retrieving file: /dtb/amlogic/meson-gxl-s905x-p212.dtb Moving Image from 0x8080000 to 0x8200000, end=9cd0000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 22783777 Bytes = 21.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 08008000 Booting using the fdt blob at 0x8008000 Loading Ramdisk to 7a982000, end 7bf3c721 ... OK Loading Device Tree to 000000007a975000, end 000000007a98169c ... OK "Synchronous Abort" handler, esr 0x96000004 elr: 00000000010656ec lr : 0000000001055038 (reloc) elr: 000000007dfb46ec lr : 000000007dfa4038 x0 : e14b4287a666c25d x1 : 000000007dfbc290 x2 : 0000000000000010 x3 : 000000007bf54e10 x4 : 0000000000000000 x5 : e14b4287a666c25d x6 : 0000000001000000 x7 : 0000000000000000 x8 : 0000000000000007 x9 : 0000000000000000 x10: 0000000000000188 x11: 000000007bf409ec x12: 00000000000000b4 x13: 000000007bf409a8 x14: 000000007a975000 x15: 0000000000000020 x16: 000000007df7a768 x17: 0000000000000000 x18: 000000007bf4cdb0 x19: 000000007af41040 x20: 000000007df4fb18 x21: 000000007dfbc290 x22: 0000000000001000 x23: 000000007bf54d60 x24: 000000007dfdacb8 x25: 0000000001000000 x26: 0000000000000000 x27: 0000000001000000 x28: 0000000000001000 x29: 000000007bf409a0 Code: eb04005f 54000061 52800000 14000006 (386468a3) Resetting CPU ... resetting ... bl31 reboot reason: 0xd bl31 reboot reason: 0x0 system cmd 1. Is there any way to restore original firmware?

So, I got the boot log. It boots to an "emergency"? shell. Give root password for maintenance (or press Control-D to continue): after login I see: root@system:~# uname -a Linux system 5.10.60-meson64 #21.08.1 SMP PREEMPT Wed Aug 25 19:29:40 UTC 2021 aarch64 GNU/Linux I would expect 6.6.16 - no clue why it says 5.10.60, when in /boot/ anything sys 6.6.16. Full boot log follows. So what's wrong here? 😞 G12B:BL:6e7c85:2a3b91;FEAT:E0F83180:402000;POC:F;RCY:0;EMMC:0;READ:0;0. bl2_stage_init 0x01 bl2_stage_init 0x81 hw id: 0x0000 - pwm id 0x01 bl2_stage_init 0xc1 bl2_stage_init 0x02 L0:00000000 L1:00000703 L2:0000c067 L3:14000020 B2:00402000 B1:e0f83180 TE: 180255 BL2 Built : 06:17:13, Jun 28 2019. g12b gf0505d7-dirty - qi.duan@droid13 Board ID = 5 Set A53 clk to 24M Set A73 clk to 24M Set clk81 to 24M A53 clk: 1200 MHz A73 clk: 1200 MHz CLK81: 166.6M smccc: 00030852 eMMC boot @ 0 sw8 s DDR driver_vesion: LPDDR4_PHY_V_0_1_14 build time: Jun 28 2019 06:17:09 board id: 5 Load FIP HDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0 fw parse done Load ddrfw from eMMC, src: 0x00030200, des: 0xfffd0000, size: 0x0000c000, part: 0 Load ddrfw from eMMC, src: 0x0002c200, des: 0xfffd0000, size: 0x00004000, part: 0 PIEI prepare done fastboot data load 00000000 emmc switch 1 ok 00000000 emmc switch 2 ok fastboot data verify verify result: 255 Cfg max: 2, cur: 1. Board id: 255. Force loop cfg DDR4 probe ddr clk to 1320MHz Load ddrfw from eMMC, src: 0x00014200, des: 0xfffd0000, size: 0x0000c000, part: 0 00000000 emmc switch 0 ok Check phy result INFO : End of initialization INFO : End of read enable training INFO : End of fine write leveling INFO : End of read dq deskew training INFO : End of MPR read delay center optimization INFO : End of Write leveling coarse delay INFO : End of write delay center optimization INFO : End of read delay center optimization INFO : End of max read latency training INFO : Training has run successfully! 1D training succeed Load ddrfw from eMMC, src: 0x00020200, des: 0xfffd0000, size: 0x0000c000, part: 0 Check phy result INFO : End of initialization INFO : End of 2D read delay Voltage center optimization INFO : End of 2D write delay Voltage center optimization INFO : Training has run successfully! R0_RxClkDly_Margin==70 ps 6 R0_TxDqDly_Margi==106 ps 9 R1_RxClkDly_Margin==0 ps 0 R1_TxDqDly_Margi==0 ps 0 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0001 2D training succeed auto size-- 65535DDR cs0 size: 2048MB DDR cs1 size: 2048MB DMC_DDR_CTRL: 00600024DDR size: 3928MB cs0 DataBus test pass cs1 DataBus test pass cs0 AddrBus test pass cs1 AddrBus test pass pre test bdlr_100_average==407 bdlr_100_min==407 bdlr_100_max==407 bdlr_100_cur==407 aft test bdlr_100_average==407 bdlr_100_min==407 bdlr_100_max==407 bdlr_100_cur==407 non-sec scramble use zero key ddr scramble enabled 100bdlr_step_size ps== 398 result report boot times 0Enable ddr reg access 00000000 emmc switch 3 ok Authentication key not yet programmed get rpmb counter error 0x00000007 00000000 emmc switch 0 ok Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0 Load BL3X from eMMC, src: 0x0003c200, des: 0x0172c000, size: 0x00099400, part: 0 0.0;M3 CHK:0;cm4_sp_mode 0 E30HDR MVN_1=0x00000000 MVN_2=0x00000000 [Image: g12b_v1.1.3375-8f9c8a7 2019-01-24 10:44:46 guotai.shen@droid11-sz] OPS=0x40 ring efuse init chipver efuse init 29 0c 40 00 01 11 0c 00 00 07 31 33 32 58 33 50 [0.019858 Inits done] secure task start! high task start! low task start! run into bl31 NOTICE: BL31: v1.3(release):ab8811b NOTICE: BL31: Built : 15:03:31, Feb 12 2019 NOTICE: BL31: G12A normal boot! NOTICE: BL31: BL33 decompress pass ERROR: Error initializing runtime service opteed_fast U-Boot 2015.01 (Aug 08 2021 - 16:09:39) DRAM: 3.5 GiB Relocation Offset is: d6eeb000 spi_post_bind(spifc): req_seq = 0 register usb cfg[0][1] = 00000000d7f83db0 MMC: aml_priv->desc_buf = 0x00000000d3edb7c0 aml_priv->desc_buf = 0x00000000d3eddb00 SDIO Port C: 0, SDIO Port B: 1 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x1, tx-dly 0, clock 40000000 aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x2000 [mmc_startup] mmc refix success [mmc_init] mmc init success In: serial Out: serial Err: serial vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters vpu: driver version: v20190313 vpu: detect chip type: 9 vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz) vpu: clk_level = 7 vpu: vpu_power_on vpu: set_vpu_clk vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100) vpu: set_vpu_clk finish vpu: vpu_module_init_config vpp: vpp_init vpp: g12a/b osd1 matrix rgb2yuv .............. vpp: g12a/b osd2 matrix rgb2yuv.............. vpp: g12a/b osd3 matrix rgb2yuv.............. cvbs: cpuid:0x29 cvbs_config_hdmipll_g12a cvbs_set_vid2_clk ** File not found boot-logo.bmp.gz ** ** File not found boot-logo.bmp ** movi: not registered partition name, logo movi - Read/write command from/to SD/MMC for ODROID board Usage: movi <read|write> <partition|sector> <offset> <address> [<length>] - <read|write> the command to access the storage - <offset> the offset from the start of given partiton in lba - <address> the memory address to load/store from/to the storage device - [<length>] the size of the block to read/write in bytes - all parameters must be hexa-decimal only [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]set initrd_high: 0x3d800000 [OSD]fb_addr for logo: 0x3d800000 [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]fb_addr for logo: 0x3d800000 [OSD]VPP_OFIFO_SIZE:0xfff01fff [CANVAS]canvas init [CANVAS]addr=0x3d800000 width=5760, height=2160 cvbs: outputmode[1080p60hz] is invalid vpp: vpp_matrix_update: 2 set hdmitx VIC = 16 config HPLL = 5940000 frac_rate = 1 HPLL: 0x3b3a04f7 HPLL: 0x1b3a04f7 HPLLv1: 0xdb3a04f7 config HPLL done j = 6 vid_clk_div = 1 hdmitx phy setting done hdmitx: set enc for VIC: 16 enc_vpu_bridge_reset[1319] rx version is 1.4 or below div=10 Net: dwmac.ff3f0000 syntax error Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 ## Attempting fetch boot.ini in mmc:0... ** File not found boot.ini ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.scr in mmc:0... ** File not found boot.scr ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.ini in mmc:0... 5579 bytes read in 4 ms (1.3 MiB/s) ## Executing script at 04000000 0 bytes read in 3 ms (0 Bytes/s) Found mainline kernel configuration edid extension block number : 2 Dump EDID Rawdata 000000000000000022f02033010000000a1b010380351e782ac020a656529c27 0f5054a10800d1c0b300a9c095008180810081c00101023a801871382d40582c 45000f282100001e000000fd00323c1e5011000a202020202020000000fc0048 5020323465730a2020202020000000ff0033434d37313031323246202020019f 020319b149901f0413031201021167030c0010000022e2002b023a801871382d 40582c45000f282100001e023a80d072382d40102c45800f282100001e011d00 7251d01e206e2855000f282100001e011d00bc52d01e20b82855400f28210000 1e8c0ad08a20e02d10103e96000f28210000180000000000000000000000000b No header found - count 0 hdmitx: read edid fails.. retry.. edid extension block number : 2 Dump EDID Rawdata 00ffffffffffff0022f02033010000000a1b010380351e782ac020a656529c27 0f5054a10800d1c0b300a9c095008180810081c00101023a801871382d40582c 45000f282100001e000000fd00323c1e5011000a202020202020000000fc0048 5020323465730a2020202020000000ff0033434d37313031323246202020019f 020319b149901f0413031201021167030c0010000022e2002b023a801871382d 40582c45000f282100001e023a80d072382d40102c45800f282100001e011d00 7251d01e206e2855000f282100001e011d00bc52d01e20b82855400f28210000 1e8c0ad08a20e02d10103e96000f28210000180000000000000000000000000b Manufacturer: HWP Model 3320 Serial Number 1 EDID version: 1.3 Established timings supported: 720x400@70Hz 640x480@60Hz 800x600@60Hz 1024x768@60Hz Standard timings supported: 1920x1080@60Hz 1680x1050@60Hz 1600x900@60Hz 1440x900@60Hz 1280x1024@60Hz 1280x800@60Hz 1280x720@60Hz Detailed mode (1) : Clock 148 MHz, 527 mm x 296 mm 1920 2008 2052 2200 hborder 0 1080 1084 1089 1125 vborder 0 +hsync +vsync Monitor ranges (GTF): 50-60Hz V, 30-80kHz H, max dotclock 170MHz Monitor name: HP 24es Serial number: 3CM710122F Has 1 extension blocks Checksum: 0x9f (valid) CEA extension block Extension version: 3 21 bytes of CEA data VIC 16 1920x1080@60Hz (native) VIC 31 1920x1080@50Hz VIC 4 1280x720@60Hz VIC 19 1280x720@50Hz VIC 3 720x480@60Hz VIC 18 720x576@50Hz VIC 1 640x480@60Hz VIC 2 720x480@60Hz VIC 17 720x576@50Hz Vendor-specific data block, OUI 000c03 (HDMI) Maximum TMDS clock: 170MHz YCbCr quantization: (0) RGB quantization: (0) PT scan behaviour: (2) IT scan behaviour: (2) CE scan behaviour: (3) Detailed mode (1) : Clock 148 MHz, 527 mm x 296 mm 1920 2008 2052 2200 hborder 0 1080 1084 1089 1125 vborder 0 +hsync +vsync Detailed mode (1) : Clock 148 MHz, 527 mm x 296 mm 1920 2448 2492 2640 hborder 0 1080 1084 1089 1125 vborder 0 +hsync +vsync Detailed mode (1) : Clock 74 MHz, 527 mm x 296 mm 1280 1390 1430 1650 hborder 0 720 725 730 750 vborder 0 +hsync +vsync Detailed mode (1) : Clock 74 MHz, 527 mm x 296 mm 1280 1720 1760 1980 hborder 0 720 725 730 750 vborder 0 +hsync +vsync Detailed mode (1) : Clock 27 MHz, 527 mm x 296 mm 720 736 798 858 hborder 0 480 489 495 525 vborder 0 -hsync -vsync Checksum: 0xb (valid) bestmode is custombuilt, IEEEOUI 0x000c03 HDMI Mode bestmode is custombuilt, IEEEOUI 0x000c03 HDMI Mode 161 bytes read in 3 ms (51.8 KiB/s) ** File not found uImage ** 25461312 bytes read in 713 ms (34.1 MiB/s) ** File not found dtb/amlogic/meson-g12b-odroid-n2-plus.dtb ** 80112 bytes read in 13 ms (5.9 MiB/s) ** File not found uInitrd ** 16366032 bytes read in 460 ms (33.9 MiB/s) ee_gate_off ... ## Booting kernel from Legacy Image at 01100000 ... Image Name: Linux Image Type: AArch64 Linux Kernel Image (uncompressed) Data Size: 25461248 Bytes = 24.3 MiB Load Address: 01080000 Entry Point: 01080000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 03700000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16365968 Bytes = 15.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK active_slot is <NULL> Unknown command 'store' - try 'help' No dtbo patitions found load dtb from 0x1000000 ...... ## Flattened Device Tree blob at 01000000 Booting using the fdt blob at 0x1000000 No valid dtbo image found Loading Kernel Image(COMP_NONE) ... OK kernel loaded at 0x01080000, end = 0x028c8200 libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND [rsvmem] fdt get prop fail. Loading Ramdisk to 3c864000, end 3d7ff990 ... OK Loading Device Tree to 000000001ffe9000, end 000000001ffff8ef ... OK Starting kernel ... uboot time: 8836498 us Give root password for maintenance (or press Control-D to continue): root@system:~# uname -a Linux system 5.10.60-meson64 #21.08.1 SMP PREEMPT Wed Aug 25 19:29:40 UTC 2021 aarch64 GNU/Linux root@system:~# cat /var/log/apt/history.log Start-Date: 2024-04-03 10:11:58 Commandline: apt upgrade --without-new-pkgs Upgrade: libnetfilter-conntrack3:arm64 (1.0.8-3, 1.0.9-3... End-Date: 2024-04-03 10:16:32 Start-Date: 2024-04-03 10:20:02 Commandline: apt full-upgrade Install: libperl5.36:arm64 (5.36.0-7+deb12u1, automatic), libnode108:arm64 (18.19.0+... End-Date: 2024-04-03 10:52:59 Start-Date: 2024-04-03 10:59:13 Commandline: apt full-upgrade Upgrade: php-redis:arm64 (6.0.2-1+0~20231128.56+debian11~1.gbp9f3071, 6.0.2-1+0~20231128.56+debian12~1.gbp9f3071), ... End-Date: 2024-04-03 11:00:44 Start-Date: 2024-04-03 11:53:03 Commandline: apt full-upgrade Install: armbian-bsp-cli-odroidn2-current:arm64 (24.2.1) Upgrade: armbian-config:arm64 (23.02.2, 24.2.1), linux-image-current-meson64:arm64 (21.08.1, 24.2.1), armbian-zsh:arm64 (23.02.2, 24.2.1), linux-u-boot-odroidn2-current:arm64 (21.08.1, 24.2.1), base-files:arm64 (12.4+deb12u5, 24.2.1-12.4+deb12u5-bookworm), linux-dtb-current-meson64:arm64 (21.08.1, 24.2.1), armbian-bsp-cli-odroidn2:arm64 (23.02.2, 24.2.1) End-Date: 2024-04-03 11:54:34 root@system:~# content of /boot drwxr-xr-x 3 root root 4096 3. Apr 11:58 . drwxrwxrwx 19 root root 4096 3. Apr 11:54 .. -rw-r--r-- 1 root root 161 3. Apr 11:58 armbianEnv.txt -rw-r--r-- 1 root root 161 2. Nov 2021 armbianEnv.txt.old -rw-r--r-- 1 root root 1531 30. Okt 2021 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 26. Aug 2021 boot.bmp -rw-r--r-- 1 root root 8075 3. Apr 11:54 boot.cmd -rw-r--r-- 1 root root 5579 16. Jun 2023 boot.ini -rw-r--r-- 1 root root 8147 3. Apr 11:54 boot.scr -rw-r--r-- 1 root root 258772 29. Feb 18:56 config-6.6.16-current-meson64 -rwxr-xr-x 1 root root 120 1. Jan 1970 display.bin lrwxrwxrwx 1 root root 26 3. Apr 11:54 dtb -> dtb-6.6.16-current-meson64 drwxr-xr-x 3 root root 4096 3. Apr 11:53 dtb-6.6.16-current-meson64 -rwxr-xr-x 1 root root 256 1. Jan 1970 edid.bin lrwxrwxrwx 1 root root 30 3. Apr 11:54 Image -> vmlinuz-6.6.16-current-meson64 -rw-r--r-- 1 root root 16365968 3. Apr 11:54 initrd.img-6.6.16-current-meson64 -rw-r--r-- 1 root root 0 3. Apr 11:54 .next -rw-r--r-- 1 root root 4424139 29. Feb 18:56 System.map-6.6.16-current-meson64 -rw-r--r-- 1 root root 25461312 9. Dez 2021 uImage lrwxrwxrwx 1 root root 30 3. Apr 11:54 uInitrd -> uInitrd-6.6.16-current-meson64 -rw-r--r-- 1 root root 16366032 3. Apr 11:54 uInitrd-6.6.16-current-meson64 -rw-r--r-- 1 root root 28346880 29. Feb 18:56 vmlinuz-6.6.16-current-meson64 content of /boot/dtb/amlogic: root@system:/boot# ls dtb/amlogic/ amlogic-c3-c302x-aw409.dtb meson-gxl-s805x-p241.dtb amlogic-t7-a311d2-an400.dtb meson-gxl-s905d-libretech-pc.dtb amlogic-t7-a311d2-khadas-vim4.dtb meson-gxl-s905d-mecool-kii-pro.dtb meson-a1-ad401.dtb meson-gxl-s905d-p230.dtb meson-axg-jethome-jethub-j100.dtb meson-gxl-s905d-p231.dtb meson-axg-jethome-jethub-j110-rev-2.dtb meson-gxl-s905d-phicomm-n1.dtb meson-axg-jethome-jethub-j110-rev-3.dtb meson-gxl-s905d-sml5442tw.dtb meson-axg-s400.dtb meson-gxl-s905d-vero4k-plus.dtb meson-g12a-radxa-zero.dtb meson-gxl-s905w-jethome-jethub-j80.dtb meson-g12a-radxa-zero-spidev.dtb meson-gxl-s905w-p281.dtb meson-g12a-sei510.dtb meson-gxl-s905w-tx3-mini.dtb meson-g12a-u200.dtb meson-gxl-s905x-hwacom-amazetv.dtb meson-g12a-x96-max.dtb meson-gxl-s905x-khadas-vim.dtb meson-g12b-a311d-bananapi-m2s.dtb meson-gxl-s905x-libretech-cc.dtb meson-g12b-a311d-khadas-vim3.dtb meson-gxl-s905x-libretech-cc-v2.dtb meson-g12b-a311d-khadas-vim3-spidev.dtb meson-gxl-s905x-nexbox-a95x.dtb meson-g12b-a311d-khadas-vim3-spinor.dtb meson-gxl-s905x-p212.dtb meson-g12b-bananapi-cm4-cm4io.dtb meson-gxm-gt1-ultimate.dtb meson-g12b-gsking-x.dtb meson-gxm-khadas-vim2.dtb meson-g12b-gtking.dtb meson-gxm-mecool-kiii-pro.dtb meson-g12b-gtking-pro.dtb meson-gxm-mini-m8s-pro.dtb meson-g12b-odroid-go-ultra.dtb meson-gxm-minix-neo-u9h.dtb meson-g12b-odroid-n2.dtb meson-gxm-nexbox-a1.dtb meson-g12b-odroid-n2l.dtb meson-gxm-q200.dtb meson-g12b-odroid-n2-plus.dtb meson-gxm-q201.dtb meson-g12b-odroid-n2-plus-spidev.dtb meson-gxm-rbox-pro.dtb meson-g12b-odroid-n2-plus-spinor.dtb meson-gxm-s912-libretech-pc.dtb meson-g12b-odroid-n2-spinor.dtb meson-gxm-t95z-plus.dtb meson-g12b-radxa-zero2.dtb meson-gxm-vega-s96.dtb meson-g12b-radxa-zero2-spidev.dtb meson-gxm-wetek-core2.dtb meson-g12b-s922x-bananapi-m2s.dtb meson-s4-s805x2-aq222.dtb meson-g12b-s922x-khadas-vim3.dtb meson-sm1-a95xf3-air.dtb meson-g12b-ugoos-am6.dtb meson-sm1-a95xf3-air-gbit.dtb meson-g12b-waveshare-cm4-io-base-b.dtb meson-sm1-bananapi-m2-pro.dtb meson-gxbb-kii-pro.dtb meson-sm1-bananapi-m5.dtb meson-gxbb-nanopi-k2.dtb meson-sm1-h96-max.dtb meson-gxbb-nexbox-a95x.dtb meson-sm1-khadas-vim3l.dtb meson-gxbb-odroidc2.dtb meson-sm1-khadas-vim3l-spidev.dtb meson-gxbb-p200.dtb meson-sm1-khadas-vim3l-spinor.dtb meson-gxbb-p201.dtb meson-sm1-odroid-c4.dtb meson-gxbb-vega-s95-meta.dtb meson-sm1-odroid-c4-spidev.dtb meson-gxbb-vega-s95-pro.dtb meson-sm1-odroid-hc4.dtb meson-gxbb-vega-s95-telos.dtb meson-sm1-sei610.dtb meson-gxbb-wetek-hub.dtb meson-sm1-x96-air.dtb meson-gxbb-wetek-play2.dtb meson-sm1-x96-air-gbit.dtb meson-gxl-s805x-libretech-ac.dtb overlay Before the last upgrade (with armbian bookworm repository), there was an directory rockchip in /boot/dtb (as link to dtb-5.10.60-meson64) root@system:/boot/dtb-5.10.60-meson64# ls -al insgesamt 16 drwxr-xr-x 4 root root 4096 9. Dez 2021 . drwxr-xr-x 3 root root 4096 3. Apr 16:48 .. drwxr-xr-x 3 root root 4096 9. Dez 2021 amlogic drwxr-xr-x 2 root root 4096 9. Dez 2021 rockchip

I wrote a full guide for X96 Mini. It is available there. https://github.com/kdrapel/x96mini_linux/blob/main/README.md ---- Installing Linux on X96 Mini Goal is to install a Linux on a X96 Mini that I did not use anymore as a TV box and wanted to recycle as a DNS server for ads-blocking (https://pi-hole.net/) and other experiments. Important: I will not give any support or answer questions related to issues happening with your own X96 Prerequisites Instructions are covering steps on a Windows machine. Should be similar for Linux. Based upon (messy) instructions found at https://forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw-aarch64-armv8/ Hardware X96 Mini 2GB CPU is S905X. Label behind say "X96 mini RAM 2GB, ROM 16 GB". SD card, 16 GB. Smaller will be ok too (needs at least 8GB) Toothpick or small stick (reset button inside AV jack) Software Rufus 3.12 7Z Preparation Download https://users.armbian.com/balbes150/arm-64/Armbian_20.10_Arm-64_focal_current_5.9.0.img.xz Unzip this file to get Armbian_20.10_Arm-64_focal_current_5.9.0.img Launch Rufus, select the img. Click on 'Start'. SD card will be formatted and content will be written. Configuration of u-boot In Windows Explorer, navigate to your SD card. You should see a structure a 'extlinux' folder, 'dtb', etc. Rename the file 'u-boot-s905x-s912' to 'u-boot.ext' Configuration of device tree block A Device Tree Block (DTB) is a file that contains important information about the target hardware (more info http://junyelee.blogspot.com/2015/07/a-tutorial-on-device-tree.html). So it is necessary to use the proper one. This is a tricky part and if an improper DTB is used, your target system will fail loading or the kernel will panic. Edit the file /extlinux/extlinux.conf Comment out all lines starting with FDT and APPEND (we don't want RK or AW configuration, we are only interested in AML s9xxx section). Uncomment 'FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb' and 'APPEND ....'. See example below LABEL Armbian LINUX /zImage INITRD /uInitrd # rk-3399 #FDT /dtb/rockchip/rk3399-rock-pi-4.dtb #FDT /dtb/rockchip/rk3399-nanopc-t4.dtb #FDT /dtb/rockchip/rk3399-roc-pc-mezzanine.dtb #APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 # rk-3328 #FDT /dtb/rockchip/rk3328-roc-pc.dtb #FDT /dtb/rockchip/rk3328-box-trn9.dtb #FDT /dtb/rockchip/rk3328-box.dtb #APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 # aw h6 #FDT /dtb/allwinner/sun50i-h6-tanix-tx6.dtb #APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 video=HDMI-A-1:e #APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 mem=2048M video=HDMI-A-1:e # aml s9xxx #FDT /dtb/amlogic/meson-gxbb-p200.dtb FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb #FDT /dtb/amlogic/meson-gxm-q200.dtb #FDT /dtb/amlogic/meson-g12a-x96-max.dtb #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 Launching Unplug the X96 Mini Insert the SD card Using a toothpick, small stick or whatever suitable, press on the 'reset' switch which is located inside the AV jack. You don't need to press too hard. While the reset switch is maintained pressed, plug the power. The X96 Mini screen will appear and normally after a few seconds, it should switch to the Linux boot. You can release the reset switch. Linux should run if everything is properly configured. I access it through SSH on port 22. It is of course recommended to change the default root password (root / 1234) Installing Pi-Hole on the X96 Upgrading system First upgrade your system with "apt-get upgrade" About 50 packages or so are upgraded. Install Pi-Hole It may fail by saying that your OS is not supported, just follow the instructions they provide in the error message in this case. I will not detail the complete installation, I used the default configuration step without doing any tweaking except giving the target IP address of my X96 on my network. curl -sSL https://install.pi-hole.net | PIHOLE_SKIP_OS_CHECK=true sudo -E bash Configuration of router Assign a static IP to the MAC address of your X96. This must match what you defined in the PI-hole configuration. Switch the router to your new DNS server (as the primary). I left the secondary DNS server to my ISP default, just in case the X96 crashes or fails for whatever reason. Smoke testing Disable ad-blocking in your browser and navigate to some heavy websites Additional lists may be useful for Youtube adblocking, here is my configuration. Known issues Wifi is not working. I did not investigate more as I don't need it right now. Probably some (proprietary) Realtek drivers are needed from what I have read on the web. Troubleshootings You can attach a keyboard and mouse to the USB ports. The Logitech receiver is also working such that I could use my keyboard.

Hi, I'm using the image Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11.img on my Box TV Tigre 2 with Amlogic S905x processor and the dtb meson-gxl-s905x-p212.dtb and all the things I need are working, except the HDMI Audio output. Using the command "aplay -l" it shows no soundcards found but using the command lsmod | grep snd it shows different sound modules so I think it's a driver problem Also using armbian-config and going to system->hardware it shows an empty list. Any ideas on how to make it work?

Based on what my android recovery says, use the following dtb amlogic "meson-gxl-s905x-p212.dtb"

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!

Hey @balbes150, thank you for creating this awesome image! I've managed to successfully boot an MXQPro 4k (Amlogic S905X p212 board) from SD Card, however upon running the installation script Armbian, it doesn't seem to find the internal eMMC. root@arm-64:~# ./install-aml.sh Start script create MBR and filesystem UNABLE TO FIND YOUR EMMC DRIVE OR YOU ALREADY RUN FROM EMMC!!! I'm using the `u-boot-s905x-s912` bootloader, `ODROIDN2-UBOOT-CONFIG` in boot.ini, and the following DTB config in `extlinux.conf`: # aml s9xxx FDT /dtb/amlogic/meson-gxl-s905x-p212.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 However, I can't seem to find my internal eMMC: root@arm-64:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 7.3G 0 disk ├─mmcblk0p1 179:1 0 512M 0 part /boot └─mmcblk0p2 179:2 0 6.6G 0 part / zram0 254:0 0 50M 0 disk /var/log zram1 254:1 0 459.5M 0 disk [SWAP] (Please note that `mmcblk0` is my sd card.) Can you please help me identify the problem, so I can install Armbian into the internal storage of my board? Any help would be much appreciated.

I'm unable to make this work. I have what I believe is some random generic box (this one), with an Amlogic S905X. I'm sure I'm doing something wrong, or perhaps I'm missing a step or something. This is what I do: 1- Burn Armbian_20.08_Arm-64_focal_current_5.7.16_desktop.img.xz into a MicroSD with rufus. 2- In the BOOT partition, modify the 'extlinux.conf' and comment out everything except 'FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb' and the APPEND that is there below (I honestly don't know how this thing works, I don't know if I have to change something or even if I should use it, sometimes I left it out with no difference). 3- Renamed the 'u-boot-s905x-912' into 'u-boot.ext'. When I try to boot the SD card in the tv box nothing happens, I go directly to the Android system. I have another SD card with 'Alexelec' that boots fine. This box doesn't have a reset button, I tried flashing 'aml_autoscript' but it says 'error' after rebooting. What I'm missing? Regards!

The box is a Leelbox Q2 (s905x p212 2g). Image used is Armbian_20.08_Arm-64_focal_current_5.7.15_desktop.img booting from SD. I have followed instructions, set dtb to /boot/dtb/amlogic/meson-gxl-s905x-p212.dtb in extlinux/extlinux.conf and copied u-boot-s905x-s912 in u-boot.ext. Now u-boot sets my mac-address to 4e:6b:62:04:f1:00 which is not correct, from u-boot console i can't set ethaddr property (error is can't overwrite). I also tried to convert dtb to dts, add local-mac-address (and mac-address) property to ethernet and convert this dts to a dtb used in extlinux.conf but this doesn't work, mac address is always overwritten (by uboot I guess). Another issue is that activity/link leds on port are not working. Every thing just works booting original android image from internal flash.

Hi, I am trying to install Armbian_20.07_Arm-64_buster_current_5.7.9.img onto the emmc (internal storage) of my TVBOX. Its a T95N S905X device with 1g RAM and 8g emmc. I followed the process at the start of this thread and I can get it running fine off of the micro sd card, using either/both of the meson-gxl-s905x-p212.dtb or meson-gxl-s905x-nexbox-a95x.dtb and I have successfully used the Amlogic USB burning tool to install and run stock firmware images for MXQPro, T95N, T95X and A95X-nexbox. I have tried without success once running ambian from the external microsd to install it to the intermal emmc using the /root/install-aml.sh or /root/install-aml-S905.sh. I have tried to debug why it does not work and it appears to come down to how the storage is seen by the kernel/OS. fdisk -l shows the emmc in the form of /dev/mmcblkX with /dev/mmcblkXp1 and /dev/mmcblkXp1 but the devices tree has them as /dev/mmcblkXboot0 and /dev/mmcblkXboot1. The X varies according to which dtb I use, its either 0 or 1. I tried renaming the /dev/xxxxxboot0 and 1 entries to match what fdisk and the script wants but it does not resolve the issue. Any pointers or solutions will be gratefully received, thanks

Hi, i have been trying to install armbian on my m8s ii since a couple of days. I followed https://forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw-aarch64-armv8/ guide. Downloaded 2 different versions of armbian and im always using the "toothpick method" but i still do not manage to boot on my tv box. Things i did 1. edited the uEnv file as on the image https://i.imgur.com/UWvwEiB.png and did not add the dtb.img to the root folder 2.without editing uEnv, add dtb.img 3.edited uEnv and added dtb.im (related to the edition) Files i used 1. meson-gxl-s905x-p212 2. meson-gxl-s905x-nexbox-a95x 3. meson-gxl-s905x-libretech-cc 4. meson-gxl-s905x-khadas-vim 5. meson-gxl-s905x-hwacom-amazetv I tried using the SD card, and a usb drive. Considered the option that the sd card or usb where failing, i used ColeELECT and booted instantly. Information showed on android recovery Anlogic/p212/p212 6.0.1/MHC19J/20170601 Can i please ask for a hand here as i do not know what else to do?