This package has been upstreamed to Alpine.

This package has been upstreamed to Alpine.

Missed the x86 version with the last commit.

This uses resource groups in gitlab CI to limit the cross arch build
test jobs to only allow one at a time.

This is a workaround for
postmarketOS/postmarketos#83

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

(cherry picked from commit 0eaba406)

Casey authored 3 months ago and Oliver Smith committed 2 months ago

when stdin is /dev/null (e.g. when console=null is on the kernel
cmdline) syslogd will call read() over and over and never handle the
SIGTERM we send it, pinning a CPU core on every boot.

Hooking up syslogd std I/O to /dev/zero prevents this.

Co-authored-by: Richard Acayan <mailingradian@gmail.com>
Co-authored-by: Clayton Craft <clayton@craftyguy.net>
[ci:skip-build]: already built successfully in CI

(cherry picked from commit 4b367a43)

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

(cherry picked from commit 71d0b5d3)

Jan Jasper de Kroon authored 3 months ago and Oliver Smith committed 3 months ago

Enable CONFIG_LEDS_GROUP_MULTICOLOR as a module to fix issue #3424.
Previously, notifications triggered the torch flash instead of the
status indicator LED. This change allows proper use of the multicolor
LED driver, ensuring notifications utilize the status indicator LED.

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

(cherry picked from commit fb0be371)

Done with:
  $ pmbootstrap --offline aportgen grub-efi-x86

Johannes Krampf authored 3 months ago and Newbyte committed 3 months ago

Fixes #3414.

The package `device-pine64-pinephone-vccq-mod` installs a u-boot user script.
The user script was loaded at address 0x50700000 partially overwriting
the initramfs (0x4FF00000-0x50883fd1), and causing a boot loop.

The user script load address was increased to 0x50f00000, leaving 16MB
of free space for the initramfs, the current initramfs size is 9.52MB.

Tested: Build and install package on Pinephone 1.2a running PMOS 24.12.
[ci:skip-build]: already built successfully in CI

(cherry picked from commit 8e0a56fd)

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

Somehow enabling in-kernel PD mapper (introduced in 5b9f51b200dcb
"remoteproc: qcom: enable in-kernel PD mapper"), breaks the bottom mic
on xiaomi-beryllium (Poco F1) and distorts audio on OP6 (and possibly
OP6T). Temporarily disable it and log the rprocs in use until we better
understand what causes the issue.

Link: #3353
Link: #3320
Link: #3245
Link: #3253

Signed-off-by: Frank Oltmanns <frank@oltmanns.dev>
[ci:skip-build]: already built successfully in CI
(cherry picked from commit 399121b8)

boot-deploy uses 'local', which technically isn't POSIX-compliant
and if someone has 'sh' from something else that strictly adheres to
POSIX then boot-deploy will fail.
This is a workaround for boot-deploy#38

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

(cherry picked from commit dcc52796)

Anjan Momi authored 4 months ago and Oliver Smith committed 3 months ago

closes #3386

Needed to fix eduroam iwd on qcom laptots. This config option used to be enabled on v24.06.
[ci:skip-build]: already built successfully in CI

(cherry picked from commit c31bc1a1)

fixes #3384

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

(cherry picked from commit 3d1f84a2)

Allows using allwinner devices with usb devices that implement ACM (3d
printers, serial things, etc)

(cherry picked from commit ec7a77f7)

Richard Acayan authored 4 months ago and Oliver Smith committed 4 months ago

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

(cherry picked from commit dda11062)

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

The xdefaults file is not i3wm-specific, but can be used with any X11 UI the
user may want to try

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

(cherry picked from commit f5b44733)

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

lock.sh is only reliable when used with i3wm, where we disable gpio_keys from
being handled by X/i3wm. When this is not done (e.g. when testing a different
X11 UI), the script becomes unreliable since the display turns on due to the
SCREENLOCK key being toggled, and therefore only the display=on case is ever
run.

Improve reliability of the script by basing the decision making on the
enabled/disabled state of the touchscreen instead.

(cherry picked from commit 86fb190a)

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

Current pinephone images built pmbootstrap >= 3.0.0 don't boot on the
pinephone anymore. At least part of this must be the switch from GPT to
MBR that has been done by default in pmbootstrap. Set msdos explicitly
to revert this for the pinephone.

With Tow-Boot we could probably use GPT instead, but this should be a
well-tested, concious decision. Let's fix this regression first.

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

(cherry picked from commit ad0d82fb)

Raymond Hackley authored 4 months ago and Oliver Smith committed 4 months ago

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

(cherry picked from commit b4f94a46)

