Search the Community

I have an OTT TV Box, model ABOX-A1 ( 1G + 8G, S905X ). Inside it looks very similar to NEXBOX A95X discussed at https://www.savagemessiahzine.com/forum/index.php?showtopic=770346 . It has an analog AV port, with a 3PEAK TPF632A audio line driver on the output. So, all the digital audio stuff is inside the S905X SOC, and maybe some GPIO switches mute of that analog output chip. I first booted Devmfc_Debian-Bookworm_6.1.57-meson64_Minimal-23.10.12.img.xz from https://github.com/devmfc/debian-on-amlogic and had sound on the analog output. (The later Devmfc_Debian-Bookworm_6.6.1-meson64_Minimal-23.11.09.img.xz did not work.) I used its aml-multiboot-setup.sh script to set up automatic boot from USB or SD if they're present, without needing to hold the button in the bottom of the AV port. Then I decided I'd rather run Armbian, and I got Armbian_23.11.1_Aml-s9xx-box_bookworm_current_6.1.63_minimal.img.xz running from a USB drive. (I couldn't run Armbian_23.11.1_Aml-s9xx-box_bookworm_current_6.1.63.img.xz and some others, but I'm not 100% sure that I didn't do something wrong that prevented them from running.) This works fine, except there are absolutely no audio devices, either for HDMI or analog audio. I saw that the kernel modules that seem needed were present, but they weren't loaded and loading them didn't help. I guess they only work if the device tree informs Linux about that hardware being present. Using grep gx-sound-card /boot/dtb/amlogic/*s905x* I see only meson-gxl-s905x-khadas-vim.dtb, meson-gxl-s905x-libretech-cc.dtb, and meson-gxl-s905x-libretech-cc-v2.dtb contain that. I had had tried meson-gxl-s905x-p212.dtb and meson-gxl-s905x-nexbox-a95x.dtb so far, and neither have sound. Then I found https://github.com/torvalds/linux/commit/7e01e14e9f75385910d1e42f97a5e98f36244967 "arm64: dts: meson: add audio playback to S905X-P212 dts". After applying that patch, rebuilding the .dtb, and rebooting, I got a sound device. I could play audio files, and that took the appropriate amount of time, as if audio was going somewhere, but there was no analog audio output. Then, changing some things via amixer got it to work. These changes must have persisted, because I shut down, removed power, and booted again, and analog audio worked without having to do anything. I am attaching the altered .dtb file, the .dts file with the patch applied, and amixer output showing the current configuration with working analog audio. If you don't get audio, you can diff your amixer output against that output and see what might need to be changed. If you want to build the .dtb file yourself, note that the dtc program cannot handle the C preprocessor include directives found in these files. So, you first need to run them through the C preprocessor, and then you need to run dtc on the preprocessed output. Use something like cpp -nostdinc -I include -I arch -undef -x assembler-with-cpp arch/arm64/boot/dts/amlogic/meson-gxl-s905x-p212.dts ~/p212.dtsp To obtain the source code, I simply used https://github.com/armbian/build to start a build of a minimal Armbian system, telling it I want to custom configure the kernel. Then when the kernel configuration menu came up, I killed that, knowing all the files I needed were present. s905x-p212_audio_fix.tar.xz

Hi wifi work from SD card, after installing to emmc WIFI HW not recognized. Image from https://github.com/armbian/community bookworm edge minimal 222M 6.2.14 How to solve it? instal via armbian-config dtb: meson-gxl-s905x-p212.dtb IMG: Armbian_23.5.0-trunk.140_Aml-s9xx-box_bookworm_edge_6.2.14_minimal.img HW: mbox s905x v0.3 WIFI: RTL8723BS

Question, should I continue with this? I cannot do the "toothpick" method, but I can try the "update" method. My dtb is meson-gxl-s905x-p212.dtb My u-boot is u-boot-s905x-s912 I also have changed the build, I use the "Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11_xfce_desktop.img.xz" image. And the result is: the update app cant even read the sd card. Anyways, I follow the instructions download the image of this tutorial on the Internet https://i12bretro.github.io/tutorials/0316.html and I use this image "Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz" I get the "map file is too short" message

