belegdol

There could be a variable to define, but you can just remove the patches from the respective patch/kernel subfolder. Once you want them back, do git restore.

I just tried running fstrim on my HC1 which has a Samsung 860 EVO in it and got no errors. I was not aware that fstrim support is device-specific. As mentioned by @Igor, try the official ubuntu image and report the issue to https://forum.odroid.com/viewforum.php?f=225 if you can reproduce it. Other than that, do you mind sharing a link to the bug you posted? Are there any specific errors you are seeing?

Thanks, it worked.

Hello, for quite some time I have noticed that it seems impossible to build just the kernel, an image is built every time. I am using the following command: ./compile.sh BOARD=odroidxu4 BRANCH=current RELEASE=bullseye BUILD_MINIMAL=yes BUILD_DESKTOP=no BUILD_ONLY="kernel" KERNEL_CONFIGURE=no USE_CCACHE=no KEEP_KERNEL_CONFIG=no DEB_COMPRESS=xz Additionally, output/debs seems not to be cleaned, despite documentation indicating this should happen with default CLEAN_LEVEL. Am I doing something wrong? Or does documentation need updating? Thanks!

As I mentioned above, it is really a lot of work: I neither have the time nor the skill to do this unfortunately.

I have now checked the rebase path and there are over 14k commits to go through. At 142nd commit I have arrived at 4th merge conflict. At this rate there are going to be 400 merge conflicts to go through. Given that my knowledge of C is non-existent, I think we might need a new plan.

@rpardini, thank you for the detailed explanation and for clarifying where 5.4.228 is coming from. I incorrectly assumed it comes from the git tag. As far as odroidxu4 is concerned, your description of the current update process is correct. I was not aware it is an exception in terms of how this kernel is kept up-to-date. Knowing this, I think my preference would be to invert the patching order as well. Please note that I have not tried it yet. Having said that, almost all of the point release updates did not require manual fixing, which gives hope that rebasing could potentially work once initially set up. The solution with the variable would only realistically fly if we can generate the said variable automatically. Otherwise, someone is bound to forget to update both at some point leading to misleading version numbers.

$ dpkg --info output/debs/linux-image-*.deb neues Debian-Paket, Version 2.0. Größe 28852376 Byte: control-Archiv= 1284 Byte. 710 Byte, 10 Zeilen control 807 Byte, 16 Zeilen * postinst #!/bin/bash 612 Byte, 13 Zeilen * postrm #!/bin/bash 891 Byte, 21 Zeilen * preinst #!/bin/bash 608 Byte, 13 Zeilen * prerm #!/bin/bash Package: linux-image-current-odroidxu4 Version: 5.4.228-S3043-De511-P2c81-C951fH6842-Bb436 Source: linux-5.4.234 Architecture: armhf Maintainer: Igor Pecovnik <igor.pecovnik@****l.com> Section: kernel Provides: linux-image, linux-image-armbian, armbian-current Description: Armbian Linux current kernel image version "5.4.228" git revision "3043e57d9fe81d5031c98da852e84e7956b4a953" codename "Kleptomaniac Octopus" drivers hash "e511b9159daace9f" patches hash "2c81c7c1a0a42d1f" .config hash "951f7fdd7fb40928" .config hook hash "68429bb5c7c735ac" framework bash hash "b436f1853a32cf25" This package contains the Linux kernel, modules and corresponding other files, kernel_version_family: 5.4.234-odroidxu4. With the new scheme the package version appears to come from the git tag, not from the makefile. I am applying a lot of patches to change the kernel version because hardkernel only update their tree irregularly. If you check the git history of the patches folder, this is what the other maintainers have been doing before as well: https://github.com/armbian/build/commits/main/patch/kernel/archive/odroidxu4-5.4

Yes: https://github.com/armbian/build/pulls?q=is%3Apr+author%3Abelegdol+is%3Aclosed The issue of versions not going up consistently is bound to affect official packages as well. Until hardkernel tag a new release, the kernel version is not going to change. Patches hash (Pxxxx) will change, but hashes cannot be guaranteed to go up. Until now I was adding another element to the VERSION file (23.02.2.1, 23.02.2.2, etc.). This way my local builds will not get updated by the system 23.02.2 unless armbian shipped a larger update.

@going it is predominantly about local assemblies. I often update kernels to a new point release and knowing which package is the newest one helps a lot. Not having local update overwritten by the distributed one is a welcome bonus but i understand that there is going to be some churn when switching from one scheme to another.

I agree regarding the one-time change. I also agree that the old scheme was not ideal either. Having said that , with the old version I could either edit the VERSION file or use a variable (was it sublevel?) To get the versions to go up consistently. With the new versioning scheme this does not seem to be possible, saving for forking the hardkernel repo, tagging kernel versions myself and telling the compile script to use that instead.

Would I get the old version scheme if I checkout v23.02 branch? I tried building with LIB_TAG=v23.02 but it still got me the new scheme: ./compile.sh BOARD=odroidxu4 BRANCH=current LIB_TAG=v23.02 BUILD_ONLY=kernel KERNEL_CONFIGURE=no USE_CCACHE=no KEEP_KERNEL_CONFIG=no DEB_COMPRESS=xz

