All Activity

Thank you so much! I will try it tonight!

You're in luck. Major work has been done. https://github.com/armbian/build/pull/9049 Still needs testing Once this is merged 4A and other more recent Allwinner Soc related work can be rebased on top of that.

That would be my best guess too. Check other PRs which add support for boards to get some clues how to achieve. If there are questions, feel free to state.

(https://www.pcgamingwiki.com/wiki/Vampire_Survivors) Vampire_Survivors is a 64-bit / Direct3D 11.1 game. You may not be setting DXVK (stripped) properly. Set var environments as below: export WINEDLLOVERRIDES="d3d12,d3d12core,d3d11,dxgi,d3d10,d3d10_1,d3d10core,d3d9,d3d8,dinput8=n,b" Download the DXVK (stripped) here: https://github.com/khanh-it/dxvk/releases/tag/releases (You may want to try to know which version works best for this game) Extract and then copy the x64/d3d11.dll, x64/dxgi.dll files to the game's executable file. If you're setting up the DXVK properly, you will see the output with something like the following:

Hi @Nick A, I have an identical motherboard as shown on page 1. Ik316-emcp_v1.0 2021.06.01 I can boot from the SD card, but it doesn't detect the internal memory. The Wi-Fi isn't working either, but that's already explained in the topic. How can I tell if the EMCP is damaged? Or if it's not being identified correctly? I have a CH431A available if needed. I believe it's possible to access UART via CH431. Previous reports suggest that the internal memory worked on this model, but I'm not certain of that. However, I must inform you that I was unable to install the supposed ROM on this model using PhoenixTool or PhoenixCard, This could indicate a failure in the emcp in the storage block. Thank you in advance for your support. boot.log

Well, two things. 1: The cpu clock changing on the fly was not the issue. That may just be an old issue with H3 series SOCs. 2: The XU4 likes running at 1.4ghz continually just fine. fwiw I'm using a newish 5v 4a power supply. It doesn't even get warm or spin up the fan while printing.

hello, is there any armbian build i can try now?

I just used wine-proton 10.0.3. While replace the wine to 11.0-rc1 to my previous proton environment, which is working fine on some games, such as VampireSuvivors, after installing Wine-mono, none game can be played. Comes out a dialog says that "Failed to initialize graphics, Make sure you have DirectX installed"

AFAIK, this is only good for installing a desktop,etc, NOT upgrading a version of Debian. I am trying to stay on topic here. So yes, "tasksel" will allow me to install a desktop but what is more pertinent to the situation I have would be to upgrade from "bookworm" to "trixie", if the "noble" release is going to be a stubborn problem for me. There is some other strangeness with the "noble" distro where for example I cannot run "synaptic" from the XFCE menu, instead I have to open a terminal and use "sudo synaptic". I am sure there are other issues as well. I doubt very much it is the pi-hole as the "bookworm" distro of Armbian has no DNS issues, nor do any Linux Mint/Dietpi distros that I currently use. Ditto with the Armbian "trixie IOT" distro currently available, that has no issues with DNS either. It would be ideal if there was a list of all the software that is installed in the current "bookworm" distro such that if I use the "Trixie IOT of Armbian" I can duplicate the desktop setup/installation which includes LibreOffice, Emacs, Firefox, etc. Where can I find that information or is there an install script that is used that can be downloaded for Armbian to install the software suite? Thanks for your help and understanding.

I also have the same problem, it used to work fine with an older version of armbian and the old 4.4 Kernel, but after an upgrade it just stopped working. The following should serve as a test when connection MOSI and MISO: ~# dd if=/dev/urandom bs=1 count=16 status=none | spi-pipe -d /dev/spidev1.0 -s 1000000 -b 16 | hexdump -C Querying my MCP3008 it just returns all zeros: ~# printf '\x01\x80\x00' | spi-pipe -d /dev/spidev1.0 -s 100000 -b 3 | hexdump -C 00000000 00 00 00 |...| 00000003 I'm using the following DT: /dts-v1/; /plugin/; /{ metadata { title = "Enable spidev on SPI1"; compatible = "unknown"; category = "misc"; exclusive = "GPOI3_B2", "GPOI3_B3", "GPOI3_B4", "GPOI3_B5"; description = "Enable spidev on SPI1 on pin 39, 40, 41 & 42."; }; }; &spi1 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&spi1_clk &spi1_csn0 &spi1_miso &spi1_mosi>; #address-cells = <1>; #size-cells = <0>; spidev@0 { compatible = "rockchip,spidev", "armbian,spi-dev"; reg = <0>; spi-max-frequency = <50000000>; }; }; The SPI is showing up, but it's just always producing zeros, it seems there's just something wrong with a newer SPI driver or something, maybe a new kernel upstream fix or kernel patch is needed here. I sadly don't have a backup of the old image to test with, but it the same rust software I wrote that worked before, doesn't work anymore now and it can't even talk to itself anymore. I don't have an oscilloscope to see exactly whats going on, but something funky is happening with the clock signal indeed: ~# cat /sys/kernel/debug/clk/clk_spi1/clk_rate 108333334 Max clock should be 50M as per the DTS file, but it seems the driver just ignores this. Event though spi-config shows something else (when reconfiguring it): /dev/spidev1.0: mode=0, lsb=0, bits=8, speed=100000, spiready=0 I also don't find any way to build an old kernel 4.4 image anymore (the legacy branch doesn't exist anymore), so I can't do that either and the edge-based Kernel 6.18.0-rc6-edge-rockchip64 also don't bring any improvements it seems.

Have you tried other wine/proton versions?

Realistically I can't promise that. But I think with very small patches this board can work (it already does, minus the ethernet and armbian-install). I will try to solve the problems in this board and then post my solution here (as a single post, not as a series of posts). I don't think it needs to be added to the list of supported boards as long as this thread is indexed by search engines and someone else with the same board can use these forums to successfully install armbian on orangepi cm5.

Probably the latter. https://docs.armbian.com/User-Guide_Board-Support-Rules/ has more information. We already have a lot of boards in Armbian. Probably too many from a maintenance POV. Do you simply want to do the work of bringing up your board in Armbian or do you want to become the maintainer of this board going forward? That's an artefact that @Igor may be able to fix. The page should not really exist at this point.

I decided to klipperize an old 3d printer and found some of my orange pi boards dead, so i ended up selecting my XU4 for the task. Fast forward 24 hours and i'm fighting MCU timeouts. Klipper doesn't know what happened just that the mcu stopped responding. And their knowledge base article is basically "gosh it could be anything". One seat of the pants observation i made was that the XU4 idles along at 600mhz with a load average of about 0.1 and it seemed like the load average increased maybe before the mcu stopped responding. The MCU in question is an SKR Pico, aka rp2040 with a usb connection. The mcu is not receiving power from the xu4 (there's a jumper) - I've tried both usb3 and usb2 ports on the XU4 with no difference. I recall that many years ago i resolved a similar issue with an H2+ based board and Octoprint by switching the cpufreq governor to "performance" which of course just pegs it at the top speed. But on that board, armbian-config lets me select what that maximum speed is, so as to avoid overheating. My XU4 is equipped with the flat little fan. I do have some large heatsinks and thermal adhesive. I'm a little worried that it might run too hot if it's at 1.4ghz all the time. sysfs tells me there are a ton of scaling frequencies available, but it appears that i can't just, select one. Any hints?

Thanks for sharing your updates, any idea about the function of the 8 pin holes close the lcd display?

Weird. I set verbosity to 7 but still nothing. See this https://paste.armbian.eu/zubunigowi.vbnet Nothing afterwards. Claude suggested adding the parameter SERIALCON="ttyS0" because apparently the default is ttyS2, which does not match rk3528. Let's see if it's just a hallucination. EDIT: nope. Still no luck. EDIT2. Something is wrong with the serial console on the vendor image too. I cannot type in it. It is connected correctly.

Is there a specific reason why orangepi cm5 isn't supported? Or is it simply because nobody has contributed? Because I am willing to add support for it if there aren't any serious issues when building armbian for this board. The webpage for the board is currently empty. I see two issues when using Armbian on orangepi cm5: 1. The ethernet and the fan won't work. There is a device tree published by Laurent Pinchart that may fix this. 2. armbian-install bricks the board. The only way to recover the device is by enabling maskrom and using rkdeveloptool to flash a new image. Other than these Armbian seems to work fine on orangepi cm5. Has anyone tried using (and also installing) armbian on this board?

@Mohammad Adel You need a image with a AXP313a (Power Management IC). Try these images. Armbian-unofficial_25.05.0-trunk_Tanix-tx6s-axp313_bookworm_edge_6.12.11_xfce_desktop.img.xz Armbian-unofficial_25.05.0-trunk_Transpeed-8k618-t_bookworm_edge_6.12.11_xfce_desktop.img.xz Armbian-unofficial_25.05.0-trunk_Vontar-h618_bookworm_edge_6.12.11_xfce_desktop.img.xz Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img.xz If it still doesn't boot. You might have secure boot enabled. You can try to compile this image. It includes secure boot. https://github.com/NickAlilovic/build/tree/mainline If it's still not working. Then it might be your Dram Settings. You should install a Usb to serial device on your UART. So we can see your debug messages.

@MrBros1509 I think you want to read this thread:

@Galeno Fernandes What does your question have to do with Armbian? It doesn't look like you are using Armbian at all. These forums are for Armbian linux.

Set verbosity to 7 in armbianEnv.txt to get an idea about what happens after "Starting kernel..."

Yup, there are numerous boot attempts if you take a look. There are two that are successful but not much happens afterwards, look for "Starting kernel". So when it finds the tree, it "boots" but there is no further output.

Make sure the file is there and name is correct

The kernel seems to be starting but there is no further output from the serial console. Here are some attemps (forst one with FDT commented out, which prevented the kernel from loading, the last ones also, maybe due to SD card corruption). The green light is on and the blue light is pulsing. This is the config it came up with with my guidance: # Rockchip RK3528 quad core 1-4GB SoC WIFI/BT 0-32GB eMMC BOARD_NAME="ROCK 2F" BOARD_VENDOR="radxa" BOARDFAMILY="rk35xx" BOOTCONFIG="rock-2-rk3528_defconfig" BOARD_MAINTAINER="CodeChenL" KERNEL_TARGET="vendor,edge" KERNEL_TEST_TARGET="vendor" FULL_DESKTOP="yes" BOOT_LOGO="desktop" BOOT_FDT_FILE="rockchip/rk3528-rock-2f.dtb" BOOT_SCENARIO="spl-blobs" IMAGE_PARTITION_TABLE="gpt" enable_extension "radxa-aic8800" AIC8800_TYPE="usb" function post_family_config__rock-2f_use_mainline_uboot() { # use mainline uboot for _edge_ [[ "${BRANCH}" == "vendor" ]] && return 0 display_alert "$BOARD" "Mainline U-Boot overrides for $BOARD - $BRANCH" "info" declare -g BOOTCONFIG="generic-rk3528_defconfig" # Use generic RK3528 config since rock-2f specific config doesn't exist yet in mainline declare -g BOOTDELAY=1 declare -g BOOTSOURCE="https://github.com/u-boot/u-boot" declare -g BOOTBRANCH="tag:v2025.10" declare -g BOOTPATCHDIR="v2025.10" declare -g BOOTDIR="u-boot-${BOARD}" declare -g UBOOT_TARGET_MAP="BL31=${RKBIN_DIR}/${BL31_BLOB} ROCKCHIP_TPL=${RKBIN_DIR}/${DDR_BLOB};;u-boot-rockchip.bin" unset uboot_custom_postprocess write_uboot_platform write_uboot_platform_mtd # disable stuff from rockchip64_common; we're using binman here which does all the work already # Just use the binman-provided u-boot-rockchip.bin, which is ready-to-go function write_uboot_platform() { dd "if=$1/u-boot-rockchip.bin" "of=$2" bs=32k seek=1 conv=notrunc status=none } } Here is the log: pastebin Any ideas? I observed that with some boards, the line "BOOT_FDT_FILE=..." is absent altogether. is removing it possibly the way to go?

Hello everyone, I’m trying to flash a firmware on a generic Android TV Box and I’m stuck at a hardware/bootloader compatibility issue. Device technical details: - SoC: Allwinner H618 - Board / PCB: FX-H618-D4_V10 - RAM: 4GB DDR4 - Storage: eMMC (unknown size, likely 32GB) - USB FEL ID: VID_1F3A PID_EFE8 - Original OS: BigdroidOS (Android generic) - Commercial name: Transpeed 8K618-T Current situation: - Device enters FEL mode correctly (VID_1F3A PID_EFE8) - PhoenixSuit detects the device but firmware upgrade hangs at “Beginning Firmware Upgrade” - Tried multiple PCs (Windows 10 and 11), different USB ports and cables - Allwinner FEL driver installed correctly - SD card flashing with PhoenixCard (Startup mode) is ignored, device boots normally to Android - Reset timing variations tested (short press / long press / no reset) Tested firmware: - sbx_transpeed_h618_atv_12_11.img - H618.apollo-p3.T-H618_100M_12_FD650.2023.09.13.1720.img Both firmwares show similar behavior (FEL detected but no successful flash). I believe the issue is bootloader / DDR4 initialization mismatch. I’m specifically looking for: - A firmware confirmed to work with board FX-H618-D4_V10 - Or the original BigdroidOS firmware dump for this board - Or confirmation whether this board requires a specific boot0/boot1 Any help, working firmware, or dump from the same board would be greatly appreciated. Thank you! Allwinner H618, FX-H618, DDR4, PhoenixSuit, FEL, Transpeed