All Activity

Armbian_26.2.1_Bananapi_trixie_current_6.12.68_minimal.img.xz (Bananapi M1) - only power, ethernet and serial console cable connected: 1st boot and user creation all fine - network up, WAN IP shown - then connecting a SATA SSD ('hotplug'), pops up in dmesg, so recognized OK

I follow this instructions The reset button in the case of my box is inside Av connection, I already boot the images with press the button and maintain IT. The result is a screen with HKSERIES screen, I can wait one hour nothing happens only the image. A video to you see that I press the reset multiboot button. Thanks.

some things are happening at the bleeding edge https://lore.kernel.org/u-boot/?q=a733 pay attention to u-boot, the most important thing are dram controller, pmic, mmc/sd etc then of course kernel as well https://lore.kernel.org/linux-sunxi/?q=a733

Take some time but I was able to identify the CLK pin. Shorting the marked pins (CLK and GND in this case) was able to switch MaskRom mode. Note: in early boot stages the eMMC CLK only working in legacy mode (24Mhz).

Sorry in advance, but this is a bit of a dive. But, I haven't seen this fully captured and explained anywhere, and think this would be a useful thing to know for anyone who's doing arm64 development on a PC, which seems very relevant here ... I started pulling this thread when moving some software from Ubuntu Jammy to Noble, where the arm64 build process went from 20 mins to 50 mins. When I was done, it below to 15 min, and all I did was poke some flags for qemu's emulated CPU. The TL;DR version is that setting the environment variable QEMU_CPU to something like "cortex-a53" or "max,pauth-impdef=on" or even what I settled on, "max,pauth=off" saves massive amounts of time, and should be used anywhere you are running debootstrap, apt, or python in an emulated environment. However, you can't blindly set it everywhere because these flags are not defined for other architectures and will cause a hard stop when emulating PC or RISC-V. This has also shown up in the Armbian Build System. If you want to see this first hand, use the example here. Just save the following in test.sh: echo -n "testing... " for i in $(seq 2 10000); do is_prime=1 j=2 while ((j*j <= i)); do if (( i % j == 0)); then is_prime=0 break fi ((j++)) done if (( is_prime == 1 )); then echo $i > /dev/null fi done echo "done" And then run it in docker after ensuring a few things are installed ... ~ $ sudo apt install binfmt-support qemu-user-static ~ $ time docker run --rm -it --platform linux/arm64 -v .:/test ubuntu:noble /test/test.sh testing... done real 0m37.620s user 0m0.013s sys 0m0.022s ~ $ time docker run --rm -it --platform linux/arm64 -v .:/test ubuntu:jammy /test/test.sh testing... done real 0m4.700s user 0m0.011s sys 0m0.023s And we can wrestle that performance back by fiddling with QEMU flags ... ~ $ time docker run --rm -it --platform linux/arm64 -v .:/test --env QEMU_CPU=max,pauth=off ubuntu:noble /test/test.sh testing... done real 0m4.694s user 0m0.011s sys 0m0.024s So qemu bug? Not quite. The qemu emulator is a host application, and is the same both jammy and noble docker images, and I think the root cause was found here, and first appears in Ubuntu Lunar (23.10). The short version looks like gcc's stack protection logic wasn't operating as expected as the stack layout is a little different than it is on PC, a CVE was filed, and the "fix" is now stressing a slow code path in qemu. For the record, my heart goes out to "steev" and his slow, hours-per-bisect march to the answer. Pulling that thread a bit more, the QEMU Documentation has the following to say on the subject of arm64 pointer authentication: The qemu docs also suggest that the qemu impdef algorithm is the default, but I've not seen this on my version. It's possible this may be addressed in a much newer version of qemu, but that's not available in the Noble repos. It could be overridden via tonistiigi/binfmt (but I've not yet tested that). For what it's worth, it's not possible to just add a simple wrapper to qemu fix this either, as seen in this Github Example, and that's due to the Linux Kernel Binfmt Interface. The 'F' flag forces the kernel to store a handle to the specified emulator, and make it available in chroot and Docker contexts, and that doesn't help if it's only the wrapper it grabs and not the emulator binary. Similarly, it's not possible to pass additional flags via this interface, so without a change to the qemu binary, the QEMU_CPU environment variable may be the only way to work around this immediately. The other curious bit is what does QEMU_CPU=cortex-a53 enable to recover qemu speed? The answer is absolutely nothing. it just turns CPU features off. At a glance, I'm not sure if that something qemu is doing indirectly, or glibc conditionally enables at runtime. If anyone knows better than I here, please drop a comment. The curious can check can via: ~ $ docker run --rm -it --platform linux/arm64 ubuntu:noble cat /proc/cpuinfo processor : 0 model name : ARMv8 Processor rev 0 (v8l) BogoMIPS : 100.00 Features : fp asimd aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp sve2 sveaes svepmull svebitperm svesha3 svesm4 flagm2 frint svei8mm svef32mm svef64mm svebf16 i8mm bf16 rng bti mte mte3 sme smei16i64 smef64f64 smei8i32 smef16f32 smeb16f32 smef32f32 smefa64 mops hbc CPU implementer : 0x00 CPU architecture: 8 CPU variant : 0x0 CPU part : 0x051 CPU revision : 0 ~ $ docker run --rm -it --platform linux/arm64 --env QEMU_CPU=cortex-a53 ubuntu:noble cat /proc/cpuinfo processor : 0 model name : ARMv8 Processor rev 4 (v8l) BogoMIPS : 100.00 Features : fp asimd aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4

