All Activity

I don't know what else to do... I usually research and learn on the go Search the 88xxau.c in your downloaded linux source. Try to find any link to documentation or github. Search 8812au in the respberry pi forum

Hi! On the Orange Pi 5 plus with the 6.1 image (KDE), with a 4k monitor @ 60FPS and 200% scaling, when opening discord on Chrome it gets incredibly laggy. I'm just curious, is this a limitation with the GPU itself, or is this related to something in the software stack? Thanks!

The actions in the dts for setting the GPIO pin are is based on the boot log line. marlin chip en dummy pull up -- need manually set GPIO You can check the whole discussion here and the reasoning https://chatgpt.com/share/68466d15-e5bc-8013-b200-17ae7f7c89fc However, After your last answer, Chatgpt suggests this is not really the issue, but a delayed initialisation would help. When the bt fails to initialise, try the following: sudo hciattach /dev/ttyS0 any 115200 flow sudo hciconfig hci0 up If this works, you can put this in a service to run at every boot. You can try yourself to continue the above conversation with chatgpt and see if you find the final solution. Then you can post it here.

I have decompiled the dtb file but am unable to incorporate the patch. How do i incorporate the patch or change it? In terms for a newbie please! I should say it is for debian 12 Cinnamon 6.12.

NO_PUBKEY 93D6889F9F0E78D5 while using apt (e.g. apt update) symptom: > apt update ... Err:8 https://github.armbian.com/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 ... W: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 observed in Armbian image for Orange pi zero 3 Armbian_community_25.8.0-trunk.90_Orangepizero3_bookworm_current_6.12.30_minimal.img build date May 28, 2025 fix: - run this as root > su - ^ login as root > wget -O - https://apt.armbian.com/armbian.key | gpg --dearmor -o /usr/share/keyrings/armbian.gpg you should find a file /usr/share/keyrings/armbian.gpg about 2 KB in size repeat apt update etc should have resolved the error

NO_PUBKEY 93D6889F9F0E78D5 while using apt (e.g. apt update) symptom: > apt update ... Err:8 https://github.armbian.com/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 ... W: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 observed in Armbian image for Orange pi zero 3 Armbian_community_25.8.0-trunk.90_Orangepizero3_bookworm_current_6.12.30_minimal.img build date May 28, 2025 fix: - run this as root > su - ^ login as root > wget -O - https://apt.armbian.com/armbian.key | gpg --dearmor -o /usr/share/keyrings/armbian.gpg you should find a file /usr/share/keyrings/armbian.gpg about 2 KB in size repeat apt update etc should have resolved the error

symptom: > apt update ... Err:8 https://github.armbian.com/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 ... W: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 observed in Armbian image for Orange pi zero 3 Armbian_community_25.8.0-trunk.90_Orangepizero3_bookworm_current_6.12.30_minimal.img build date May 28, 2025 fix: - run this as root > su - ^ login as root > wget -O - https://apt.armbian.com/armbian.key | gpg --dearmor -o /usr/share/keyrings/armbian.gpg you should find a file /usr/share/keyrings/armbian.gpg about 2 KB in size repeat apt update etc should have resolved the error

@Igor no worries about the delay, I'm just adding a feedback that symptoms are observed in the orangepi zero 3 miminal images as well, I've not tried other images hence can't comment about it. I'd likely try to reproduce the error and post my solution in this thread as well as in the orange pi zero 3 thread, possibly in the tutorials section of the forum as well i found the solution via some google searches then, and I'd try to reproduce that.

Just FYI why images are delayed. GitHub, which we rely our build infrastructure on, is having many troubles and builds does not start due to out of (their) resources (probably). 30 out 30 tries, I am getting Error: Error 504: We couldn't respond to your request in time. Sorry about that. Please try resubmitting your request and contact us if the problem persists. Perhaps this is a limitation of free tier, dunno.

So I understand that no one will help me because I am not a programmer.

At this point anything like thoughts, clues and things you heard about would be helpful because I don't find any solutions online too

4 of 5 times works well then failed. bt_boot_fail_05.txt Could you explaint it to me what you suggest to do? As I see you tried to set logic level on PH1 pin on CPU. In accordance with schematic this pin is connected to debug UART (RX) signal and doesn't affect on wireless chip. So I don't understand what you try to do. One more thing is BT and WiFi are in one chip, WiFi works well every time. As I understand the issue doesn't affect the chip itself otherwise WiFi wouldn't work either.

You can try on actual machine by editing device tree file. (/boot/dtb/rockchip/name.dtb probably rock5b something) https://chatgpt.com/share/684bbac2-2728-8005-bb50-a2751316ac2b If similar changes work - you need to reboot to apply changes - then report here.

