All Activity

spendist is the maintainer of the Nanopi Neo. Maybe he has something to say. Did you try another kernel? Another OS?

I've already performed that search. The connector on the motherboard is a Mini Molex 8 Pin connector. Here is a link to the Kobol website with an image of the harness. HDD Cable Harness

Awesome! Please do elaborate. Please do elaborate. What is the cargo cult practiced here at Armbian? I'm old, but I'm still interested to learn, so please do teach me.

That is surprising. I don't think they are custom. Isn't this what you need? Or this one for just 1€. Search for "SATA power cable" and skip the 4-pin ones.

Excerpts are often useless. Provide full logs using the curl command from the end of each run. If the used hardware isn't very powerful, yes, can be.

Kobol went out of business years ago. I don't think you will be able to find replacement parts.

A google search indicates that the MXQ Pro 4K 5G often uses a RK3229 quad-core CPU

Hi All I've made for my sbc image, however found during this process messages including 1 marked as error : ``` Error response from registry: failed to fetch the content of "ghcr.io/armbian/os/armbian-bsp-cli-bananapipro-current:1-PCc91e-V4b00-H9299-B1e5d-Rf36a": ghcr.io/armbian/os/armbian-bsp-cli-bananapipro-current:1-PCc91e-V4b00-H9299-B1e5d-Rf36a: not found ``` some repeatible during the process: ``` gpg: WARNING: unsafe ownership on homedir '/home/bask/.gnupg' /usr/bin/deb-systemd-helper was not called from dpkg. Exiting. /usr/bin/deb-systemd-helper was not called from dpkg. Exiting. invoke-rc.d: unknown initscript, /etc/init.d/iperf3 not found. ``` and finally filtered from log: ``` filtered from log @output/logs/log-build-322ed1c8-a4db-4873-85ac-be8e6a87fbd6.log.ans Error 3 occurred in main shell /home/bask/Dokumenty/build/lib/functions/configuration/menu.sh:38 dialog_if_terminal_set_vars() --> lib/functions/configuration/menu.sh:38 interactive_config_ask_board_list() --> lib/functions/configuration/interactive.sh:149 config_possibly_interactive_kernel_board() --> lib/functions/main/config-interactive.sh:16 prep_conf_main_build_single() --> lib/functions/main/config-prepare.sh:21 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:22 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ``` Not sure if I should worry or it is handled somehow? I'll try an expert mode as there was not too much to configure and verify Second thing: 90 mins for this process is normal? I was doing it on newly installed Ubuntu (directly on the disk in dual mode so whole HW available for it)

