Standardize the use of pkgver=9999$_pkgver, allowing easier upgrades but
also a single expected behaviour for users like nightly-builder.
[ci:skip-vercheck]: some package have the same $pkgver-r$pkgrel
[ci:ignore-count]: this is expected
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7802>
For some reason, apk preferred to satisfy g-s-d's pulseaudio dependency
by pipewire-pulse-9991.4.9-r1 (with k=1) and not pulseaudio-17.0-r7
(with k=10), and therefore didn't respect provider_priority but pkgver.
This then resulted in the apk solver preferring
pmos-base-ui-audio-pipewire over -pulseaudio, because the
!pipewire-pulse dep by -pulseaudio wasn't satisfiable.
[ci:skip-build]: alpine binary repos incomplete for some archs
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7776>
This disables swap-based killing and sets a lower pressure threshold
for user apps in the app slice so they will get killed sooner than other
things (e..g the whole session slice).
Killing based on swap usage was resulting in some sudden kills from
oomd, and upon further investigation is seems like other distros
(ubuntu, fedora) either never enabled this or walked it back due to it
being confusing for users.
The override for app.slice and sets the pressure limit to a value less
than the other slices, in an attempt to fix situations where an app
(e.g. firefox) was creating a ton of pressure and systemd-oomd was
killing the entire UI/session.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7751>
This "size"/factor/percentage represents the total amount of
**uncompressed** data that is allowed to be written to the zram-backed
swap device. It is **not** the amount of RAM to use for zram swap (as I
had previously and erroneously thought.) What this means is that if we
set the percent to 50% on a device with 3GB of RAM then up to 1.5GB of
*uncompressed* data can be written to it, BUT since compression algos
usually do better than a ratio of 1:1... less than 1.5GB of RAM will
actually be occupied by this data when it is compressed.
A 1.5:1 compression ratio seems relatively safe to assume, even if we
use lz4 (which is less "good" at compressing than zstd), so I propose we
set the size to 150%. Some distros (PureOS) set this higher (200%), but
I think we should be somewhat conservative since we want to avoid any
thrashing in case the compression ratio at runtime ends up being less
than 2:1 for some reason.
This does set a limit of 50% for devices with >32GB of RAM, to
reduce overhead with using a larger amount of zram swap. The kernel
documentation for zram suggests there's a 0.1% overhead, so if we let
this amount get large then it could be tens or hundreds of MB of RAM
"wasted." The amount I chose is kinda arbitrary, I think this can be
improved later. At the very least, users can change this amount in the
deviceinfo variable.
Fixes#4250
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7754>
This is meant to replace zram-init. It's much simpler, since it only
sets up zram swap and doesn't try to do all the things that zram-init
does. This also lets us add additional logic, such as selecting
different default algorithms based on the runtime CPU arch and
conditionally applying sysctl settings that might be inappropriate when
*not* using zram swap.
To create zramstart, I took the zram-configurator, which reads config
from deviceinfo vars, and extended it to create the zram swap device.
zramstart and zramstop were inspired by what Fedora does. The sysctl
config is from the work done here:
https://source.puri.sm/Librem5/librem5-base/-/merge_requests/381
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7754>
* Set Co-Mainatiner as maintainer, if they exist
* Add me as co-maintainer of QEMU packages to fulfill main requirements
* Add people interested in maintainance to their packages
* device-google-snow now has no maintainer, if someone is interested,
please add yourself as maintainer, otherwise it has to be dropped
As we all know they are inactive nowadays, the maintainer variables
should reflect the reality who cares/is responsible about a package, and
inactive members are not. And waiting for a inactive maintainer 2 weeks
is just staling the MR.
Thanks for all the work Minecrell & Jenneron, and feel free to add
yourself again if you're back again.
[skip ci]: too many false positives :p
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7748>
Manual kconfig changes:
* CONFIG_NTSYNC should be enabled and preferably set to 'm' (category:wine)
* CONFIG_ZRAM_BACKEND_842 should be enabled and preferably set to 'y' (category:zram)
* CONFIG_ZRAM_BACKEND_DEFLATE should be enabled and preferably set to 'y' (category:zram)
* CONFIG_ZRAM_BACKEND_LZ4 should be enabled and preferably set to 'y' (category:zram)
* CONFIG_ZRAM_BACKEND_LZ4HC should be enabled and preferably set to 'y' (category:zram)
* CONFIG_ZRAM_BACKEND_LZO should be enabled and preferably set to 'y' (category:zram)
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7599>
As explained in the previous commit, this was initially envisioned to
be used in a different way, and with ci-tron the way to add the
console is different (just a gitlab variable), so this won't be needed
in the future.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7489>
The check in Python did not work with devices without kernel variants
due to it returning None and that breaking the has_kernel_variants
check. Fix that, and also adding the kernel variant to install
packages, which was missed. In the process, rename kernels to
kernel_variants. All devices have at least one kernel, but not all
have "variants" :)
Signed-off-by: Pablo Correa Gómez <pabloyoyoista@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7489>
So we can read the complete output in the logs. This was initially
done to avoid the output from being interrupted, and therfore easier
to read. However, it avoids kernel logs to be collected, which is an
important part of the tests, and necessary for debugging. So let dmesg
be as default.
Signed-off-by: Pablo Correa Gómez <pabloyoyoista@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7489>
Busybox su and login are not aware of PAM, so on a system
with linux-pam installed, they entirely ignore any rules.
These issues can be mitigated by removing the suid binary
that the symlinks point to and require, which is installed
by busybox-suid. Because busybox-suid handles more than su
and login, this commit replaces all the tools we use that
would be called through it.
Note that this does not remove Busybox su and login, as they
are in Busybox itself. This commit instead only removes the
suid interface that they would normally be called from.
See https://gitlab.alpinelinux.org/alpine/aports/-/issues/11730
for more information.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7724>
While this is not my package, I emailed the maintainer as he hasn't made
a new account since we migrated to our self-hosted instance. Today he
replied with that he may return to it in the future but that it would be
best to remove his maintainer line in the meantime.
Signed-off-by: Stefan Hansson <newbyte@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7742>
This unit will activate `time-sync.target` after system time is synced,
e.g. by NTP. We can use this target to delay starting some units until
we know that system time is correct. IIUC this shouldn't have any impact
on system startup otherwise, including existing units we enable, so
nothing should be slowed down by adding this.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7711>
Setting it to =y requires also setting CONFIGFS=y, but since we have
CONFIGFS=m this needs to be adjusted or else config generated from this
toml will fail validation / kconfigcheck.
```
[09:25:01] Copy kernel config back to pmaports dir
[09:25:02] (native) generate checksums for linux-postmarketos-asahi
[09:25:03] INFO: config-postmarketos-asahi.aarch64: CONFIG_USB_F_FS is preferably y, but currently m (category:usb_gadgets)
[09:25:03] Fragment pmos.config: CONFIG_USB_F_FS expected to be 'y' but has different value in final config
[09:25:03] ERROR: Fragment validation failed: Some options from fragments did not make it to the final kernel config. This usually means missing dependencies.
```
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7713>
It is true that Phosh originally was developed for the Librem 5,
but at this point that is more of a "fun fact" than relevant
information with Purism no longer funding Phosh development and
the Librem 5 losing prominence. Replace it with something more
descriptive.
Signed-off-by: Stefan Hansson <newbyte@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7704>
It has no other packages depending on it and _if_ somebody has _some_
use of it, it should be in Alpine.
This package hasn't been touched since the initial inclusion in 2019,
and also the upstream repo had it's last activity in 2017.
Rel: 322cec513c ("main/columbiad: new package (full screen launcher) (!364)")
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7695>
The previous rule is too vague and would also tag /dev/fastrpc-cdsp
devices too. Sometimes iio-sensor-proxy would bind to this which
seemed to always produce inverted orientation values. If only
/dev/fastrpc-adsp* is tagged, then orientation always seems to be
correct.
fixes#3741
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7681>
MTP transfers write files to the home folder of the user.
If no GID and UID are specified, uMTP-responder will use the GID/UID
under which it is running at the time of the file transfer.
This causes users to not be able to access the files on the device after transfering.
This patch adds a systemd generator that:
1) reads /etc/default_user, and appends config to
/etc/umtprd/umtprd.conf to set the MTP default user/group. If this
file doesn't exist, 10000:10000 is the fallback uid:gid.
2) installs this config to /run/umtprd/umptrd.conf
3) adds a unit override to /run for umtprd.service that runs the daemon
with this modified config
The generator is used instead of hardcoding a uid and gid in umtprd.conf
so that this can support immutable installs or situations where the
default UID/GID is not 10000.
Co-authored-by: Dylan Van Assche <dylan@postmarketos.org>
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7658>
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>
The initramfs can sometimes use the device-mapper to open dynamic
partitions. Dynamic partitions are used for testing a full installation
without touching userdata (so testers can quickly revert to a working
phone at any time). Since subpartitions are still used on google-sargo,
do not skip device-mapper devices.
Fixes: 0268336968 ("main/postmarketos-initramfs: fix bug with booting from usb")
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7675>
It's taken from the third-party kodi-standalone-service repo, which just ships
services & configs to be used with kodi. They seem opinionated enough
that they won't make sense in upstream Kodi. So I think vendoring it
downstream is fine.
Also adding me as a co-maintainer for kodi, as I'm the aports maintainer
and care enough about it.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7672>
Fixes CI being broken everywhere:
File "/builds/postmarketOS/pmaports/.ci/testcases/conftest.py", line 32, in args
init_args(args)
File "/tmp/pmbootstrap/pmb/helpers/args.py", line 94, in init
context.ccache = args.ccache
^^^^^^^^^^^
AttributeError: 'PmbArgs' object has no attribute 'ccache'
Signed-off-by: Stefan Hansson <newbyte@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7670>
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>
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>
Else systemd/meson may try to generate it at build time, which doesn't
work when the host kernel is a different arch than the target.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
This builds from upstream now.
- tests are re-enabled
- disable BTF support / drop vmlinux.h dependency, enabling bpf is
enough for mkosi/testing stuff, and getting a sane vmlinux.h that
systemd can compile with seems to be "complicated."
- armhf is re-enabled since we don't enable BTF anymore
- workaround stage0 linking failing on riscv64 by enabling tests
- increase test timeout for main pkg, because running in qemu is slow
- a lot more dependencies are explicitly listed now, because they are
dlopened and abuild doesn't know how to detect these
- meson build options re-arranged / cleaned up (some of these are
implicitly disabled by using -Dlibc=musl)
- tests are skipped for archs that we build in CI/bpo that don't have
native hw, since ~13 of them fail for unknown (or timeout) reasons. 2
of them time out after >1200 seconds and 11 fail for mysterious
reasons.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7584>
Just pull in postmarketos-artwork-wallpapers-gnome which provides a
gschema override that is updated when the artwork package gets updated -
and won't break every so often.
Usually that package is pulled in via an "install_if" with
postmarketos-base-ui-gnome but since we just want the artwork
subpackage, depending on base-ui-gnome would be quite much and probably
not what we want for Lomiri.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7593>
This is device-agnostic, and allows to not depend on a package that
might end up in alpine in the future. In the process, also remove the
unnecessary postmarketos-test dependency in makedepends. That is just
an empty package.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7553>
This will be removed from unl0kr in the following commits, since at
some point it might be that unl0kr is not packaged in postmarketOS,
and this is a completely device-agnostic test, which is what this
package is for.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7553>
Since this was introduced, we no longer create "initramfs-extra"
unconditionally. So the "extra" files will be included in the
initramfs anyway. In addition, to be able to test the initramfs-extra
split for devices that need it, we require:
* To have one of those devices available for test.
* To modify our test setup to pass a rootfs that can be mounted.
Both are long into the future, if they will ever materialize. So let's
remove this, reducing the complexity.
Signed-off-by: Pablo Correa Gómez <pabloyoyoista@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7553>
Changes are roughly:
- Rebase on-top of 6.12.62
- Add isa1200 driver (from exynos4), and use it on manta (@lat3st)
- Add camera flash for manta (@lat3st)
- Improve manta audio driver to decrease CPU load (@alexmrqt)
- Fix wacom w9000 pen being always active unless inserted (@eisenbahnfan)
- Drop a pm_domain hack, and instead make exynos5 subcmu driver wait
for pm_domain to probe first (@eisenbahnfan)
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7582>
Apparently the user slice and root slice weren't being configured
correctly and oomd was not stepping in during high swap pressure events
before the kernel oom killer showed up to the party. This (hopefully)
properly configures systemd-oomd now... The configuration was inspired
by Fedora.
https://fedoraproject.org/wiki/Changes/EnableSystemdOomd
I used the test in that wiki page to confirm it's now properly configured:
$ systemd-run --user tail /dev/zero
$ journalctl -f
...
systemd[1081]: Started [systemd-run] /usr/bin/tail /dev/zero.
systemd-oomd[517]: Considered 79 cgroups for killing, top candidates were:
systemd-oomd[517]: Path: /user.slice/user-10000.slice/user@10000.service/app.slice/run-p5146-i5147.service
systemd-oomd[517]: Swap Usage: 4.6G
systemd-oomd[517]: Killed /user.slice/user-10000.slice/user@10000.service/app.slice/run-p5146-i5147.service due to memory used (2458>
systemd[1081]: run-p5146-i5147.service: systemd-oomd killed 1 process(es) in this unit.
systemd[1081]: run-p5146-i5147.service: Main process exited, code=killed, status=9/KILL
systemd[1081]: run-p5146-i5147.service: Failed with result 'oom-kill'.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7556>
In an effort to have the option to start with a vanilla sway experience,
the sway subpackage is renamed to sway-hrdl to allow for a vanilla sway
config by default, but give the option for hrdl's opiniated
configuration if desired. Non-opiniated eink optimizations will be added to
the now empty sway subpackage as they are developped. A post-install
script was added to move back to vanilla sway.
In favor of using the more automated systemd subpkg. `tinydm-ebc.service` is
removed in favor of an override file for `tinydm.service` packaged in a
device-wide systemd subpackage. A post-install script was added to
disable `tinydm-ebc.service` and enable `tinydm.service` is tinydm is
in-use at time of upgrade.
Enabling systemd units is now handled by postmarketos-base-systemd's
90-base.preset.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7515>
Just like before with b4c55cbd90 ("systemd/systemd-services:
remove a few upstreamed services")
Also reflect the maintainers to the people actually reviewing
systemd-services MRs and replace the "how-to package serives"-guide to a
message to upstream them instead.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7522>
Makes it much easier to use plain gnome-shell on tablets or even phones
and is already enabled on GNOME Mobile.
@rmader remebers upstream not enabling this by default because of bugs
with XWayland, but since XWayland applications are much more rare on
mobile phones, plus it's still 100% by default and a fractional scale
has to be enabled manually.
> Makes mutter default to layout logical monitors in a logical pixel
> coordinate space, while scaling monitor framebuffers instead of window
> content, to manage HiDPI monitors. Does not require a restart.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7529>
In version 1.1.1, the new install target in the Makefile was used to
install rmtfs. This installs rmtfs to /usr/bin instead of the expected
/usr/sbin. Use the new /usr/bin directory for the OpenRC service file so
rmtfs can keep working under OpenRC.
Fixes: f7052461da ("modem/rmtfs: subpackage -systemd")
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7517>
Update kconfig as per following "pmbootstrap kconfig check" messages.
* CONFIG_BTRFS_FS is preferably y, but currently m (category:filesystems)
* CONFIG_BTRFS_FS_POSIX_ACL should be enabled and preferably set to 'y' (category:filesystems)
* CONFIG_CFI_CLANG should be enabled and preferably set to 'y' (category:hardening)
* CONFIG_CFI_ICALL_NORMALIZE_INTEGERS should be enabled and preferably set to 'y' (category:hardening)
* CONFIG_CRYPTO_CMAC is preferably m, but currently y (category:iwd)
* CONFIG_DM_CRYPT is preferably y, but currently m (category:default)
* CONFIG_DM_VERITY should be enabled and preferably set to 'm' (category:immutable)
* CONFIG_EFIVAR_FS is preferably m, but currently y (category:immutable)
* CONFIG_EROFS_FS should be enabled and preferably set to 'y' (category:immutable)
* CONFIG_EROFS_FS_ZIP should be enabled and preferably set to 'y' (category:immutable)
* CONFIG_F2FS_FS is preferably y, but currently m (category:filesystems)
* CONFIG_HID_GENERIC is preferably m, but currently y (category:input)
* CONFIG_INPUT_EVDEV is preferably m, but currently y (category:default)
* CONFIG_INPUT_UINPUT is preferably y, but currently m (category:input)
* CONFIG_IP6_NF_FILTER should be enabled and preferably set to 'm' (category:nftables)
* CONFIG_IP6_NF_IPTABLES_LEGACY should be enabled and preferably set to 'm' (category:nftables)
* CONFIG_IP6_NF_NAT should be enabled and preferably set to 'm' (category:nftables)
* CONFIG_IP6_NF_TARGET_MASQUERADE should be enabled and preferably set to 'm' (category:containers)
* CONFIG_IP_NF_FILTER should be enabled and preferably set to 'm' (category:nftables)
* CONFIG_IP_NF_IPTABLES_LEGACY should be enabled and preferably set to 'm' (category:waydroid)
* CONFIG_IP_NF_MANGLE should be enabled and preferably set to 'm' (category:waydroid)
* CONFIG_IP_NF_NAT should be enabled and preferably set to 'm' (category:nftables)
* CONFIG_IP_NF_TARGET_MASQUERADE should be enabled and preferably set to 'm' (category:containers)
* CONFIG_IP_NF_TARGET_REDIRECT should be enabled and preferably set to 'm' (category:containers)
* CONFIG_LEDS_CLASS_MULTICOLOR is preferably m, but currently y (category:input)
* CONFIG_LEDS_TRIGGER_PATTERN is preferably m, but currently y (category:community_various)
* CONFIG_LEDS_TRIGGER_TIMER is preferably m, but currently y (category:community_various)
* CONFIG_LTO_CLANG_THIN should be enabled and preferably set to 'y' (category:hardening)
* CONFIG_NETFILTER_XTABLES_LEGACY should be enabled and preferably set to 'y' (category:waydroid)
* CONFIG_NULL_TTY is preferably m, but currently y (category:default)
* CONFIG_SHADOW_CALL_STACK should be enabled and preferably set to 'y' (category:hardening)
* CONFIG_SYN_COOKIES should be enabled and preferably set to 'y' (category:default)
* CONFIG_TUN is preferably m, but currently y (category:waydroid)
* CONFIG_USB_CONFIGFS is preferably m, but currently y (category:usb_gadgets)
* CONFIG_ZRAM is preferably y, but currently m (category:zram)
* CONFIG_ZSMALLOC is preferably y, but currently m (category:zram)
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7368>
The kernel package has been renamed, so update the dependency
accordingly.
And remove append_dtb, this was actually used with boot-deploy < 0.20.0
because deviceinfo_header_version="2" was ignored and therefore v0 was
used, which requires appended dtb. Now that boot-deploy is actually
passing this parameter, we do not have to append the dtb to the kernel
image anymore, because the dtb is passed in a separate field.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7368>
On systemd installs, pbsplash causes the device to hang during init and
reset. OpenRC does not exhibit this behavior. Let's disable the splash
screen for now to get the devices working out of the box again and look
into this again after 25.12 when we have plymouth.
The serial getty setup is broken on some devices. Not all of them have
the UART TX/RX connected in hardware, so the ttyMSM0 does not exist on
all devices. On those that have it, it works, on those that don't, it
causes logspam.
Signed-off-by: Jens Reidel <adrian@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7509>
Add modules required to successfully boot the Lenovo Thinkpad T14s Gen 6 (Snapdragon X Elite).
Changes:
- Add rtc_pm8xxx module to initfs for RTC support
- Add pinctrl_sm8550, as this is required for boot and the keyboard to work
Tested-on: Lenovo Thinkpad T14s Gen 6 (21N1)
Part-of: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6306
# Kernel config based on: arch/arm64/configs/vendor/willow-perf_defconfig
maintainer="Eli Riggs <eli@rje.li>"
pkgname=linux-xiaomi-willow
pkgver=4.14.117
pkgrel=3
Loaded 100 of 1381 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Clayton Craft
Achill Gilgenast
bluebunny
tiel
Stefan Hansson
Ferass El Hafidi
Aster Boese
Robert Eckelmann
Aelin
Francesco D'Alessano
Vasiliy Doylov
Luca Weiss
Richard Acayan
Paul Sajna
Joshua Murphy
Bart Ribbers
Pablo Correa Gómez
Antoine Martin
adamthiede
Sebastian Fleer
methanal
faveoled
Sreeranj Krishna MandFerass El Hafidi
Barnabás Czémán
Ingo Reitz
Arnav Singh
ell1e
Hacker1245
Jane RachingerandClayton Craft
Oliver Smith
moeenio
Henrik Grimler
Mazzotti2
Duje Mihanović
Dylan Van AsscheandClayton Craft
Alexandre Marquet
Sid Pranjale
Joel SelvarajandAchill Gilgenast
user0-07161
Casey Connolly
Jakob Hauser
dominduchami
C-VD
Eisenbahnfan
Affe Null
Jens Reidel
postmarketOS CI
WeirdTreeThing
Clayton Craft
Igor Belwon
Rudraksha Gupta
Abdullah AL Shohag
Liam Hurwitz
bengris32
