pixdrift

Hi everyone,
 
Apologies, have been away for Christmas.. and still not completely back on deck.

My Zero2W with expansion and expansion boards for Zero2 and Zero3 arrived during the break so I will also have those to test.

Welcome to the new people in the forum! @johndo100 and @Mako, can you let us know which boards and which variants you have (ie. memory configuration) and if you have IO boards? would be great to get some more testers with hardware contributing feedback here

Regarding testing for @Gunjan Gupta I am happy to create builds of his pull request efforts into mainline Armbian to make it easier for others to test, all I ask is that when people are posting feedback for different images they provide a link to the image they have downloaded/flashed so we can keep track of which feedback relates to which build. I will also include the PR (pull request) and commit ID in the builds I do.

I will try and get a build / image of the 6106 PR that @Gunjan Gupta is requesting testing for.. out today.

I am interested in what people prefer to test as there is a large number of combinations. I will build Bookworm and Bookworm + XFCE initially, and happy to take feedback if people have trouble with Debian.

@pixdrift, @Gunjan Gupta I built an image by getting  a repository:
git clone https://github.com/viraniac/armbian_build.git.
The image works with HDMI using my brand new cable that arrived less than an hour ago.
I will test more later.  Is this a good way to produce an image? I'm not quite sure.

Hi everyone,
 
Apologies, have been away for Christmas.. and still not completely back on deck.

My Zero2W with expansion and expansion boards for Zero2 and Zero3 arrived during the break so I will also have those to test.

Welcome to the new people in the forum! @johndo100 and @Mako, can you let us know which boards and which variants you have (ie. memory configuration) and if you have IO boards? would be great to get some more testers with hardware contributing feedback here

Regarding testing for @Gunjan Gupta I am happy to create builds of his pull request efforts into mainline Armbian to make it easier for others to test, all I ask is that when people are posting feedback for different images they provide a link to the image they have downloaded/flashed so we can keep track of which feedback relates to which build. I will also include the PR (pull request) and commit ID in the builds I do.

I will try and get a build / image of the 6106 PR that @Gunjan Gupta is requesting testing for.. out today.

I am interested in what people prefer to test as there is a large number of combinations. I will build Bookworm and Bookworm + XFCE initially, and happy to take feedback if people have trouble with Debian.

Hello everyone. I would like to thank you all for the time you are putting on this.
 
 
I would like to help a bit and test it, but I'm pretty noob to playing with WIP Linux distribution. I have a developper background so I might be able to understand the principles, but I'll need a quick 'How to' or any tutorial to start with.

Thanks again for what you are doing, can't wait to be able to play with this Opi zero 3 with Armbian.

I just warned against wasting time on work that has already been done.
Having a reference that already works and has been tested is also useful.

There is a warpme development with arch, which contains all the necessary patches, including many test things that have not yet made it to the mainline, but are being tested in linux-sunxi. Support for Zero2 and zero3 was added a very, very long time ago. https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.6
HDMI support and everything related to it is handled by jernej, last effort is branch h616-var: https://github.com/jernejsk/linux-1/tree/h616-var
 

@Gunjan Gupta the changes for zero3 CPU Frequency are all bundled into this commit
https://github.com/pixdrift/armbian_build/commit/e53cba13aea0d1d7c555599bd4fbd6ae94d49dd0

It's on my branch zero3_cpufreq
https://github.com/pixdrift/armbian_build/tree/zero3_cpufreq
 
Changes of interest are are
https://github.com/pixdrift/armbian_build/blob/e53cba13aea0d1d7c555599bd4fbd6ae94d49dd0/patch/kernel/archive/sunxi-6.6/patches.armbian/arm64-dts-allwinner-h616-Add-efuse_xlate-cpu-frequency-scaling-v1_6_2-dtsi.patch#L98-L141

Thanks for the offer to take a look

That message is pretty early in boot. Also 517 is EPROBE_DEFER which means pin is not available right now and driver will retry to grab it later. Its feel its ok to have that message unless it breaking some functionality. 
 
