Active threads

I burned the image with Balena Etcher and verified it. After the first attempt it did not boot. Downloaded and burned the image a second time on a different SD card, again not booting. The green light on the board stays on. I'm a fan of Armbian. Never had issues on my RPI5. I hoped this new powerfull SBC would be the same but no, Armbian is not working and the RADXA OS also is giving me lots of problems. Sorry to say, I'm a little dissapointed... Ernst-Jan

With the errant icon, yeah that kind of thing can be really frustrating with linux design. I'm not that deeply familiar with it. Usually when I experience something like that, I look it up in a search engine. What I can say is that many settings are stored in hidden directories under the user home folder. Hidden files start with a period. Go to your home directory: ls -la ...but which one to explore and what to look for... You'll probably find what you're looking for with a search engine. And on your rant, yes I've sensed our views of the computing world to be similar as well. Punching holes in cards - yes! You really would have to think and get it right the first time. And it's not so hard to do. You set the standard, practice it and make it a habit. My second computer was a Commodore 64, back in the early-mid '80s. I played lots of games on there. Even though I'd started programming in BASIC before that, I learned more to program on that computer, in BASIC, and in assembly language. I experienced from others' software and what I could do on my own, to be resourceful, and that creating software that is highly functional and can do "a lot" really doesn't require much more than a tiny program. There's no excuse for complicated software. Also others and myself created it right the first time without any "patches" or "software updates" BS - once it was done, it was done right! I almost never encountered bugs from others' software on my C64. I think there was one game than had bugs in it - that's it, it was an outlier. My first experience with the extremeness of bloating was with my first x86 PC around 1991 i think. It ran MS-DOS 5.0, which took up around 7 or 8 MB as I recall, on the hard drive (or was that Windows 3.1?). And to create an assembly language program that was just a "hello world", an executable .com of that would be around 30 bytes or so, but an executable .exe was around 784K or something crazy like that. 99% of that was .exe format overhead junk! And for today's operating systems and their functionality, there really is no excuse why the total size of the complete operating system on the hard drive should exceed a megabyte (or half that), let alone several gigabytes. The bloating of today is so far beyond reason it's way off in another galaxy. A minimum of 10,000 to 1. So much software today is based on scripting languages and run-time interpreters. Plus the linux operating system was originally designed back in the 1960s!!! ...as unix, before it was ported to personal computers as linux. Apparently, they've got layer upon layer upon layer of patches and changes and different ideas and outdated models all enmeshed in a galactic-sized mess. I've also seen how the MB, GB, and TB have been hijacked by a crooked industry which has redefined those terms to be powers of 1000 rather than the truth that they're powers of 1024. Even with that, the amount delivered on memory and storage devices, in may cases, falls short even of that crooked re-definition. Now an actual GB or MB is called "GiB" or "MiB", while what is often now called a MB or GB is a bold-faced lie! What the computer hardware and OS development needs is to throw away the existing model and create a new one from scratch. As a software engineer, I have done that numerous times on my own projects, and the result is always a spectacular improvement because I can apply what I learned from the previous iteration in developing the new foundation. And that's always a simple, creative and enjoyable process. It does take a some time to do, but the results are more than worth it, and the resulting accelerated pace of development later more than makes up for it. The Orange PI 5 Plus is my first ARM board. What I'm more looking forward to though is getting into RISC-V. I'm not to familiar with it yet, but It's completely open and apparently values simplicity. That might be a really great development environment for something genuinely new.

@Faheem328 Do you have free time? how much free time do you have exactly? we are looking for someone like you with a RK3528 box we are depending on him finding a weekend to dedicate to the community https://github.com/ilyakurdyukov/rk3528-tvbox he will help us by taking this repository and including it in armbian with a wonderful pull request let's talk?

Hi @Fiery_Fire, all the changes I used have been merged to armbian. I tried to build an image from the current main branch and I got no HDMI output too. I tried a newer kernel and applied all the patches from xdarklight's branch https://github.com/xdarklight/linux/tree/meson-mx-integration-6.15-20250608, here is an armbian branch: https://github.com/domin144/armbian-build/tree/meson_6.16 I compiled with this command: ./compile.sh build BOARD=aml-s805-mxq BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=trixie Now I get some output on HDMI, but it is so distorted, I cannot read any text. Something must have been changed in the 6.12 kernel between the time I tried it last and now. Unfortunately I will not have time to debug this in a foreseeable future. Hopefully this distorted output will be a better starting point for you than no output at all.

