Werner

@Igor can do that. My guess is that the previous owners of the domain forgot to extend and therefore it expired and now some domain grabber registered it.

Why not ask where it might more sense and chances for answers are greater? https://forums.rockylinux.org/

Actually the first bsp was that which was built around a 5.10.110 and later .160 android hacked together kernel. 6.1 is AFAIK a real linux kernel rockchip used for newer bsp.

There is nothing we can do about this error.

https://developer.arm.com/Arm Security Center/Speculative Processor Vulnerability On the bottom line there is nothing we can do about this. If mitigation is upstreamed to ATF, Kernel or wherever needed/possible Armbian will adapt it most likely automatically. Dug a bit deeper https://developer.arm.com/-/media/Arm Developer Community/PDF/Security update 21 May 18/Software_Overview_for_Arm_Cores_PUBLIC v1.2.pdf?revision=7bb9a901-9a1d-4975-b460-743f5da90502&hash=14B19D60AC5650AF05225AEECC5E3D816E08B47B https://cateee.net/lkddb/web-lkddb/MITIGATION_PAGE_TABLE_ISOLATION.html Though this seems to be a software mitigation for x86 only. No clue if there is further development ongoing.

https://backports.debian.org/news/Removal_of_buster-backports_from_the_debian_archive/

Debugging boot issues: https://debug.armbian.de

Hi and welcome. tl;dr version: ./compile.sh and following interactive menu will output an image based on selection. Image will be in output/images created debs are just side products ./compile.sh kernel BOARD=orangepi5plus BRANCH=vendor will create a set of kernel deb files only and will be in output/debs

Try PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u I leave this here for others to find and use this workaround.

Hi, have you tried to check with a tool like this? https://github.com/speed47/spectre-meltdown-checker Just found this: https://patchwork.kernel.org/project/linux-arm-kernel/cover/20241214005248.198803-1-dianders@chromium.org/ So there might come some enhancements with Linux 6.14 or 6.15

Tried suggestions from here? https://docs.armbian.com/User-Guide_Recovery/#replacing-boot

Easiest way to make adjustments for uboot and kernel for a specific board is using the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } uboot-patch and code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } kernel-patch commands. This will pause compilation and tells you where the sources are that you want to patch. When done it automatically creates proper patch files for you. So like this for example: ./compile.sh kernel-patch BRANCH=current BOARD=orangepi4

Hi Nobody here has a second sight. What exact error message? What exact did you try? What exact image did you use? Insufficient information.

Hm @Igor might be playing with Oracular. Though both this userspace and the upgrade to it are completely unsupported by Armbian. Therefore moved out of standard support for now.

mainline support for rk3588 isn't complete yet. I suggest to try vendor 6.1.y kernel based image.

Yes, something doesnt work well there. In the mean time try this: code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u

This board has lots of features. So it is kind of expected that not everything works just yet oob. You may wanna try a more recent vendor bsp kernel based image from the ci: https://github.com/armbian/os/releases/tag/25.2.0-trunk.128 (search for "itx") Maybe this was fixed already.

Did you reach out to the author? https://github.com/cgomesu/nanopim4-satahat-fan It seems there were a few adjustments since we implemented it: https://github.com/cgomesu/nanopim4-satahat-fan/commits/master/pwm-fan.sh

hwclock might be a part of the util-linux-extra package. Make sure that one is installed as well and then logout/login to refresh shell.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

best chances to get an idea what happens inside is using debug console: https://debug.armbian.de

Known issue https://github.com/armbian/configng/issues/316#issuecomment-2535941450

moved Standard support forums are missing. Will be adjusted later

Welcome https://docs.armbian.com/User-Guide_Getting-Started/

I am not aware that this can or needs to be setup in any way. I just boots up when power is connected. I did not test with microsd (I use SPI/NVMe) but I assume it works the same way.