This reverts commit 4960460b82.
This produces an invalid depthcharge payload on devices with kernel packages that install both a .efi kernel and vmlinuz. mkinitfs runs boot-deploy with the .efi kernel (because `deviceinfo_generate_systemd_boot=true`) and depthcharge can't boot a kernel in this format
pkgrels have been bumped
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7682>
Changes are roughly:
- Rebase on-top of 6.12.63
- Disable not-needed ARM_ERRATA_643719
- Set ARM_ERRATA_798181=y and ARM_ERRATA_814220=y
- Modify config to make kernel and initramfs smaller:
- Change some option to modules
- Unset debug options, instead move them to new kernel fragment
exynos_debug.config
- Make all filesystems in initramfs built-in
- Compress modules with xz
- Also change some options to make pmbootstrap kconfig check happy
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7663>
Device-specific improvements are as follows:
* Some of the SoC DTS stuff has been upstreamed and therefore dropped
from here (the rest, which constitutes most of the aport patches, has
been cleaned up and will land in 6.19)
* Dropped some unnecessary reserved memory (~65.5MiB)
* Power domain support added (fixes IOMMU probing and will be useful
for some other stuff)
* Added a workaround for the WiFi firmware crashes
* Fixed `kconfig check` complaints
Signed-off-by: Duje Mihanović <duje@dujemihanovic.xyz>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7661>
`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>
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>
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>
Aster Boese