That sounds correct
 
That not needed. Are your changes in your git branch? May be I can take a look

Jus one more piece of news. After rebooting the device (I believe I had to reboot it twice), bluetooth started and I was able to pair it with a loudspeaker, working beautifully.  On top of that, I was then able to set VLC to use OpenGL for embedded systems (which did not work before) and, with this configuration, some videos even played with 0 lost frames.
I also connected a 4G modem that supported the rndis driver through the USB and it was recognised without problem. I then installed SQM and cake-autorate to keep the latency in control and so far so good. It seems to be working quite stable. This little device seems to be quite promising, with several nice features at an unbeatable price...

First of all, I would like to congratulate and thank you all for the effort put in this initiative. Besides @Gunjan Gupta , special thanks to @pixdrift for making available a test image that we can play with, thus hiding the complexity of compiling the image ourselves.
 
Having said that, and with the intention of giving some testing feedback as you requested, here are some comments. I own a 4GB orange pi Zero 3 with extension board. I started playing with the first image a bit until you uploaded the second image, with which I played a little bit more.
 
With any of both images I did not seem to have good hdmi output initially. By "good" I mean that my monitor detected "something" but I suspect it was not able to synchronize properly. Unplugging the cable and plugging it again seemed to force some recognition and I was able to see the login prompt, but with a lot of flicker and unstability. I remember having similar problems when I played with the miniarch image.  With your second image I believe it was worst and I was not able to see anything. So I logged in using the serial connection (see attachment for the boot log over serial).  I followed the initial configuration steps and then here the two images seemed to behave differently. While I think the first image started the desktop environment after that, I had to run armbian-config with the second image to activate it.  In the first image, once the desktop environment started, I got a good signal through HDMI, albeit in 600x800. I was able to change the resolution but after rebooting I lost the signal again. Getting into armbian-config, deactivating the desktop and activating it again seemed to fix the issue, probably because it activated also the autologin functionality. No browser seemed to be installed, so I installed chromium and I checked the playability of some videos in youtube and they were quite unplayable (not that I expected much, anyway).
 
With the second image, as I said, I had to go to armbian-config to activate the desktop. I selected xfce and it took a while to download and install the packages. After rebooting, nothing was displayed on the monitor. Again I tried the trick of disabling and enabling the desktop to activate the autologin and I was able to have a nice desktop on my monitor, although I had to wait maybe more than one minute until something was shown, and by default I had more than 10 display configuration windows already opened that I had to close (I know, really weird).
The usb ports on the expansion board worked nicely and the wifi was also working fine. I was not able to activate bluetooth, though. Maybe I was missing something there.
Anyway, I saw that firefox was installed and tried to run it, but it stayed on the task bar without being able to get maximized or anything. So I installed chromium and it behaved much better. It was much snappier than with the previous image. So I checked youtube and to my surprise the videos seemed to be quite playable. I installed then vlc, had to configure it in preferences-video to use xvideo output (xbc) and tested some 1080p sample videos at https://oliverx.link/samples/ . Two samples showed very few lost frames, while using a reasonable amount of CPU, which make me believe they were HW decoded: V206 AVI – MPEG-4 24fps – MP3 and V207 TS – AVC 24fps – AAC 
 
So far so good. And I'd say this looks very promising.
 
Thank you again for the effort put in this.
 
 
armbian serial log.txt

Sorry @Gunjan Gupta not having much luck with these images unfortunately.

I did a quick test of both kernel versions on a Zero2, and neither had HDMI output, although interestingly after the kernel boots it appears to send an HDMI signal (monitor detects it) but doesn't have any output. I tested both kernel versions using Bookworm as the OS.

I noticed in your branch, you haven't enabled console output 'both' or marked display as 'yes', so I rebuilt after updating the configuration and unfortunately I still didn't get anything displaying on HDMI out.
https://github.com/viraniac/armbian_build/blob/h616-hdmi/config/boards/orangepizero2.conf#L7-L8

