All Activity

I have a temp fix for the WIFI on newer hardware with AIC8800 SDIO WIFI module. Download or wget : https://github.com/radxa-pkg/aic8800/releases/download/3.0%2Bgit20240327.3561b08f-4/aic8800-firmware_3.0+git20240327.3561b08f-4_all.deb https://github.com/radxa-pkg/aic8800/releases/download/3.0%2Bgit20240327.3561b08f-4/aic8800-sdio-dkms_3.0+git20240327.3561b08f-4_all.deb Then : sudo dpkg -i aic8800-firmware_3.0+git20240327.3561b08f-4_all.deb sudo dpkg -i aic8800-sdio-dkms_3.0+git20240327.3561b08f-4_all.deb

As seen in some other threads for mvebu-based boards (helios4, etc), the current images for clearfog base (and I assume) pro are broken in that it appears the initrd can't be loaded. I also haven't been able to use the u-boot for SATA booting in a while. I have been hitting both of these issues for a while and as I showed above in the past you can still flash old images, use an even older u-boot binary for SATA and get up and running - but now (and I'm not sure when it started) any upgrade to current packages renders the system unbootable. It's unfortunate, but it seems these boards are old enough that their support is rotting (and to be clear, I'm not blaming Armbian for this). While this hardware is old it's plenty performant as my home firewall to the Internet and so I don't want to replace it - but it's maybe time to start looking for a replacement anyways. Just a few nights ago, I installed updates for the first time in a few months and when I rebooted it, it failed to come back up. Considering this is my router, that really cramped my style! But I got another box in place in this role and since then I've poked at this a bit. It's easy to reproduce: Flash a copy of Armbian_23.11.1_Clearfogbase_bookworm_current_6.1.63.img to an m.2 SATA drive (if this isn't available any more, ping me and I can post it somewhere). Write a copy of the old u-boot for SATA support to the beginning of the drive (dd if=u-boot.sata of=/dev/foobarbaz bs=512 seek=1) Put the m.2 SATA drive into your clearfog and configure the jumpers to boot off SATA - see here. Plug in ethernet and micro USB to another system and attach to it for console (picocom -b 115200 /dev/ttyUSBFOOBARBAZ) Power it on and hopefully observe it boot - then go through the initial setup Update and upgrade packages (apt update && apt upgrade) Reboot - and watch it stall before it gets anywhere The trick then is to put a "hold" on the kernel and firmware packages before doing #6. The latest kernel I've been able to get running stable is 6.6.63-current-mvebu (installed via armbian-config). for pkg in armbian-bsp-cli-clearfogbase-current armbian-firmware linux-dtb-current-mvebu linux-image-current-mvebu linux-u-boot-clearfogbase-current; do echo "$pkg hold" | dpkg --set-selections done Then you should be able to upgrade everything else and reboot and have it not break. That list of packages is likely larger than it really needs to be, but after rebuilding my drive a couple of times I decided to not take any chances. The rest is either pure Debian or at least things that shouldn't break due to bit rot. If I have more time I'll try to actually dig in and figure out what's wrong with the ramdisk (or whatever it is that causes this) and submit a fix, but this is better than nothing for now.

Hey, how did you do this? I would like to do the same. Did you replace the 'Max' dtb file content or placed the new file and referenced it from elsewhere (like /boot/armbianEnv.txt)?

I'm not an expert, the logs from Cockpit probably helped me. I found this (Rock 5 ITX Version 1.12): I'm testing 6.14 rc4 right now: everything seems to work.

On 6.13.7 edge kernel sound should works without any changes. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.13.10&id=86a8f1aef9702f730c824aa96ae24ffa1b401988

Or install the Orange Pi Zero 3 image with the 6.13.7 edge kernel. On the Zero 2W image, the edge kernel doesn't boot.

moved

Can I enable wifi (SV6256P) in H616 DDR3 Tv box https://github.com/paolosabatino/ssv6x5x/tree/master or build from old kernel 4.4.x

I assume you have a GitHub account (if not, make it)? Click "Subscribe" on that issue and you will get a notification when its closed down. 4 hours later, still not fixed. No, there is no cheap and quick solution to patch this problem. I would like to see that too.

You also have to do as described here: https://dietpi.com/forum/t/no-sound-card-detected-for-opi-zero-2w/20133/26 /usr/bin/amixer -c 0 set 'Left Output Mixer DACL' 100% unmute /usr/bin/amixer -c 0 set 'Left Output Mixer DACR' 100% unmute /usr/bin/amixer -c 0 set 'Right Output Mixer DACL' 100% unmute /usr/bin/amixer -c 0 set 'Right Output Mixer DACR' 100% unmute

You can see my changes in bolt codec@05096000 { #sound-dai-cells = <0x00>; compatible = "allwinner,sun50i-h616-codec"; reg = <0x5096000 0x31c>; interrupts = <0x00 0x3a 0x04>; clocks = <0x02 0x5d 0x02 0x5b 0x02 0x5c>; clock-names = "apb\0audio-codec-1x\0audio-codec-4x"; resets = <0x02 0x24>; dmas = <0x0d 0x06>; dma-names = "tx"; status = "okay"; phandle = <0x50>; }; ahub_dam_plat@5097000 { #sound-dai-cells = <0x00>; compatible = "allwinner,sunxi-snd-plat-ahub_dam"; reg = <0x5097000 0x1000>; resets = <0x02 0x25>; clocks = <0x02 0x5b 0x02 0x5c 0x02 0x5e 0x02 0x5f>; clock-names = "clk_pll_audio\0clk_pll_audio_4x\0clk_audio_hub\0clk_bus_audio_hub"; status = "okay"; phandle = <0x51>; }; ahub1_plat { #sound-dai-cells = <0x00>; compatible = "allwinner,sunxi-snd-plat-ahub"; apb_num = <0x01>; dmas = <0x0d 0x04 0x0d 0x04>; dma-names = "tx\0rx"; playback_cma = <0x80>; capture_cma = <0x80>; tx_fifo_size = <0x80>; rx_fifo_size = <0x80>; tdm_num = <0x01>; tx_pin = <0x00>; rx_pin = <0x00>; status = "okay"; phandle = <0x0f>; }; ahub1_mach { compatible = "allwinner,sunxi-snd-mach"; soundcard-mach,name = "HDMI"; soundcard-mach,format = "i2s"; soundcard-mach,frame-master = <0x0e>; soundcard-mach,bitclock-master = <0x0e>; soundcard-mach,slot-num = <0x02>; soundcard-mach,slot-width = <0x20>; status = "okay"; phandle = <0x52>; soundcard-mach,cpu { sound-dai = <0x0f>; soundcard-mach,pll-fs = <0x04>; soundcard-mach,mclk-fs = <0x00>; phandle = <0x0e>; }; soundcard-mach,codec { sound-dai = <0x10>; phandle = <0x53>; }; }; gpu@1800000 { compatible = "allwinner,sun50i-h616-mali\0arm,mali-bifrost"; reg = <0x1800000 0x40000>; interrupts = <0x00 0x5f 0x04 0x00 0x60 0x04 0x00 0x61 0x04>; interrupt-names = "job\0mmu\0gpu"; clocks = <0x02 0x23 0x02 0x24>; clock-names = "core\0bus"; resets = <0x02 0x03>; status = "okay"; mali-supply = <0x11>; phandle = <0x54>; };

I deleted the build folder and built votar image a second time to make sure. same result. brcmfmac4334-sdio.tanix,tx6s.bin again was listed. just thought it strange. was trying to solve bluetooth not working and see what different dmesg give. originally compiled tanix tx6 then after compile vontar, though it may because used same build folder. that why did again with clean build. also tanix tx6 is brcmfmac4330-sdio.tanix,tx6s.bin

Indeed, I wrote it very briefly. There are problems with analog audio output/input in the linux kernel for h616-h618 processors. We are solving this problem, which exists in several drivers and their interaction with each other. Audio output via HDMI works today only because one of the Armbian users added this feature. This is an expansion board. Obviously, in order for it to work, we need overlays for everyone. sun50i-h616-audio-out.dtso /dts-v1/; /plugin/; / { fragment@0 { target = <&codec>; __overlay__ { allwinner,audio-routing = "Line Out", "LINEOUT"; status = "okay"; }; }; };

@Robert Roig Santamaria this is not an android forum. I can only show you how to install linux on your box. If you want to run linux on your box then write the transpeed image onto a SDcard. I use this software to write images. https://etcher.balena.io/ and you can find my custom made images here. https://github.com/NickAlilovic/build/releases/tag/20250306

That odd are you sure you didn't mix up the images? I think Tanix, tx6 image can boot on Vontar.

Three demos. One stand. From end-to-end HDR and a brand-new SoC running PanVK, to NVK and WebGPU out of the box — discover how Collabora pushed open source graphics forward at Embedded World 2025. View the full article

When you have a solution you can post it here or even if you have a script to fix it I would be grateful.

Aha, its probably this: https://github.com/armbian/build/issues/8052 Working on it.

build with SHARE_LOG=yes SHOW_DEBUG=yes and provide full log. This tells noting.

This is everyone's problem. Buy boards that are supported and maintained. We have not received any support from Orange Pi, contrary, their business model is very damaging to us and donations only pays coffee and beer. We do not maintain or officially support hardware you have, and AFAIK it is not maintained by anyone else - but if it is, it will get to Armbian too. However, given the similarities across these boards and the nature of open source, it’s difficult to prevent Orangepi and their customers (you) from abusing open source development. This is everyone's problem. Stop buying hardware that we don't and won't support as making a pressure to open source developers is worse thing you can do. Hardware dealer abuse is already big enough. Just a polite reminder that you are not a customer, so adjust your over-expectations.

I tested Armbian 25.2.2 Bookworm Minimal / IOT on both the REV1 and REV2. Wifi worked fine in both cases.

Noticed some strange wifi setting for my Vontar H618, its asking for Tanix,Tx6s wifi firmware I am using brcmfmac4334-sdio.bin and wifi works.

I don't understand your answers. This problem has been occurring for months. Does no one use the audio expansion card? I'm currently developing an audio application and this is a major hindrance for me. Please, when you have solved the problem, don't forget to write to me.

I constantly get this error message when I try to generate the version for rpi4. : Unable to correct problems, you have held broken packages. [💥] Error 1 occurred in main shell [ at /home/raspberry/build/lib/functions/logging/runners.sh:15 chroot_sdcard_apt_get_install() --> lib/functions/logging/runners.sh:15 pre_install_distribution_specific__add_rpi_packages() --> config/sources/families/bcm2711.conf:227 pre_install_distribution_specific() --> <extension_magic>:184 call_extension_method() --> lib/functions/general/extensions.sh:57 build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:19 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ] [💥] Cleaning up [ please wait for cleanups to finish ] When this happens I have to delete the build folder and redo everything. git clone --depth=1 --branch=main https://github.com/armbian/build cd build ./compile.sh Can someone help me solve this without having to start from scratch?

I checked armbian images with disabled and enabled secure boot. Yesterday I tested official generic image from ubuntu(http://www.cdimage.ubuntu.com/daily-live/current/plucky-desktop-arm64.iso) and it is working, but it is creating bootable iso not image which is containing 3 parts free space, ARMBI_EFI and armbi_root. One of bigger difference is lack grubaa64.efi and mmaa64.efi on EFI directory in ARMBI_EFI in armbian image.