Active threads

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. 😪

@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.

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.

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

I went back to the default Armbian rootfs. The Arch rootfs broke the boot, probably due to the use of the latest systemd. It is possible to mitigate this but it is not worth it. Now I am running normally from the sdcard, I just wanted help with the armbian-config options. I know that led-conf7 and uart2 are correct for my board, right? I'm still looking for the others in the thread And what do I have to do to make the wifi work?

Thanks for all the info! As I can see the device fine, I'm assuming my DT is alright. I think I'm going to try some other images (ie. debian, main kernel, etc...) and see where it leads me, maybe I can get a hint of what's happening. I can change devices fine in KDE, the jack detect works as I see it toggle, but I don't get anything out. HDMI audio works fine though. I've seen some weird audio stuff a long time ago, I'll see what little I can remember since it doesn't seem to be something blatantly obvious. I have a hunch or two but unlikely to make any difference Ubuntu making it worse doesn't sound good to me... hehehe (pun intended) I'm planning to use it as a 2nd desktop/media player, most of the time I don't need the "power" of the "workstation" so running the opi works great (well, will hopefully) I went with KDE since that's what I'm using on the "workstation". To be honest, there's very high probabilities I'm going to buy a USB sound card and be done with it, but it feels like a waste.

It was solved https://github.com/armbian/configng/issues/344 , but It looks like bug with overlay_prefix back again

Hi, are you using a usb to serial converter or the real serial com port? I did not see any ttyUSB0 listed in your boot log. In case of the real serial com port you should not be using /dev/ttyUSB0, but /dev/ttyS0.

So I decided to modify the armbianEnv.txt with the values you provided and it has moved to "Starting kernel..." It is taking quite a while to boot. The older version seemed to take quite a while as well but this seems to be hanging possibly. I tried changing the armbianEnv.txt verbosity to 7 but it is still stuck on Starting kernel... U-Boot 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-V1f00-Bb703-R448a (Mar 16 2025 - 04:03:33 +0000) Allwinner Technology CPU: Allwinner V3s (SUN8I 1681) Model: PineCube IP Camera DRAM: 128 MiB Core: 47 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28800 Out: serial@1c28800 Err: serial@1c28800 Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 5475 bytes read in 2 ms (2.6 MiB/s) ## Executing script at 41900000 U-boot loaded from SD 227 bytes read in 1 ms (221.7 KiB/s) Load fdt: /boot/dtb/sun8i-s3-pinecube.dtb 12286995 bytes read in 509 ms (23 MiB/s) 11013984 bytes read in 456 ms (23 MiB/s) Found mainline kernel configuration 19691 bytes read in 4 ms (4.7 MiB/s) Working FDT set to 41000000 Kernel image @ 0x41080000 [ 0x000000 - 0xa80f60 ] ## Loading init Ramdisk from Legacy Image at 42080000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 12286931 Bytes = 11.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41000000 Booting using the fdt blob at 0x41000000 Working FDT set to 41000000 Loading Ramdisk to 42248000, end 42dffbd3 ... OK Loading Device Tree to 421da000, end 42247fff ... OK Working FDT set to 421da000 Starting kernel ...

https://libera.catirclogs.org/linux-amlogic/2023-11-18# It appears the bl30 blob is the only non free software file required for the le potato. What can you tell about the bl30 blob? Can it get reverse engineered? Where can you get the bl30 file? Thanks.

If you don't need GPIOs, don't take SBCs - they are too expensive, without a case and power supply. For the same money, you can buy a mini X86 PC such as razen5 4600 and you will have no problems with support. If you need an ARM, then buy an H96 Max V56 from two TV boxes. The time of SBCs has come to an end - they are no longer so popular and are mainly needed by developers. Leave these SBCs to the developers!

I was looking for a solution to this for a long time before seeing John's post and figuring it out. Here's a more explicit explanation to hopefully help make this info easier to find. This was tested and does work on both the Orange Pi 5 16GB, and the Orange Pi Zero 3 4GB. I haven't run into this issue on my x86 nodes as it doesn't appear zram exists on them at all on a fresh install. If you go to the /etc/default directory, there should be a file called <distro>-ramlog. If you're on armbian it will be armbian-ramlog, for me on Debian it's called orangepi-ramlog. In this file there will be a line reading "SIZE=50M" Simply edit this line to whatever value you'd like, and then reboot the device. If rebooting the system will cause serious problems, you can use the following command on armbian: service armbian-zram-config restart Again, I'm using the official Orange Pi Debian image, so for me, the command would instead be as follows: service orangepi-zram-config restart Don't panic if you notice that this command results in the creation of a zram2 and zram3, as these duplicates will automatically remove themselves the next time you reboot the machine

Hi all, I was quickly able to get the 3.5inch RPi LCD (B) working with an Orange Pi Zero 2W, but the colors are all wrong, it seems that it wants BGR. Any hints where to change color order? I could not find anything for the DTS. Using this driver with following DTS:

Hi catotinha, Can you please share which image you successfully used, and where you downloaded it from, please? Thanks!!

Hi Pilinha and Werner. My problem was that I misidentified the board and thus installed the wrong software. https://forum.armbian.com/topic/51779-orange-pi-plus-2e-usb-ports-not-working/ Thanks for your help, I learn a few things here.

OK .. now i must "cleanup" all voltage regulators

https://www.loverpi.com/collections/le-potato It says open-source support. Free software is software you may use, share, modify and redistribute. Can le potato run entirely on free software, such that there is no piece of non free software on the computer? If so are the armbian le potato images free software images? https://www.armbian.com/lepotato/ Thank you.

This may or not be the case. Looking through the Ubuntu bug tracker, I find a lot of similarly failed upgrades. But at least ports.ubuntu.com was not disabled in the past: https://launchpadlibrarian.net/757026143/VarLogDistupgradeMainlog.txt from https://bugs.launchpad.net/ubuntu/+bug/2086530

Sounds like an error with X. @ALL above: Did you recently update any packages? Please pastebin or attach the content of the ~/.xsession-errors file. Go and search for it if necessary "sudo find / -name .xsession-errors*"

A quick google search seems to suggest that the Orange Pi Lite is prone to overheat. Obvious question that you did not mention in your original question: Do you have a heatsink installed? Is there sufficient airflow? In general, are you sure you want to use this board with a mate environment? Even if you get to work around the heat issues. RAM and CPU are likely to cause this to be a bit of an underwhelming experience.

Hi @Vaclav Rada, You can also disable the systemd 'predictable naming convention' of interface naming by adding: net.ifnames=0 to your kernel commandline. This can be done in armbianEnv.txt by adding them to the extraargs variable as follows: extraargs=net.ifnames=0 Would be better to adjust your armbianEnv.txt instead of changing on-disk systemd service unit files, as they will be overwritten whenever an update comes along. I have not seen a situation myself where using the 'new' naming convention for network interfaces would work out better. But perhaps my use cases are not as flashy as other's 🙂 Groetjes,

Probably topic name was changed, because originally my case is that bootloader doesn't even read dtb or extlinux.conf, it says no partition table on mmc 1. My box has thgbmbg7d2kbail. If booted from sd or usb it can access mmc without a problem.

Thank you for reporting back. Glad you got it solved.