manjaro-arm-tools issueshttps://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools/-/issues2021-06-16T18:55:53Zhttps://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools/-/issues/10Add logging2021-06-16T18:55:53ZGhost UserAdd loggingWould be nice to have logs of what the tools have done somewhere.
And maybe even copy out the build logs from the rootfs.Would be nice to have logs of what the tools have done somewhere.
And maybe even copy out the build logs from the rootfs.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools/-/issues/32Add support for FDE2021-05-04T19:31:06ZOz N TiramAdd support for FDEPlease accept my apologies if this is the wrong place.
I think it is possible to add support for Full Disk encryption based on the work done here:
https://github.com/dreemurrs-embedded/archarm-mobile-fde-installer/blob/002d54086a4e9cc6...Please accept my apologies if this is the wrong place.
I think it is possible to add support for Full Disk encryption based on the work done here:
https://github.com/dreemurrs-embedded/archarm-mobile-fde-installer/blob/002d54086a4e9cc69f1c2f828102c1445963a572/installer.sh#L156
This depends also on adding the [OSK package](https://github.com/dreemurrs-embedded/Pine64-Arch/tree/master/PKGBUILDS/danctnix/osk-sdl) and calling mkinitcpio similar to what is already done for btrfs:
```shell
sed -i '/^MODULES/{s/)/ btrfs)/}' $ROOTFS_IMG/rootfs_$ARCH/etc/mkinitcpio.conf
$NSPAWN $ROOTFS_IMG/rootfs_$ARCH mkinitcpio -P 1> /dev/null 2>&1
```
I would be happy to collaborate on this.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools/-/issues/37Implement EFI/multikernel setups2022-10-04T12:46:26ZGhost UserImplement EFI/multikernel setupsThis is an issue to track what is needed to implement EFI/multikernel setups, instead of device specific bootscripts.
We assume we will go with either Grub or SystemD-Boot, depending on what easiest for us to use.
This here is a list o...This is an issue to track what is needed to implement EFI/multikernel setups, instead of device specific bootscripts.
We assume we will go with either Grub or SystemD-Boot, depending on what easiest for us to use.
This here is a list of Tasks and Problems that needs to be solved for this to be implemented correctly:
- [ ] Find out which of our currently supported devices support EFI.
- [ ] Create new kernel packages with correct naming.
- [x] Make the new kernel packages provide a "skeleton" loader entry conf, with kernel name and version.
- [ ] Create scripts in uboot packages, to get correct "options" lines into all the loader entry conf files for all devices.
- [ ] If amlogic uboots can not be updated, find a way to also update the initramfs filename to .uimg in the loader entry conf files only for amlogic devices that need it.
- [x] Update the tools with new partition layout setup and bootloader installation commands.
- [X] Update the tools to enable EFI partition depending on DEVICE selected.
- [ ] Find a way to make sure existing installs is not broken, either by keeping the current stuff or create automatic migration. This includes reformatting the boot partition with $esp flag if it's needed on existing installs.
- [ ] How do we load the correct DTB when multiple kernels are installed, as they would have to be placed at different location to not conflict?
More tasks will be added as I think of them.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools/-/issues/57[generic-efi] Images using btrfs does not boot2022-10-06T19:19:03ZGhost User[generic-efi] Images using btrfs does not bootA couple of small changes is needed to the default grub.cfg to be able to boot from btrfs, but even with `rootflags=subvol=@` and `rootfstype=btrfs` added, when we boot we still get:
```
error: sparse not found
error: extent not found
e...A couple of small changes is needed to the default grub.cfg to be able to boot from btrfs, but even with `rootflags=subvol=@` and `rootfstype=btrfs` added, when we boot we still get:
```
error: sparse not found
error: extent not found
error: kernel image needs to be loaded first
```
As far as I can tell, the extent error point to errors on the btrfs filesystem it self, but it does not happen with other profiles. Only the EFI/GRUB based one.