Search the Community

DISCLAIMER (PLEASE READ): everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Thank you! This is CSC Armbian for XT-Q8L-V10 boards, also known as Chiptrip Q8, Vsmart Q8, ENY 3288 Q8, etc... All source code has been merged into Armbian mainline project. I still keep my personal public Armbian fork for experimental features: https://github.com/paolosabatino/armbian-build Nightly images: download directory Quick installation instructions on eMMC: Build or download your preferred Armbian image from Download directory and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the sd card, then push the power button for 1 second (the led will turn blue) After 10 seconds HDMI will turn on and you will get logging messages; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Boot from SD Card/USB stick (with Armbian already installed in eMMC, empty eMMC or no eMMC😞 Build or download your preferred Armbian image from Download directory; Burn the image on your SD card/USB stick; Plug the SD card/USB stick in the device; Push the power button for 1 second (the led will turn blue); After 10 seconds HDMI will turn on and you will get logging messages; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Boot from SD Card/USB stick (with original firmware or other firmware): In case your box has the original firmware installed, use the Multitool to erase the internal flash. Don't worry, you will not brick your box: once the eMMC is emptied, the box will automatically boot from SD Card. This is called Maskrom mode and is common to all Rockchip devices. Instructions and download links for the Multitool are at the bottom of this post. After erasing the internal eMMC, just follow the "Boot from SD Card" procedure above and then you are fine. Boot priority: Newer images (those with mainline kernel >= 4.14.50) now support booting from multiple devices. Priority is fixed and boot devices are probed in this order: External SD card External USB storage device (Any USB Stick/Hard drive attached to USB host ports) Internal eMMC This way even if you install armbian to internal eMMC, you can still easily test different images booting from external devices. Experts notes: when armbian is installed into eMMC you get U-boot installed too in eMMC. This is important to know because the box won't boot in Maskrom Mode, but instead will always boot the embedded U-boot, no matter if you put an sdcard/usb stick. In practice the embedded U-boot is totally responsible for the boot priority. If you want to restore the Maskrom Mode, just erase U-boot from eMMC using this command: dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=8128 conv=sync,fsync Current status: Wireless: works. pretty fast and stable, signal is strong on my box; Bluetooth: works. I was able to transfer files and stream audio without problems USB ports: works, with autosuspend too. A quick benchmark show that transfer rate is quite good (topped at 34 MB/s) USB OTG: works in host mode. Transfer rate is very good (> 40 MB/s) MMC: works and is perfectly accessible as storage device. The images above with "eMMC friendly" have been tested and work when installed in eMMC using the standard armbian-config eMMC installer SDCard: works. legacy kernel is limited to high speed, while mainline works fine in UHS mode too. A quick benchmark with a Samsung EVO card shows the promised 48Mb/s read speed. Gigabit Ethernet: works, fast and reliably HDMI: works perfectly Serial: works Audio: both HDMI audio and SPDIF connector works IR remote: works on legacy and mainline kernels Reboot/Suspend process: rebooting the device is a working in progress, at the moment sometimes it works and sometimes it doesn't. Suspend is still not available. Hardware acceleration: everything which works for rk3288 boards applies here too. This guide or maybe the Media Testing Script will help you gain an hardware accelerated X11 and Chromium (using GL4ES I enjoyed Quake 2 from the start till the end, but also Quake and Quake III Arena work flawlessy, here a quick how-to to compile and install GL4ES) Multimedia: On mainline kernel 3D acceleration is provided by Panfrost driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Multitool: The Multitool is a small but powerful tool to easy operate on internal eMMC flash of RK3288 devices. Features: Backup the content of internal eMMC Restore a previously backed-up image to eMMC Erase the eMMC (via fast blkdiscard or zero-fill as fallback) Burn an Armbian (or LibreELEC) image directly on the eMMC Provide a recovery shell for manual maintenance Windows-friendly: everything is placed in a NTFS partition Image compression format autodetection: they are decompressed on-the-fly during burn process Network support for remote maintenance via SSH (instructions to access via network here) Instructions are simple: Download the image from here Burn it on an sdcard Open the NTFS partition with your preferred file manager Place the images you want to burn on the device in images directory (backups will be stored in backups directory) Plug the sd card in the RK3288 device Power the device and wait few seconds, the Multitool menu will appear on screen and can be navigated with the keyboard Last edit: 07/06/2020 - updated installation instructions