I understand what is happening, the comment explains it well. I am merely asking if what is happening can be overridden.

Hello, the new kernel versioning scheme consists of the latest git tag and several hashes: https://github.com/armbian/build/blob/main/lib/functions/artifacts/artifact-kernel.sh With boards like odroid-xu4 for which the upstream git is only updated occasionally, this leads to two problems: 1. the generated version is lower than what is currenty getting shipped: `5.4.228-S3043-De511-P0a53-C0750H6842-Bb436` vs `23.02.2` 2. it cannot be guaranteed that the versions go up reliably: 5.4.232 is `5.4.228-S3043-De511-Pc02c-C0750H6842-Bec1c` and 5.4.233 is `5.4.228-S3043-De511-P0a53-C0750H6842-Bb436` While I can understand using the kernel version than armbian version is better, this currently only works if every version is tagged. Is there a variable which I could use to get the old behaviour back? Thanks.

I hit another problem today. I tried updating to my local 5.4.199 build, but the free space ran out during the uInitrd conversion. I was able to rescue the system by putting the SD card in my Fedora machine and doing the conversion there, but the 58 MB boot is slowly becoming an issue. Is this still the default? If not, what is the current default? Can I just increase the partition size with gparted and be done with it?

OK, with update from 5.4.184 to 5.4.185 the hooks finally worked:

After the reboot it is still the same. I have tested the logic comparing the contents of /lib/modules to /boot and it seems to work. Can the issue be that I am installing the packages with apt install? Is there another way?

This still seems not to be working as intended with the versions from git:

I did as you suggested, but after doing the changes and installing 21.08.8.3 aka 5.4.181 kernel I have 5.4.177 leftovers in /boot: Should I have rebooted before installing the new kernel? I can give it a try once 5.4.182 is available.

Thanks, I will give it a shot tomorrow.

Sure, please go ahead. Having to delete the old kernel leftovers after every update is somewhat annoying. Having said that, it is interesting that the last change is from 2017 but the issue only appeared now.

I think I am slowly starting to understand where these issues are coming from. I cleaned up /var/log.hdd/journal by running $ sudo journalctl --dir=/var/log.hdd/journal/1ded17e370994bc2bfab08257042ce4c/ --vacuum-time 1w as long as there was only around 40 mb or so of logs in the stored journal, all was fine. Tonight the space on /var/log ran out again: I checked, and the stored journal is 49 MB: $ sudo du -h /var/log.hdd --max-depth=1 24K /var/log.hdd/unattended-upgrades 164K /var/log.hdd/apt 20K /var/log.hdd/cron-apt 200K /var/log.hdd/nginx 0 /var/log.hdd/proftpd 100K /var/log.hdd/samba 0 /var/log.hdd/private 0 /var/log.hdd/sysstat 0 /var/log.hdd/chrony 0 /var/log.hdd/openmediavault 28K /var/log.hdd/salt 0 /var/log.hdd/watchdog 49M /var/log.hdd/journal 0 /var/log.hdd/runit 55M /var/log.hdd Does armbian-ramlog and/or armbian-truncate-logs need to put the systemd logs from /var/log.hdd to /var/log in order to do its job? Right now the log in /var/log is only 6.3 MB so I find it unlikely to grow to over 50 MB in 5 hours: $ sudo du -h /var/log --max-depth=1 0 /var/log/watchdog 0 /var/log/unattended-upgrades 0 /var/log/sysstat 52K /var/log/samba 0 /var/log/salt 0 /var/log/runit 0 /var/log/proftpd 0 /var/log/private 0 /var/log/openmediavault 192K /var/log/nginx 6.3M /var/log/journal 8.0K /var/log/cron-apt 0 /var/log/chrony 0 /var/log/apt 7.0M /var/log

/dev/mmcblk0p1 is ext4, /dev/mmcblk0p2 is btrfs and /dev/sda1 ext4.

$ sudo cat /etc/kernel/preinst.d/initramfs-cleanup #!/bin/sh version="$1" [ -x /usr/sbin/update-initramfs ] || exit 0 # passing the kernel version is required if [ -z "$version" ]; then echo >&2 "W: initramfs-tools: ${DPKG_MAINTSCRIPT_PACKAGE:-kernel package} did not pass a version number" exit 0 fi # avoid running multiple times if [ -n "$DEB_MAINT_PARAMS" ]; then eval set -- "$DEB_MAINT_PARAMS" if [ -z "$1" ] || [ "$1" != "upgrade" ]; then exit 0 fi fi STATEDIR=/var/lib/initramfs-tools version_list="$(ls -1 "$STATEDIR" | linux-version sort --reverse)" for v in $version_list; do if ! linux-version compare $v eq $version; then # try to delete delete old initrd images via update-initramfs INITRAMFS_TOOLS_KERNEL_HOOK=y update-initramfs -d -k $v 2>/dev/null # delete unused state files find $STATEDIR -type f ! -name "$version" -printf "Removing obsolete file %f\n" -delete # delete unused initrd images find /boot -name "initrd.img*" -o -name "uInitrd-*" ! -name "*$version" -printf "Removing obsolete file %f\n" -delete fi done exit 0

I went through the files and all of them are identical to the ones in my install.