Add polkit-elogind to _pmb_recommends, to help apk resolve the polkit
depends again. Otherwise it fails with a conflict since recent changes
in apk's dependency resolving code.

Fixes: issue 3349
[ci:skip-vercheck]: pmb_recommends change doesn't need rebuild
[ci:skip-build]: already built successfully in CI

Change <=…-r0 to <=…-r999 as it was just bumped to fix a build error and
might be bumped again in the future. I've also tried just removing -r0,
but that results in a conflict.

Richard Acayan authored 4 months ago and Anjan Momi committed 4 months ago

The Linux stable team merged v6.12 into linux-rolling-stable as
of Thursday, so here's a new release.

This release cycle was very quiet with small fixes.

The ttynull driver was enabled in the configuration to fix a bug
where userspace would start with no stdio open.

A patch that made the fuel gauge driver compatible with v6.10
was dropped.

Patches from MSM8916 and MSM8953 were re-picked, to include the change
from strlcpy to strscpy and to remove duplicate q6voice entries in a
Makefile.

Some flashlight and charging patches were staged.

The thermal nodes were sorted by the thermal sensor to match
other platforms.

Bluetooth, camera, call audio, display, USB, I2C, eMMC, modem, video
acceleration, WiFi, haptics, NFC, sensors, and touchscreen should
work and be slightly broken like before.

Ferass El Hafidi authored 4 months ago and Robert Eckelmann committed 4 months ago

After commit 8335d050bf24977afefee6612dd347abd555bc53 in pmbootstrap the
partition table now defaults to GPT instead of MBR.  This breaks booting
on Amlogic devices for the following reasons:

 * On set-top boxes: downstream U-Boot most likely does not have GPT
   support
 * On boards where we install mainline U-Boot as BL33 on eMMC/SD: the
   bootROM checks for an `@AML` image header at offset 512 (second LBA),
   which means we are basically stuck on MBR

Some Amlogic boards have U-Boot + the proprietary Amlogic firmware
stages in SPI flash (mainly the Libre Computer boards do), which means
they can use GPT, because the firmware is simply not stored on eMMC/SD.
For that reason I chose not to change the partition table on those.

Signed-off-by: Ferass El Hafidi <funderscore@postmarketos.org>

Adam Thiede authored 4 months ago and Newbyte committed 4 months ago

[ci:skip-build]: already built successfully in CI

Jianhua Lu authored 4 months ago and Newbyte committed 4 months ago

[ci:skip-build]: already built successfully in CI

Anri Dellal authored 4 months ago and Anjan Momi committed 4 months ago

Fix TypeError when RuntimeError is thrown

Example:
FAILED testcases/test_device.py::test_aports_device -
	TypeError: can only concatenate str (not "PosixPath") to str

Merge the following Samsung Galaxy Grand Prime devices into
samsung-fortuna:
- samsung-fortuna3g
- samsung-fortunaltezt (firmware only due to armv7 architecture)
- samsung-gprimeltecan
- samsung-grandprimelte (was samsung-gprimeltexx)

Jan Jasper de Kroon authored 4 months ago and Newbyte committed 4 months ago

Resolves deadlock between Rockchip crypto hardware and dm-crypt causing
kernel panic during disk decryption on devices like PinePhone Pro.

- Disables RK3399 hardware crypto engine (CONFIG_CRYPTO_DEV_ROCKCHIP)
- Enables ARM64 CPU crypto extensions for AES/SHA
- Makes core crypto components built-in instead of modules

Fixes: kernel panic in queued_spin_lock_slowpath() when accessing
encrypted devices.
[ci:skip-build]: already built successfully in CI

Jianhua Lu authored 4 months ago and Anjan Momi committed 4 months ago

[ci:skip-vercheck]

Frank Oltmanns authored 4 months ago and Oliver Smith committed 4 months ago

Update ucm conf to a version that contains a workaround to get the
bottom mic working again in voice calls.

Fixes: postmarketOS/pmaports#3322
[ci:skip-build]: already built successfully in CI

Minecrell authored 4 months ago and Oliver Smith committed 4 months ago

There might be additional kernel modules needed for the USB UDC to show up.
This used to work fine, but broke when the initramfs was unified with the
minimal one. We need to load modules/start udev before setting up USB.

Fix this by duplicating the setup calls in both init.sh and init_2nd.sh.
Both calls already have checks to allow calling them multiple times,
so we don't need to handle the initramfs-extra case in a special way.
[ci:skip-build]: already built successfully in CI

Alistair Francis authored 4 months ago and Oliver Smith committed 4 months ago

