Active threads

http://armbian.lv.auroradev.org/beta bookworm/main armhf armbian-bsp-cli-bananapim2ultra-current armhf 25.11.0-trunk.302 [434 kB] http://armbian.lv.auroradev.org/beta bookworm/main armhf armbian-firmware all 25.11.0-trunk.302 [100 MB] http://armbian.lv.auroradev.org/beta bookworm/main armhf linux-dtb-current-sunxi armhf 25.11.0-trunk.302 [211 kB] http://armbian.lv.auroradev.org/beta bookworm/main armhf linux-image-current-sunxi armhf 25.11.0-trunk.302 [41.8 MB] http://armbian.lv.auroradev.org/beta bookworm/main armhf linux-u-boot-bananapim2ultra-current armhf 25.11.0-trunk.302 [271 kB] after update fastfetch: Armbian 25.11.0-trunk.297 bookworm armv7l

Thank you for the answer. Yes I will try the various dts, so far I have found that librelec - despiite not running at all, is crashing giving a visible prompt on the HDMI. I will try to compare that dtb/dts to the default rk3318-box and be back.

Try the 'minimal-iot' flavor, I think that's the only one that boots from the current images. You can then add the desired packages and even switch to the 'edge' kernel from armbian-config.

If you don't mind, just a few points of confirmation. Reading the documentation and the info on the GitHub page for boards, I gather I can probably expect to use ./compile.sh cubox-i However looking in the cubox-i.csc file, which at this moment looks like: # Freescale / NXP iMx6 dual-quad core 1GB/2GB RAM SoC Wifi/BT GBE BOARD_NAME="Cubox i2eX/i4" BOARDFAMILY="imx6" BOARD_MAINTAINER="" BOOTCONFIG="mx6cuboxi_defconfig" KERNEL_TARGET="current,edge" KERNEL_TEST_TARGET="current" FULL_DESKTOP="yes" BOOT_LOGO="desktop" PACKAGE_LIST_BOARD="rfkill bluetooth bluez bluez-tools" I suspect I want to add/change (at least) the following build switches BUILD_MINIMAL="yes" FULL_DESKTOP="no" since I (think I) want the minimal Ubuntu 24.04. The build switches page doesn't talk about the KERNEL_TARGET nor the KERNEL_TEST_TARGET switches. I'm puzzled why there are two kernel targets but only one test target. Also, is there somewhere I can read up on the differences between targets, especially "current" and "edge"? Same sort of question about BOOT_LOGO - are those listed / explained somewhere? Given that I'm looking for a minimal / non-desktop configuration, I still guess I can build from either a server or a desktop Ubuntu running in a VM (or bare metal) as per @Werner's comment. Does that sound correct? Finally I'm guessing this should generate a u-boot based image, given that the Cubox uses u-boot; is that correct? Thanks very much in advance for any clarification.

@NiTr0 Armbian doesn't use $fdtfile because U-Boot carries the same DT already, in memory. If you want to use a different DT, add fdtfile=yourdt to the /boot/armbianEnv.txt. I haven't tried this method. I don’t remember if I tested orange pi 2w. It’s been awhile since I released the image. I think someone has. I have a board laying around somewhere. I'll try it when I'm not busy.

Maybe another important data point to consider – are both of you running the same firmware?

Thank you very much. You are my superman.

I didn't test eMMC, whilst the bug occurred (it definitely impacted the SD card), but I did try using a USB drive and I can confirm (for me at least) the issue went away (the issue impacts the MMC stack, specifically), so if you have a spare USB drive hanging around, and you want an easier interim "fix" you can try putting the rootfs on a USB drive in the meantime. To be clear, the bug still did occur, but as it only impacted the SD card (which was for boot only), it only spammed my log files, but did not impact my day to day running (which with rootfs on SD, it definitely did. Made the device completely unusable pending a hard reset). I'll put the build instructions here too, because it's very simple (This was using a Debian Bookworm/Trixie host): sudo apt install git git clone --depth=1 https://github.com/armbian/build.git cd build ./compile.sh \ BOARD=odroidc1 \ BRANCH=current \ RELEASE=trixie \ BUILD_MINIMAL=yes \ BUILD_DESKTOP=no \ CLEAN_LEVEL= \ PREFER_DOCKER=no \ KERNEL_CONFIGURE=no \ COMPRESS_OUTPUTIMAGE=sha,gpg,img And that's it. Image is saved in: ./output/images

For this 16xx displays we need to ask @Jean-Francois Lessard he was in contact with this drivers for a while. these 16xx displays will be included in the mainline 6.18 drivers as tm16xx_i2c make sure to adjust your device according to this repository to benefit from the update https://github.com/jefflessard/tm16xx-display

Read this entire topic, It's all there, just read it

oh how cool, send a shout out: https://forum.slitaz.org/ Let me read this https://doc.slitaz.org/en:start and I will give you the answer The answer is Yes https://arm.slitaz.org/

Hi, for 2 day i am searching for set a bootlogo on the screen while loading klipper but all i get is the linux text that fly by. I set bootlogo= true in armbianEnv.txt does not help i can't find any other option. There should also be Splash can find any decent information about that either So is it possible to show a logo at booting klipper, if yes is it also possible to change it to custom logo or video because it would be nicer to show a logo or video then al these linux lines And i am not a professional programmer so easy language if possible

