Active threads

Its 64bit, but support quality (tl;dr;) of Allwinner is behind Rockchip.

Created another standalone version of script for this ... https://gist.github.com/avatar21/e0deca347665bd620d0ea3f9f299028e I believe we need to compile our own armbian/ Kernel 6.13 (or above? because as @elvis claimed user driver is only 1/2 of the equation) before running this script ya? all copy/ flatten to a temp/fake root folder (where I understand the chroot sdcard means, build to a fakeroot not patching existing OS) and repackage as an img file ya? Or better still, can someone compile the whole thing? start from burning image ...

Thanks for your help, and I found the official image not support NPU, only Joshua-Riek image support? @Hqnicolas root@h96-tvbox-3566:~# ls /dev/dri/ by-path card0 card1 renderD128

During the first few boots on my Orange Pi Zero 3 1GB, RAM size seemed to be detected correctly. Yesterday I saw RAM size being reported as 2GB, also after a reboot. As soon as the fixed U-Boot is available to install I am happy to provide test results or other test procedures when needed!

Glade to see you back @sicxnull. Thanks for the shoutout! Tried my best while you were gone. I don’t own one of these boxes. But I guess it doesn’t matter which one I get because theirs so many variations of the same box.

I try your prebuild image, and no luck with wifi/Bluetooth. My tv box new revision and have YC8800D wifi chip. Can i do something to get work WiFi?

Thanks for this!

Rockchip devices generally cannot be bricked. Short the maskrom pin i showed you and reflash. You can build the image from source or from here https://github.com/armbian/community/releases

Am also have T95Z Plus w/ H616 and my TV box new revision. It has another wifi chip YC8800D. tried to run this build https://github.com/LYU4662/t95zplus-h618-build It work fine but no wifi and Bluetooth. Looks like it made already with 8800 driver, but system does recognize any wireless interfaces. Also try to run community build Armbian-unofficial_25.05.0-trunk_Vontar-h618_bookworm_edge_6.12.11_server Its running good, but still no wifi and Bluetooth. In android /vendor/lib/modules found attached modules. Can i use them to get work wifi? aic8800_bsp.ko aic8800_btlpm.ko aic8800_fdrv.ko

Try looking for hints here: https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/rockchip/ They use mali blobs for hw en-/decoding.

seems like the config should be distinguishing by models, not by .. idk even what it is. let say config->OrangePi2->hardware->peripherals->i2c->i2's enumerate.

All the kernel panic options that you have shown here occur on v6.12.23. It all happens randomly. I suspect that this may be due to the presence of broken (faulty) blocks on the memory device. It's easy to check this.If you connect the SD card via an adapter to a Linux computer: sudo fsck.ext4 /dev/sdX1

I assume should work with vendor. Maybe missing node in device tree. Maybe missing firmware blobs or same as above. Expected since neither SPI nor eMMC are present by default. Direct boot from NVMe isn't support by any Rockchip soc.

does anyone know how to get maskrom and uart on this rk3228a board from mxq pro 4k 5G since pushing the little button shows up as armlogic devices on device manager but the actual chip is rockchip and sorry for bad quality images

Seems it is an option for timer resolution in the measurement of duration. But the topic is about CPU usage precision returned by getrusage function. it is hardcoded interval of time when kernel updates CPU usage of particular thread/process.

All Armbian board configurations files live in build/config/board/ Besides the Pcduino2 Cubieboard and OlinuXino-lime board, I don't know what other A10 boards still have some level of support. After that the next step would probably be to confirm that it works with uboot. Here you have another config file and dts. For any tweaks to uboot you will need to pass uboot-patch when running compile.sh. Note that when you do this you will need to open a new tab and navigate to cache/sources/u-boot-worktree/ Similiarly for the kernel you would navigate to cache/sources/kernel/ currently 6.12 is "current" while 6.14 is "edge" Hope this helps Ryzer

For production, boxes are much more interesting than boards. We just need to deal with a honest manufacturer. The last dtb from @mmie4jbcu worked very well for me in a x88 pro 20.

That solves it thank you very much for your time! If I want to change between boards like Rockpro64, Raspberry Pi4, etc. is there anything that needs to be considered as far as "reset" to a fresh state. For the guide I am writing I would like to make sure there is no lingering configuration that could cause problems when switching between builds for different boards.

All things being equal....... steve@fedora43:~$ uname -a Linux fedora43 6.16.0-0.rc0.250528gfeacb1774bd5.5.fc43.aarch64 #1 SMP PREEMPT_DYNAMIC Wed May 28 19:45:02 UTC 2025 aarch64 GNU/Linux kernel-6.16.0-0.rc0.250529g90b83efa6701.6.fc43. created by jforbes 6 hours ago for Fedora 43 .

Hello. I wonder if this issue is connected to my issue - to show something on i2c, while there is nothing, and not be able to communicate on it ?

Beta repository. - should be on servers where we push on directly and this error can't occur (unless something broke down) - is the same quality as other Linux distributions (there is no other distro that would maintain those custom devices) - currently assembly is broken as some patches are failing and thus (beta) repo is not getting any updates until its fixed https://github.com/armbian/os/actions/runs/15337468717/job/43160986093

Since you are on current you cannot expect a major bump until the next LTS kernel is released. current will receive security fixes only. If you want something more recent you need to switch to edge kernels which follow non-LTS mainline kernel releases.

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

@remolaan I think this is the most current info that may help you:

I own a CM3588 NAS board from FriendlyElec. The eMMC drive was factory-installed with the FriendlyElec version of OpenMediaVault, and any other FriendlyElec or Armbian image could be booted from an SD card. After installing the current version of Armbian OpenMediaVault (Debian 12 Bookworm - Armbian Linux v6.1 Build Date: Mar 6, 2025) on eMMC and updating bootloader via armbian-config (option Boot from eMMC + system on eMMC), nothing else can be booted from the SD card except Armbian images. Please, is there a simple way to fix bootloader back to original option of booting FriendlyElec images from SD card without having to erase entire eMMC drive? Boot from SD card does not work even for FriendlyElec automatic eflasher (SD to eMMC) images. I have Windows 11 and RKDevTool 3.30 is quite confusing and too complex software for me. PS. Does the CM3588 NAS board have SPI NOR flash? And how can I upload UEFI 1.1 boot (https://github.com/edk2-porting/edk2-rk3588) to eMMC or to SPI NOR?