In order to reduce the power usage when using sensors let's implement
set_polling as described [1]. The patch was linked in the MR that adds
libssc support [2] and is from [3].

An alternative implementation is also avaliable [4], but that seems to
have GLib threading issues [5].

1: #2455 (comment 453587)
2: https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/381#note_2567822
3: https://gitlab.freedesktop.org/verdre/iio-sensor-proxy/-/commit/7a7a5f3ea04ff4c134f3dbbbc005b8c26d0af300
4: https://gitlab.freedesktop.org/verdre/iio-sensor-proxy/-/commit/74a5860474b6e79cd6e3be13d1ff8dd9cd810b8b
5: https://mastodon.social/@verdre/113390737074625004



Signed-off-by: Alistair Francis <alistair@alistair23.me>
[ci:skip-build]: already built successfully in CI

Split -nofde into a separate package to resolve the cyclic depenency:
postmarketos-base -> postmarketos-initramfs -> postmarketos-base-nofde

Fixes: issue 3236
[ci:skip-build]: already built successfully in CI

Fill out makedepends, so pmbootstrap and bpo know that these packages
need to be built before building postmarketos-cros-common, because it
has subpackages depending on these packages. Without this,
bootstrapping v24.12 currently fails:
https://builds.sr.ht/~postmarketos/job/1381582

This is intended behavior, abuild works the same way:
https://gitlab.alpinelinux.org/alpine/abuild/-/issues/10138

[ci:skip-build]: already built successfully in CI

Willow Barraco authored 4 months ago and Oliver Smith committed 4 months ago

[ci:skip-build]: Oliver verified locally that it builds

[ci:skip-build]: already built successfully in CI

This is a generic kernel for qcom laptops (sc8280xp & x1e), meant to
replace the lenovo-21bx kernel for the x13s.

- Uses johan_defconfig as base, and includes Minecrell's pmos.config
- Adds some extra kconfig for supporting virtualization

Maarten van Gompel authored 4 months ago and Clayton Craft committed 4 months ago

[ci:skip-build]: already built successfully in CI

sicelo authored 4 months ago and Oliver Smith committed 4 months ago

As of upower 1.90.5, it is possible to configure upower to not take an action
when the battery capacity is reported as critically low. Since the Nokia N900
now monitors its battery capacity using udev scripts, which is more accurate
than upower's calculation, enable the new ignore feature for the N900.

sicelo authored 4 months ago and Oliver Smith committed 4 months ago

The bq27200 fuel gauge depends on its battery-backed memory for capacity
reporting. If the supply is off for some time, the fuel gauge's last known
capacity is reset, after which a capacity value can only be read after a
full charge cycle. Thus, most of the time, as used on the Nokia N900, the
reported percentage cannot be relied on for making power-off decisions on
battery low conditions, e.g. through UPower.

However the fuel gauge can very accurately detect and report a low battery
condition internally, even if the reported capacity is incorrect, e.g. when
it has been reset. The low battery condition is reported by the kernel via
capacity_level in sysfs, and also generates uevents.

So we can implement safe battery shutdown by requesting the kernel to more
regularly polling for status changes, then performing an immediate shutdown
when the capacity_level is reported as Low and the device is not charging.

sicelo authored 4 months ago and Oliver Smith committed 4 months ago

pmos now defaults to droid sans font

sicelo authored 4 months ago and Oliver Smith committed 4 months ago

Do not duplicate udev rules that are also shipped by upstream

sicelo authored 4 months ago and Oliver Smith committed 4 months ago

The deviceprofile is now in a tagged sxmo release.

The conky issue will be mentioned in wiki for users to manually disable, until
upstream allows toggling it.

Caleb Connolly authored 4 months ago and Pablo Correa Gomez committed 4 months ago

It's possible that additional sources have been made to an APKBUILD
which are unstaged, but if the hunks adding those sources haven't been
staged either then it doesn't make sense to fail on this.

Use git show to get only the staged hunks for the APKBUILD.

Signed-off-by: Caleb Connolly <caleb@postmarketos.org>

Fix the following error during "pmbootstrap install":

  ERROR: unable to select packages:
    sudo-1.9.16_p1-r1:
      conflicts: doas-sudo-shim-0.1.1-r1[cmd:sudo=1.9.16_p1-r1]
      breaks: doas-sudo-shim-0.1.1-r1[!sudo]
      satisfies: postmarketos-base-38-r0[sudo-virt]
                 postmarketos-base-nofde-38-r0[sudo-virt]
    doas-sudo-shim-0.1.1-r1:
      conflicts: sudo-1.9.16_p1-r1[cmd:sudo=0.1.1-r1]
      satisfies: postmarketos-base-doas-38-r0[doas-sudo-shim]
                 postmarketos-base-38-r0[sudo-virt]
                 postmarketos-base-nofde-38-r0[sudo-virt]

