Rework the messages and avoid re-spawning the splash on every check.
Additionally, add a call to check_keys, this lets users drop to a debug
shell or export logs to triage this failure (particularly useful for
hard-to-reproduce issues).

Finally, add a (liberal) 30 second timeout and dump logs at the end. If
we're just waiting for a device to show up and it doesn't after 30
seconds then it's probably never going to...

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

In mount_subpartition we currently try to look for the boot partition,
to see if we're done (either we aren't using subpartitions or we found
the right one). However it is possible that a device might have
originally used the subpartition scheme, but was later converted to have
a real boot partition (for EFI for example).

In this scenario, the boot partition would be found immediately, but the
root subpartition would not be.

Address this by making mount_subpartition check for success by calling
find_root_partition instead of find_boot_partition. For most
installations this has no impact.

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

This incorprates the debug-shell functionality directly into the
initramfs, so it's no longer necessary to build and boot a custom
initramfs in order to debug your device.

Additionally, the behaviour of the debug-shell is entirely reworked,
removing the telnet feature. Instead it creates an ACM serial gadget
which can be accessed via any normal terminal emulator (picocom,
minicom, etc; or PuTTY on windows). Rather than just invoking sh, the
debug-shell now creates a respawning getty on both the new virtual
console and the active console (this will either be the UART console
or tty0/1).

If fbkeyboard is available (it can be added by install
postmarketos-mkinitfs-hook-console-shell) then it will be launched on
tty0. A getty will also be launched on tty0 in this case even if it
otherwise wouldn't be (if the active console was the serial port for
example).

It is necessary to spawn these shells via getty since the logging rework
means we can no longer assume that stdin/out/err reference a TTY.

In addition to the above, it is now possible to trigger a log dump by
holding volume up during boot (if iskey is available). This can be
useful for helping users debug their devices if the issue doesn't result
in a failure that can be detected in the initramfs.

With these changes, the console-shell and debug-shell hook packages are
reduced to only adding the additional tools/features. console-shell is
still required for fbkeyboard, and debug-shell for the setup_usb_storage
tool.

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

iskey is a tiny tool that reports if any of the given keys are pressed.

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

This split is only to handle differing dependencies. At runtime the
initramfs should have a fall-back for when they're unavailable.

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

This step is the most likely to go wrong or have issues, and it has side
effects which can make it difficult to run multiple times on one boot.
Move it to after hooks so that e.g. when dropping to a debug shell, we
land before the first call.

This also makes booting to hooks a faster in many cases.

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

fallocate seems to cause some strange behaviour where the logs.img file
is treated like it's empty. Given it's small and in a ramdisk let's just
create it with dd instead.

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

This fixes the annoying "sh: write error" and "Couldn't write to clear
UDC" messages that happen on every single boot.

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

This variable is being used in more places, just make it global.

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

Rework logging to always log the initramfs output to the kernel
ringbuffer and deprecate PMOS_NO_OUTPUT_REDIRECT in favour of following
the kernel loglevel.

I know it seems silly to use syslogd for this, but it's necessary to
buffer writes to /dev/kmsg per-line if we want to correctly set the log
level, and "tee" does not do this (it will write multiple lines at once,
resulting in "<14>" prints in the ringbuffer). The main advantage to
this is that we won't have kernel logs cut in half by initramfs logs
anymore, everything will be nicely line buffered!

The previous logging solution of multiple "tail" commands would actually
fail to log up to the last few lines before a crash due to how tail
works (it polls the file and buffers lines).

I attempted something like this before, but I stopped after running into
ratelimiting issues. These are now resolved by configuring the
printk_devkmsg sysctl.

Dropping PMOS_NO_OUTPUT_REDIRECT:

The general motivations behind PMOS_NO_OUTPUT_REDIRECT was to avoid
cluttering up the console with initramfs logs when they aren't wanted;
this is now handled instead by the kernels logging facility. We log to
the ringbuffer at LOGLEVEL_INFO, so if "quiet" is specified on the
cmdline (or the loglevel is otherwise set above info) then initramfs
logs will also not be shown.

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

The previous name stopped being valid with the kernel 6.8 upgrade. This caused
ALSA to think a headset was connected, which in turn caused callaudiod to
select the Headphones port in the PA sink instead of Earpiece / Speaker.

