applications issueshttps://gitlab.manjaro.org/groups/manjaro-arm/applications/-/issues2023-07-14T14:52:13Zhttps://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/52Please pull -- support for passing environment variables and installing from ...2023-07-14T14:52:13ZJérôme CarreteroPlease pull -- support for passing environment variables and installing from other distrosSorry I'm not a Manjaro developer and can't fork the repo here, so I forked at https://gitlab.com/cJ/manjaro-arm-installer
In there, I added support for installing from distros which have configured binfmt_misc differently than Manjaro ...Sorry I'm not a Manjaro developer and can't fork the repo here, so I forked at https://gitlab.com/cJ/manjaro-arm-installer
In there, I added support for installing from distros which have configured binfmt_misc differently than Manjaro does.
Since I was doing some repetitive testing I also added support to bypass the dialog interaction.
Example usage:
```sh
sudo \
MANJARO_ARM_INSTALLER_KEEP_VARIABLES=1 \
DEVICE=pinephone \
EDITION=plasma-mobile \
USER=cj \
FULLNAME=cJ \
PASSWORD=secret CONFIRMPASSWORD=secret \
ROOTPASSWORD=secreter CONFIRMROOTPASSWORD=secreter \
TIMEZONE=America/Montreal \
SDCARD=mmcblk0 \
FSTYPE=f2fs \
LOCALE=C.utf-8 \
CLIKEYMAP=us \
X11KEYMAP=us \
HOSTNAME=pinecone \
./manjaro-arm-installer
```
Thanks,https://gitlab.manjaro.org/manjaro-arm/applications/arm-profiles/-/issues/17[Sway] nerd-fonts-terminus is not found in pacman database2023-05-04T11:48:52ZRan[Sway] nerd-fonts-terminus is not found in pacman databaseI failed sway image build with buildarmimg.
```
==> Installing packages for sway edition on rockpi4b...
:: Synchronizing package databases...
core downloading...
extra downloading...
community downloading...
error: target not found: n...I failed sway image build with buildarmimg.
```
==> Installing packages for sway edition on rockpi4b...
:: Synchronizing package databases...
core downloading...
extra downloading...
community downloading...
error: target not found: nerd-fonts-terminus
==> ERROR: Aborting...
```
Seems nerd-fonts-terminus is now replaced with ttf-terminus-nerd in pacman database.
I think need to replace nerd-fonts-terminus in arm-profiles/editions/sway.
Similar issue were found here: https://forum.manjaro.org/t/pbp-update-issue-nerd-fonts-terminus/139433
This is my very first issue, Sorry if i'm rude.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.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/37Error: /dev/sdb: unrecognised disk label2021-07-29T09:34:05ZFolât PjêrsômêjError: /dev/sdb: unrecognised disk labelAt every install I see something like this:
```
==> Proceeding....
-> Getting package lists ready for rpi4 minimal edition...
==> Getting /dev/sdb ready with btrfs for rpi4...
Error: /dev/sdb: unrecognised disk label
```
[And I don't...At every install I see something like this:
```
==> Proceeding....
-> Getting package lists ready for rpi4 minimal edition...
==> Getting /dev/sdb ready with btrfs for rpi4...
Error: /dev/sdb: unrecognised disk label
```
[And I don't seem to be the only one](https://forum.manjaro.org/t/manjaro-arm-installer-error-dev-mmcblk0-unrecognised-disk-label/63480)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/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/26tools should stop when there is an error2020-08-13T12:12:17ZPhilip Müllertools should stop when there is an errorcurrently the tools solder thru, even if there was an error during build process. As soon as there is something, the tools should stop at that position.currently the tools solder thru, even if there was an error during build process. As soon as there is something, the tools should stop at that position.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/22Allow ROOT_MNJRO to reside on different device2021-08-02T10:31:37ZYaheAllow ROOT_MNJRO to reside on different deviceCurrently, the installer seems to be restricted so that BOOT_MNJRO and ROOT_MNJRO reside on the same device. This is unfortunate, as I installed an NVMe M.2 SSD into my PineBook Pro. As it seems, the PBP currently cannot boot from that d...Currently, the installer seems to be restricted so that BOOT_MNJRO and ROOT_MNJRO reside on the same device. This is unfortunate, as I installed an NVMe M.2 SSD into my PineBook Pro. As it seems, the PBP currently cannot boot from that device, but I guess it should be possible to boot from the internal eMMC storage (or MicroSD card) but have the root partition reside on the NVMe SSD. Would it be possible to implement that into the installer and also support LUKS for that separate root partition? I guess there're some people out there who would prefer not to rely on the eMMC for daily use.https://gitlab.manjaro.org/manjaro-arm/applications/arm-profiles/-/issues/3Kernel cleanup2022-12-19T15:09:39ZGhost UserKernel cleanupWe currently have a lot of kernels in our repository and our goal is to have maintain as few as possible, mainly mainline upstream kernels.
So this list is just show what kernels we have, and which are getting used in a profile.
I wil...We currently have a lot of kernels in our repository and our goal is to have maintain as few as possible, mainly mainline upstream kernels.
So this list is just show what kernels we have, and which are getting used in a profile.
I will list the kernels in 3 categories. "Used in profile", "Not used in profile" and "Removed kernels". A check means it's a kernel that needs to be kept and a reason should be appended to the entry.
**Used in profile**
* [X] linux (upstream mainline kernel)
* [X] linux-rpi4 (upstream does not have good enough support yet)
* [X] linux-pinephone (used in PinePhone profile, hopefully mainline support soon)
* [ ] linux-aml (currently used by some odroid and khadas boards, goal is to switch them to `linux`)
* [ ] linux-vim (currently used in oc2 profile, should be shifted to `linux`, when it can boot it again)
* [ ] linux-odroid (currently used by some Odroid boards, goal is to switch them to `linux`)
**Not used in profiles**
* [X] linux-rc (used to test new features in the upcoming release)
* [X] linux-rpi4-mainline (based on stable kernel branch while regular linux-rpi4 is based on LTS)
* [X] linux-rpi4-rc (based on RC branch, for testing)
* [X] linux-rpi4-udl (for @darksky 's satelite stuff, is in community repo)
**Removed kernels**
* linux-pine64
* linux-odroid-n2
* linux-vim3
* linux-next
* linux-aarch64-udl
* linux-rpi4-next
* linux-pinebookpro
* linux-quartz64
* linux-khadashttps://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/6Create a pyqt5/pyqt6 GUI2021-09-12T21:12:32ZGhost UserCreate a pyqt5/pyqt6 GUIIt's been a wish of mine for a while now to have a GUI for the Manjaro ARM Installer and Tools in general.
Right now, it's all written in bash.
I would love a version written in either PyQt5 or PyQt6, whatever is easier to maintain wh...It's been a wish of mine for a while now to have a GUI for the Manjaro ARM Installer and Tools in general.
Right now, it's all written in bash.
I would love a version written in either PyQt5 or PyQt6, whatever is easier to maintain when adding new features.
Problem is, I can't code for sh**. So if someone could create a GUI that does what the Installer does and be willing to maintain it, it would be really awesome.
So I am putting this on my "wishlist"!https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools/-/issues/14Failed to open file "/sys/devices/system/cpu/microcode/reload": Read-only fil...2019-01-20T11:20:16ZBernhard LandauerFailed to open file "/sys/devices/system/cpu/microcode/reload": Read-only file systemCreating user usbmux (usbmux user) with uid 140 and gid 140.
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported sys...Creating user usbmux (usbmux user) with uid 140 and gid 140.
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
qemu: Unsupported syscall: 285
(17/24) Creating temporary files...
Failed to open file "/sys/devices/system/cpu/microcode/reload": Read-only file system
error: command failed to execute correctly
(18/24) Reloading device manager configuration...
Skipped: Device manager is not running.