All Activity

Some modules are not included in the kernel package by default. In my case I had to install zfs-dkms built upon Dynamic Kernel Module Support(DKMS). The module gets rebuilt whenever I upgrade the kernel—I'm not sure exactly which package I have to upgrade first though, header? dtb? Somehow the zfs module was not successfully built after I upgraded the kernel, its header files, and the device tree blobs.

I think it's easier than that. I looked into the postinst file for kernel headers on my Ubuntu machine, and I found this: #!/bin/sh set -e version=6.17.0-7-generic if [ "$1" != configure ]; then exit 0 fi if [ -d /etc/kernel/header_postinst.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error --arg=$version \ /etc/kernel/header_postinst.d fi exit 0 The postinst script for the headers package doesn't have anything similar, so we should add it this part related to execute the scripts under `/etc/kernel/header_postinst.d`. Can you do that or should we add someone else to the discussion? EDIT: Debian does something similar. Same goal, just a different code: #!/bin/sh -e version=6.12.48+deb13-amd64 linux-run-hooks headers postinst $version -- "$@" exit 0

Perhaps package dependencies need to be adjusted so the installation order matches the requirements? Cannot help there though, I have very little insight.

Yes That's on us

@Jeeva Kandasamy it’s on this page https://github.com/NickAlilovic/build/tree/v20250306

Hi @Werner It seems the problem is in another place. The unattended upgrade updates the kernel, but the dkms hooks are not installed. I just got a couple kernel updates, and neither of them ran the DKMS, and since I'm using ZFS, it causes serious problems since the ZFS module wouldn't be build, so after a reboot wouldn't load and I couldn't access the data in my disks. I don't think adding the command to `armbian-upgrade` would solve since `apt upgrade` would still have the problem, and also the unattended upgrades, like mentioned before. Any ideas? EDIT: I found the problem, but couldn't find a solution. What is happening, is the kernel package is updated first, so actually it calls the dkms hook, but the headers wouldn't be installed, at least the latest version, yet, so the dkms can't run. The problem is how to install the headers before the kernel, or call the dkms hook from the headers package, so even if the kernel calls dkms but can't run because of the lack of updated headers, the headers will do that and succeed.

Thanks for the details @Nick A I tried with fedora/docker Can you please share the OS details, originally build OS and "./compile" options for https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-ddr3-v5-1_bookworm_edge_6.12.11_server.img.xz

Latest compile for odroid xu4 does have a desktop. Any reason why?

Okay, thanks for the explanation! So, I got Armbian compiled and running by just adding the .dts file and the .csc file. The .csc file is a copy of the ODROID M1 .config file, but with some modifications: I threw out the SPI-related stuff, because the M1S does not have a SPI flash to boot from and it gave me arrors during compilation. I tested basic functionality with a Ubuntu Noble Cinnamon desktop image as well as a headless server image. Is this enough to create a pull request? How is the Download page created? Is that made by the Armbian team or do I need to add it there as well (how?) ? Greetings

Same answer and further reasoning as here:

better in which way? performance? driver support? size? from our pov the better the support conditions, the more likely to recommend. https://www.armbian.com/download/?device_support=Standard support Is one platinum? Go for it? If not, check standard support. If one is in this category, go for it. If not, check further down for community support.

Yes. In the past everything was added as patch. The problem was (and still is for other reasons) that some patches modifying a dt build on top of each other or stuff breaks. Now the dt can be edited directly and using git blame it is documented who edited what for whatever reason. Of course sometimes there is an almost perfect dt upstream that needs minor adjustments. Those can be perfectly fine done with a patch. Also both patches and our dt files only stay for as long as there is no proper equivalent upstream. Once everything is in mainline they are no longer needed.

I think the upstream kernel has fixed it recently. Could your try the patch? https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a28352cf2d2f8380e7aca8cb61682396dca7a991

Thank you for the answer. @Nick A

orange pi 5, orange pi 5 pro, orange pi 5 ultra or orange pi 5 max?

I'm currently in the process of deciding between the Orange Pi 3B and the Raspberry Pi 4, and i'd love to hear your thoughts. I know that Raspberry Pi has a huge community and a ton of resources, which is super appealing for someone like me who's looking to learn and tinker. The support from the community is definitely a big selling point, especially since I'm just starting out. That said, l'm also considering the Orange Pi because it's much more affordable. The price difference is hard to ignore and l have heard it's a pretty solid option for DlY projects and development. Plus, l'm thinking ahead - l might want to stick with Orange Pi for future projects as well, since it seems like a great budget-friendly option for other boards down the road. I'm curious if anyone here has experience with both, and if so, how does Orange Pi compare to Raspberry Pi in terms of performance, compatibility, and overall experience? ls the community support for Orange Pi on the same level, or does it feel a bit lacking? Any advice or personal experiences would be much appreciated! Thanks in advance!

@snow https://linux-sunxi.org/FEL/USBBoot I haven’t tried this before.

WebGL1 and WebGL2 is reported to be working. But the performance is horrible...

Hello everyone, my name is Virgilio. I've been here for 3 days fighting against the RK3229 to install Armbian... My equipment is an RK3229 (R329Q_V3.1). I've already followed as many procedures as possible until I could run the image directly via OTG with RKdevtools, but I can't get anything working. I admit I tried Lakka, PostmarketOS, legacy versions, current versions, everything related to 322x I've tried... but nothing works, I'm almost giving up. adc: wifi sv6051p

uhm, there is misconfiguration in the server actually; I see users.armbian.com is serving the certificate for stpete-mirror.armbian.com, perhaps @Igor can fix the issue

@Nick A Shoot, I don't think it actually has an SD card slot: https://www.aliexpress.com/item/1005006258812291.html I am holding it in my hand now, unless it's somehow obscured or hidden then it looks like there's only a USB-A port and then a USB-C port for input power

Understood, all good. That is a good example for something that is not that clear. I tried to find a ready-to-use dts file for the M1S in the mainline repo, but it is not one single dts file, but a composition of several files where one file refers to the next one and so on (here). I was confused and so I asked ChatGPT how to merge the mainline dts into Armbian. This was how my patches were created. After compilation there was indeed one single all-in-one dts file for my board but not before... EDIT: I just tried another build with just taking the top-level dts file from the mainline repo and placing it in the location you mentioned. Worked like a charm, despite my confusion... 😅 From my point of view it seemed better to have the patches in place to be sure to always pull the most recent DT from the mainline kernel (that of course would require a defined place to put those patches). But what you say sounds as if it would be preferable to have dts files instead of patches. Is that correct and why?

Thanks let me try that

Agreed. A check if the package is installed (and if not install it beforehand) would be sufficient too. PRs to fix this are highly appreciated. https://github.com/armbian/build/blob/main/packages/bsp/common/usr/bin/armbian-install

I suggest to retry later