Ok I burned the Armbian_20.05.6_Arm-64_bullseye_current_5.7.2_desktop_20200612.img.xz but this image still uses the old method with the .deb file I tried the following .deb files renaming them to deb.img but none make me boot still on the arc64 s905x screen! meson-gxl-s905x-p212.dtb meson-gxl-s905x-khadas-vim.dtb meson-gxbb-vega-s95-meta.dtb meson-gxbb-p200.dtb meson-gxbb-p201.dtb I am attaching my uEnv.txt configuration uEnv.txt armbian_first_run.txt.template

I from the extlinux.conf file he burned etcher just stripped the # off the file FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb

LABEL Armbian LINUX /uImage INITRD /uInitrd #FDT /dtb/amlogic/meson-gxbb-p200.dtb FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb #FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.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=UUID=a9d31d97-348f-4685-9a2c-675531952cd1 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian

I just noticed this from your post above. If this is from your extlinux.conf, you have a typo. It should be "meson-gxl-s905x-p212.dtb" (note - not . )

Nothing there actually says what CPU you have, "S905 series" doesn't mean anything specifically. But from what I do see, I would guess you have an s905x or s905w. The board type is p212 which is the reference board for the s905x. So I would recommend you first try using the u-boot-s905x-s912 uboot and the meson-gxl-s905x-p212.dtb The best way to know what cpu you have is to remove the heatsink and look at the markings on the chip

@SteeMan, thanks for the link! I don't have original firmware around, but I do have 10 boxes I've flashed `Armbian_23.02.2_Aml-s9xx-box_jammy_current_6.1.11` on sd card and inserted it in fresh box, that was only booted in stock Android And with following configuration $ md5sum u-boot.ext u-boot-s905x-s912 81af2e7c3577b983e4ec88ff870c5ffb u-boot.ext 81af2e7c3577b983e4ec88ff870c5ffb u-boot-s905x-s912 $ cat extlinux/extlinux.conf LABEL Armbian LINUX /uImage INITRD /uInitrd #FDT /dtb/amlogic/meson-gxbb-p200.dtb #FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb FDT /dtb/amlogic/meson-gxl-s905w-p281.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=UUID=89c45261-1cd5-4b2d-9970-1b5a56ff98e2 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 I'm getting black screen if I hold reset for 2,3,4,5 seconds. With 6 seconds and more I get X96mini splash screen for a second and then black screen again. I tried using `gxl_p281_2g.dtb` from coreelec image, but result is the same — black screen.

Since I meet the same issue with the thread owner, then I reply this thread. Historical data: On the same box I made it successfully with the steps (but I do not remember that I make it works either using an sd card or USB, or the exact image), I remember I used u-boot-s905x-s912 , then I move all the data to eMMC successfully too (I remember the LAN works ok, wifi worked with a Wifi USB Dongle). Now after 2 years the OS was broken because the disk is full, I tried again and see this issue. I actually do not set high expectation for this box: Just a place where I can install small tools like Pihole, I do not need wifi just the Ethernet. As I tried and failed many times so I tried to flash the eMMC to Android & now I can use the Android OS. Here is my configuration: Hardware: X905W 2G RAM, 16GB eMMC storage. Software: Try this Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz (both Balena Etcher & Rufus 3.12) Also try this: Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11.img.xz u-boot.ext copied from u-boot-s905x-s912 (635kB) (copied not moved) extlinux.conf (also tried with meson-gxl-s905x-p212.dtb) LABEL Armbian LINUX /uImage INITRD /uInitrd #FDT /dtb/amlogic/meson-gxbb-p200.dtb #FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb #FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb FDT /dtb/amlogic/meson-gxl-s905w-p281.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=UUID=afbf3a1b-d905-4b27-b78a-3682d3db0dca 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 Note: The above extlinux.conf is generated with the build Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11.img.xz, for Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz the last line is slightly different: root=UUID=ROOTFS ... Tried on both SD Card(32GB & 64GB) & USB (16GB) and get the same issue, I cannot boot to the install screen. - Using Method 2 I got the same error as the thread owner shows. - Using Method 1 (the toothpick method): I hold the toothpick and see that the screen show X96 Mini screen (same as when I boot to the Android OS) then it boot again to that screen and make it a forever loop, if I withdraw the toothpick there will be no HDMI signal, the monitor will turn off. Thank you so much if you have any suggestion.