I missed this in my own kernel upgrade testing because I use
a custom callaudiod that doesn't care about the headphones port.
I now confirmed the issue with regular callaudiod and that this change
fixes it.

Co-authored-by: Fiona Klute <fiona.klute@gmx.de>

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

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

Clayton Craft authored 1 year ago and Newbyte committed 1 year ago

- usbguard config: these are builtin USB devices that should be allowed
  by default

- removed nonfree-fw package, I decided that everything from that should
  be required since some fairly major features are broken without these
  firmwares and relevant userspace apps

- re-enabled EFI runtime services, so efifb is used (and probably other
  benefits?)
        - Laptops need the "Linux Boot" option enabled
        - "With recent UEFI firmware efi=noruntime can be left out when
          the Linux Boot option is enabled."
        - https://github.com/jhovold/linux/wiki/X13s#kernel-command-line
[ci:skip-build]: already built successfully in CI

Saalim Quadri authored 1 year ago and Robert Eckelmann committed 1 year ago

Signed-off-by: Saalim Quadri <danascape@gmail.com>

Clayton Craft authored 1 year ago and Robert Eckelmann committed 1 year ago

This subpackage now installs a file that was previously in the other
subpackage it is meant to replace, leading to upgrade conflicts that
have to be manually resolved (i.e. with apk fix)

Fixes: 126f4322 and 1712a2d0

Johannes Marbach authored 1 year ago and Clayton Craft committed 1 year ago

Co-authored-by: Newbyte <newbie13xd@gmail.com>

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

Doni Halim authored 1 year ago and Newbyte committed 1 year ago

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

Authorship of this commit was incorrectly reset when merging. As such,
it is being reverted to fix this problem.

This reverts commit fa68f4a9.

Authorship of this commit was incorrectly reset when merging. As such,
it is being reverted to fix this problem.

This reverts commit dc6dc897.

Authorship of this commit was incorrectly reset when merging. As such,
it is being reverted to fix this problem.

This reverts commit 6ac49408.

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

To get unl0kr working, add subpackage unl0kr for the quirk.

Brady Norander authored 1 year ago and Clayton Craft committed 1 year ago

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

This is used in the post-install script, so it's actually a dependency

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

sleirsgoevy authored 1 year ago and Newbyte committed 1 year ago

It seems that wireplumber is now installed by default, instead of pipewire-media-session. Thus we need to set api.alsa.headroom in wireplumber configuration too to get working audio.

This basically copies /usr/share/wireplumber/wireplumber.conf.d/alsa-vm.conf and relaxes the filters.
[ci:skip-build]: already built successfully in CI

Brady Norander authored 1 year ago and Newbyte committed 1 year ago

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

sicelo authored 1 year ago and Robert Eckelmann committed 1 year ago

Take screenshots in any x11 UI by depressing the camera key while keeping the
proximity sensor covered

This is a variation of [1] and [2] from postmarketOS/pmaports!4133.

[1] https://gitlab.com/postmarketOS/pmaports/-/merge_requests/4133/diffs?commit_id=35007eaefd0e471634c74aad9294234ceed260ae
[2] https://gitlab.com/postmarketOS/pmaports/-/merge_requests/4133/diffs?commit_id=0ef9ffe3928313b7afc5ce68ad0ec4487f1f2f11



Co-Authored-By: DvaMishkiLapa <thesame.personal@gmail.com>
Signed-off-By: Sicelo A. Mhlongo <absicsz@gmail.com>

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

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

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

exkc has stated that he cannot maintain the ports anymore,
see #postmarketos-devel discussion:

	<@f_[xmpp]> af2e02839bcfb0aae789a9ea66f63a: hiya, are you available?
	<@f_[xmpp]> It's about 2 of your Amlogic device ports. You said
	before that your beelink-gt1 and xiaomi-once were broken
	<@f_[xmpp]> are you still able to maintain these ports?
	<@f_[xmpp]> If not then they should probably be dropped.
	<af2e02839bcfb0aae789a9ea66f63a> drop them
	<@f_[xmpp]> af2e02839bcfb0aae789a9ea66f63a: sure

[ci:skip-vercheck]

Suggested-by: exkc <exxxxkc@getgoogleoff.me>
Signed-off-by: Ferass El Hafidi <funderscore@postmarketos.org>