I did test CPU Freq though and that appears to be working correctly. Here is some debugging output from the 6.1 Bookworm build.
 
root@orangepizero2:~# uname -a Linux orangepizero2 6.1.69-current-sunxi64 #1 SMP Wed Dec 20 16:00:29 UTC 2023 aarch64 GNU/Linux root@orangepizero2:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 244 us. hardware limits: 480 MHz - 1.51 GHz available frequency steps: 480 MHz, 600 MHz, 792 MHz, 1.01 GHz, 1.20 GHz, 1.51 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 1.51 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.51 GHz (asserted by call to hardware). cpufreq stats: 480 MHz:16.49%, 600 MHz:2.47%, 792 MHz:0.66%, 1.01 GHz:0.03%, 1.20 GHz:0.05%, 1.51 GHz:80.31% (333) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 244 us. hardware limits: 480 MHz - 1.51 GHz available frequency steps: 480 MHz, 600 MHz, 792 MHz, 1.01 GHz, 1.20 GHz, 1.51 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 1.51 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.51 GHz (asserted by call to hardware). cpufreq stats: 480 MHz:16.49%, 600 MHz:2.47%, 792 MHz:0.66%, 1.01 GHz:0.03%, 1.20 GHz:0.05%, 1.51 GHz:80.31% (333) analyzing CPU 2: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 244 us. hardware limits: 480 MHz - 1.51 GHz available frequency steps: 480 MHz, 600 MHz, 792 MHz, 1.01 GHz, 1.20 GHz, 1.51 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 1.51 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.51 GHz (asserted by call to hardware). cpufreq stats: 480 MHz:16.49%, 600 MHz:2.47%, 792 MHz:0.66%, 1.01 GHz:0.03%, 1.20 GHz:0.05%, 1.51 GHz:80.31% (333) analyzing CPU 3: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 244 us. hardware limits: 480 MHz - 1.51 GHz available frequency steps: 480 MHz, 600 MHz, 792 MHz, 1.01 GHz, 1.20 GHz, 1.51 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 1.51 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.51 GHz (asserted by call to hardware). cpufreq stats: 480 MHz:16.49%, 600 MHz:2.47%, 792 MHz:0.66%, 1.01 GHz:0.03%, 1.20 GHz:0.05%, 1.51 GHz:80.31% (333) root@orangepizero2:~# lsmod Module Size Used by algif_hash 16384 1 algif_skcipher 16384 1 af_alg 24576 6 algif_hash,algif_skcipher bnep 28672 2 hci_uart 135168 1 btqca 24576 1 hci_uart btrtl 28672 1 hci_uart btbcm 20480 1 hci_uart btintel 40960 1 hci_uart bluetooth 724992 29 btrtl,btqca,btintel,hci_uart,btbcm,bnep ecdh_generic 16384 2 bluetooth ecc 32768 1 ecdh_generic sprdwl_ng 352256 0 sunxi_addr 20480 1 sprdwl_ng cfg80211 376832 1 sprdwl_ng sunrpc 290816 1 snd_soc_hdmi_codec 24576 0 lz4hc 16384 0 lz4 16384 0 polyval_ce 16384 0 sunxi_cedrus 45056 0 polyval_generic 16384 1 polyval_ce v4l2_mem2mem 36864 1 sunxi_cedrus videobuf2_dma_contig 24576 1 sunxi_cedrus videobuf2_memops 20480 1 videobuf2_dma_contig dw_hdmi_cec 16384 0 dw_hdmi_i2s_audio 16384 0 videobuf2_v4l2 24576 2 sunxi_cedrus,v4l2_mem2mem videobuf2_common 49152 5 sunxi_cedrus,videobuf2_dma_contig,videobuf2_v4l2,v4l2_mem2mem,videobuf2_memops videodev 204800 4 sunxi_cedrus,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem panfrost 69632 0 mc 53248 5 sunxi_cedrus,videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem gpu_sched 28672 1 panfrost dump_reg 24576 0 apple_mfi_fastcharge 20480 0 drm_shmem_helper 20480 1 panfrost display_connector 20480 0 cpufreq_dt 20480 0 zram 28672 3 binfmt_misc 24576 1 sprdbt_tty 36864 2 uwe5622_bsp_sdio 208896 2 sprdbt_tty,sprdwl_ng rfkill 36864 7 sprdbt_tty,bluetooth,cfg80211 fuse 126976 1 dm_mod 131072 0 hid_apple 28672 0 realtek 32768 1 dwmac_sun8i 28672 0 mdio_mux 16384 1 dwmac_sun8i root@orangepizero2:~# dmesg | grep -i hdmi [ 1.444604] sun8i-dw-hdmi 6000000.hdmi: Detected HDMI TX controller v2.12a with HDCP (DWC HDMI 2.0 TX PHY) [ 1.445267] sun8i-dw-hdmi 6000000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.445657] sun4i-drm display-engine: bound 6000000.hdmi (ops 0xffff800008ea4d48) [ 96.336072] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 96.336102] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 1 [ 103.529860] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 189.979691] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin
It seems very close, just not displaying anything. I will do some more testing and let you know if I get something to work.