Hi with the curiosity of being able to install Armbian I got a friend to give me an MXQ PRO 4K similar to mine in aesthetics but with different hardware this one has a s905 processor below I release the info screens. I renamed u-boot-s905 to u-boot.ext with .dtb p200 because I understand from the info that this model mounts the hardware, then I boot with the toothpick method and it stops on the screen in the picture below, I tried both from SD and from usb pendrive same result! extilux.conf LABEL Armbian LINUX /uImage INITRD /uInitrd FDT /dtb-6.1.0-meson64/amlogic/meson-gxbb-p200.dtb #FDT /dtb/amlogic/meson-gxbb-p201.dtb #FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb #FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.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=UUID=999837fd-ddfc-4ce5-b624-7d109af0d3f8 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian

OK, now that you have the latest build, I would recommend that you start over. Reinstall a fresh android firmware and then try again. Because you used an old build, that caused you to set uboot variables that are not correct for the latest build. Also, it looks like you are using either the wrong dtb or the wrong u-boot.ext. Since the dtb you mentioned above is for an s905x cpu (meson-gxl-s905x-p212.dtb) but you are using the s905x2 uboot.ext (rename u-boot-s905x2-s912 to u-boot.ext)

Please read the two FAQ items in the TVBox forum FAQ, one being the amlogic instructions. Your box should have an s905x or s905w CPU. I would start by trying the meson-gxl-s905x-p212.dtb

***APOLOGIES FOR DELAY, LIMIT ON HOW MANY TIMES I CAN POST PER 24 HOURS*** I've managed to connect via TTL EEPROM connection and am getting the below. I'm using the meson-gxl-s905x-p212.dtb dtb file. With the "Armbian_20.02.0-rc1.037_Aml-s9xxx_bionic_current_5.5.0-rc6_desktop_20200205.img" image. Is "fdt_instaboot: no instaboot image" causing the issue? Any advice is much appreciated. Courtesy note: any one else using this the ttl speed is 115200.

