Active threads

Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img This works for my 1.1 board

What happens after this is needed. make sure loglevel is 7 in armbianEnv.txt Hopefully yo have a serial console cable so you can copy and paste the text here on the forum, is better than pictures on imgur (site is blocked in UK by the way)

moved

I operate an Odroid HC4, that has 4 x A55@1.8 and the board discussed here has 8 x X60@1.?. A fast sysbench says: single thread on OpiRv2 is slower (792 vs 1034) , multithreaded is faster (6342 vs 4151). Compiling a current kernel on RV2 needs 3 hours, nothing one would do do regularly. If you really need speed buy a Radxa Rock 5 (see platinum support devices on this site). Edit1: NPU -> Opi Wiki, USB and SPI yes, for MIPI DSI/CSI you need to test yourself. Edit2: Just remembered that I have a H618 (Opiz3). Single=708, Multi=2828 with the same Trixie sysbench. HTH + LG // Sven-Ola

ok

You use a Desktop/Xfce installation, and it is for a low-power ARM64 computer. So I would not be surprised if in modern Xfce, the Power Management default to suspends after 30 minutes or so. Last time I used Xfce was when Debian Buster, also then in then I remember in the GUI there should be some system setting where you can configure power settings. So there you can make sure that it never enters suspend state. I do not know how to configure that from command line, but that should also be possible, maybe search internet. You can also look into the journal and see what happened, maybe something is wrong. 7 Watts is way too high for suspend state at least, but maybe things connected on USB still draw power and is it only the CPU that is halted. Other option is not to use a Desktop image/installation, but a CLI for server/IoT variant. Those images should have suspend disabled.

This might help you: https://github.com/nyecov/roobi-config-anyOS It details how install basically any OS via Roobi

Just confirmed. Running bookworm on the same RockPi-S, it "just works". Any suggestions on what happened in Trixie and if there's a fix?

I missed the fact that you have an orange pi zero 2w... I think there's a success experience with that orange pi in this thread or in this Allwinner section. Please share if you have success

That's the version I'm running as well, and I have no issues either. I think replacing the device tree (.dtb) at this point only helps with the onboard flash speed?

Ethernet should be working (after rebooting), but wifi doesnt work out of the box.

I currently have a X96 Air S905X3 4GB/64GB box that has 1Gbit ethernet and a USB 3.0 port that works well with Armbian. This was bought 5 years ago for only 35 USD. I would like to find another box for Armbian that also has 1000M/1Gbit ethernet + USB 3.0. The same or similar boxes are selling for 50-60USD at the moment which is a lot for an old box. Are there any other boxes with 1Gbit ethernet at a low price that work with Armbian? Not bothered about other features, wifi quality, performance otherwise - just Gbit ethernet and USB 3. Open to all processors - Amlogic, Allwinner, Rockchip etc

mxq pro 4k maybe "shortpin" Hope it is useful

Maybe are you experiencing the same issue ? https://forum.armbian.com/topic/56946-h3-reboot-issue/

Today I needed to reboot one of the Orange Pi which is at a remote location.... It did not come back to life.... Maybe some update removed the extraargs=reboot=warm parameter ....

No standard way to do what you want. The Armbian images from this site depend on the original android bootloader on the emmc to boot. Since you don't have working emmd these images wont boot. Theoritically if you found a working boot loader for your box and it was put on the SD card, then you would have more options.

Hi Armbian community, I'm trying to install Armbian on my Worldchip K16 tablet and would appreciate guidance on compatibility and installation steps. Device Specifications: · Model: Worldchip K16 · SoC: Allwinner sun50iw10p1 (likely A64/H5 variant) · CPU: Quad-core Cortex-A53 (ARMv8 64-bit) · Current OS: Android 11 · Architecture: aarch64 (ARMv8l) · GPU: Mali-400MP2 (typical for this SoC) · RAM: Unknown (estimated 2-4GB based on similar devices) · Storage: Unknown (likely 32-64GB eMMC)