@billymore I was able to detect my transpeed box using the toothpick trick. Here are some links that might help figure it out. Maybe even going on irc and asking the sunxi guys. https://oftc.catirclogs.org/linux-sunxi/search?q=tx1 https://groups.google.com/g/linux-sunxi/c/OrktE3duFDA

Hello Nick, Thanks for your reply. I tried to do this with a basic USB A to C cable, with an adapter on the USB-C part to have a USB male. The TX1 started (LED lit up) but no detection of the TX1 as USB device on my machine I'm using a Macbook M1 with Debian Linux VM to detect this. And the TX1 is never detected as USB OTG.

Hello, I'm stuck as well. I tried to boot on different version of Armbian made for H313 (X96Q) but without success (burning image on USB drive, booting with AV FEL button pressed during boot). LED remains RED and no booting. I tried miniarch. I tried to enter fel mode via USB and Debian virtual Machine witout succcess (the TX1 does not appear as USB peripheral during my USB FEL attempts).

This is required to use Armbian on the amlogic TV boxes. Enabling multiboot is one of the steps on the install instructions.

Thank you OP, I used HeliOS64 for a long time until it started to get disconnected after few hours of use that that was annoying. And so I stopped using it. I have just started using Claude-code. I am missing a remote backup solution. Claude-code gave me encouragement to revive it. I got directed to https://www.armbian.com/helios64/ to download, the only issue I found was that initially my 2.5Gbe worked and then after reboot stopped. Cloud code help me get that fixed. Below is what got it working again: # Step 1: Enable 2.5GbE (then reboot) echo "overlays=rk3399-pcie-gen2" | sudo tee -a /boot/armbianEnv.txt sudo reboot # Step 2: Install driver & Tailscale sudo apt update && sudo apt install -y build-essential dkms git linux-headers-current-rockchip64 cd /usr/src && sudo git clone https://github.com/awesometic/realtek-r8125-dkms.git r8125-9.013.02 cd r8125-9.013.02 && sudo ./dkms-install.sh Best of luck

Yes running on gnome-wayland session. jfl@orangepi5-plus:~$ apt list labwc Listing... Done labwc/noble 0.7.1-1build1 arm64

@billymore https://linux-sunxi.org/Tanix_TX1 Use a toothpick or any other non-conductive stick to push the button inside the A/V connector when powering up the box. Connect a USB-A/USB-A cable to the only USB port and a host PC. https://www.slashinit.com/posts/boot-uboot-orange-pi-zero-2-using-usb-mode/ https://linux-sunxi.org/FEL/USBBoot