@SteeMan When I insert the USB and boot up, then the device turns on, but stays on with a black screen without displaying or proceding to something else. Here is the list of the different dbt's that I have currently tried: meson-sm1-x96-max-plus.dtb X meson-sm1-x96-max-plus-q2.dtb X meson-sm1-x96-max-plus-q1.dtb X meson-sm1-x96-max-plus-oc.dtb X meson-sm1-x96-max-plus-ip1001m.dtb X meson-sm1-x96-max-plus-ip1001m-2.dtb X meson-sm1-x96-max-plus-100m.dtb X meson-sm1-x96-air.dtb X meson-sm1-x96-air-gbit.dtb X meson-sm1-ugoos-x3.dtb X meson-sm1-ugoos-x3-oc.dtb - meson-sm1-tx3-qz.dtb X meson-sm1-tx3-qz-oc.dtb - meson-sm1-tx3-bz.dtb X meson-sm1-tx3-bz-oc.dtb - meson-sm1-skyworth-lb2004-a4091.dtb X meson-sm1-sei610.dtb X meson-sm1-odroid-hc4.dtb X meson-sm1-odroid-c4.dtb X meson-sm1-khadas-vim3l.dtb X meson-sm1-hk1box-vontar-x3.dtb X meson-sm1-hk1box-vontar-x3-oc.dtb - meson-sm1-h96-max.dtb X meson-sm1-h96-max-x3.dtb - meson-sm1-h96-max-x3-oc.dtb - meson-sm1-bananapi-m5.dtb X meson-sm1-a95xf3-air.dtb - meson-sm1-a95xf3-air-gbit.dtb X meson-gxm-x92.dtb X meson-gxm-wetek-core2.dtb X meson-gxm-vega-s96.dtb X meson-gxm-tx9-pro.dtb X meson-gxm-tx8-max.dtb meson-gxm-t95z-plus.dtb meson-gxm-s912-libretech-pc.dtb meson-gxm-rbox-pro.dtb meson-gxm-q201.dtb meson-gxm-q200.dtb meson-gxm-q200-mod.dtb meson-gxm-phicomm-t1.dtb meson-gxm-octopus-planet.dtb meson-gxm-nexbox-a2.dtb meson-gxm-nexbox-a1.dtb meson-gxm-minix-neo-u9h.dtb meson-gxm-mecool-kiii-pro.dtb meson-gxm-khadas-vim2.dtb meson-gxm-fake-octopus-planet.dtb meson-gxm-beelink-gt1.dtb meson-gxl-s905x-vero4k.dtb meson-gxl-s905x-tx9.dtb meson-gxl-s905x-tbee.dtb meson-gxl-s905x-p212.dtb meson-gxl-s905x-nexbox-a95x.dtb meson-gxl-s905x-libretech-cc.dtb meson-gxl-s905x-libretech-cc-v2.dtb X meson-gxl-s905x-khadas-vim.dtb meson-gxl-s905x-hwacom-amazetv.dtb meson-gxl-s905x-b860h.dtb meson-gxl-s905w-x96-mini.dtb meson-gxl-s905w-tx3-mini.dtb meson-gxl-s905w-p281.dtb meson-gxl-s905w-jethome-jethub-j80.dtb meson-gxl-s905l3b-m302a.dtb meson-gxl-s905l2-x7-5g.dtb meson-gxl-s905l2-ipbs9505.dtb meson-gxl-s905d-vero4k-plus.dtb meson-gxl-s905d-sml5442tw.dtb meson-gxl-s905d-phicomm-n1.dtb meson-gxl-s905d-phicomm-n1-thresh.dtb meson-gxl-s905d-p231.dtb meson-gxl-s905d-p230.dtb meson-gxl-s905d-mecool-m8s-plus.dtb meson-gxl-s905d-mecool-kii-pro.dtb meson-gxl-s905d-mecool-ki-pro.dtb meson-gxl-s905d-mecool-ki-plus.dtb meson-gxl-s905d-libretech-pc.dtb meson-gxl-s805x-p241.dtb meson-gxl-s805x-libretech-ac.dtb meson-gxbb-wetek-play2.dtb meson-gxbb-wetek-hub.dtb meson-gxbb-vega-s95-telos.dtb meson-gxbb-vega-s95-pro.dtb meson-gxbb-vega-s95-meta.dtb meson-gxbb-p201.dtb meson-gxbb-p200.dtb meson-gxbb-odroidc2.dtb X meson-gxbb-nexbox-a95x.dtb meson-gxbb-nanopi-k2.dtb meson-gxbb-mxq-pro-plus.dtb meson-gxbb-minix-neo-u1.dtb meson-gxbb-mecool-kii-pro.dtb meson-gxbb-mecool-ki-plus.dtb meson-gxbb-kii-pro.dtb meson-gxbb-beelink-mini-mxiii.dtb meson-gxbb-beelink-mini-mx.dtb meson-g12b-ugoos-am6b1.dtb meson-g12b-ugoos-am6b-plus.dtb meson-g12b-ugoos-am6b-plus-oc.dtb meson-g12b-ugoos-am6.dtb meson-g12b-ugoos-am6-plus.dtb meson-g12b-s922x-khadas-vim3.dtb meson-g12b-radxa-zero2.dtb meson-g12b-odroid-n2.dtb meson-g12b-odroid-n2-plus.dtb X meson-g12b-gtking.dtb meson-g12b-gtking-pro.dtb meson-g12b-gtking-pro-rev_a.dtb meson-g12b-gtking-pro-rev_a-oc.dtb meson-g12b-gtking-pro-h.dtb meson-g12b-gtking-pro-h-oc.dtb meson-g12b-gtking-oc.dtb meson-g12b-gsking-x.dtb meson-g12b-dreambox-two.dtb meson-g12b-dreambox-one.dtb meson-g12b-a311d-khadas-vim3.dtb meson-g12a-x96-max.dtb meson-g12a-x96-max-rmii.dtb X meson-g12a-u200.dtb X meson-g12a-tanix-tx5max.dtb meson-g12a-sei510.dtb meson-g12a-s905l3a-m401a.dtb meson-g12a-s905l3a-e900v22c.dtb meson-g12a-s905l3a-cm311.dtb meson-g12a-radxa-zero.dtb meson-axg-s400.dtb X meson-axg-jethome-jethub-j100.dtb X meson-a1-ad401.dtb X I have tried to use the dbt's that are denoted with an X letter. Should I continue trying them out or might I be out of luck and won't be able to find one that matches my board? @maka Thanks for the tip!

