All Activity

Ok, maybe I made a mistake before. I tried with an no secure-boot .img file and it give a long list of DRAM params and I put it in the file below. But I don't know What I can do with it... I will appreciate your help. Thanks. DRAM_Transpeed_M98txt

I received my new LCD today. It is a 9486 but luckily it worked with my 9488 dts HOWEVER: The touch xpt2046/ads7846 is not sending any events…checking with evtest… same dts works with the ili9488 4.0” I already tried changing the GPIO polarity (level and clock transition) has anyone worked with any of the red 3.5 lcd ili9488 or 9486

Thanks again @Nick A, I already did it, the file I got, cant understood well, and there are very low information about dram, just 3 params dram {phandle = <0x7a>;}; vcc-dram = <0x04>; dram = "/dram"; dtb.0.dts

I don't think increasing the SPI clock can help Try adding "BGR=<1>;" under the rotation line... this works for the ili9341, but i dont know about the driver that you use.

Hi Dan, how did you go with this one. Any luck? I didn't know these chips supported sleep and hybernate modes.

hello, agesome! The same thing happened to me, test 20mhz (20000000), I suggest increasing above 32mhz and test. I'm using mine at 46mhz and it's normal, but it used to give an error, it wouldn't update the screen, it would freeze, now it's normal because I disabled “dma-names=””;” Try it and let me know.

