All Activity

I've been doing some research/reading and I see that this was a problem before with a somewhat similar box with 1.5gb ram: I will try copying the patches over, thank you for all your help so far!

My main theory is that linux 6.12 doesn't have the v4l2 improvements needed for hw acceleration, that you can only get with linux 6.13.... The link i published explains that.

Oh sorry I forgot… you can add the secure boot patch but compiling minimyth2 might take awhile. or you can copy over minimyth2 latest uboot patches. https://github.com/warpme/minimyth2/tree/master/script/bootloaders/u-boot-aw/files these patches are for uboot version 2025.04. So you need to change the version number here. https://github.com/NickAlilovic/build/blob/v20250306/config/sources/families/include/sunxi64_common.inc declare -g BOOTBRANCH="${BOOTBRANCH:-"tag:v2025.01"}"

Do any of those images use secureboot uboot (toc0) that you know of?

You can find secure boot in that link. Also, we are having issues with 1.5g boards. You can read the latest posts in that thread.

@Randlin Have you tried the latest minimyth2 images? https://github.com/warpme/minimyth2/releases/tag/v14.3.0 maybe you can revert to the old ram size detection. https://github.com/warpme/minimyth2/commit/962ac7da6cb84d0e41826c5555cb101b70a53a8d

How does /etc/os-release get updated? Do I need to change bookworm to trixie and 12 to 13 myself after I upgraded?

Unfortunately that patch has not made a significant difference in how far it boots. It does detects 1.5gb in startup now but then detect 2gb later once uboot dts loads and then halts as usual:

Hello everyone, does anyone have his image: https://github.com/NickAlilovic/build/releases/download/20250130/Armbian-unofficial_25.02.0-trunk_Q1_bookworm_edge_6.12.11_xfce_desktop.img.xz I have an h313 board with 1.5Gb DRAM with secureboot

Zero3 root on NFS ，pxlinux cfg： LABEL linux KERNEL /zero3/vmlinuz-6.15.4-edge-sunxi64 FDTDIR /zero3/dtb-6.15.4-edge-sunxi64 DEVICETREE-OVERLAY /zero3/dtb-6.15.4-edge-sunxi64/allwinner/overlay/sun50i-h616-uart5.dtbo /zero3/dtb-6.15.4-edge-sunxi64/allwinner/overlay/sun50i-h616-spi-spidev.dtbo /zero3/overlay-user/spidev1_1.dtbo APPEND root=/dev/nfs initrd=/zero3/initrd.img-6.15.4-edge-sunxi64 nfsroot=192.168.20.20:/mnt/mass/data/linux/zero3/zero31 ip=dhcp rw rootwait DEFAULT linux

Thank you so much for your generosity, @coroner21. I shall do my very best to keep the machine well maintained in Armbian.

No, I did not compile this time. I used the downloaded image (need to double check exactly which one). Before trying this path (have to update my build env first😀) I'd try to get a better understanding about the root cause of the slowness. I think next I'll play around with mpv instead of ffmpeg. I'd prefer ffmpeg for other reasons, but testing mpv is worth to spend some time. T.

Start reading here..

Getting the grub bootloader right with tow-boot's efi implementation seems like the most urgent as it is a hard blocking anyone trying to install. As tow-boot isn't unique to pinebook pro my guess is that handling it impacts other systems. I don't know what would be involved in maintaining it.

hello everyone! I bought this tv box..https://www.aliexpress.com/item/1005009346784515.html?spm=a2g0o.order_list.order_list_main.11.79e81802pgNRxu but after starting it was not possible to log in to googleplay even though I had a connection via wifi or ethernet. the preinstalled version for applications was Aptoide TV..through it I wanted to update all applications (youtube, netflix, etc.) I managed to do that but no application could be started. the original file manager did not show the internal memory or USB disk or SD card until I managed to download ES file manager through aptoide and it showed my flash disk I installed HW info device and there I found out that it was an RK3528 chip. so I wanted to flash the firmware and I used a rom image for H96max with the same parameters. the firmware upgrade went OK but the device is dead. I can't find the correct firmware. I'm attaching a photo--- maybe someone will recognize the board and identify which rom-img should be correct. the seller can't help me in any way.

Did you compile your armbian OS with linux edge 6.15.x, bookworm, xfce? https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/#findComment-216587

Our release will also be around Noble / Trixie + minimal image with Bookworm. For those that wants to stay on a safe side x86 images were already released: https://www.armbian.com/uefi-x86/ and few others ...

@Thiên Thư Lục USB3 is little half working and i have USB-3 HD/SSD and its freezing some times but normally Armbian is running stable on it. Also general devices in the USB3 jack is freezing like SDR dongle stop being recognized then being pullrd out and in agenand need one repower of the box for getting the USB3 jack working agen. The factory Android bootloader is not supporting USB boot only SD-Card or eMMC . Write one updated / new on the eMMC (can soft bricking the box) or erase the eMMC shall doing it then the chip is loading it from the SD-Card if not found eMMC. Also putting in one SD-Card with updated boootoader and it shall being possible "jump starting" to USB devices like sticks and HDs from the SD-Card.

@robertoj right, that worked for me as well But the remaining issue is the slowness. Meanwhile I also tested ffmpeg unscaled and no rgb conversion to /dev/null outputt but still slow. Maybe there is some pre/postprocessing done which cloud be tuned further. If i remember right there are some v4l2* features which may impact the processing but I'm not sure if this was camera capture related. Another idea: It seems the VPU clock source is configurable (inside DT) maybe that's not quite right? T.

@Nick A sorrry but i didn't found where you replied to me could you repost it to mine trhead?😁

Thanks for noticing me!!! I will check the last thread ive been in and the dram settings and dts, i havent checked also i cant edit/change dram and dts, i use windows but i will use a virtual machine to get the armbian doing its job. and from the secure boot, it could be because when i do the “toothpick method”, it showed the updating screen but nothing updated thanks you for replying to me edit: is the text too blurry? I could take more 😃

The helios4 is on its way to @laibsch. It is not available anymore...

Some fixes are kernel specific. If I understand correctly, the "memory-region" is only necessary when using the legacy cedar driver with a more recent kernel. It is supported up to kernel 6.1. You can confirm CMA allocation by running "sudo dmesg | grep CMA" or by running "cat /proc/meminfo | grep Cma" That's interesting, although cedrus only acts as the video decoding engine while the display engine is responsible for the actual rendering.

@Ducdanh Nguyen @ccs1664 is correct.. there’s a lot of information on that thread and the x96q threads to get your box running. I have to post the same advice over and over again. The last thread you posted in. I gave instructions to get your dram settings and dts. Have you extracted them? it could be possible that you have secure boot.