Got following error where upgrade from 6.0.7 to 6.0.8 and 6.0.8 to 6.0.10. Running on a s905l box with meson-gxl-s905x-p212.dtb aml-s9xx-box:~:# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up linux-image-edge-meson64 (22.11.0-trunk.0138) ... * dkms: running auto installation service for kernel 6.0.10-meson64 [ OK ] update-initramfs: Generating /boot/initrd.img-6.0.10-meson64 W: Couldn't identify type of root file system for fsck hook update-initramfs: Converting to u-boot format Free space after deleting the package linux-image-edge-meson64 in /boot: 396M mv: cannot stat '/boot/vmlinuz-6.0.10-meson64': No such file or directory dpkg: error processing package linux-image-edge-meson64 (--configure): installed linux-image-edge-meson64 package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-edge-meson64 E: Sub-process /usr/bin/dpkg returned an error code (1)

Thanks Tido, Seriously, I wish I was kidding. I have already followed the steps prior to your message. and I get the same error regardless of the dtb file I use. I have renamed and tried both u-boot-s905x-s912 and the s922 --> renamed to u-boot.ext See the screen capture below. Note I have even tried copying the files and renaming it to dtb.img and I get the same crappy error message. The 1st screen capture shows the use of the "meson-gxl-s905x-p212.dtb" which btw like all makes no difference.

Hi on my Mecool M8S Pro W (with meson-gxl-s905x-p212.dtb): 1) after installing the images from August I cannot start the remote desktop -even manual installation in the console of xrdp does not solve this problem - (in older images like aml9xxX-Armbian_20.06.0_Arm-64_focal_current_5.7.6_desktop_20200630.img.xz - remote desktop works well and this from armbian-config). It is true that there is a possibility to log in, but the remote desktop does not appear. 2) so far I have not found an image where the built-in BT in Mecool would work - does starting BT require any additional actions?

Device : Fiberhome HG680-P S905X mali-450 Image : focal_current_5.7.6 Dtb:meson-gxl-s905x-p212.dtb On LXDE, LLVM driver is still being used. https://pastebin.com/k02E5upP https://pastebin.com/dgAXMXpH Tried on Sway, lima is detected, but glxgears is glitchy and stutters. Also lima echo a lot of pp pp2 reset time out when running glxgears https://pastebin.com/6CJGrjUV https://pastebin.com/HXBN0sYX Mpv plays Test.mp4 with no problem in windowed size. When fullscreened, the outputs dropping frames like crazy either with default vo or with --vo=wlshm Sent from my ASUS_X00TD using Tapatalk

Same problem here, arm-64:~:# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: GXLS905XP212 [GXL-S905X-P212], device 0: fe.dai-link-0 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 arm-64:~:# aplay -L null Discard all samples (playback) or generate zero samples (capture) lavrate Rate Converter Plugin Using Libav/FFmpeg Library samplerate Rate Converter Plugin Using Samplerate Library speexrate Rate Converter Plugin Using Speex Resampler jack JACK Audio Connection Kit oss Open Sound System pulse PulseAudio Sound Server speex Plugin using Speex DSP (resample, agc, denoise, echo, dereverb) upmix Plugin for channel upmix (4,6,8) vdownmix Plugin for channel downmix (stereo) with a simple spacialization default hw:CARD=GXLS905XP212,DEV=0 GXL-S905X-P212, Direct hardware device without any conversions plughw:CARD=GXLS905XP212,DEV=0 GXL-S905X-P212, Hardware device with all software conversions sysdefault:CARD=GXLS905XP212 GXL-S905X-P212, Default Audio Device hdmi:CARD=GXLS905XP212,DEV=0 GXL-S905X-P212, HDMI Audio Output dmix:CARD=GXLS905XP212,DEV=0 GXL-S905X-P212, Direct sample mixing device usbstream:CARD=GXLS905XP212 GXL-S905X-P212 USB Stream Output