Board: ODroid C4 Image: Armbian_26.2.1_Odroidc4_noble_current_6.18.8_xfce_desktop.img.xz Tested OK: - Installation to SD card - Boot to desktop, login - OpenGL / Panfrost - USB 2.0 - Ethernet Not tested: - Audio via HDMI (Though alsamixer reports there's stuff there) If anything, the serial console seems rather quiet. But attached ... minicom.cap

I have two boards I can test. ODroid C4 and NanoPi M4v2. I'll pull down the C4 build and give it a go. I don't see a build for the M4v2? (EDIT - Doesn't look like the Github action failed)

I don't use multiboot. I test also to put the sd-card on the SD-Card of box and with armbian images (both - xfce bookworm or the last version Xfce of the armbian site) don't work. I test images separately, I erase the SD-Card and then try the other version image, One by One. With the steps that I already mention above. I think that I can write documents on the device and system if that boot apps like Office should work I think but I only can test it if the system armbian boot. Thanks.

You don't need to decompile.this as the original source dts is available in the Linux git source code.

Have you used Armbian on other amlogic TV Boxes? I would never recommend using an amlogic TV Box as a mini pc. The graphical performance is poor. See the FAQ for TV boxes pined in this forum.

Why are you using USB? Does the box not have an SD card slot? Also what method are you using to enable multiboot?

I decompile the dtb [meson-sm1-sei610.dtb] to dts any idea if I can edit some option on it ? meson-sm1-sei610.txt

@Nick A Thank you for your excellent work! I managed to compile it myself and shared it with someone who has the same board (IK316-EMCP_V1.0). 1. Changed kernel preemption mode from full preemption to voluntary preemption. 2. Added MediaTek Wi-Fi drivers (MT7601U etc). 3. Embedded kernel headers. https://github.com/cdhigh/armbian_build/releases/tag/v20250306

Hello, I'm also interested in finding an image and getting feedback on Tanix TX1 QHZIW_H313_TX1_EMCP_V2.0. I bought this cheap box on Temu for 15 USD (2GB/16GB) I tried with USB drive and BalenaEtcher several images, without success (trying to boot on it, with tootpick on button) : 🔴 Armbian-unofficial_26.02.0-trunk_X96q-v1-3_bookworm_current_6.12.64_minimal.img.xz 🔴 Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img.xz 🔴 Armbian-unofficial_26.02.0-trunk_X96q-v5-1_bookworm_current_6.12.64_cinnamon_desktop.img.xz Based on my other experiences, this box, although close to x96q, is different. With X96Q, you just have to use SD card and boot was succesful. However, here, nothing is working. Looking for other's experience and advice.

Hello Orima, Thank you for asking. I am doing well. I've been mainly distracted by an online drawing class. I will try to make a complete written guide in the weekend. It will be a new project in my github, and I will make a new thread here.

i had to do it on my own, no worries but it surprised me about it.

I put extra dtb files that I download on /boot/amlogic . For example I find that devmfc uses meson-sm1-ac2xx-generic.dtb on /boot/dtb/amlogic. So I copy it to Armbian boot partition on dtb/amlogic/meson-sm1-ac2xx-generic.dtb Then I edit extlinux/extlinux.conf label Armbian_community kernel /Image initrd /uInitrd fdt /dtb/amlogic/meson-sm1-ac2xx-generic.dtb append root=UUID=7dc5c0a3-acfc-4d51-a066-6c14d983a9de 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 also test with other dtb files ad of course with the stock (default) image of Armbian just when donwload it, I use balenaetcher to write image on sd-card put it on a usb with sd-card reader and boot the tvbox, but doesn't work at all. The u-boot that I use is the u-boot-s905x3 that I copy to a directory and rename as u-boot.ext and then copy It to /boot. I oly try to run Armbian Systems from here → https://www.armbian.com/amlogic-s9xx-tv-box/ And I find devmfc when I search on google for " Debain s905x tv boxes" → thiss ystem works perfect, I only need to put on sd-card and put the sd-card on the usb with the sd-card reader and Tv Box shows HKSERIES and then go enter on the system devmfc. But I want some graphical friendly image to test the performance of tvbox as mini pc and because this I try to install xfce version of armbian. Thanks.

Please explain in more detail what you mean by these statements. "put dtb file" - there is no dtb file to put, just test the ones that are in the build and I would start with meson-sm1-sei610.dtb (which is the reference board for the s905x3 cpu). And what u-boot-* are you using? Also have you run any other linux distribution on this box other than an official Armbian build downloaded from this site?