Hi all. I reproduced the same behaviour on my custom uboot built with enabled debugging. The problem is not solved, but I got more detailed information. It turns out spl freezes at loading main uboot loader. Here is part from logs: Jumping to U-Boot... SPL malloc() used 0x198 bytes (0 KB) image entry point: 0x4a000000 More detailed logs can be found here

So if this works for you and you apparently know how to change bootloader, I can not really say or conclude more in addition to what is already said. I do not use images nor Imager and also do not own the ITX, I only tried to see if this issues is maybe something RK3588 generic.

Hi all, I know this is a bit of a long shot given the age of the hardware, but I’m wondering if anyone here has ever experimented with running Armbian on an EVPad 2S (the old Android TV box). I’ve been tinkering with some older devices and thought it might be interesting to see if this one can be repurposed. I’ve attached a screenshot of the system info - unfortunately, it’s pretty sparse. The box is running Android 4.4.2 with kernel version 3.4.39, but the processor type is listed as “UNKNOWN,” and I haven’t found much documentation on the chipset or board layout. so before I dive deeper I wanted to ask: Has anyone managed to get Armbian (or any Linux distro) running on it? Are there known limitations with the chipset or bootloader that make it a dead end? Any tips, resources, or even “don’t bother” experiences would be appreciated. Thanks in advance for any insights - sometimes these older boxes surprise us, but I realize support may be very limited.

Hi @ff255, It's been a while, I'm assuming you are still getting the same error as mentioned below: Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... The output you shared helps, but can you share a little bit more? Would need to know the following for your case: Filesize of your kernel image file Filesize of your initrd file If possible, filesize of the DT file being loaded. With those three values, we should be able to calculate the correct load addresses and try booting. (All this also presuming that your issue is that the load addresses used by U-Boot/the bootscript do not leave enough room for either a kernel or initrd file, causing one of those to overlap the start of the other.) Groetjes,

Hello all, nice to see helios64 is still alive. I have mine and i was a bit worried about needing to switch to something else, there is not really other stuff as cool as this one. I'm using my helios64 since i go it for small it task: small webserver, xmpp server, vpn, NAS. Btrfs "raid1-like" work without issue for me an allow me to upgrade the disks one by one (it allow different sizes). The UPS shutdown mechanism stuff still work without issue. I'm thinking about upgrading it to armbian trixie to use quadlet (podman feature) on it. I just have to find the motivation. It frighten me a bit because there is very few discussion and mostly about issues in this forum.

Yes you can work to make things better. But since I don't have this box (nor even one with that specific cpu version) there isn't anything I can really help you with. But anything you find/improve can be submitted back to Armbian as a PR. This stuff is all community supported, thus it depends on people like you to make improvements and submit them back for others to benefit from.

Hi Everyone, I managed to have it booted off the SD card only without FEL fiddling (also because my A-to-A OTG cable was dumb so I've soldered a UART and get on there trying to dodge the hardcoded protected boot on eMMC by playing with u-boot and tricking it with DTB hacks forcing an internal eMMC disable in favor of SD boot.) I've ultra simplified the procedure for mere mortals: 1- Flash Pine64 Armbian image on an SD card 2- Flash the "magic 1st Magabyte" (dd brutally the first meg) 3- Insert the SD card in your Remix Mini 4- Boom The stupid part is that I've done this in a 24 hours rush and kind of tried of backtrack what I did to make it happen... I'm not able to reproduce it but I have all the notes here: https://gist.github.com/penzoiders/582bfab2c9265716dd375fb5e7679bcf if anyone of the deveolpers is interested in this I can ship to the maintainers a couple of units (I have dozens of these used-to-be-ewaste devices). I'll attach the 1M magic boot sector. remix_mini_armbian_first_1m_pine64.bin

A long time ago, I made an armbian guide, which included adding a kernel patch. Can you try this method? "Move them* to ~/armbian-2023.05/build/userpatches/kernel/archives/sunxi-6.1 (using the scp command or sshfs)" * would mean the cpio file (use diff3 to convert to patch file**) and any linux configuration patches needed to make your initramfs. ** diff3 linux_orig_source_folder linux_source_folder_with_cpio_file https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md#73-add-the-tv-encoder-driver-to-the-linux-kernel-source