X96 mini 2 gb-16 gb I have followed this tutorial.. https://github.com/kdrapel/x96mini_linux I can't get the X96mini to boot. installed image: Armbian_20.10_Arm 64_focal_current_5.9.0.img.xz. renamed the file 'u-boot-s905x-s912' a 'u-boot.ext'. The extlinux.conf file contains: LABEL Armbian LINUX /zImage INITRD /uInitrd #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=sí fsck.repair=sí net.ifnames=0 Can somebody help me?

I just bought the Q96 Mini TV Box with 8GB RAM and 128GB ROM: https://www.aliexpress.com/item/1005004079154677.html I have managed to boot Armbian in desktop mode with "Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img" But the problem is that it only allows me to use 1GB of RAM What do I have to do to be able to use the 8GB? I have tried decompiling "meson-gxl-s905x-p212.dtb" and changing the value to: memory@0 { device_type = "memory"; reg = <0x80000000 0x80000000 0x80000000 0x80000000>; }; and I've recompiled it, but I'm still able to use only 1GB of RAM I don't know what else to try any idea is welcome Thank you

I wanted a stable version because I thought that would involve less problems. Replacing the device tree only means replacing a single file and it is an easy fix that should easily persist across updates. I see that the weekly development builds at https://github.com/armbian/community/releases/tag/24.2.0-trunk.103 involving "Aml_s9xx_box" all use 6.1.66 kernel, and the patch is clearly not there: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/amlogic/meson-gxl-s905x-p212.dts?h=v6.1.66 . It clearly is in 6.6.1 and later: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/amlogic/meson-gxl-s905x-p212.dts?h=v6.6.1 To fix this problem, builds need to either transition to the 6.6 kernel, or add the patch before building the 6.1 kernel.

I found this box running Armbian at much cooler temperature than H603. Running around 40+-70c depending on ambient temperature and cpu load. The cpu never throttle. TV Box Name X96 mini CPU amlogic S905X Armbian build file name: Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img DTB file used: meson-gxl-s905x-p212.dtb Kernel Version: 5.9.0 Distribution Installed (focal, buster, etc): focal Working Ethernet (Yes/No): yes Max Ethernet Speed that works (100/1000): 100 Does wifi work (Yes/No): No after boot. But managed to compile from source (RTL8189ES) and now it is working (see attaching working 8189es.ko) Does bluetooth work (Yes/No): no Does HDMI audio work (Yes/No): didn't test Additional Comments (provide any additional information you feel is important): to make the wifi works, using the attached .ko file: # Enable the driver sudo cp 8189es.ko /usr/lib/modules/5.9.0-arm-64/kernel/drivers/net/wireless/realtek/ sudo depmod -a sudo modprobe 8189es In case you want to compile by yourself: # Install kernel headers wget https://users.armbian.com/balbes150/arm-64/deb/linux-headers-current-arm-64_20.10_arm64.deb or download from https://disk.yandex.ru/d/_rQgn_FosYuW0g/20.10/deb sudo dpkg -i linux-headers-current-arm-64_20.10_arm64.deb # Download the wifi driver git clone https://github.com/jwrdegoede/rtl8189ES_linux.git # Compile, cd rtl8189ES_linux/ make -j4 ARCH=arm64 KSRC=/usr/lib/modules/5.9.0-arm-64/build # Enable the driver sudo cp 8189es.ko /usr/lib/modules/5.9.0-arm-64/kernel/drivers/net/wireless/realtek/ sudo depmod -a sudo modprobe 8189es 8189es.ko

Help me please. Does not see the internal memory eMMC. I got dts from the original firmware. There the addresses are completely different. https://yadi.sk/d/4XpKrgPr_nSryQ It is launched only from the SD card and USB when using meson-gxl-s905x-p212.dtb, but EMMC is not visible. If you start from the SD card - he sees it as an eMMС.