How the error gets triggered:
* postmarketos-base depends on sudo-virt. During "pmbootstrap install",
  pmbootstrap has to resolve this to a sudo implementation (sudo, doas,
  ...).
* pmbootstrap does this by looking at the packages that get installed
  at the same time. Before this patch we did not install doas-sudo-shim
  directly through _pmb_recommends, only indirectly through a
  postmarketos-base-doas subpackage that pulls doas-sudo-shim in via
  install_if.
* pmbootstrap cannot look at install_if as it resolves dependencies,
  so it has to pick one and goes for "sudo".
* pmbootstrap tells apk to install a list of packages including "sudo",
  and because apk also resolves install_if correctly, the solver fails
  at the conflict between "doas-sudo-shim" and "sudo". (This only fails
  since apk-tools-static 2.14.6-r0, apparently beforehand apk just
  installed "doas-sudo-shim" in this scenario.)

Teaching pmbootstrap to look at install_if while resolving packages
would be one way to fix this. But it would be a lot of effort, not
feasible to quickly stop the problem at hand that breaks "pmbootstrap
install" for all edge installs. IMHO it is not worth implementing this
at all in pmbootstrap, as it is just supposed to do some more or less
basic package resolving until apk takes over and does it properly.

Put doas-sudo-shim in _pmb_recommends so pmbootstrap knows that this is
the sudo implementation we want without looking at install_if.

Remove the now obsolete postmarketos-base-doas subpackage. This will
lead to doas-sudo-shim getting removed for old installations on upgrade,
but it can easily be installed back (doas add doas-sudo-shim). I'll make
an edge post about it and put it in the v24.12 release notes. If we
don't remove it here, we would need to keep this legacy subpackage
around forever and I'd rather avoid that to reduce maintenance effort.

Another alternative to this was removing sudo-virt from depends="". But
that would lead to sudo getting uninstalled for users upgrading from
old releases from before we had doas in pmb_recommends, so I've decided
against it.

Fixes: pmaports issue 3340

dabao1955 authored 4 months ago and Newbyte committed 4 months ago

[ci:skip-build]: already built successfully in CI

Daniel Langbein authored 4 months ago and Robert Eckelmann committed 4 months ago

Inspired by the Alpine aports README: https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/README.md?ref_type=heads



Co-authored-by: Clayton Craft <craftyguy@postmarketos.org>

Richard Acayan authored 4 months ago and Alexey Minnekhanov committed 4 months ago

The Google Pixel 3a automatically appends console=null to the command
line. In the kernel, the preferred console is set to ttynull. Since
ttynull is not automatically enabled, a warning is currently emitted:

	[    0.909853] Warning: unable to open an initial console.

This also causes stdin, stdout, and stderr to be missing from the init
process.

In the busybox implementation, syslogd creates the /dev/log socket and
opens /dev/kmsg. This happens just before daemonizing, which opens
/dev/null and aliases stdin, stdout, and stderr to it. After daemonizing
and potentially closing the socket, stdin is aliased to the socket to
save stack memory. If the program starts without stdin under Linux, the
socket gains the constant STDIN_FILENO file descriptor, which is cleared
when daemonizing.

Syscalls when the 0, 1, 2 file descriptors aren't open:

	socket(AF_UNIX, SOCK_DGRAM, 0)    = 0
	openat(AT_FDCWD, "/dev/kmsg", O_WRONLY|O_LARGEFILE) = 1
	openat(AT_FDCWD, "/dev/null", O_RDWR|O_LARGEFILE) = 2

Enable the CONFIG_NULL_TTY option and update the configuration to allow
the kernel to open stdin, stdout, and stderr for the init and (by
inheritance) syslogd processes. It's technically an expert option but
isn't enabled by default (and can be enabled in config fragments).

Closes #3269
[ci:skip-build]: already built successfully in CI

Jakko authored 4 months ago and Newbyte committed 4 months ago

The main goal of switching LightDM to slick-greeter is to ease
enabling/disabling autologin. With "lightdm-settings" installed, there
is an administration/settings GUI "Login Window" available that allows
among others to configure autologin. Contrary to its general purpose
name, it works on LightDM greeter "slick-greeter" only.

[ci:skip-build]: already built successfully in CI