belegdol

I do not have either of the lines in my boot.ini: ODROIDXU-UBOOT-CONFIG # DO NOT EDIT THIS FILE # # Please edit /boot/armbianEnv.txt to set supported parameters # # U-Boot defaults setenv initrd_high "0xffffffff" setenv fdt_high "0xffffffff" # default settings, will be overwritten from armbianEnv.txt setenv macaddr "00:1e:06:61:7a:55" setenv rootdev "UUID=d0da7bbe-e3af-4588-8715-aa5c4478eb88" setenv rootfstype "btrfs" setenv console "both" setenv verbosity "1" # To update boot loader on your eMMC use the nand-sata-install tool # run copy_uboot_sd2emmc if ext4load mmc 0:1 0x44000000 /boot/armbianEnv.txt || fatload mmc 0:1 0x44000000 armbianEnv.txt || ext4load mmc 0:1 0x44000000 armbianEnv.txt; then env import -t 0x44000000 ${filesize}; fi if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=tty1"; fi if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "${consoleargs} console=ttySAC2,115200n8"; fi setenv bootrootfs "${consoleargs} consoleblank=0 loglevel=${verbosity} panic=10 root=${rootdev} rootfstype=${rootfstype} rootwait rw" # --- Screen Configuration for HDMI --- # # --------------------------------------- # Uncomment only ONE line! Leave all commented for automatic selection. # Uncomment only the setenv line! # --------------------------------------- # ODROID-VU forced resolution # setenv videoconfig "video=HDMI-A-1:1280x800@60" # ----------------------------------------------- # ODROID-VU forced EDID # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x800.bin" # ----------------------------------------------- # 1920x1200 60hz without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1200_60hz.bin" # ----------------------------------------------- # 1920x1200 30hz without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1200_30hz.bin" # ----------------------------------------------- # 1920x1080 (1080P) with monitor provided EDID information. (1080p-edid) # setenv videoconfig "video=HDMI-A-1:1920x1080@60" # ----------------------------------------------- # 1920x1080 (1080P) without monitor data using generic information (1080p-noedid) # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1080.bin" # ----------------------------------------------- # 1920x1080 50hz (1080P) with monitor provided EDID information. (1080p 50hz-edid) # setenv videoconfig "video=HDMI-A-1:1920x1080@50" # ----------------------------------------------- # 1920x1080 50hz (1080P) without monitor data using generic information (1080p 50hz-noedid) # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x1080_50hz.bin" # ----------------------------------------------- # 1920x800 60hz without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1920x800.bin" # ----------------------------------------------- # 1792x1344 60hz without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1792x1344.bin" # ----------------------------------------------- # 1680x1050 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1680x1050.bin" # ----------------------------------------------- # 1600x1200 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1600x1200.bin" # ----------------------------------------------- # 1600x900 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1600x900.bin" # ----------------------------------------------- # 1400x1050 60hz without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1400x1050.bin" # ----------------------------------------------- # 1440x900 with monitor provided EDID information. # setenv videoconfig "video=HDMI-A-1:1440x900@60" # ----------------------------------------------- # 1440x900 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1440x900.bin" # ----------------------------------------------- # 1366x768 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1366x768.bin" # ----------------------------------------------- # 1360x768 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1360x768.bin" # ----------------------------------------------- # 1280x1024 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x1024.bin" # ----------------------------------------------- # 1280x768 60hz without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x768.bin" # ----------------------------------------------- # 1280x720 (720P) with monitor provided EDID information. (720p-edid) # setenv videoconfig "video=HDMI-A-1:1280x720@60" # ----------------------------------------------- # 1280x720 (720P) without monitor data using generic information (720p-noedid) # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1280x720.bin" # ----------------------------------------------- # 1152x864 75hz without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1152x864_75hz.bin" # ----------------------------------------------- # 1024x768 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1024x768.bin" # ----------------------------------------------- # 1024x600 without monitor data using generic information (ODROID VU7+) # setenv videoconfig "drm_kms_helper.edid_firmware=edid/1024x600.bin" # ----------------------------------------------- # 800x600 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/800x600.bin" # ----------------------------------------------- # 848x480 60hz without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/848x480.bin" # ----------------------------------------------- # 800x480 without monitor data using generic information (ODROID 7") # setenv videoconfig "drm_kms_helper.edid_firmware=edid/800x480.bin" # ----------------------------------------------- # 720x576 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/720x576.bin" # ----------------------------------------------- # 720x480 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/720x480.bin" # ----------------------------------------------- # 640x480 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/640x480.bin" # ----------------------------------------------- # 480x800 without monitor data using generic information # setenv videoconfig "drm_kms_helper.edid_firmware=edid/480x800.bin" # --- HDMI / DVI Mode Selection --- # ------------------------------------------ # - HDMI Mode setenv vout "hdmi" # - DVI Mode (disables sound over HDMI as per DVI compat) # setenv vout "dvi" # --- HDMI CEC Configuration --- # ------------------------------------------ setenv cecenable "false" # false or true # set to true to enable HDMI CEC # CPU Governor Selection # Available governos: conservative, userspace, powersave, ondemand, performance, schedutil setenv governor "performance" # DRAM Frequency # Sets the LPDDR3 memory frequency # Supported values: 933 825 728 633 (MHZ) setenv ddr_freq 825 #------------------------------------------------------------------------------ # # HDMI Hot Plug detection # #------------------------------------------------------------------------------ # # Forces the HDMI subsystem to ignore the check if the cable is connected or # not. # false : disable the detection and force it as connected. # true : let cable, board and monitor decide the connection status. # # default: true # #------------------------------------------------------------------------------ setenv HPD "true" #------------------------------------------------------------------------------ # # TMDS data amplitude control. # #------------------------------------------------------------------------------ # # 1LSB corresponds to 20 mVdiff amplitude level. # tx_amp_lvl : 0 = 760 mVdiff(Min), 31 = 1380 mVdiff(Max) # # Hardkernel default hdmi_tx_amp_lvl = 31(1380 mVdiff); #------------------------------------------------------------------------------ setenv hdmi_tx_amp_lvl "31" #------------------------------------------------------------------------------ # # TMDS data amplitude fine control for each channel. # #------------------------------------------------------------------------------ # # 1LSB corresponds to 20 mVdiff amplitude level. # tx_lvl : 0 = 0 mVdiff(Min), 3 = 60 mVdiff(Max) # # Hardkernel default # hdmi_tx_lvl_ch0 = 3, hdmi_tx_lvl_ch1 = 3, hdmi_tx_lvl_ch2 = 3, #------------------------------------------------------------------------------ setenv hdmi_tx_lvl_ch0 "3" setenv hdmi_tx_lvl_ch1 "3" setenv hdmi_tx_lvl_ch2 "3" #------------------------------------------------------------------------------ # # TMDS data pre-emphasis level control. # #------------------------------------------------------------------------------ # # 1LSB corresponds to -0.45dB emphasis level except for 1 # tx_emp_lvl : 0 = 0 db(Min), 1 = -0.25 db, 2 = 0.7 db, 15 = -7.45 db(Max) # # Hardkernel default hdmi_tx_emp_lvl = 6 (-2.50 db); #------------------------------------------------------------------------------ setenv hdmi_tx_emp_lvl "6" #------------------------------------------------------------------------------ # # TMDS clock amplitude control. # #------------------------------------------------------------------------------ # # 1LSB corresponds to 20 mVdiff amplitude level. # clk_amp_lvl : 0 = 790 mVdiff(Min), 31 = 1410 mVdiff(Max) # # Hardkernel default hdmi_clk_amp_lvl = 31 (1410 mVdiff) #------------------------------------------------------------------------------ setenv hdmi_clk_amp_lvl "31" #------------------------------------------------------------------------------ # # TMDS data source termination resistor control. # #------------------------------------------------------------------------------ # # tx_res : # 0 = Source Termination OFF(Min), 1 = 200 ohm, 2 = 300 ohm, 3 = 120 ohm(Max) # # Hardkernrel default hdmi_tx_res = 0 (Source Termination OFF) #------------------------------------------------------------------------------ setenv hdmi_tx_res "0" #------------------------------------------------------------------------------ setenv hdmi_phy_control "hdmi_tx_amp_lvl=${hdmi_tx_amp_lvl} hdmi_tx_lvl_ch0=${hdmi_tx_lvl_ch0} hdmi_tx_lvl_ch1=${hdmi_tx_lvl_ch1} hdmi_tx_lvl_ch2=${hdmi_tx_lvl_ch2} hdmi_tx_emp_lvl=${hdmi_tx_emp_lvl} hdmi_clk_amp_lvl=${hdmi_clk_amp_lvl} hdmi_tx_res=${hdmi_tx_res} HPD=${HPD} vout=${vout}" # Load kernel, initrd and dtb in that sequence ext4load mmc 0:1 0x40008000 /boot/zImage || fatload mmc 0:1 0x40008000 zImage || ext4load mmc 0:1 0x40008000 zImage ext4load mmc 0:1 0x42000000 /boot/uInitrd || fatload mmc 0:1 0x42000000 uInitrd || ext4load mmc 0:1 0x42000000 uInitrd # this is for mainline only if test "${board_name}" = "xu4"; then setenv fdtfile "exynos5422-odroidxu4.dtb"; fi if test "${board_name}" = "xu3"; then setenv fdtfile "exynos5422-odroidxu3.dtb"; fi if test "${board_name}" = "xu3l"; then setenv fdtfile "exynos5422-odroidxu3-lite.dtb"; fi if test "${board_name}" = "hc1"; then setenv fdtfile "exynos5422-odroidhc1.dtb"; fi # legacy shares a single DT for all boards if ext4load mmc 0:1 0x00000000 "/boot/.next" || fatload mmc 0:1 0x00000000 ".next" || ext4load mmc 0:1 0x00000000 ".next"; then echo "Found mainline kernel configuration"; else setenv fdtfile "exynos5422-odroidxu3.dtb"; fi ext4load mmc 0:1 0x44000000 /boot/dtb/${fdtfile} || fatload mmc 0:1 0x44000000 dtb/${fdtfile} || ext4load mmc 0:1 0x44000000 dtb/${fdtfile} # set FDT address fdt addr 0x44000000 if test "${cecenable}" = "false"; then fdt rm /cec@101B0000; fi # final boot args setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr} governor=${governor} ${hdmi_phy_control} usb-storage.quirks=${usbstoragequirks} ${extraargs}" # set DDR frequency dmc ${ddr_freq} bootz 0x40008000 0x42000000 0x44000000

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.