@rockamal maybe you’ll have better luck with x96q lpddr3 https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build pico patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch Change @@ -0,0 +1,191 @@ to @@ -0,0 +1,192 @@ add this to the bottom of the patch "+CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" Then you need to include the secure boot patch. pico patch/u-boot/u-boot-h616/secure-boot.patch create the secure boot patch. you can find it here.

Thanks for giving it a nudge. Looks like some activity's brewing on it now. @laibsch, As I said before, I don't have an account with github. But I had looked at your Commit, and it looked to me like you copied the existing edge kernel's .dts, but with the needed modification. From my looking at it, I think it would work. Although if I were doing it, I would do it in 2 commits: 1. An initial commit that's just a copy of the present devicetree to bring it into the patch system, since it's apparently never been part of the patch system. 2. The change to address the specific issue. To address what paolosabatino's, comment on github said... The current kernel and edge kernel have two different devicetrees. The one this is about is the edge kernel's devicetree.

sorry for the delay, @mvpwar for RK3566 NPU you can use the original armbian DTB that enables NPU support: https://github.com/armbian/linux-rockchip/blob/rk-6.1-rkr5.1/arch/arm64/boot/dts/rockchip/rk3566-h96max-v56.dts I think you will take fragments from ancient builds like this: https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/16/#findComment-211031 I don't know what the status is in version 6.17 but we are still required to use vendor 6.1

Recently, when I run `armbian-upgrade`, I was greeted with an update to raspi-firmware. However, this version of firmware doesn't seem to work with the corresponding intramfs with kernel 6.12.44. sudo armbian-upgrade Hit:1 https://mirrors.ustc.edu.cn/armbian trixie InRelease Hit:2 https://mirrors.ustc.edu.cn/debian trixie InRelease Hit:3 https://mirrors.ustc.edu.cn/debian trixie-updates InRelease Hit:4 https://mirrors.ustc.edu.cn/debian-security trixie-security InRelease Hit:5 https://github.armbian.com/configng stable InRelease Get:6 https://apt.syncthing.net syncthing InRelease [24.2 kB] Fetched 24.2 kB in 2s (14.8 kB/s) 2 packages can be upgraded. Run 'apt list --upgradable' to see them. The following packages will be upgraded: armbian-config raspi-firmware Summary: Upgraded: 2, Newly installed: 0, To remove: 0, Not upgraded: 0 Download size: 13.2 MB Space required/available: 272 kB / 553 GB Get:1 https://mirrors.ustc.edu.cn/armbian trixie/trixie-utils arm64 raspi-firmware all 1:1.20250915-1~bookworm [13.0 MB] Get:2 https://github.armbian.com/configng stable/main arm64 armbian-config all 25.11.0-trunk.234.0923.175957 [157 kB] Fetched 13.2 MB in 2s (5,967 kB/s) (Reading database ... 46602 files and directories currently installed.) Preparing to unpack .../raspi-firmware_1%3a1.20250915-1~bookworm_all.deb ... Unpacking raspi-firmware (1:1.20250915-1~bookworm) over (1:1.20250430-4~bookworm) ... Preparing to unpack .../armbian-config_25.11.0-trunk.234.0923.175957_all.deb ... Unpacking armbian-config (25.11.0-trunk.234.0923.175957) over (25.11.0-trunk.192.0915.191809) ... Setting up armbian-config (25.11.0-trunk.234.0923.175957) ... Setting up raspi-firmware (1:1.20250915-1~bookworm) ... Installing new version of config file /etc/initramfs/post-update.d/z50-raspi-firmware ... Installing new version of config file /etc/kernel/postinst.d/z50-raspi-firmware ... WARNING: Unsupported kernel version (6.12.44-current-bcm2711) - skipping setup NOTE: Manual boot configuration may be required Processing triggers for initramfs-tools (0.148.3) ... update-initramfs: Generating /boot/initrd.img-6.12.44-current-bcm2711 WARNING: Unsupported initramfs version (6.12.44-current-bcm2711) - skipping setup NOTE: Manual boot configuration may be required Summary: Upgraded: 0, Newly installed: 0, To remove: 0, Not upgraded: 0 How exactly should I do in this case? In the past, I normally invoke update-intramfs to perform the the intramfs update. Thanks,

