All Activity

Upgrade to Armbian 25.11.2 successful.

Yes, it is a custom Armbian image (no coding needed) Download the Armbian build system from github Select panel-mipi-dbi to be a kernel module (M) Choose Trixie, minimal (the greeter+desktops available in Armbian need to be pure wayland, but the greeter is not) Try the DTS and firmware file again I will try to explain better tonight

@wolf7250fyi: I upgraded my Helios4 from OMV6 to OMV7 RC1 in February 2024 already. Upgrade went smoothly. But after that further OMV updates were not possible, solution found at https://forum.armbian.com/topic/23465-apt-get-update-fails-with-public-key-errors/?do=findComment&comment=178626

By helping cleaning gigantic Allwinner patchset so we can upgrade it to 6.18.y and merge already prepared Cubie a5e https://github.com/armbian/build/pull/8831 Then it become easier.

@Maxim Shell it’s possible to boot using USB OTG. You’ll need the latest u-boot. You can use my mainline build. Not sure if your stick has secure boot enabled. You can remove the secure boot patches if you don't need it. https://github.com/NickAlilovic/build/tree/mainline/patch/u-boot/u-boot-mainline git clone https://github.com/NickAlilovic/build.git --branch mainline cd build ./compile.sh build BOARD=transpeed-8k618-t BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED=browsers DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=trixie https://linux-sunxi.org/FEL/USBBoot#Mainline_U-Boot_.28v2015.04_and_newer_versions.29 build/cache/sources/u-boot-worktree/u-boot/v2025.10/spl/u-boot-spl.bin You can mount the compiled image to get the other files. sun50i-h618-transpeed-8k618-t.dtb uImage boot.scr I haven't done this before. Let us know how it works out for you.

Short of KIckPi opening a contract with Armbian and providing the units they want worked on. I don't see how?

How can I help with the development of Armbian for the Orangepi-4A?

Thanks @c0rnelius Is there a sustainable way of building working images for kickpi k2b v2?

Also I need wifi.

@Nick AIt has only usb and hdmi, no any SD card slots. Also I dont know anything that it has, I just need graphics acceleration, sound and support of usb, its all.

I haven't personally had issue with 6.17.y, but 6.18.y is a mess on meson-g12. It is basically unusable in my opinion. PCIe is hosed, even the patch that kind of fixes the issue just makes the error go away and doesn't fix the underlining problem "performance". I also get topology errors, but as I haven't really seen anyone yet complain about that, I'm assuming its me. For my personal use, I will be sticking with 6.12.y until things get sorted.

Hello! I'm so glad you responded! I've been trying to reflash this device for three days. Unfortunately, the behavior after reflashing is always the same: the red LED lights up, goes out after 15-20 seconds, and the device no longer shows any signs of working. I've reflashed the device about 50 times with different settings. And of course, I checked the "Write to address" box. I built the firmware from your git - https://github.com/vidplace7/armbian-build/tree/luckfox-lyra-ultra I also built the firmware from the Armbian office git. There were no errors during the build. I've built the firmware from Debian and Ubuntu. I've also tried various methods (again, I've been trying to reflash the device for three days now). I'm desperate. Would you be so kind as to post the firmware that works 100% for you and tell me how to flash it correctly? I'm pinning all my hopes on you!

There's no problem of course, I just did not have time for testing the built image yet, and was asking if it's not pointless. Thanks for the response so far, I'll try... As far as I understand it, the device tree from the vendor kernel won't work on mainline and I have no clue how to point armbian to the proper one. Maybe I'll just try removing the line about fdtfile from armbianEnv.txt lol

Yeah I ended up ordering a refurbished office mini pc, might repurpose the android box for something else down the line, like a pihole or something. Moved the plex server to my desktop and running it like that atm. That was pretty much all I was using the box for. Thanks a lot for all the help!

Hi @Mayuyu, I burned the image "Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz" using Balena Etcher onto an SD card, then inserted it into the box and booted normally. Before that, I had tested the MiniArch-20231112-6.6.2-board-h313.x96_q-SD-Image.img image, and I found that it resolved my boot issue after performing an update.

@Malay You were really close, from what I can see in your screenshot. You need to check the "Write by Address" box when using the Windows tool there, everything else in the screenshot looks correct.

This means to me that there is a power problem. That can be complex, with a backfeeding situation that exists with the CPU box but not with other computer. Might be electronically something damaged now, not impossible even if it worked for weeks. Might a different U-Boot that does incomplete initialization or does finally something correct but as a consequence that your setup does not work anymore. I see things initiated in the kernel log, but what is what is not clear to me. So maybe have a look at lsusb (with proper options) output. I must also say that USB connected storage is something I avoid. Wasted loads of time on it on RPI4, eventually made own power-supply, also battery fed now, that was main reason for own electronics actually. Else I could also have sold it, I have RK35xx devices now and use SATA from those and 12V based power.

moved

Thanks for the tip regarding armbian logs. I have a hunch that the hub is not the problem as it worked before reimagine and works on windows. here’s armbian logs: https://paste.armbian.com/hinutehewa

Hi, I suggest you try with a different powered hub see if there's a difference. However, please provide logs with armbianmonitor -u

@Робертс Hi friend, I tried your instructions, but I'm probably doing something wrong. My situation is similar to yours. Could you please tell me step by step what you did to get the screen working? I tried following this article, but it looks like you're using a custom Linux installation. I watched Pancake's instructions; he's building his own Armbian. I'd really appreciate it if you could give me a step-by-step explanation of how you set up these devices. I'm using the base Armbian from orangepi version 6.1.31 I also tried this DTS, but had no success with it.

Hi @wolf7250, I'm not familiar with OMV, so not sure what that update/upgrade process looks like. If it will update/upgrade the armbian packages to the latest release 25.11, then the correct version of armbian-bsp-cli will be installed. The installation of that package should update /boot/boot.scr and make a new U-Boot image available that you would have to install with nand-sata-install. Gr,

Hello, I have been trying to get sound working on my Orange Pi Zero 3, and I am facing persistent issues. I installed every operating system listed on Armbian’s Orange Pi Zero 3 page and followed all the standard setup procedures. Despite updating all packages and even performing kernel updates, I have never been able to get any sound output from the device. I have checked multiple configurations, tried different OS images, and ensured that all drivers are up to date, but nothing works. The device otherwise functions normally, but audio simply does not come through under any circumstances. Could you please provide guidance or a solution? Any help would be greatly appreciated.

It looks like the training of AI bots is getting to a stall. Anyway, a knowledgeable contributor does not feed the bots. Instead, they judge if the info from the bot can save their life. Will this bot come to my house with food for free and put it into my mouth. Asking the bot to give money first might look a good first thing to do, but it isn't. Even if real coins or paper and not bank transaction.

Ok. This might have been caused by a partial update. Running OMV there is a script to run to update to the latest in that version - in my case v6. Once that completes successfully then I need to run a release update script which will increment the major version to 7. But I never got that far. So maybe if I do the quick workaround to get me onto the latest and then the correct U-Boot and bootscript will then be included as you said in the latest? Hope that all made sense 😁