rvalle

thanks! that explains everything.

Yes, managed to build OdroidXU4 on the main tag but not on v23.11.2, I need to investigate why is this. I even deleted the local armbian build docker container, just in case.

@Igor it is a bit confusing. OdroidXU4 is now building on main. I guess a fix was posted. However, I am not sure if it is building on v23.11. Should a kernel update break the v23.11 tag? Perhaps it is an issue at my environment.

is there anyway to point the checkout to a particular revision?

I can see the checkout is here: ``` [🐳|🌱] git: Fetch from remote completed, rev-parsing... [ 'kernel:6.1' 'odroidxu4-6.1.y' 'FETCH_HEAD' ] [🐳|🌿] Using Kernel git revision [ 5737e0cc255c905e3c35a0186ee528ba7f056ae8 at 'Mon Jan 29 21:34:07 UTC 2024' ] ``` I can see there was an update yesterday at hardkernel repo, that is used here. I guess something broke.

Hi, I have been recently working on a couple of extensions: lvm and cloud-init I forked off "v23.11.2" tag when creating my branches, since they are extensions, and wont alter the framework much. Today I noticed that OdroidUX4 is not building, but it was building last week. A patch seems to be failing. I guess it is a kernel/driver patch. Then my question is: is it possible that, on the same tag (v23.11.2), builds break? I am starting to think that the tag is only for the build process/patch set, but excludes, for example a reference to kernel code. I suppose then the situation is that a kernel update has "broken" a patch, would that be the case? If so, is it possible to also checkout a particular working kernel for the sake of a stable dev environment? How do you normally do? R.

Traditionally I use LVM in our Storage in our servers, and we started doing it on the ARM64 servers too. I am using this with Raspberry PIs and now with Armbian too. I also use cloud-init for server customization, just like ubuntu does with the RPI image now. This is very good, as you can create users, add keys, install packages, set networking... extend partitions, all in an standard way. So, the requirements for my Armbian image are, an extra vfat partition for cloud-init metadata, and the ROOT to be created with LVM instead of just ext4. I managed to implement most with user extensions, except the Dockerfile that required extra packages and configurations, and also I had to patch the partitioning part of the script, in a similar way the CRYPT extension does, as the root filesystem will come from mapper and not from the root device, this is not possible to do from an extension. I have it working for the HC4 in the master branch. I want to port it to the M1 and possibly XU4.

ok... looks like does not like the docker container from other branch.... I think. will investigate.

@rpardini any idea why I get this from docker-shell when switching to the armbian_next branch? fatal: not a git repository: /root/armbian/../.git/modules/build

Ohh, thanks for this, I did not notice. I just want to build the image with a patch of mine too. See if we are lucky and get it to work. Are you using Tobetter code from Hardkernel? We have a discussion over there because most modules are disabled in the kernel even if they have nothing to do with the actual silicon. He is looking into it, be aware.

@rpardini maybe I can test. I don't need or want HDMI.... I am trying to make sense of your code. The code is in your rpardini/extensions branch, but was it from armbian-build/master? You seem to be working from another branch with scripts split in a tree, right?

Well, armbian has a lot of code for server initialization, and cloud-init is designed specifically for this. It is becoming a de-facto standard, and it fits nicely with armbian in general. OK! I had not noticed that file. Thanks! So far I am trying to remove files from the system via customize_image.sh , but I don't think this may be the best way to disable this functionality.

Hi! I am creating an Image that uses Cloud Init for customization. It involves creating an extra vfat partition for the CloudInit meta data. This is becoming an industry standard way to initialize virtual machines and now physical too. MAAS and Ubuntu on RPI also use it. What is the cleanest way to remove or disable equivalent scripts in Armbian ? In particular firstlogin and firstboot ?

OK, It worked after using armbian-config to flash bootloader to SPI. (also did to mmc card, but did not make any difference)

Hi! Just testing the HC4. I have disabled petit boot as explained in the documentation. Boot, works, except with a "reboot" command, the board enters in a boot loop. Any idea why?

Thanks Werner, and is it possible to partition in a custom way? I can only find a variable for selecting a partition fixed size...

Hi! I have been using Armbian for long, but I am new to the Development/build system. I have however set the environment and I can build images. Now, I want to create a custom Armbian image with the following customization: - Separate ext2 partition for boot - second partition for LVM - Root Filesystem in Logical Volume and fixed size. - Cloud Init, with an extra partition for NoCloud Datasource. I see in the documentation how to install new packages, but not how to partition the SD card. How can I change the partitioning? On the other hand. Can I just build an image without compiling the Kernel? I have no interest in kernel customization in this case, I would rather install the distribution's default without compiling. Is it possible?

Has anybody successfully used the USB type-c displayport of the nanopc-t4? How do you configure it? It works on the images provided by friendlyelec, so, I guess it is just a config/install issue ?