Raymond Hackley authored 1 year ago and Newbyte committed 4 months ago

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

(cherry picked from commit 3d7ac0d5)

Raymond Hackley authored 4 months ago and Newbyte committed 4 months ago

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)

(cherry picked from commit 660518e1)

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

With AES built as a module, it is not possible to unlock the rootfs, at least
on the Nokia N900.

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

(cherry picked from commit a092ed54)

[ci:skip-vercheck], [ci:skip-build]: moving devices

(cherry picked from commit 0260dfaa)

(cherry picked from commit 230d684e)

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

Added a config file to /etc/unl0kr.conf.d/ to fix issue with unl0kr
being invisible during boot.

Commit-Msg-Tweaked-By: Oliver Smith <ollieparanoid@postmarketos.org>
(cherry picked from commit aa7eb4ed)

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

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

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

(cherry picked from commit f261f55e)

Fiona Klute authored 4 months ago and Clayton Craft committed 4 months ago

/usr/lib/NetworkManager/dispatcher.d/50-tethering.sh had a typo in the
"killall" command in the "disable_tethering" function, leading to it
never stopping any unudhcpd process. As a new instance is started each
time a USB cable is connected, so the number of instances kept growing
until reboot. Fix the typo so any old unudhcpd instance is actually
stopped before starting a new one.

To illustrate the bug, a sample with an uptime of 4 days:

$ ps w | grep unudhcpd
 2467 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
 5009 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
 5525 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
 6360 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
 7271 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
 9356 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
11045 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
14779 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
15696 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
17454 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
19119 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
24729 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
25565 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
25691 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
27417 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
30649 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
31690 root      0:00 unudhcpd -i usb0 -s 172.16.42.1 -c 172.16.42.2
[ci:skip-build]: already built successfully in CI

(cherry picked from commit 1b83a764)

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

* reduce op6 default earpiece volume
* add symlinks to enable audio when booting with u-boot

Signed-off-by: Caleb Connolly <caleb@postmarketos.org>
(cherry picked from commit 3becd343)

Related: https://fosstodon.org/@postmarketOS/113624366198561582

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

(cherry picked from commit e195bc11)

Fix the bug that prevented "pmbootstrap install" from working with
postmarketos-ui-gnome (not -mobile).

This bug has been here in pmaports for a long time, but until recent
changes in apk's resolver code, this did not fail (apk installed
gnome-extensions-app instead of gnome-mobile-extensions-app in that
scenario).

How it happened:
* postmarketos-ui-gnome has _pmb_recommends="gnome-extensions-app".
* pmbootstrap: pmb.install._install.get_recommends() works like this:
  1. Look at the packages i in _pmb_recommends of the packages that
     will be installed in "pmbootstrap install".
  2. For each package j in _pmb_recommends of i:
    2.1 Add all packages in j's _pmb_recommends to the list of
        packages to be installed.
    (2.2 Recurse by doing 1. with each package in j's _pmb_recommends.)
* In step 2:
  * pmaports doesn't have a gnome-extensions-app (it's in Alpine, a
    subpackage of gnome-shell).
  * Therefore our gnome-shell-mobile fork gets looked at, which has a
    gnome-mobile-extensions-app subpackage that provides
    gnome-extensions-app.
  * pmbootstrap looks at the _pmb_recommends of the gnome-shell-mobile
    package, which has "gnome-mobile-extensions-app" (this is wrong,
    it should be in postmarektos-ui-gnome-mobile instead and this patch
    fixes this!).
  * pmbootstrap adds the "gnome-mobile-extensions-app" to the list of
    packages to be installed.
* The result is an "apk add" line that has "postmarketos-ui-gnome" and
  "gnome-mobile-extensions-app" (and more packages), which results in a
  conflict betwen gnome and gnome-mobile packages.

Fixes: issue 3360
[ci:skip-vercheck]: _pmb_recommends changes don't need package rebuilds
[ci:skip-build]: already built successfully in CI

(cherry picked from commit 22087e93)

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

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

(cherry picked from commit 52f58a9c)

Ferass El Hafidi authored 4 months ago and Oliver Smith committed 4 months ago

lafrite has u-boot in SPI already

it also prevents lafrite from booting because pmbootstrap uses GPT partitioning now.

Signed-off-by: Ferass El Hafidi <funderscore@postmarketos.org>
(cherry picked from commit cd1599ba)

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

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

(cherry picked from commit 948ed6c7)

Ferass El Hafidi authored 4 months ago and Newbyte 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>
(cherry picked from commit 05d9b256)

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

(cherry picked from commit 0431845a)