If anyone else has a Zero2 and wants to validate my testing, I have posted the images built from @Gunjan Gupta's HDMI testing branch here
https://armdev.pixeldrift.net/orangepi/zero2/viraniac/

Hi @Ivan Sy thanks for your interest in our Zero3 work and welcome to the forum!

I won't speculate on timelines for official support, but a PR with everything necessary (that @Werner alludes to) shouldn't be far off and we have most of the pieces working to different degrees which is what you will see in some of the testing and discussion in this thread.

The biggest challenge with merging to mainline is really getting the HDMI patch working for the zero2 as the zero2 and zero3 share a lot of similarities in their SoC. @Gunjan Gupta has done some incredible work to wrangle patches for the Zero2 to get everything working, and that is why you will see some Zero2 discussion here which may seem out of place.

Unfortunately the most recent Zero2 test for HDMI still has some challenges, and I have given as much feedback as possible to @Gunjan Gupta but unfortunately @Gunjan Gupta doesn't have a physical Zero2 to test on (yet). Once this patch is merged into the mainline Armbian, I think there will be some effort to move the remaining pieces that are common for both Zero2/Zero3 into a consolidated .dtsi file so both boards can benefit, then it will only take a small amount of effort to add Zero3 configuration (because it's almost identical).

The Zero3 fork I am maintaining, and posting here doesn't take into consideration anything other than the Edge branch and making the Zero3 work, where @Gunjan Gupta has put incredible effort into the Zero2 specifically and I have been porting/testing those changes on Zero3 as we go.

I think the Zero3 is a great board and I am confident that if we maintain momentum with the people who are contributing feedback and assistance from the community here, combined with the amazing patching work form upstream.. we will be able to put together a PR of the quality the project will approve of

Also, if you do buy a Zero2 or Zero3 board, please hang around and help us test  and to anyone else browsing this thread that has a Zero2/Zero3 board, create an account and say hi

@pixdriftTry hdmi on orange pi zero 2 for both 6.1 and 6.6 kernel from my branch - https://github.com/viraniac/armbian_build/tree/h616-hdmi 
 
If this works, I will then move all the orangepizero2 patches to orangepizero.dtsi. I want to get this out of the way before I bump the edge kernel to 6.7

@pixdrift could you please test the kernel from the following link on Orange Pi Zero 2 - https://drive.google.com/drive/folders/1cjCyISx3r7bVlXEPapf_5BbONQMyTcHX?usp=drive_link 
 
This kernel has all of the sun4i-drm patches enabled. See if HDMI works

The 'most complete' testing build at time of writing is this version, USE AT YOUR OWN RISK!
https://armdev.pixeldrift.net/orangepi/zero3/Armbian-unofficial_24.2.0-trunk_Orangepizero3_bookworm_edge_6.6.7.tar.xz

