All Activity

Since the RK3399 U-Boot can use an HDMI display and a USB keyboard, I would simply configure a jumpstart option in the boot flow that mounts a different root filesystem. When booting, you just have to select this option. If interacting with the firmware console is too complicated, the recovery system can be placed on a removable storage device. In this way, in case of need, only the rescue media needs to be connected and the system restarted; no firmware console access is required. A completely firmware-controlled fallback mechanism is also possible, but it requires further special configuration of the firmware. Read this thread to understand what I mean by my statement.

If tester is not available, I'd try powering failing ports with their respective cables but feeding them from pins powering other ports (eg with wires from some molex cable, just need to be careful with polarity and shortcuts) - to exclude failure of the power rail feeding these ports on the board. If cables are faulty, I'd check them for electrical connections and if they are ok, would replace capacitors.

What I like to do in such a case is link to archive.org. some spam got posted to this thread which I removed, so I felt like I might as well add an answer at the same time

fair enough, no idea where i would get the right android image from for my unknown box so I guess I am stuffed putting Armbian on my box. never mind, will repurpose an old laptop when corelec updates for the s905x2 stop thanks for the help

You are missing something. The boot process starts with the uboot from the emmc (even if ultimately booting the SD card). And coreelec changes the uboot environment of the emmc in ways that are incompatible with with the armbian code. So you need to reflash a fresh android image if you want to use armbian as that will restore the basic state that armbian is expecting.

the guide has a 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. I have run coreelec but only ever from an SD card, I don't think the firmware has ever been changed as if I remove the SD card it boots into the original android system. Is this likely to be true or am I again missing something.

HP Pavilion8 core processor, 32Gig RAM laptop. I wanted to limit information to limit time for digging into it, but here they are: log-build-322ed1c8-a4db-4873-85ac-be8e6a87fbd6.log.ans summary-build-322ed1c8-a4db-4873-85ac-be8e6a87fbd6.md

dig through the github actions, how the images are compiled is public information ;-)

probably time for the serial console my suspicion tells me that it will be hard to get proper logs otherwise my suspicion is that some umounts does not come back. <- try to unmount everything you can before the reboot and see if that helps.

This is great. Apparently mine didnt persist after reboot either, yours seems to be permanent and working even better. Thanks!

I have looked at a lot of other 4 and 8 PIN cables and considered using multiple single SATA power connector to double connectors but I have reservations because the harness cable included with the Helios64 has those capacitors. I am not certain what their purpose is and I am concerned if I do some sort of unique solution I will damage the motherboard. Also this was being used as an offsite NAS for a production environment backup data and so stablity is essential. I've asked this question in multiple places, I am at the point that I am just going to have to order a new NAS unit that doesn't use custom cables.

Oh, my bad. That does indeed look very custom-made. Just an idea, maybe get yourself a Molex 4-Pin IDE to SATA power cable (this one even has five power outlets) and then power the HDD separately? Maybe there is 12V on the board somewhere you can tap into. I am not an electrical engineer so better verify. You will likely have to come up with a unique solution at this point.

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