Yep, looks like it's about the netplan renderer. I've tried the actual image instead of the one I built locally and even just a reboot is able to reproduce the issue. The main difference is that on the image I built networking was via NetworkManager by default, while the image on the website uses systemd-networkd.

Any news on this subject ? Official Ubuntu is too limited .... I'm thinking to change to armbian my server ..... To install it, does it need a full recompilation ? or is there an img ? where can I find the DTB file for M2 ?

@Hqnicolas I'm a bit late because I have overlooked your request for testing. Now I can confirm that the AuxDisplay works correctly with my H96_tvbox_3566 (with AIC 8800 wlan chip). Thank you for your effort.

Hardware: OrangePI-5-Plus (rk3588), with "32 GB" of RAM Operating System: Debian Trixie (pure, except EFI boot and Armbian edge kernel) Root File System: Ext4 (encrypted) Desktop: KDE Plasma 6.3.6 (wayland, GDM3), KDE Frameworks version: 6.13.0, QT version: 6.8.2 EFI Source: https://github.com/edk2-porting/edk2-rk3588 The boot messages, after a few starts (spaced apart) of the low-memory-monitor.service, say there's a failure to start it. After booting is complete, here's a screenshot of the output of: systemctl status low-memory-monitor.service This error didn't show up until I installed a number of packages. I tracked down the offending package from the Trixie repository: Package: xfsprogs Version: 6.13.0-2+b1 Size: 4774 kB Description: A set of commands to use the XFS filesystem, including mkfs.xfs Once this package was removed, the error vanished, and a repeat of the above Status command reported low-memory-monitor-service as active and okay. I also found that, while the error occurred with the Armbian edge 6.16.4 kernel, it did NOT occur with the Debian 6.16.3 kernel. Kernel With The Error (kernel source: Armbian trixie) --------------------- Package: linux-image-edge-rockchip64 (Armbian Linux edge kernel image 6.16.4-edge-rockchip64) Version: 25.8.1 Size: 282 MB Kernel Without The Error (kernel source: Debian trixie-backports) ------------------------ Package: linux-image-6.16.3+deb13-arm64-unsigned (Linux 6.16 for 64-bit ARMv8 machines) Version: 6.16.3-1~bpo13+1 Size: 210 MB I also briefly tried regressing the Armbian edge kernel from 25.8.1 (6.16.4) to the previously available version of 25.5.2, which was 6.16.0-rc3 (I think). The error occurred with that kernel as well. An Effect of This Bug (Possibly) When this error was showing up, I was once using the internet (firefox-esr package version 140.3.1esr-1~deb13u1) for a while, when after closing it, I discovered that my desktop background image had changed on its own. I could not change it back, no matter what I did (in the KDE settings gui). I could change it to something else, but whenever I changed it back, the altered image returned instead of what it should have been. But once I rebooted, the background was back to normal. While this one experience (very much an outlier) may not be conclusive, it is indicative of a possible memory leak.

ARM CPU running Linux 2GB RAM NPU for AI (maybe as little as CV) ARM MPU running Sketch (Arduino) https://store-usa.arduino.cc/products/uno-q Closed source

PR for these changes: https://github.com/armbian/build/pull/8734

Anyone trying to compile mpv 0.3.9, is it possible to do it with Linux 6.15? With the libraries in Debian Trixie? (considering mpv 0.3.9 is from sept 2024, and Trixie came with mpv-0.4.0) https://github.com/mpv-player/mpv/releases I think I am failing the compilation's linking stage, because I had a different mpv and its libraries already installed. Probably I need to format my microSD and re-image.

apt install f2fs-tools

Is your monitor a standard 1080p resolution or something else? If you try a server build that doesn't load a graphical interface does it work? Have you tried something more standard like gnome instead of cinnamon?

Hey @amazingfate, I have an issue with the build-in IR receiver on my OPI5+: ##O#O## OS: Armbian 25.8.1 noble aarch64 ####### Host: Orange Pi 5 Plus ########### Kernel: 6.1.115-vendor-rk35xx ############# Uptime: 2 mins ############### Packages: 1934 (dpkg), 5 (snap) ################ Shell: bash 5.2.21 ################# Resolution: 3840x2160 ##################### DE: GNOME 46.0 ##################### WM: Mutter ################# WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: x-terminal-emul CPU: (8) @ 1.800GHz Memory: 2585MiB / 15957MiB After a reboot it works just fine, but once I suspend/resume it stops working. Logs look clear of errors. I have tried to troubleshoot with ChatGPT but goin' in circles and gave up. Lastly ended up with some speculations from it like: static int rockchip_pwm_remotectl_resume(struct device *dev) { struct remotectl_dev *rc_dev = dev_get_drvdata(dev); // Re-init or restart the device if (rc_dev && rc_dev->restart) rc_dev->restart(rc_dev); return 0; } static const struct dev_pm_ops rockchip_pwm_remotectl_pm_ops = { .resume = rockchip_pwm_remotectl_resume, }; static struct platform_driver rockchip_pwm_remotectl_driver = { .probe = rockchip_pwm_remotectl_probe, .driver = { .name = "rockchip_pwm_remotectl", .pm = &rockchip_pwm_remotectl_pm_ops, }, }; Do you think this is the problem, or if not can I share some details so you can try to find it?

moved

Not an Armbian image. If you want to use this one, try to get support from where you got the image from.

That's already a topic (with a solution): https://forum.armbian.com/topic/55129-trixie-apt-warning-policy-will-reject-signature-within-a-year/