There are elements that we know aren't working (Bluetooth, CPU Frequency scaling) and items that are currently untested (audio output via HDMI and the expansion board).

I understand you are looking for a working image, but the Zero3 Armbian image is still in early development and depends heavily on people testing and providing feedback with identified issues. If you do run this image, please provide feedback on specific items you have tested and let us know. It is too early in the development at this stage to provide any advice or assistance for third party user space programs/applications that may produce errors or not work.

Another day another update

I merged in the Bluetooth fixes from @Gunjan Gupta's pull request to Armbian main branch into my zero3 fork, this includes moving to the extension pattern for the wifi driver.

I did a quick build and tested Bluetooth (pairing to a BT speaker) and the pairing worked, but I didn't test past this. If you have some tests you can do with Bluetooth, I would appreciate the feedback (USE AT YOUR OWN RISK etc.)
https://armdev.pixeldrift.net/orangepi/zero3/Armbian-unofficial_24.2.0-trunk_Orangepizero3_bookworm_edge_6.6.7.bt.fixed.tar.xz

I have looked at the CPU Frequency patch @Gunjan Gupta mentioned and I will look at modifying this patch to write to the shared .dtsi as suggested so both zero2 and zero3 benefit, I think that is a great suggestion.. this update doesn't include any CPU Frequency fixes yet unfortunately.
 
Thanks to everyone here that is providing feedback from their testing!
 
The github repo isn't updated with the BT fixes yet, I will try and get to this tonight so everyone can build updated images.
 
-edit-
 
GitHub fork for zero3 is now up to date with BT fixes
https://github.com/pixdrift/armbian_build/tree/zero3

@pixdrift oops for that cpufreq lockup on zero 2
 
I tried probing the cpufreq modules:
 
>find /lib/modules -type f -name "*freq*" /lib/modules/6.6.4-edge-sunxi64/kernel/drivers/cpufreq/cpufreq-dt.ko /lib/modules/6.6.4-edge-sunxi64/kernel/drivers/cpufreq/scpi-cpufreq.ko > ls /lib/modules/6.6.4-edge-sunxi64/kernel/drivers/cpufreq cpufreq-dt.ko scpi-cpufreq.ko > sudo modprobe cpufreq-dt scpi-cpufreq > sudo cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms.  
perhaps like @Gunjan Gupta
mentioned it may require additional codes e.g. that patch.
 
well no worries, I'd try to get around with my kernel build, hope I can resolve the loop devices nspawn limitations
but that the freeze for orange pi zero 2 isn't good, and i'm half guessing the symptom may be observed on zero 3 if cpufreq is after all patched in and some how work.
possibly a problem with the wifi driver design. I'm not sure where I read about that always 1 load is possibly caused by the uwe5622 wifi driver disabling interrupts and go into a busy polling loop.
if for some reason changing frequencies causes interrupts, it can cause other process to stall/freeze waiting for the interrupt to be served.
 
 

https://github.com/armbian/build/pull/6070 should fix the cpufreq hang issue and should also get bluetooth working for orange pi zero 2

I have updated the Zero 3 image with a few minor updates

1. The build now uses the u-boot upstream repository tag v2024.01-rc5 instead of the specific commit for the merge of the zero3 defconfig
2. The default configuration now includes the bluetooth tools installation to match zero2 in mainline armbian repository (if someone could test bluetooth and provide feedback it would be appreciated)
3. Kernel bumped from 6.6.4 to 6.6.7 and all patches apply cleanly and build works as expected (and CLI bookworm version has been tested).

I have built some new images (bookworm cli and xfce) with this configuration using 6.6.7 here that you are welcome to use at your own risk
https://armdev.pixeldrift.net/orangepi/zero3/
 
Source repo with the changes is here, use zero3 branch for latest stable of these changes.. I will try and make sure that this branch remains deployable
https://github.com/pixdrift/armbian_build/tree/zero3
 