I tried, unfortunately the other one I have here at home doesn't recognize when I use it. To try another one, I'll have to buy a new one... =(

I have uploaded an updated version here. Also, for thoses who want to use internal emmc (boot without sdcard), you can run this script: You can reinstall android using this, connecting DQ08's usb2 port (using a male-male usb cable) to the computer while pushing the button in the AV connector. Then, in the app (extracted to c:\), choose firmware / firmware.bin / restore / run.

Armbian_community_25.5.0-trunk.538_Orangepizero2w_bookworm_current_6.12.23_minimal.img When try to boot. It get stuck trying to boot from emmc. It does not have emmc. After several power restart sometimes it boots form microsd. also it ask for tags which has only one option "Solved". I had to tag this topic as solved in order to be able to submit it.

It could be a problem with the solder Buy a board from https://www.armbian.com/partners/

I was hit by this on a fresh install (after I had to replace my SSDs due to SMART errors). Can confirm that Armbian_community_25.5.0-trunk.538_Helios4_bookworm_current_6.6.90_minimal.img.xz now boots and works again. Thanks, @djurny for your great work!

@rafaeldavid Try a different sdcard.

At a guess, you are probably running the panthor gpu driver rather than the mali kernel driver. To check this, run something like: sudo dmesg | grep -i panthor and report what comes back. Further information can be found at https://forum.jellyfin.org/t-rockchip-transcode-missing-dev-mali0 Hope this helps,

This week, the Armbian development team pushed several noteworthy enhancements, with improvements spanning user experience, bootloader upgrades, and broader system support. Notably, this week saw the debut of OpenMediaVault in Armbian’s software installer, a move that brings plug-and-play NAS functionality to supported boards. OpenMediaVault is a feature-rich platform that enables users to turn single-board computers into fully-fledged network storage devices. Thanks to a contribution by Igor, the integration is now available through armbian-config interface, giving users a streamlined way to install and configure OpenMediaVault without needing to manually manage services or packages. The usability of the software stack also saw a meaningful improvement. A previously persistent “Disable Wireless Hotspot?” prompt was eliminated when no hotspot had been enabled, reducing unnecessary friction during the setup process. This fix helps clarify Armbian’s default network behavior for users during first boot, particularly when configuring headless or appliance-style deployments. On the hardware front, the Orange Pi 5 Max received a key upgrade: it now boots using mainline U-Boot. This transition replaces vendor-specific boot code with upstream-supported U-Boot, easing future updates and kernel integration. A related improvement was made to the PocketBeagle2, which migrated to extlinux for boot configuration—bringing it in line with Armbian’s broader standardization efforts. Further enhancements came to the Rockchip64 platform. Previously missing Operating Performance Points (OPPs) were added to ensure proper voltage and frequency scaling across supported boards, which improves energy efficiency and stability under load. In addition, older workarounds for wireless firmware issues were removed, as upstream drivers have now resolved the compatibility concerns that necessitated them. Finally, infrastructure refinement continued with the cleanup of unused or deprecated build artifacts, keeping the codebase lean and future-proof. The team also laid the groundwork for upcoming testing initiatives to ensure that new features like OpenMediaVault are validated across a wide array of supported devices. For those interested in exploring OpenMediaVault or other curated software installations, the updated documentation is available in the Armbian Software User Guide. The post Armbian Updates: OMV support, boot improvents, Rockchip optimizations first appeared on Armbian. View the full article

Using screen is sufficient. No settings besides baud rate (115200 for any Allwinner) need adjustments. As mentioned above make sure your serial device is correct. If you are unsure, simply - unplug - run sudo dmesg -ew - plug in and check output in the terminal with the command above. Also make sure wiring is correct. Ground to ground and rx/tx crossed.

You don't have to trust/use torrents to download Armbian. All images are available via http/s download as well. We cannot do anything against people (ab)using torrent protocol for non-legal things nor can we control where these torrents spread/end up if this is your main concern. If you are concerned that an images you have downloaded is non-geniune run a check before proceeding with installation: https://docs.armbian.com/User-Guide_Getting-Started/#download-and-verfication

You could use this tool to extract your dram settings from an android update or boot0.bin. https://github.com/apritzel/sunxi-fw sunxi-fw info -v boot0.bin

I tried, nothing happens, it stays on a black screen. 😪

It shouldn’t take that long.. did you try booting without the sdcard?

@Igor Fans working great with fancontrol. I have 92 MM Noctua Fan attached and it is working perfectly. I can adjust the configuration as described here https://wiki.kobol.io/helios4/pwm/ @all I also edited the default 2.5 inch drives case provided from helios4 (replaced fan mounts from default 70 mm fan to 92 mm fan) and added holes to mount ssds horizontally as well using 3.5 to 2.5 metal adapter from aliexpress .. It looks like this.. Very quiet and the drives stay cool.

From logs I can only conclude that problems are at your side - wrong configuration. Anyone can help you - problem is almost certainly not Armbian specific. May 10 21:05:09 pirogue systemd-helper[8502]: dnsmasq: unknown interface end0 May 10 21:05:09 pirogue dnsmasq[8502]: unknown interface end0 I am not an expert of application you try to install, in fact I never heard about until now.

I would like to create Lab with PiRogue and add suricata custom rules for Pegasus attack preventions: https://pts-project.org/guides/g7/ I would like to use internal PiRogue_VPN_server and add additional 3x-ui or S-ui server with xray-vless-realty as second layer because mobile operators or internet providers from specific country like RU or CN may block simple wireguard proto, this will be looks like: NanoPI_R4S with [ PiRogue(internal_wireuard) -> XRAY_server(xray-vless-realty) ] -> Android Phone with XRAY client(xray-vless-realty) and host level firewall that will be forward all mobile trafic to the VPN client NanoPI + Arambian lasted with all updates For PiRogue installation I use the instruction: https://pts-project.org/docs/pirogue/installation/ Step #1 sudo apt-get update sudo apt-get dist-upgrade Step #2 sudo apt-get install wget sudo wget -O /etc/apt/sources.list.d/pirogue.list https://pts-project.org/debian-12/pirogue.list sudo wget -O /etc/apt/trusted.gpg.d/pirogue.gpg https://pts-project.org/debian-12/pirogue.gpg sudo apt-get update sudo apt-get install pirogue-base I have PiRogue's after installation message: My currient problem is starting process of a dnsmasq.service on my NanoPI_R4S Dears @Igor @Werner could you pls help me or forward to nanopi r4s maintainer that may fix the prob I alredy describe similar problems with "systemd-networkd-wait-online.service" in my previos my topic, see link: or pirogue_log.txt

Yes, I installed the efi version on SPI when I thought I could boot UEFI images that way. And that's what I kept because I had no problem booting other uboot images, like the joshuas archlinux one I'm currently using to write this. Now I'm downloading the last one you posted because I'm so stubborn. But after that, I plan to boot with version 20240201-current to install a new uboot on SPI.

How long does it take? I left it on overnight, for about 11 hours, and it just stayed on the same image. The upgrade was just for testing... But I've already redone Armbian to the original.

WOW, I was really unhappy when I saw this, just goes to show you not to trust even projects like ARMBIAN on where they will connect to from your network, advise before anyone finds themselves in trouble having to explain why some of these connections..... I was downloading Armbian image and then got a warning that I couldn't connect to site called "FOREVER PIRATES" and became concerned... You can read it yourself... https://imgur.com/a/IQyzlvr