There are probably 20 different CPUs that have cortex a53 (cpus from Allwinner, Rockchip and Amlogic). TV box manufacturers all the time will use different CPUs in TV boxes that have the same external markings. Which ever component is the cheapest at the time of manufacture is what gets used. The only way to really be sure what you have is to look at the chip on the board (but even then there are cases where chip markings have been altered to make you think you have something else). Welcome to the world of TV boxes (and why Armbian doesn't support them officially because they are a mess).

Hello, Recently the HDD Cable Harness for my Helios64 malfunctioned. SATA Ports 1 and 2 are both no longer getting power/HDDs are not spinning up. I confirmed that it was power by plugging the SATA cable into ports 3, 4, and 5 on the motherboard which all function. I also iterated through the system by removing all the HDD's and testing each HDD slot one at a time. All 5 HDDs fucntion individually in a USB drive enclosure, and all 5 function in my server system and I can mount the RAID array. My question is, does anyone know how to contact the Helios/Kobol team so I can purchase a replacement HDD Harness Cable? I checked on Aliexpress and can't find anything similar so I presume that the cable is custom. Thank you.

@Ducdanh Nguyen Yes does it tell you in android Google Ai: To find your Android device's GPU, download a hardware info app like Dev Check from the Google Play Store, go to Settings > About Phone > Hardware Information (though this is less reliable on some Android versions), or use developer tools like Android GPU Inspector (AGI) for detailed profiling.

Thank you SteelMan for the pointer. Downloaded the rolling build and wrote it to my USB using balenaEtcher in Windows, the resulting USB was MBR and I could read the boot partitions contents. That's a massive improvement from using the images from https://www.armbian.com/uefi-arm64/ which were GPT and regardless of writing the USB under Windows/Linux the boot partition was unreadable. My box is probably an A95X Max (S905x2 SOC, 4G Ram, gbit ethernet & 5g wifi) so the uboot should be u-boot-s905x2-s922 All that's left is to find the best dtb Thanks for all the help

Hi, many thanks for your hints @brentr and @laibsch! 😀 Using COMPRESS_OUTPUTIMAGE=xz did the trick and the image size is now more in an expected range. However, using the paramters and commandline above gives me an image with a size of 342MB whereas the current rolling Trixie image is 273MB. I don't think it is a big deal, but I still would like to understand the difference 😊 Cheers

@dale it seems like vfd-convert has not worked well. Perhaps because of some mix between script version and the template files version. Whatsoever, I've looked closer at the patch link you previously posted, this is the older pre-review dt-bindings syntax. You should be go to start with something like: /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = <&gpio 7 GPIO_ACTIVE_HIGH>; mosi-gpios = <&gpio 2 GPIO_ACTIVE_HIGH>; cs-gpios = <&gpio 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0x0>; spi-3wire; spi-lsb-first; spi-rx-delay-us = <1>; spi-max-frequency = <500000>; titanmec,digits = [00 01 02 03]; titanmec,segment-mapping = [03 01 02 06 04 05 00]; #address-cells = <2>; #size-cells = <0>; led@4,0 { reg = <4 0>; function = LED_FUNCTION_ALARM; }; led@4,1 { reg = <4 1>; function = LED_FUNCTION_USB; }; led@4,2 { reg = <4 2>; function = "play"; }; led@4,3 { reg = <4 3>; function = "pause"; }; led@4,4 { reg = <4 4>; function = "colon"; }; led@4,5 { reg = <4 5>; function = LED_FUNCTION_LAN; }; led@4,6 { reg = <4 6>; function = LED_FUNCTION_WLAN; }; }; }; }; Note that I haven't tested it, just made it from some copy-paste. If it doesn't work, even partially, you would most likely need to replace &gpio with the right reference to the gpio controller wired to the display.

Hello, I am new to arm board, I had this android tv stick called S moon mx10 5G, it have rk322x cpu, 2GB Ram, and ap6330 wifi chip. I tried armbian on this device but wifi chip was not detected, I tried using "rockchip-rk3318-box-wlan-ap6330.dtbo" as user_overlays, but still not working, could anyone tell me how to make this wifi chip working on rk322x armbian?. I attached some files for information: dmesg.txt s_moon_mx10_5g.dts

Do you mean gpu model? Like mail-g31?

Disabling automount (drive letter assignment) in windows before flashing might help - probably it is mount time when windows is checking and changing partition table.

First off, I would recommend using the "psuedo official" instructions from this site: https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus And there you will find the following warning: Note: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attempting the install. coreelec changes the boot environment in ways that are incompatible with these Armbian builds.

Hey Guys, I know this post is old but I have some questions. I was following @Jaybyrd's instructions and I have a question pertaining to the Plugin USB-C to the power on the device "I am assuming that is on The OPi5 device." Am I supposed to plug in something else? Because it says to open a terminal "what terminal? On what device?" Thank you for your time, Michael

I wouldn't be so categorical - I have rock pi 4b, which never saw android or any os other than armbian, which has same thing- two boot devices on emmc. Since it doesn't bother me, I didn't investigate further.

@Ducdanh Nguyen Can you find the gpu version?

No that is not true. These are not from Armbian. As I said earlier if your eMMC previously had Android (which defines and uses these special partitions) even after a normal Linux repartitioning these will still appear.

It seems that eMMC has built-in boot partitions. eMMC devices are not just "raw storage" (like SD-Cards) they have special reserved hardware partitions defined by the JEDEC eMMC standard. These include: boot0 – a small partition (usually a few MB) reserved for bootloader code. boot1 – a second small boot partition, often used as a backup. RPMB (Replay Protected Memory Block) – a secure partition for keys and counters. The SoC’s boot ROM (first-stage loader) can be configured to read directly from boot0 or boot1 when powering on. Also, these partitions are read-only to decrease the risk of having corrupted boot code. Beware that they’re not used by the Linux filesystem unless explicitly written to (usually via dd when flashing U-Boot).

If the card still mounts, try running fsck first. If it’s clean but won’t boot, you can copy fresh /boot files from the same Armbian release. Otherwise, reinstalling to a new SD and restoring your data may be the safer route.

I faced a similar Ethernet throughput issue on Armbian under high latency. One thing that helped was using a USB Ethernet dongle instead of the onboard NIC. To simulate latency, you can use the tc command: sudo tc qdisc add dev eth0 root netem delay 200ms sudo tc qdisc del dev eth0 root For more solutions, check out this.