I think the next step is really to look at getting Zero 3 into the mainline Armbian repository, even if it's in a reduced state of configuration due to patch issues.. this would at least set the ground work for when the components included in these builds mature. @Gunjan Gupta as you have been through this before for other boards, I was hoping to get some of your time to assist (I will see how far I get first )


Speaking of which, @Gunjan Gupta I had a quick look at adding HDMI for the Zero 2 (to the main Armbian repo, not your fork) based off a conversation you had in another thread, but unfortunately I am having issues with the HDMI patch when adding it to the main branch in the armbian repo (fails to build/patch). Have you had any success building with this patch on the current main Armbian branch? I was going to have a closer look at it tonight, but thought I'd ask if you had already looked at it.
 
Failing patch is the main HDMI driver patch:
drivers-wip-H616-hdmi-video-output
 

Thanks for the feedback.

This is interesting, looking at the kernel config for the build, the following is configured, and I assumed this is correct for this board.

If anyone has any feedback/advice on this it would be appreciated.. happy to update the image if we can find a fix. I will do some reading myself
 
│ Symbol: ARM_ALLWINNER_SUN50I_CPUFREQ_NVMEM [=y] │ │ Type : tristate │ │ Defined at drivers/cpufreq/Kconfig.arm:32 │ │ Prompt: Allwinner nvmem based SUN50I CPUFreq driver │ │ Depends on: CPU_FREQ [=y] && (ARM || ARM64 [=y]) && ARCH_SUNXI [=y] && NVMEM_SUNXI_SID [=y] │ │ Location: │ │ -> CPU Power Management │ │ -> CPU Frequency scaling │ │ -> CPU Frequency scaling (CPU_FREQ [=y]) │ │ (3) -> Allwinner nvmem based SUN50I CPUFreq driver (ARM_ALLWINNER_SUN50I_CPUFREQ_NVMEM [=y]) │ │ Selects: PM_OPP [=y]
-edit-
 
Your output appears to be an improvement over the current state of the Zero2 (my recent build from Armbian main branch at least).
 
When I run the cpufreq-info command, the Zero2 appears to lock up and never recover
___ ____ _ _____ ____ / _ \| _ \(_) |__ /___ _ __ ___|___ \ | | | | |_) | | / // _ \ '__/ _ \ __) | | |_| | __/| | / /| __/ | | (_) / __/ \___/|_| |_| /____\___|_| \___/_____| Welcome to Armbian-unofficial 24.2.0-trunk Bookworm with bleeding edge Linux 6.6.6-edge-sunxi64 No end-user support: built from trunk System load: 26% Up time: 0 min Memory usage: 12% of 919M IP: XXX.XXX.XXX.XXX CPU temp: 41°C Usage of /: 4% of 58G RX today: 146.6 MiB Last login: Fri Dec 15 18:29:24 AEDT 2023 on ttyS0 root@orangepizero2:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0:  

Unfortunately these images aren't from Armbian, or related to this thread so I think your best option for support is to raise this request on the site that you downloaded these images from.

Yes this board is new, and as a result it's not fully supported so not all components are currently working.

Unfortunately these images aren't from Armbian, or related to this thread so I think your best option for support is to raise this request on the site that you downloaded these images from.

Yes this board is new, and as a result it's not fully supported so not all components are currently working.

Bluetooth is not going to work. Its currently broken in zero2 as well. The kernel has the required driver, but the hciattach binary and corresponding service file for the same is missing. I am going to create a extension for uwe5622 wireless module that should make it easy to set this thing in the future

There are five different patches that are imported from megous kernel tree (xff.cz) that conflicts with hdmi patch. The hdmi patch has to be rewritten to fix the same. I haven't started working on it yet, but I will do it soon. Most likely within next 2 weeks window as I would be bumping the allwinner kernel versions. Legacy kernel will be moved o 6.1, current to 6.6 and edge kernel to 6.7

I have updated zero3 branch in my fork so it's up to date and you should be able to build Zero 3 images from it for testing: https://github.com/pixdrift/armbian_build/tree/0f9820ff2238ab15fdbfef9adfefca47b031a757