You're welcome @Hqnicolas 👍

Thank you for that additional information, Igor. The lack of desktop images is only a minor inconvenience, I'd say. Easy enough to install the required packages after installation of the base image to the SBC itself.

HW (features are determined by kernel used in the image) related issues are shared among all variants, desktop, cli, minimal, Debian or Ubuntu.

@Fredrik thank you for the reply. I wonder what's Gnome doing to initialize the audio that's different from a regular (non-graphical) boot. FWIW I installed also Pipewire/Wireplumber and tried to test the audio through the PW ALSA emulation, but that didn't work either. Just out of curiosity, does speaker-test work from the CLI once booted into Gnome or is it just the sound test in Gnome settings that's working ?

I troubleshooted my problem! So for some reason (I'm not sure if this is for all x88 pro 10's), the SD card needed to be under pressure on it to read Multitool. So, throughout the entire Multitool process, I needed to hold down the SD card with my thumb. I did hurt a bit, but it flashed to the EMMC

I retried that image now but with a different installation method, booting into OOWOW (?) via the Function+Reset button, control via serial debug console. I then wget the image from my local server and dd out to /dev/mmcblock0. Subsequent boot was indeed successful.

The three holes could be access to a serial console if necessary. Ground Transmit Receive. If you want to try this, baudrate is most likely 115200 like all Allwinner SoCs.

I think the easiest would be to get/build an image with mesa-vpu extension enabled. Unfortunately there is no automated way to do the stuff this extension does while building, in a live system. In general there are two ways to get hw acceleration: panthor or proprietary mali blobs. Former is from my feels better for general desktop usage and latter for hw encoding/decoding. Both cannot co-exist, no idea why. Latter needs vendor kernel branch. This would give you a Noble Gnome desktop image with Panthor driver enabled: ./compile.sh BOARD=youyeetoo-r1-v3 BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers desktop_tools internet multimedia' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base ENABLE_EXTENSIONS=mesa-vpu KERNEL_CONFIGURE=no RELEASE=noble Feel free to test: https://testing.armbian.de/Armbian-unofficial_25.11.0-trunk_Youyeetoo-r1-v3_noble_vendor_6.1.115_gnome_desktop.img.xz

the current filogic kernel has no info [in github] for where it was forked from, and trying to apply incremental patches from kernel.org I found it contains pieces of 6.14 in an ostensibly 6.12 branch. @chainsx might you be able to divulge where you forked it from?

PR Has been merged. I rebuilt on commit 1cf20837d27a3c09d93395f075cc305c81b4663f and things look good. Build instructions remain the same as my last post on this /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v25.11 rolling for Odroid C1 running Armbian Linux 6.12.49-current-meson Packages: Debian stable (trixie) Support: DIY (custom image) IPv4: (LAN) 192.168.1.95, 10.8.0.1, 10.10.0.1 (WAN) ww.xx.yy.zz IPv6: 0000:1111:2222:3333:444:555:6666:7777 Performance: Load: 2% Uptime: 23:36 Memory usage: 8% of 986M CPU temp: 49°C Usage of /: 15% of 6.9G

Has anyone here configured armbian with a Wayland desktop, and completely free of X11? How did you do it? I have compiled labwc and it works great with my orange pi zero 3, with bookworm or trixie... but I can't figure out how to configure a wayland greeter. I need to do this because my LCD driver can't work with X11 (panel-mipi-dbi-spi).

@ebin-dev could you perhaps update your post 1 and post your latest instructions and upload the files there? That would make it much easier to find the stable files.

@pochopsp - you can buy two tv-boxes of the same type at once from the same seller and they might have different hardware internally still - that is the reason why it is not prossible to provide really good images for tv boxes: the hardware is simply too random and often also low quality

@Luckyisnotcoolest try the x96q images here. https://github.com/NickAlilovic/build/releases/tag/20250306

@emor acid could be your gpio settings for mmc0. Try the x98h image. If that doesn’t work you need to extract your android dts or use the one from the working Ubuntu.

The kernel 6.17 release benefits from improvements in the graphics subsystem, hardware enablement, and more! See where Collabora's kernel team contributed to this release. View the full article

leave a link for other users like @John Taylor to continue your work, also @fedes_gl could give a hand