Had a user contact me regarding an issue with LWM_LUKS while using installer. To be perfectly honest I have never had or needed to encrypt a device or even tested the function within installer. After many, many years never been asked or told of an issue with it. Right excuses over what about the actual problem.
Last few days I have been digging into code and started to quickly notice that it is not the partition function that is the issue but mkinitcpio and bootloader.
To reduce my own stress I have removed Syslinux from bootloader options, it is fine for use on iso images but not really up to the job for modern systems.
After making quite a few changes I have managed to get LVM+LUKS working, tested under Grub2 and all seems ok. Code is there for Systemd-boot but I feel that it too will be need to go as it would greatly reduce complexity of installer and reduce options to just Grub. Grub2 can of course handle both bios and UEFI without any problems.
Some users will notice changes in the order of things during install. Mkinitcpio has moved to after transfer of files to target device and I may move other things to get more of a flow.
For now updated installer is shipped with SwayBANG, do not want to break GreenBANG at this point.
Will say that for the most part arch installers suck! in as much as they funnel a user into a given path that is already predefined. Still say that provided you have a working network connection which is essential for Archlinux. You can do a full custom install just with arch-install-scripts.
Archlinux AI Agent anyone?
Will get something uploaded over weekend!
Stay safe 😉