I'm trying to install Armbian on the Tanix Tx1 Soc Allwinner H313 Mini TV Box, but this box doesn't have an SD card slot. How do I install Armbian on this box without an SD card?

Hello, I have some troubles with this TVBOX: it runs armbian and other distros correctly, using the meson-gxm-t95z-plus.dtb but sometimes wifi goes into kernel panic at boot, and when it does, the whole system becomes unstable (i.e. not rebooting, eth0 hangs...). I have extracted the original .DTB from the only firmware that exists for this box, the ancient 6.0 Marshmellow Android (I guess it's a 3.x kernel...). I attach it to this message hoping someone more expert than me can help in making it work ina more stable manner. I attach a picture of the board also, it reads "M8S". Box has 2GB ram and 16GB eMMC, brcmfmac wifi/bt and ZTE PHY chip. meson1.dtb

Hi, I would like to know if its possible to boot from SD card in my model of Android TV BOX. It does not have a reset button but has an update app. Its a Giga TV Box HD890 4K. It has an Amlogic CPU I do all the process of installing Armbian in the SD card, Android starts an update and it says: "Map file is too short". I really dont know what I have to do to enable multi boot. Installation is aborted. Im getting really upset for not being able to install Armbian. Any help to this issue would be really welcome. Sorry for my bad english

I am trying to install armbian on my Xiaomi mi tv box 3 I got the image on a flash drive it's a 16 gig USB 3 stick I got the files ready also but I don't know why it freezes when i enter the recovery screen and click on reboot to boatloader so If any on can help me fix this problem or start again that would be really useful thx

Hey i am looking for a suitable armbian distro for my tv box with the allwinner h313, 2gb ram and 8bg emmc.

I’ve been testing Armbian on an Amlogic-based TV box, and wanted to share a short user experience. The device originally runs Android, but thanks to the Amlogic S9xx platform, it can boot Armbian from an SD card without touching the internal firmware. In my case, the system booted reliably and was usable for basic tasks like SSH access, light services, and general Linux testing. Ethernet and USB worked out of the box, while Wi-Fi and power management still required some manual tweaks, which seems common for community-supported TV boxes. For reference, the hardware I used belongs to the category of Amlogic TV boxes that are widely available on the market. These devices are not officially supported by Armbian, but they can still be interesting low-cost platforms for learning, testing, or small home projects. I’m curious if others here have experience with Armbian on similar Amlogic TV boxes, and which SoCs or configurations worked best for you.

Stock rom of this tv stick is so bad that it lags even with just watching youtube and it wrote it can play 4k. So I need armbian/any other linux distro for this tv stick.

I installed ambian in this tv box to run klipper for my 3d printer, but its been a years since I last used it and I totally forgot what was the user I created. I really didn't want to wipe the SD card because of my 3d printer's config files etc. Is there anything I can do to retrieve the user and password? Thanks.

The purpose in this guide is to make installation simple for those who wish to follow what I did. This is specifically for the Yoka TV KB2 Pro which uses the S912 chipset with 3GB RAM and 32 GB ROM. It was successful and works for setting up windows mapped drives just fine with Samba. (for example Z:\) I am using it off the SD card, I left Android 7.1 on the EMMC. Notes: My intentions are to use it for a file server for use with USB 2.0 drives I have laying around that are old but still technically usable. The file transfer speed is only expected to be around 30% of the 1GBPS wired network. The bottleneck will definitely be the USB 2.0, but for what I am using it for, it should work just fine. Leaving it on 24/7 is only slightly more power than a Raspberry PI 4, so very low cost. The Wireless and Bluetooth do not work as is, I am not sure if you can get the drivers to make them work, I did not try. The 1GBPS network port works just fine. There is also no GPU/VPU acceleration, but for a file server who cares? This was done with windows 11 and win32diskimager (note the original website is https://sourceforge.net/projects/win32diskimager/) the other links are not what you are looking for and likely viruses and malware. Balena Etcher did not like the image file, win32diskimager had no issues once I extracted the .img file. Head to https://www.armbian.com/amlogic-s9xx-tv-box/ Download the Armbian 26.2.0-trunk.22 Noble Gnome - I did not test any of the other images. Burn it to an SD card - note (it says it will only work with up to 32GB micro SD cards. My 64GB amazon micro SD card worked just fine after upgrading my Yoka TV KB2 PRO to android 7.1 earlier, go figure.) I would suggest for this get a name brand SD card that is 32GB or less (the image uses around 2GB) At the boot partition you have to rename the file u-boot-s905x-s912 to u-boot.ext Now you have to edit the /extlinux/extlinux.conf file, look for the line that says FDT /dtb/meson-something (and change it to say FDT /dtb/meson-gxm-q200.dtb save the file This lets it know what chipset/model you are using, this is for the S912 chip that is in your Yoka TV kb2 pro You will need a usb keyboard and mouse, you also have to have it plugged into an HDMI cord that runs to a monitor or TV. Now for booting it in multiboot mode - hold the reset button (between AV and HDMI ports, this button is inside and very small, google suggests a toothpick, I used a phone sim remover tool) for 10 seconds before and while powering it on, do not let go until you hit 10 seconds. Now every time you restart it, it defaults to SD card first. It may take 2 or 3 attempts, but it does work. To boot to Android, just remove the SD card. First boot username and password is root and 1234, it will force you to change the password. When it asks for bash or zsh, I chose bash because I am way more familiar with it. When it asks for locale I used en_US.UTF-8 Time zone is based on wherever you are I used America/Chicago It will also ask you to create a new user account (non-root) and a password) This should get you up and running. The button to access everything is in the upper left corner, then you can access all your apps. There are tutorials to upgrade it to android 7.1 - it does work and well documented. I upgraded mine to android 7.1 it worked just fine. Do Not try to upgrade to android 9 slimBOXtv, there are no successful attempts proven, just bricked devices. I did not see a single picture of anyone having it running. I did however see plenty of complaints for bricked devices. Good enough for me to steer clear. I know this is rather long, but it will get you through the entire process, be safe, and hope you enjoy this how-to guide.

How I can install armbian on Xiaomi Mi tv stick 4k with SoC Amlogic S905Y4 & GPU Arm Mali-G31 MP2? Specifications Output Resolution - 4k CPU - Quad-core Cortex-A35 GPU - Mali-G31 MP2 RAM - 2GB Storage - 8GB Operating System - Android TV™ 11 Wireless connectivity - Wi-Fi 2.4GHz/5GHz, Bluetooth 5.2

The wifi and ethernet both are not working for my transpeed 8k tv device. it has a rk3528 chipset. 1. I tried resetting it from its android factory setting. it did not work. 2. I found its image which i flashed via RKdevtool. Still the both wifi and lan did not work. 3. i tried external usb wifi dongle but it did not detect it. 4. I tried to install debian OS i found somewhere on internet designed for rk3528 on it as alternative but rkdevtool did not identified the image Any suggestions would be welcome. Thanks in advance,

Hello SliTaz community, I would like to know how I could install SliTaz on an Android TV box powered by a Rockchip RK3229 processor. I understand that the standard SliTaz ISO is for x86 architecture, but my device uses ARM. Is there any ARM-compatible version of SliTaz that could run on this hardware? Or is there a way to build a custom ARM rootfs with the SliTaz ARM toolchain and use it with a compatible kernel and bootloader? Any help, guidance, or example would be greatly appreciated! Thanks in advance!

Hello, I have an Android M98-Y6 HDMI stick that reportedly has an Allwiner H313 processor with 2GB of RAM and 16GB of storage. When I opened the case, I identified the emcp memory module KMQNW000SM-B316. I don't have access to console mode. I can only access adb commands as root.The RAM type DDR3 seems LPDDR3 ( version ??) I've tried different Armbian images without success. Unfortunately, Secure Boot is enabled. I read this post and test Armbian-20240716-unofficial_24.5.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12_xfce_desktop_Secure_Boot.img.tar.xz from Nick, without success I have an Android image named M96-Y6.img. EDIT1: Also it has a AP6330 Wifi Chip ( thanks to "dmesg") It has a internal AC300 PHY ( thanks to "Device info HW") Attached is the "dts" file devicetree.dts device_tree_dump.txt

How do install armbian in my TX98 TV BOX Processor:Allwinner H313 I bought it on tiktok shop

Aliexpress item: https://pl.aliexpress.com/item/1005006249858881.html Extracted dtb and dts files attached. It boots Warpme/miniarch image for X96 with LPDDR3 RAM https://github.com/warpme/miniarch/releases/download/f3b14fbae071/MiniArch-20240715-6.16.1-board-h313.x96_q_lpddr3-SD-Image.img.xz However internal Ethernet port is silent. It can work through USB->ETH adapter though. Any Idea on how to make Ethernet working? sun50.dtb sun50.dts

Hello all. I have an Android-based Yundoo Y8 TV box, which I want to use for UPS management. I want it to be able to run Armbian to install the UPS management software, but I cannot figure out which Armbian I should download. The board is based on Rockchip RK3399. In cpu-z app I see the board identified as rk30sdk, and the hardware is rk30board. Can you please help me identify the board so I can understand which version of Armbian I need? I couldn't find anything in the forum about RK3399... I really appreciate any help you can provide.

Has anyone been able to use the remote control that comes with the tv bos under Armbian? Does it reqire additional driver(s)? I want to run Kodi (or any better mediacenter) under Armbian.

Hello, it's been months since I've said to myself "I've got to get a cheap TV box, since SBCs are now so expensive and my Raspberry Pi 3 is showing its I/O and memory limits", and I think I'm now finally forced to, because 2 weeks ago my Pi started to show some strange (load/power) issues, and even started to emit a funny burned smell (!!!), slowly with hours of continuous (even if light) uptime. It still works, but I fear that some component is dying, maybe having kept an USB HDD connected for months has fried something: the smell strangely is always coming even after changing PSU and disconnecting the HDD (apart from that, there are now no other connected peripherals except for the microSD), and it appears to come from the micro-USB port section of the board. Point is, I don't trust this thing to keep working 24/7 after this incident, I have to get a new small homeserver. Indeed, I mostly used the Pi as a server these years, and after reading "Status of Armbian on TV Boxes" I think I can at least give a shot at trying to buy a TV box as a Pi substitute for this kind of task. Since today and tomorrow the Amazon Prime Day takes place, and I'm finding some more-decent-than-usual deals (yes, I did check with Keepa, some boxes are really on discount today), I thought I might as well buy now and stop postponing. So, my requirements are about the following, and they seem easy enough to get on today's TV boxes with Android, but I don't know what happens if I was to desire Armbian: 4 GB RAM or more (unlike the Pi's 1 GB) USB 3.0 ports (unlike the Pi's 2.0), to add big additional storage with minimal bottleneck (but maybe we don't rely on an USB-Y cable anymore if connected to a separate PSU...) WiFi, preferably 5 GHz, because I don't have a good place to put the box near my router, and can't have Ethernet cables going from one corner of the room to the opposite... Now, I probably don't really need bare-metal pure Linux, since the majority of the software I have to run can do so in a proot container in Android (in the past I did use an half-broken Android smartphone as a server actually), but I would have to sacrifice Docker (which sometimes is really useful) and also Pi-Hole (since to work it has to bind on a privileged port, and I wouldn't bet on being able to root these Android boxes), so I am at least making an attempt at buying something that can run Armbian. From what I'm gathering from the forum, the best choices are usually Rockchip boxes (most supported), next come those with some Amlogic SoCs (driven by a small community), and lastly there are some Allwinners. However, it's a bit chaotic trying to infer what's the best choice from browsing semi-random threads, and that's why I'm asking any potential TV box expert (now that's hyperspecialization!) what could be the best choice among what I found for an acceptable price (some are on Prime Day discount, some aren't but still have a good price): X88 Pro 10, X88 Pro 12: RK3318 chip, I understood that it's good support-wise (https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/#comment-122715), WiFi works too if I'm reading correctly, but hardware-wise it's kind of crap, wastes energy, and can fail. Oh well, I'll be honest: I know I should be worried, but I don't know how much worried! X88 Pro 13: RK3528, is it a very new SoC? I can't find anything on the forum about it, and so I fear there is no support. Magcubic thingy, Magcubic 8K Ultra HD, Tanix thingy (Allwinner H618); T95H, Q Plus (Allwinner H616): It appears these are not well supported, there are some experimental builds around but many things are broken. Would be happy to discover that I'm wrong on this and support is actually good for my standards, though. TUREWELL T95 Max+: Amlogic S905X3, here I kinda don't understand at all if there's enough good community support or not, but there are many threads about issues and solutions. To be clear: I can tinker if something doesn't work out-of-the-box with Armbian, I have a bit of experience with embedded devices like routers or Android smartphones so I think I could solve minor issues if they arise, but I'm really looking for a quick replacement for my Raspi and don't want to spend more than a few days after getting the box to make Armbian work. That's why I'm thinking so hard on getting a device with good compatibility. Anyways, thank you to anyone who comes here to help, I would appreciate it. If no help comes, I think I will bet on a box with the RK3318 and hope for the best.

Armbian now has a community supported build target for amlogic TV Boxes (aml-s9xx-box). You can now build your own builds directly with the Armbian build system. This is now an opportunity for members of the community to move the support for amlogic TV boxes forward within the Armbian framework. If you are not familiar with the Armbian build system check out the Armbian developer documentation. If you have idea on how you would like to see things evolve/change please use this forum to share your thoughts and ideas and submit PRs for any code changes you would like to see. I am currently testing this code against the four different amlogic based boxes I own, but would appreciate others testing as well. Once I have completed my testing, I will be updating the FAQ amlogic install instructions with this information.

Hi everyone, I’m experiencing a recurring and very specific issue with my TX2 TV Box, with the following specifications: SoC: Rockchip RK3229 RAM: 2GB DDR3 Storage: NAND flash (not eMMC!) Board: Generic TX2 board 🛑 Main Issue The system shuts down abruptly at exactly 29 minutes and 47 seconds of uptime (i monitoring via htop). It always shuts down at this time. It’s not a clean shutdown or reboot — it behaves as if the power was cut off. No meaningful logs appear in journalctl or dmesg, and the shutdown is instantaneous and silent. 🧪 What I’ve Tried: Disabled idle and sleep functions: Masked systemd-logind Set IdleActionSec=0 and HandlePowerKey=ignore Tried different kernel versions: Legacy: Armbian 22.02.0-trunk Focal legacy 4.4.194 Mainline: Armbian Jammy kernel 5.15 Attempted to disable the watchdog: Boot parameter nowatchdog Kernel parameter rcu_cpu_stall_timeout=0 Created a systemd service to periodically write to /dev/watchdog Tried to remove dw_wdt module (modprobe -r), but it either auto-loads or refuses to unload (watchdog did not stop) Tried building a custom kernel with CONFIG_DW_WATCHDOG=n, but the process failed due to gcc-arm-linux-gnueabi toolchain issues. Used config-rk322x to properly set RAM, NAND, and Wi-Fi chip before first boot + update/upgrade. Tried adding sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target ⚠️ Additional Critical Note: The system does not work at all when flashed to eMMC/flash — only boots properly from NAND or SD card. Any image written to internal flash does not boot. Therefore, booting from NAND is required, which may be related to the watchdog being active by default on NAND-based boards. ❓ My Question: Has anyone with a TX2 or RK3229-based NAND board experienced this same issue? Is this a known watchdog timer issue on NAND models? Is there any stable image or device tree overlay known to work for this configuration? Any tips to fully disable the watchdog either via software or kernel patch? Thanks in advance for any help or suggestions!

I Have an A96X with rockchip RK3228 and i tried booting armbian on it, but I got no display on HDMI. I connected a serial adapter to it and here is the information it displays when trying to boot: ▒▒▒▒DDR Version V1.05 20160805_dbg In 300MHz DDR3 Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB mach:2 OUT Boot1 Release Time: 2016-03-15, version: 2.31 ChipType = c 275 No.1 FLASH ID:2c 64 44 4b a9 0 ECC:60 SdmmcInit=0 0 BootCapSize=0 UserCapSize=76f5000 FwPartOffset=2000 , 0 StorageInit ok = 1520008 SecureMode : SBOOT_MODE_NS hdr 0x0:ff a1 0 0 1b 0 0 0 f0 f2 2e 68 f0 f2 2e 68 hdr 0x0:a4 81 0 0 4e 23 0 0 f0 f2 2e 68 f0 f2 2e 68 hdr 0x0:ff a1 0 0 3 0 0 0 f4 f2 2e 68 f4 f2 2e 68 hdr 0x0:a4 81 0 0 44 0 0 0 f4 f2 2e 68 f4 f2 2e 68 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SecureMode : SBOOT_MODE_NS Loder code check ok! theLoader 0x60000000, loadaddr: 0x2000 Loder code check ok! theLoader 0x68400000, loadaddr: 0x4000 INF TEE-CORE:init_primary_helper:319: Initializing (1.0.1-63-g23e91df-dev #16 Tu e Mar 7 10:07:15 UTC 2017 arm) INF TEE-CORE:init_primary_helper:320: Release version: 1.8 INF TEE-CORE:init_teecore:79: teecore inits done U-Boot 2017.02-RK322X-06-02276-ga7c7ca8-dirty (May 19 2017 - 11:16:15) CPU: rk322x cpu version = 3 CPU's clock information: arm pll = 600000000HZ periph pll = 600000000HZ ddr pll = 600000000HZ codec pll = 500000000HZ Board: Rockchip platform Board Uboot as second level loader DRAM: Found dram banks: 1 Adding bank:0000000060000000(0000000040000000) Reserve memory for trust os. dram reserve bank: base = 0x68400000, size = 0x00100000 128 MiB GIC CPU mask = 0x00000001 rk dma pl330 version: 1.4 remotectl v0.1 pwm freq=0x11e1a3 pwm_freq_nstime=0x355 SdmmcInit = 0 0 SDCard Update. storage init OK! Using default environment Writing env to storage... done GetParam W: Invalid Parameter's tag (0x00000000)! Invalid parameter No pmic detect. SecureBootEn = 0, SecureBootLock = 0 #Boot ver: 0000-00-00#0.00 empty serial no. normal boot. no fuel gauge found no fuel gauge found read logo on state from dts [0] no fuel gauge found 'recovery' does not seem to be a partition nor an address Unable to boot:recovery try to start backup 'backup' does not seem to be a partition nor an address Unable to boot:backup try to start rockusb Can anybody point me to the right direction? I'd really like to turn this piece of junk into something useful 😄 Any help will be greatly appreciated! Thank you.

Dear All, First I would like to thanks all the contributors to armbian, What a great OS for our small SBC ! Context: I run succesfully latest Armbian on a X9T 4K TV Box (amlogic s912) from SD Card 2GB (following instructions here The Problem: I would like to run armbian from emmc (16GB on this box) for better reliability and performance. So, I run the install-aml.sh script, I had some error (no boot.ini ...), but the process seems to finish successfully Next Reboot: It's seems my boot partition is Not OK ... something missing ... For reference See bellow for reference the succesfull boot from the sdcard If I boot from SDCard, I can inspect the /boot and root partition on emmc, everything seems ok On the emmc partition, the /boot/extlinux/extlinux.conf is correctly modified: extlinux.conf LABEL Armbian LINUX /Image 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=LABEL=ROOT_EMMC 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 And the disk partion on the emmc fdisk -l /dev/mmcblk1 Disk /dev/mmcblk1: 14.64 GiB, 15724445696 bytes, 30711808 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x09170000 Device Boot Start End Sectors Size Id Type /dev/mmcblk1p1 1953792 2953215 999424 488M c W95 FAT32 (LBA) /dev/mmcblk1p2 2955264 30711807 27756544 13.2G 83 Linux If you can help me .... Thx in advance Nico

Hello. I have this MX10 Box S android TV box, it works well with the latest Armbian community build (Armbian_community_25.8.0-trunk.309_Rk322x-box_bookworm_current_6.12.35_minimal.img). However, I have this specific binary that is 64bit that I would like to run on my box and this build of armbian is 32bit only. Is there a 64bit build of armbian for rk322x anywhere? Thanks!

I have installed Armbian community images several times on different tv boxes that have an Amlogic S905x3, and usually there was no sound ♫. I wanted to get sound out of the tv box. So, I purchased a generic USB sound card audio dongle from Aliexpress for about $2 to $3 USD. (see attached photo). The USB audio device is described in Linux as a Texas Instruments PCM2902 Audio Codec (USB PnP Sound Device device 0 USB Audio), and when you run the command lsusb you will see the id numbers 08bb:2902. However, the specific hardware chip in the device that you receive may be different. I updated the databases for repositories by running sudo apt update -y and installed necessary packages to support the USB audio device and to use a graphical desktop such as XFCE4, for example: sudo apt install -y smplayer alsa-base alsa-oss alsa-tools alsa-utils alsamixergui pulseaudio pavucontrol pavumeter You can use smplayer or vlc or another as long as it is modern media player or audio player. Now make a backup copy of these two text files /etc/modules and /etc/modprobe.d/alsa-base.conf and save the backup copies in your home directory. Without quotes, edit the text file /etc/modules and write “snd-usb-audio” at the end of the file. Also, edit the text file /etc/modprobe.d/alsa-base.conf and change a few things. Put a hash # symbol in front of every “options snd-usb-audio index=-2” that you see in the file /etc/modprobe.d/alsa-base.conf . I found two of them. Add these two lines of text to the bottom of /etc/modprobe.d/alsa-base.conf without quotes. "alias snd-card-0 snd-usb-audio" "options snd-usb-audio index=0" Make sure that your user is in the 'audio' group. Run the usermod command against a regular user (not root) that you want to use often. And reboot. sudo usermod -a G audio {username here} sudo reboot Login to the graphical desktop, open the volume control program by clicking on the panel Applications, Multimedia, PulseAudio Volume Control. Click the Configuration tab at the far right of the volume control program and change the profile to Analog Stereo. * Important – now connect a headset, earphone, or amplifier to the 3.5mm (⅛’’) 🎧 headphone receptacle on the USB audio dongle and play some sounds, music or youtube. You can use wav audio files in the directory /usr/share/sounds/alsa/ if you don't have an internet connection.