@Igor apparently I run into a similar/same issue while using minimal / IOT images for Orange Pi Zero 3 25.8.0 Build Date: May 28, 2025 just downloaded yesterday 12 Jun 25 https://www.armbian.com/orange-pi-zero-3/ do update the links if the images are updated as well with the gpg keys files

https://source.android.com/

TV boxes are Community supported. That means they are not supported by Armbian. It is up to community members like you to figure these things out and submit them back to the community through your contributions.

This is 88XXAU in the config. Yes, this driver allows you to see the device as a network device, the adapter gets a new interface name wlx<macaddress>, but it cannot connect to the network and does not receive a list of available networks.

Those builds are made by automation, once per week if nothing else goes wrong.

Armbian Development Highlights: June 2–9, 2025 This week’s Armbian updates focused on kernel improvements, bootloader modernization, and several core enhancements to the build infrastructure. Key work spanned platforms like Rockchip, Sunxi, and Odroid, emphasizing kernel stability and broader compatibility across boards. Kernel Upgrades Several boards received kernel updates: Rockchip 32-bit edge kernel bumped to 6.15 in PR #8262 by paolosabatino. SpacemiT platforms updated to 6.6.93 in PR #8274 by pyavitz. Odroid XU4 kernel upgraded to 6.6.93 via PR #8277 by belegdol. Patches also landed to adapt Wi-Fi drivers to 6.15-era changes, including fixes for xradio and uwe5622 on Sunxi, contributed by The-going: sunxi: xradio – Switch from del_timer_sync to timer_delete_sync uwe5622: Fix timer API changes for 6.15 Bootloader and U-Boot Work Improvements were made to bootloader support: Tinkerboard 2 now uses U-Boot v2025.04 (PR #8268 by hyx0329). RK3328 boards gained setexpr support in U-Boot v2022.04/07 (PR #8260 by djurny). Build System Changes Several build system enhancements landed this cycle: PR #8276 by Ayush1325 prevented unintentional conversion of built-in kernel drivers to modules. A new helper function chroot_sdcard_custom_with_apt_logic was introduced in PR #8245 by rpardini, streamlining SD card build logic. PR #8279 by igorpecovnik removed obsolete Trixie package references. Networking Improvements PR #8259 and commit cdf71df by djurny expanded DHCP configuration in netplan to automatically include interfaces matching lan* and wan*, simplifying initial setup across devices. Miscellaneous Signing key backward compatibility was preserved in PR #8282 and commit aa5526a by igorpecovnik. Commit 0f43036 reworked prepare-host.sh after review. Contributors This Week Ayush1325 The-going djurny igorpecovnik pyavitz belegdol hyx0329 rpardini paolosabatino The post Armbian Weekly Updates first appeared on Armbian. View the full article

I forgot to write that I use meson-sm1-x96-air-gbit.dtb. Kernel 6.12.31-current-meson64. Please provide a .dtb file with working SPDIF. It may be a different kernel version. If I had any .dtb file with working SPDIF I could modify my file using the "fdtput" command.

ok thanks

@svyatoslav freeze the kernel updates using the armbian-config tool.

Thanks Igor for identifying the root cause. When will this fix be released so that I can used Orange pi Zero 2 with latest build with above problem fixed?

Thanks I saw that patch but have no idea how to apply it or what to do with it or if it even works in this version? If someone could help that would be great!

Hi there! We have some good news, a guy from the 4pda forums figured out how to make the missing SD slot work. I've replicated that on my M9s box a few days ago and it works like a charm. You can see original post in Russian here. So, basically, this TV box uses the same reference design for that circuitry as Armsom Sige5 and other boards. You can check the diagrams for Sige5 to get an idea. You need two capacitors (10uF and 100nF, on the power line) on the SD slot side (two smaller pads) and a LPW5202ADB5F chip and some resistors and caps on the other side. LPW5202ADB5F is a power switch chip with current limiter, can be bought on Aliexpress for like $5-6 for 20 pcs, also need these components: 1x 10k resistor - controls current limiter (this value is for 0.7A according to data sheet, lower values for higher current, or 3.6k = 2A), 2x 10uF caps on power input/output lines 1x 100k - pull down resistor on the 'enable' contact 1x 2k - limiting resistor from the CPU to the 'enable' line 6x 22 Ohm resistors for the data lines between CPU and SD card slot In theory, it's possible to put a zero-ohm resistor between in and out instead of that switch chip, in that case SD slot will be powered all the time and won't have a current limiter.