in reply to this object

Just removed /etc/systemd/user/udiskie.service on my . Thanks to @fossdd@chaos.social for merging the MR to !

allows to have multiple users. If automatic login is disabled on start a login screen is shown presented by typically running as the system user greetd.

greetd is logged in automatically to do its magic and systemd starts all the configured user services for that user.

is integrated as such a service and mounts all removable media to /run/media/greetd - on my the sdcard.

After logging in the greetd user session is logout out and the new session for the authenticated user is started. udiskie for the greetd session is stopped leaving the sdcard mounted to the path for greetd.

udiskie starts for the authenticated user, but does not mount the removable media, because it is already mounted for the former logged in greetd.

No music in 🤷

An easy way around this is to change the service file for udiskie to the new version from the example directory of udiskies repository by copying it to /etc/systemd/user/.

Once systemd picked up the changes udiskie will not be started for system users anymore and systemd will run udiskie-umount after stopping the service on user logout.

Now one UserA can logout and UserB can use the same sdcard if file permissions allow.

: @okias@floss.social is doing a lot work to mainstream patches to the kernel. During a meeting of Phosh.mobi e.V. members I learned that there seem to be not many testers for . I still had a broken Axolotl sitting on my desk…

  • repaired the phone that originally had been bought as part of a deal
    • cleaning inside (residue from water contact)
    • new display (two lines of broken pixels)
    • new usb-c pcb (didn't charge, data broke during testing)
  • learned about edl to recover if phone wouldn't boot to fastboot anymore (yes, really had that situation later 😉)
  • learned about the difference of fastboot and fastbootd mode
  • learned about u-boot and the boot chain on the phone
  • learned about dynamic partitions used in Android and how to use them from
  • learned about pmbootstrap
    • to build my own device images (mixture of existing axolotl and sdm845 to be compatible to the phone and the usage with u-boot and dynamic partitions)
    • changed pmbootstrap to build small (92M) boot image for boot_a/b partition
  • tried to get more space for out of the phone for boot & root than provided by boot_a/b and system_a/b
    • resized userdata of Android
    • created two additional partitions for postmarketOS
  • learned how to recover from kernel not booting without re-flashing
    • u-boot usb mass storage mode exports the mass storage of the phone over usb-c
    • phone connected to an aarch64 system ( running )
    • mounting encrypted partition, boot and what-else is needed
    • installing kernel packages via apk while in chroot on Librem5
  • learned how to compile a kernel using ./envkernel.sh and pmbootstrap

Now I'm quite sure I can recover from any failure I will encounter while testing sdm845 kernels and I have the following setup on my Shift6mq:

  • ShiftOS-L with small userdata partition in slot_b
    • applications for demoing the phone installed
    • work profile to contain closed source applications
  • postmarketOS edge installed on partitions behind userdata
    • u-boot on rescue_a
    • 1GB pmOS_boot
    • 60GB pmOS_root
    • applications for demoing
    • multi-user: my testing user, demo user
    • everything except cameras work
  • dual-boot possible on-the-go: enter fastboot (by holding vol-up at start), change slot, reboot

I put my notes on the postmarketOS wiki.

I started two merge requests:

I'll carry the phone at - Chemnitzer Linux Tage 2026 - on saturday 28th this month. I'll mostly be around the "Linux on Mobile" booth.