Let usb-moded handle the USB gadget in GNOME Mobile, Phosh and Plasma Mobile UIs.
OpenRC and systemd are both using the patches of usb-moded to allow
switching modes through a set of scripts. usb-moded supports also
activation of systemd services depending on the mode which is the
'normal' way. If this is used, the patches are not all needed for
usb-moded, but would create different code paths for systemd and OpenRC,
which is not good for maintenance.
Co-authored-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6531>
`device-pine64-pinenote-sway.post-upgrade` should check if `sway_hrdl`
is enabled but not installed (like in the case of upgrading from v7-r0
to v8-r0) before setting default session back to `sway`. Else, every
upgrade will set the session back to sway.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7644>
`device-pine64-pinenote-systemd.post-install` checks if `tinydm-ebc` was
active via `is-active` systemctl command. This does not work in chroot
environment, and exits with exit code 0, thus acting as if `tinydm-ebc`
is active. Since this check is used for v7-r0 to v8-r0 upgrade, it can
be assumed that if output isn't `active`, then the check should not
pass. This commit reworks this by looking for that output rather than a
zero exit code.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7644>
modem-gnss / qmicli depends on qrtr being up, or it fails on boot and
GPS doesn't work on this device:
sargo systemd[1]: Starting Google Sargo (Pixel 3a) GNSS Modem Setup...
sargo qmicli[1080]: error: node with id 0 not found in QRTR bus
Ideally there would be a path in /dev or sysfs so we could add a
ConditionPathExists= in the unit, but I tried hard to find something and
was unable to. Making modem-gnss depend on ModemManager seems to work
around this issue, since qrtr seems to always (in my testing) be up by
then. IIUC in the future we may not have to run qmicli to enable GPS, so
this patch is a workaround to fix a workaround.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7636>
MM does other important things (like enable GPS) even if no SIM is
installed, but when this returns non-zero after timing out waiting for a
SIM then we lose the ability to have MM enable GPS (for example). Other
failures related to selecting SIMs should still trigger a non-zero exit
and block MM (I guess), but if we waited a while and no SIM shows up
then let MM start anyways.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7634>
Now that samsung-manta uses EFI boot, its boot partition should be
formatted in FAT32.
Note that the current behaviour does not impair booting nor updating of
kernels and initramfs, but tools like bootctl do not like that.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7624>
This still comes from the aports hook, where we want to avoid too large patches,
but in pmaports we have big kernel config files that might exceed the
configured 256 kiB limit.
Currently the following files exceed that limit and used git commit
--no-verify to overcome the error (or didn't configure git hooks):
260K ./device/community/linux-postmarketos-qcom-laptop/config-postmarketos-qcom-laptop.aarch64
268K ./main/postmarketos-bootsplash/OpenSans-Regular.svg
336K ./device/downstream/linux-amazon-checkers/0003-Add-missing-kconfig-files.patch
376K ./device/downstream/linux-amazon-austin/silence-power-logspam.patch
Alternatively we can increase the file limit, but i'm not sure what that
solves.
In future for Alpine, I want to move the check to abuild's internal
linting, which makes it visible for all APKBUILDs, consistent with
other of abuild's linters and also shows up on CI.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7603>
Calls are broken for the Librem 5 with pipewire. Switch to pulseaudio
again until this is resolved by depending on
postmarketosbase-ui-audio-pulseaudio and pulseaudio<9990. The later is
needed as otherwise we get a conflict with pipewire-pulse:
ERROR: unable to select packages:
pipewire-pulse-9991.4.9-r1:
breaks: postmarketos-base-ui-audio-pulseaudio-42-r0[!pipewire-pulse]
satisfies: device-purism-librem5-9-r6[pulseaudio>17]
gnome-settings-daemon-99948.1-r3[pulseaudio]
postmarketos-base-ui-audio-pulseaudio-42-r0[pulseaudio]
That pulseaudio<9990 is needed is not great, but doing it like this
inside the device package is the best way to ensure this doesn't affect
any other devices for now, with the intention to have this change
backported to v25.12 before we announce the release. I've created issue
4187 to discuss how to improve the pulseaudio/pipewire packaging in
general so this isn't necessary in the future.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7619>
Compatibility with distros like NixOS that do not use Filesystem
Hierarchy Standard was improved. This should not affect the behavior
in postmarketOS.
Additionally a systemd target file was added.
Changelog:
- openrc: Adopt customizable binary path
- systemd: add target file
- Improve compatibility with non-FHS systems
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7607>
Stefan Hansson