manjaro-arm-installer issueshttps://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues2022-04-08T10:15:46Zhttps://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/35PinePhone support?2022-04-08T10:15:46ZJan JurzitzaPinePhone support?I got here from the [Pine64 Getting Started](https://www.pine64.org/gettings-started/) page where it directly links to this repository, however the README does not include the PinePhone as supported device and it's not available in the "...I got here from the [Pine64 Getting Started](https://www.pine64.org/gettings-started/) page where it directly links to this repository, however the README does not include the PinePhone as supported device and it's not available in the "Choose a device" dialog.
Is the link from the Pine64 page wrong and this installer doesn't support PinePhones or am I supposed to pick some other device?https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/10TTY Keyboard Layout error on install2021-03-25T19:02:08ZAndre VallesteroTTY Keyboard Layout error on install![2019-12-02-212110_740x485_scrot](/uploads/8a6e65c0e8ba1206d9b27b14f297b75c/2019-12-02-212110_740x485_scrot.png)![2019-12-02-212110_740x485_scrot](/uploads/8a6e65c0e8ba1206d9b27b14f297b75c/2019-12-02-212110_740x485_scrot.png)https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/53Patch installer for branch selection using argument2023-11-25T11:34:09ZFrede HPatch installer for branch selection using argumentInstaller default to stable branch.
To make the installer use a different branch apply the following patch and run
sudo bash manjaro-arm-installer arm-unstable
It is assumeed the argument is a valid arm branch.
~~~
diff --git a/m...Installer default to stable branch.
To make the installer use a different branch apply the following patch and run
sudo bash manjaro-arm-installer arm-unstable
It is assumeed the argument is a valid arm branch.
~~~
diff --git a/manjaro-arm-installer b/manjaro-arm-installer
index aea7b19..603320c 100755
--- a/manjaro-arm-installer
+++ b/manjaro-arm-installer
@@ -17,6 +17,10 @@ else
export DIALOGRC="/etc/manjaro-arm-installer/dialogrc_gui"
fi
+BRANCH="arm-stable"
+if [[ -n $1 ]]; then
+ BRANCH=$1
+fi
# clearing variables
DEVICE=""
EDITION=""
@@ -140,6 +144,8 @@ create_install() {
$NSPAWN $TMPDIR/root pacman-key --init 1> /dev/null 2>&1
$NSPAWN $TMPDIR/root pacman-key --populate archlinuxarm manjaro manjaro-arm 1> /dev/null 2>&1
+ info "Setting target branch ${BRANCH}..."
+ sed -i 's|^Branch.*|Branch = '${BRANCH}'|' $TMPDIR/root/etc/pacman-mirrors.conf
info "Generating mirrorlist..."
$NSPAWN $TMPDIR/root pacman-mirrors -f10 1> /dev/null 2>&1
~~~
[01_set_branch.patch](/uploads/9b8a1538979012a883e230c2eba6b500/01_set_branch.patch)https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/51Black screen2023-04-11T16:58:46ZWinterWonderland0Black screenI’m using the minimal version on a roc-rk3328-cc, and it turns on, but all I get is a blank monitor, no command line, no nothing. Does anyone know why this is happening?I’m using the minimal version on a roc-rk3328-cc, and it turns on, but all I get is a blank monitor, no command line, no nothing. Does anyone know why this is happening?https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/50no LUKS asked2022-12-29T06:14:50ZThijs van Uldenno LUKS askedI see in this issue that encryption should be enabled: https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/23
But when I run the script (sudo bash manjaro-arm-installer) there is no option to encrypt. I run...I see in this issue that encryption should be enabled: https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/23
But when I run the script (sudo bash manjaro-arm-installer) there is no option to encrypt. I run the script for the Devterm and choose EXT4.
My version: 1.4.11-1 and I read that encryption is added in 1.4.0 so what am I missing here?https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/49Dependency binfmt-qemu-static required for manjaro-arm-installer could not b...2022-12-06T23:13:18ZRiverDependency binfmt-qemu-static required for manjaro-arm-installer could not be foundmanjaro-arm-installer has a list of Dependencies
`binfmt-qemu-static`
is not available. tried but could not find this name package.
`sudo pacman -S binfmt-qemu-static`
This is the exact package listed as needed for use of the Manja...manjaro-arm-installer has a list of Dependencies
`binfmt-qemu-static`
is not available. tried but could not find this name package.
`sudo pacman -S binfmt-qemu-static`
This is the exact package listed as needed for use of the Manjaro-arm-installer
Also tried to search for any package with name qemu-static
sudo pacman -Ss qemu-static
and it could not be found.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/48/boot missing from fstab2022-08-22T10:57:18ZRichard Warburton/boot missing from fstabI suspect this may relate to full disk encryption, as everything else was standard.
After first install (August 12), I noticed that boot would appear on the desktop, but thought nothing of it.
After upgrading the kernel (days later), e...I suspect this may relate to full disk encryption, as everything else was standard.
After first install (August 12), I noticed that boot would appear on the desktop, but thought nothing of it.
After upgrading the kernel (days later), everything went wrong, no wifi, sound, etc.
Found this post: https://forum.manjaro.org/t/wifi-no-longer-works/117162
After updating fstab and copying across the boot directory files to the boot partition, everything was back as it should be. EXCEPT the FDE password is now querty instead of colemak (not sure how to fix that).
Anyway, I thought I better report it. Thanks.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/47Pinephone - Unable to install Phosh2022-07-10T17:03:00Zquakestar78Pinephone - Unable to install Phosherror: target not found: gnome-console
-> Enabling services...
sshd.service not found in rootfs. Skipping.
NetworkManager.service not found in rootfs. Skipping.
ModemManager.service not found in rootfs. Skipping.
phosh.service not...error: target not found: gnome-console
-> Enabling services...
sshd.service not found in rootfs. Skipping.
NetworkManager.service not found in rootfs. Skipping.
ModemManager.service not found in rootfs. Skipping.
phosh.service not found in rootfs. Skipping.
bluetooth.service not found in rootfs. Skipping.
zswap-arm.service not found in rootfs. Skipping.
bootsplash-hide-when-booted.service not found in rootfs. Skipping.
bootsplash-show-on-shutdown.service not found in rootfs. Skipping.
systemd-oomd.service not found in rootfs. Skipping.
eg25-manager.service not found in rootfs. Skipping.
pinephone-post-install.service not found in rootfs. Skipping.
pinephonepro-post-install.service not found in rootfs. Skipping.
pinephone-modem-scripts.pinephone-modem-setup.service not found in rootfs. Skipping.
siglo.service not found in rootfs. Skipping.
-> Applying overlay for phosh...
-> Setting up users...
-> Setting password for root ...
execv(userdel) failed: No such file or directory
-> Adding user...
-> Enabling user services...
-> Setting up system settings...
execv(timedatectl) failed: No such file or directory
Generating locales...
Generation complete.
/usr/bin/manjaro-arm-installer: Zeile 205: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf: Datei oder Verzeichnis nicht gefunden
/usr/bin/manjaro-arm-installer: Zeile 206: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf: Datei oder Verzeichnis nicht gefunden
/usr/bin/manjaro-arm-installer: Zeile 207: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf: Datei oder Verzeichnis nicht gefunden
/usr/bin/manjaro-arm-installer: Zeile 208: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf: Datei oder Verzeichnis nicht gefunden
sed: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf kann nicht gelesen werden: Datei oder Verzeichnis nicht gefunden
sed: /var/tmp/manjaro-arm-installer/root/usr/lib/systemd/system-preset/90-systemd.preset kann nicht gelesen werden: Datei oder Verzeichnis nicht gefunden
Correcting permissions from overlay...
-> Adding btrfs support to system...
sed: /var/tmp/manjaro-arm-installer/root/etc/mkinitcpio.conf kann nicht gelesen werden: Datei oder Verzeichnis nicht gefunden
-> Cleaning install for unwanted files...
==> pinephone phosh install complete
==> Writing bootloader and cleaning up after install...
mv: der Aufruf von stat für '/var/tmp/manjaro-arm-installer/root/boot/*' ist nicht möglich: Datei oder Verzeichnis nicht gefundenhttps://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/46PinePhone Pro support2022-04-23T23:24:17ZMikhail PodshivalinPinePhone Pro supportCurrently, if I understand correctly, manjaro-arm-installer allows installing only to original PinePhone. Is it possible to add PinePhone Pro support?Currently, if I understand correctly, manjaro-arm-installer allows installing only to original PinePhone. Is it possible to add PinePhone Pro support?https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/45Odroid HC4 support missing, but seems to be working2022-04-06T10:33:13ZRahul BhandariOdroid HC4 support missing, but seems to be workingMinimal was running with the script after I added ohc4, but it seems to be missing from the menu options. I also added it in the u-boot.bin section next to "|oc4)". I had also replaced linux-vim with linux-odroid in arm-profiles. I wasn'...Minimal was running with the script after I added ohc4, but it seems to be missing from the menu options. I also added it in the u-boot.bin section next to "|oc4)". I had also replaced linux-vim with linux-odroid in arm-profiles. I wasn't able to get the sway desktop version working, but this may be due to me not clearing petitboot from SPI flash.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/44Blank display when in initramfs making it impossible to see LUKS password pro...2022-02-02T18:38:44ZBart De VriesBlank display when in initramfs making it impossible to see LUKS password prompt (solution included)The screen turns black after u-boot loads the initramfs image. After typing the LUKS password blindly, the display switches on again and the boot proceeds as normal.
It turns out that a recent kernel change introduced a new module `pan...The screen turns black after u-boot loads the initramfs image. After typing the LUKS password blindly, the display switches on again and the boot proceeds as normal.
It turns out that a recent kernel change introduced a new module `panel_edp` which is split off from the `panel_simple` module. The manjaro-arm-installer adds the `panel_simple` module to `/etc/mkinitcpio.conf` for encrypted root. This was the module that enabled the video display during initial boot (i.e. initramfs). However, with recent kernels the `panel_edp` module is required. If I add `panel_edp` to the `MODULES` then I see the LUKS prompt again.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/43Support for ClockworkPI DevTerm2022-02-02T18:38:44ZGhost UserSupport for ClockworkPI DevTermWe recently started supporting the ClockworkPi DevTerm, so we should also add it to the installer at some point.
It's currently using a separate kernel package, but it's very close to mainline (ei, it just adds a couple of patches), so ...We recently started supporting the ClockworkPi DevTerm, so we should also add it to the installer at some point.
It's currently using a separate kernel package, but it's very close to mainline (ei, it just adds a couple of patches), so I think we should offer this in the installer too.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/42roc-rk3328-cc can not boot2021-11-08T01:37:05Zaeeqroc-rk3328-cc can not bootRoc-rk3328-cc can not boot black screenRoc-rk3328-cc can not boot black screenhttps://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/4100-keyboard.conf: No such file or directory2022-02-02T18:38:44Z0n0w1c00-keyboard.conf: No such file or directorymanjaro-arm-installer 1.4.7-1
When installing sway + btrfs on rpi4
```
Generating locales...
en_US.UTF-8... done
Generation complete.
/usr/bin/manjaro-arm-installer: line 197: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00...manjaro-arm-installer 1.4.7-1
When installing sway + btrfs on rpi4
```
Generating locales...
en_US.UTF-8... done
Generation complete.
/usr/bin/manjaro-arm-installer: line 197: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf: No such file or directory
/usr/bin/manjaro-arm-installer: line 198: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf: No such file or directory
/usr/bin/manjaro-arm-installer: line 199: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf: No such file or directory
/usr/bin/manjaro-arm-installer: line 200: /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf: No such file or directory
sed: can't read /var/tmp/manjaro-arm-installer/root/etc/X11/xorg.conf.d/00-keyboard.conf: No such file or directory
Correcting permissions from overlay...
-> Adding btrfs support to system...
```https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/40support for quartz64 SBC2022-04-06T14:55:00ZBobsupport for quartz64 SBCCan you please provide guidance to install manjaro arm on a pine quartz64.
There is a minimal manjaro image I wish to install to make some tests,
unfortunately I can't see any option in the dialog to select quartz64 device or install a ...Can you please provide guidance to install manjaro arm on a pine quartz64.
There is a minimal manjaro image I wish to install to make some tests,
unfortunately I can't see any option in the dialog to select quartz64 device or install a custom img file.
https://github.com/manjaro-arm/quartz64-bsp-images/releases/download/20210906/Manjaro-ARM-minimal-quartz64-bsp-20210906.img.xz
Your help is appreciated,https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/39Feature request: sshd_config with keys only support2022-04-08T10:16:06ZFolât PjêrsômêjFeature request: sshd_config with keys only supportI don't see why one would want to let easy password access be allowed for Manjaro ARM devices.
I mean technically one can enter difficult passwords in the dialog,
but I would rather choose very simple ones and have them replaced via SSH...I don't see why one would want to let easy password access be allowed for Manjaro ARM devices.
I mean technically one can enter difficult passwords in the dialog,
but I would rather choose very simple ones and have them replaced via SSH with random generated ones later.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/38Skips Timezone and keyboard layout in docker.2021-07-30T05:28:43ZFolât PjêrsômêjSkips Timezone and keyboard layout in docker.I have this dockerfile.
```text
FROM manjarolinux/base:latest
LABEL version="1.0"
LABEL maintainer="Folaht"
LABEL release-date="2021-07-19"
# Synchronize Manjaro Linux OS
RUN pacman -Sy
# Install dependencies
RUN pacman --noconfirm -...I have this dockerfile.
```text
FROM manjarolinux/base:latest
LABEL version="1.0"
LABEL maintainer="Folaht"
LABEL release-date="2021-07-19"
# Synchronize Manjaro Linux OS
RUN pacman -Sy
# Install dependencies
RUN pacman --noconfirm -S btrfs-progs
# Install Manjaro Arm Installer
RUN pacman --noconfirm -S manjaro-arm-installer
# Run command on Docker launch
CMD ["bash","manjaro-arm-installer"]
```
And when runnning it with `docker run -it --privileged=true manjaro-arm-installer`,
it skips both timezone and keyboard layout.
Once done, the information for both of these options show an error of some kind
`Expected at least 20 tokens for --men, have 4`
as seen below:
https://aws1.discourse-cdn.com/business5/uploads/safenetwork/original/3X/0/1/01072aef30da5a55086ca2ea94a9bf2dcb87ac5a.pnghttps://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/36bootloader is not written to sd card, if you choose RPi 4 in the menu2021-06-23T08:01:42ZiTuxbootloader is not written to sd card, if you choose RPi 4 in the menuIf I select RPI4 as target device in the menu, no data gets written to the sd card.If I select RPI4 as target device in the menu, no data gets written to the sd card.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/34Add F2FS support for filesystem selection2022-02-02T18:38:44ZAndre VallesteroAdd F2FS support for filesystem selection[Feature Request] Probably more than 90% of machines running Manjaro ARM will be on some type of flash storage, so it would be quite beneficial to support a FS that doesn't require tuning for maximum flash performance and longevity.[Feature Request] Probably more than 90% of machines running Manjaro ARM will be on some type of flash storage, so it would be quite beneficial to support a FS that doesn't require tuning for maximum flash performance and longevity.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/33Please guard against bricking the Pinebook Pro2021-05-07T14:20:41ZTom SzilagyiPlease guard against bricking the Pinebook ProI have successfully used this script to create a manjaro-i3 installation with encrypted root fs on my new PBP. Thanks for all your work that went into it!
Unfortunately, there is a gotcha that tripped me up, and seeing that this has alr...I have successfully used this script to create a manjaro-i3 installation with encrypted root fs on my new PBP. Thanks for all your work that went into it!
Unfortunately, there is a gotcha that tripped me up, and seeing that this has already happened before to someone else, I would like to raise this in the hope of a possible fix and also to warn other users.
So, first of all, I am a careful guy, and I wanted to test that this script works without risking the eMMC in my device.
So I have done a test install to an SD card while running the default OS from eMMC boot.
This worked well enough, so then I booted from the newly created SD card and having checked out that I generally like how things are, I decided to do the "real" install, this time to the eMMC. So now I was already in the OS created by this installer, having booted from the SD card, and I ran this installer again, directed at the eMMC.
Then, the same thing happened as described here:
https://forum.manjaro.org/t/pinebook-pro-install-with-encryption/47821
Specifically: at an early stage, I also got the printout `Device ROOT_MNJRO already exists.` but then everything continued and things looked OK. Until, they suddenly did not. My wifi connection broke down, downloads failed, and I was left with a broken system. I still had a root shell, so having already found the above forum entry, I ran `fdisk` and removed the partition entries on the eMMC in the hope that this would allow the PBP to boot through the (empty) eMMC to the SD, sparing me the "unbricking" that lay ahead. Alas, that did not work out (as explained below).
The script apparently corrupted the contents of the filesystem it was running from (SD card, /dev/mmcblk1) while it was explicitly directed to install to the eMMC (/dev/mmcblk2). Although the script had warned me that the existing contents of the target (eMMC) would be destroyed, it destroyed the SD partition as well, which I consider as a critical failure. Unfortunately, the eMMC content was also destroyed so that my PBP would not boot again (the power on button did not have any effect). Not with a freshly minted known-good SD image, not without an SD in the slot. This despite the fact that I wiped the eMMC partition table before powering off the PBP at the end of the broken install, as pointed out above.
The root cause of this has nothing to do with having SSH'd into the box as described by the above linked forum entry (I was not doing that; I ran the installer from the PBP directly!). Rather, the problem is that the partition image label(?) `ROOT_MNJRO` is hardcoded somewhere and the script gets tripped up if it is run from an OS that was created with the script itself.
Please fix this, at the very least by clearly documenting this as a limitation, and also detecting and aborting on this condition so that people careful enough to create a throwaway OS on their SD (hoping to protect their eMMC from getting bricked) and then using that SD to run the same script to install onto the eMMC do not brick their devices.
* * *
If you are reading this after having landed in the same situation: DO NOT PANIC. Write a new SD card with a vanilla manjaro factory image (whichever one you prefer; I used the manjaro-i3 image). Carefully read the hardware disassembly instructions on the Pinebook wiki. Remove the bottom plate of your PBP and flip the eMMC disable switch. Now you will be able to boot from the SD. Flip the switch back again to re-enable the eMMC. Reboot, this will now go through the eMMC stage and boot from the SD (seems the boot gets stuck on the eMMC the first time, but gets repaired by the above procedure to the point that it can be re-added to the boot sequence, at least this happened in my case). Now you are running from the SD and the OS will see the eMMC (verify the existence of `/dev/mmcblk2` with `fdisk -l`). You may now re-install the OS using the manjaro-arm-installer directly to the eMMC (and it will work, since you are *not* running from an image created with this same installer).