Hello. I can see thet avaota A1 is supported. But how it run from sd-card? I burn image put sdcard and i can see only black screen. Image does not boot...

https://debug.armbian.de

Ok i have finally booted. But kernel does not have snd-usb-audio. I would like to compile the driver from alsa-project sources but there is no linux-headers packege 5.15.123. I know that audio driver for allwinner T527 cant be done yet. But why snd-usb-audio is missing. Usb audio card can be substittute.

Edited October 16, 20241 yr by constantius

You can use the build framework to create your own set of packages with custom kernel config for this board including matching headers.

https://github.com/armbian/build

Quote

Error 1 occurred in main shell [ at /home/radek/DrugiHD/build/lib/functions/logging/runners.sh:15
   chroot_sdcard_apt_get_install() --> lib/functions/logging/runners.sh:15
   install_distribution_agnostic() --> lib/functions/rootfs/distro-agnostic.sh:247
                do_with_logging() --> lib/functions/logging/section-logging.sh:81
         build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:28
   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 ]

Quote

Hello. I build only debian 12 images. ( server and gnome )  But none of them starts. When I am trying build ubuntu 22.04 or 24.04 server or GUI there is such error

 

 

 

 

 

Edited October 21, 20241 yr by constantius

The kernel drivers for T527 from Allwinner still have issues (yes, even the original manufacturer's drivers have issues), including but not limited to HDMI and audio.
The original manufacturer's drivers also have requirements for the gcc version.
Furthermore, Allwinner currently has not provided a solution (perhaps it has not been made available to individual developers yet).

3 часа назад, constantius сказал:

Error 1 occurred in main shell [ at /home/radek/DrugiHD/build/lib/functions/logging/runners.sh:15
   chroot_sdcard_apt_get_install() --> lib/functions/logging/runners.sh:15
   install_distribution_agnostic() --> lib/functions/rootfs/distro-agnostic.sh:247
                do_with_logging() --> lib/functions/logging/section-logging.sh:81
         build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:28
   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

This trace is intended mainly for developers of the build system itself.
There is no information about the compilation error itself.

Use the command to view:

grep -Ei 'warn|err|\|' output/logs/log*.log.ans | batcat

Or a black and white version for printing:

grep -Ei 'warn|err|\|' output/logs/log*.log

And publish only the lines that relate to the error.

grep -Ei 'warn|err|\|' output/logs/log*.log.ans | batcat
grep: output/logs/log*.log.ans: no such file
───────┬────────────────────────────────────────────────────────────────────────
       │ STDIN   <EMPTY>

 

@constantius

 

Hello,

 

I have an Avaota A1 here. How you get managed to boot on SD CARD?

I'd like to run the mainline kernel https://github.com/nickfox-taterli/avaota-a1-mainline-linux

 

The board used to have a page and downloads here: https://armbian.com/boards/avaota-a1 but it's gone. Has support for this board been dropped?

 

 

Now available https://armbian.com/boards/avaota-a1

On 5/24/2026 at 4:36 PM, Sam Rossiter said:

Has support for this board been dropped?

 

Community maintained build targets are "supported" this way:

https://docs.armbian.com/contribute/board-support-rules/#community-maintained

We can only afford to sponsor build capacity and host on free public resources (Github releases). If compilation breaks, we can only (temporally) remove them, fixing is your problem. Once / If community maintainer / random luck fixes compilation, they are (automatically) back, else they are gone. For good. Or only temporally. We don't store older images for community supported hardware, but they remain in the build framework so one can build then on their own. If last build broke, there won't be download page. This is the policy in tl;dr;