Active threads

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"}"

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.

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

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.

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.

@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.

yep, thats how i connected them i think it might be that? ill try to get some fresh wires and see if it helps

I also confirmed that USB-C functionality is still not working on ODROID-M2 with Kernel 6.16 RC. I guess we would have to wait a little more for the working USB-C Port.

Depending on your location this might not be anything that can be fixed on Armbian side. If this happens on any mirror, the issue is either your setup or ISP blocking access.

THANK YOU

I get this warning because I removed lightdm-gtk-greeter.desktop... what should I do to not expect the file? roberto@orangepizero3:~$ update-alternatives --display lightdm-greeter update-alternatives: warning: alternative /usr/share/xgreeters/lightdm-gtk-greeter.desktop (part of link group lightdm-greeter) doesn't exist; removing from list of alternatives lightdm-greeter - auto mode link best version is /usr/local/share/xgreeters/pi-greeter.desktop link currently points to /usr/local/share/xgreeters/pi-greeter.desktop link lightdm-greeter is /usr/share/xgreeters/lightdm-greeter.desktop /usr/local/share/xgreeters/pi-greeter.desktop - priority 70 After some research of greeters, I see that the default greeter is compatible with wayland https://github.com/Xubuntu/lightdm-gtk-greeter I have been working as if lightdm requires X11 (which I need to avoid), and so I wanted to used pi-greeter Does anybody have lightdm+gtkgreeter in a pure wayland setup? No X11

However, we're seeing a problem with kernel 6.12.x where the first time the computer is turned on, ArmBian doesn't always boot. Only after powering down and turning it back on does the Orange Pi Zero v1 start booting. This problem didn't occur previously on the same hardware, so perhaps updating U-Boot to version v2025.04 would solve the problem. We'd like to ask those who are also making changes to the Orange Pi Zero V1 to update U-Boot.

If I remember correctly, it is possible to mount such partition flashed to usb or sd within WSL (just ensure that proper support is installed into WSL) and make any changes. It is possible even to script changes to be run under windows, though I can't remember how exactly this is done. Probably AI can hint.

I have an old and weak mxq pro 4k TV box (fake amlogic s905w), rk3228a checked, sv6051p wifi. I recorded the desired version on the micro sd via the multiboot.img adapter and it worked but did not respond to the remote control, I checked the remote for robotics, recorded libre elec and booted from it without multiboot and it even worked on wi-fi and the remote reacted, I replaced the dtb file and booted from the multiube but it no longer worked I thought that dtb was capricious and decided to replace only part of the it_receiver code in dts format and converted it and recorded it via dd on Linux, but this time the eumultool worked but the remote control did not respond again. I do not know why it stopped turning on on android 7.1.2, but I know for sure that after downloading minecraft or similar games, it will boot up and you can go to recovery, I tried two firmware for TV box in the format.zip but there was a message map location failed like I recorded the desired version on the micro sd via the multiboot.img adapter and it worked but did not respond to the remote control, I checked the remote for robotics, recorded libre elec and booted from it without multiboot and it even worked on wi-fi and the remote reacted, I replaced the dtb file and booted from the multiube but it no longer worked I thought that dtb was capricious and decided to replace only part of the it_receiver code in dts format and converted it and recorded it via dd on Linux, but this time the eumultool worked but the remote control did not respond again. I do not know why it stopped turning on on android 7.1.2, but I know for sure that after downloading minecraft or similar games, it will boot up and you can go to recovery, I tried two firmware for TV box in the format.zip but there was a message map location failed like that,this is off topic, but please help me fix this, I definitely need linux to make a server for the telegram bot.

Try SharpExt4Explorer: https://github.com/nickdu088/SharpExt4Explorer

Hello, I have a massive problem as the time/date on my Pine64 keep changing randomly to the year 2113. In my project, I use several Pine64s and the problem now occurs on many of these Pine64s. Unfortunately I need the correct time for my project. I am using the following system: ARMBIAN 5.32.170911 nightly Ubuntu 16.04.3 LTS 4.13.0-sun50iw1 (with additional overlays = uart3 and console = ttyS3) Could this be due to the error described in the post and is the bug fixed in kernel version 4.14? Could I install this kernel version 4.14 via armbian-config (next-kernel)? Thanks a lot for help.

It works like a charm. Thanks so much!

you can install and boot from the sd card, also h616 uses nand flash, which can't write on it (or maybe it uses emmc)

So I had a guy from Fiverr take a look at it and this is what he said he found. I'm not sure if this rings and bells or not? But he is still digging. Regarding the quectel card, it's extremely weird. Both images have the exact same dtbs, overlays and drivers, but it works on both Joshuas and the official image but not on armbian. One thing I have found different between those is the gpio pin states. Armbian image has different gpio states from the other. But idk if that is a side effect or the cause.

Thanks for the quick answer. I have ordered a USB serial adapter and should receive it next week. I'll update.

sudo apt-mark hold linux-image-vendor-rk35xx sudo apt-mark hold linux-dtb-vendor-rk35xx