Arch Linux ARM on PinePhone

[User 20385]

Hi there,
i am using archlinux on my latitude an i love the "rolling releases" and using brand new versions of packages.

And that is why i love your images, too.

But in order to use it as a daily driver in future, i would love to do a full disk encrytion on emmc ... How to archive that?


Regards,
Andreas

[antoyo]

Hi there,
i am using archlinux on my latitude an i love the "rolling releases" and using brand new versions of packages.

And that is why i love your images, too.

But in order to use it as a daily driver in future, i would love to do a full disk encrytion on emmc ... How to archive that?


Regards,
Andreas

This is work in progress: https://forum.pine64.org/showthread.php?...9#pid85349

[dukla2000]

Did my periodic rebuild today - lovely to come across 2021.01.24 build. And enjoy auto screen rotation etc.

A problem'ette with megapixels - it crashes when you take a picture:

Code:

$ megapixels
Found config file at /usr/share/megapixels/config/pine64,pinephone-1.2.ini
Adding camera rear from config
Adding camera front from config
Found postprocessor script at /usr/share/megapixels/postprocess.sh
/tmp/megapixels.kEzRF8/0.dng: Failed to allocate memory for custom tag binary object (-610603544 elements of 1 bytes each).
TIFF version 20191103
megapixels: tif_dirwrite.c:3071: TIFFWriteDirectoryTagData: Assertion `datalength<0x80000000UL' failed.
Aborted (core dumped)
[alarm@duklaPP ~]$

I am not sure what I can do to allow it to allocate memory?

[vkraven]

Did my periodic rebuild today - lovely to come across 2021.01.24 build. And enjoy auto screen rotation etc.

A problem'ette with megapixels - it crashes when you take a picture:

Code:

$ megapixels
Found config file at /usr/share/megapixels/config/pine64,pinephone-1.2.ini
Adding camera rear from config
Adding camera front from config
Found postprocessor script at /usr/share/megapixels/postprocess.sh
/tmp/megapixels.kEzRF8/0.dng: Failed to allocate memory for custom tag binary object (-610603544 elements of 1 bytes each).
TIFF version 20191103
megapixels: tif_dirwrite.c:3071: TIFFWriteDirectoryTagData: Assertion `datalength<0x80000000UL' failed.
Aborted (core dumped)
[alarm@duklaPP ~]$

I am not sure what I can do to allow it to allocate memory?

I encountered this problem today too. Saw this recently opened issue https://github.com/dreemurrs-embedded/Pi...issues/126 , looks like a problem with libtiff. 

I'm sure it's being repackaged as we speak, but in the meantime, I worked around it by removing megapixels from pacman and building it straight from upstream https://git.sr.ht/~martijnbraam/megapixels . It compiles and runs fine with the libtiff shipped in 2021.01.24.

[User 20385]

Hi there,
i am using archlinux on my latitude an i love the "rolling releases" and using brand new versions of packages.

And that is why i love your images, too.

But in order to use it as a daily driver in future, i would love to do a full disk encrytion on emmc ... How to archive that?


Regards,
Andreas

This is work in progress: https://forum.pine64.org/showthread.php?...9#pid85349

This has just been released: https://github.com/dreemurrs-embedded/ar...-installer


AND IT WORKS LIKE A CHARM - GREAT JOB ...

[p1trson]

Latest release, updated via pacman, Geary crashes when launched and choosing "Other email providers" with:

Code:

*[wrn] 19:57:04.0998 [no domain]:Error loading plugin: libnuspell.so.4: cannot open shared object file: No such file or directory

*[wrn] 19:57:04.0999 [no domain]:Error loading plugin: libvoikko.so.1: cannot open shared object file: No such file or directory

*[wrn] 19:57:05.0000 [no domain]:Error loading plugin: libaspell.so.15: cannot open shared object file: No such file or directory

*[wrn] 19:57:05.0001 [no domain]:Error loading plugin: libhspell.so.0: cannot open shared object file: No such file or directory

*[wrn] 19:57:05.0002 [no domain]:Error loading plugin: libhunspell-1.7.so.0: cannot open shared object file: No such file or directory

*[wrn] 19:57:05.0024 [no domain]:Error loading plugin: libnuspell.so.4: cannot open shared object file: No such file or directory

*[wrn] 19:57:05.0025 [no domain]:Error loading plugin: libvoikko.so.1: cannot open shared object file: No such file or directory

*[wrn] 19:57:05.0026 [no domain]:Error loading plugin: libaspell.so.15: cannot open shared object file: No such file or directory

*[wrn] 19:57:05.0027 [no domain]:Error loading plugin: libhspell.so.0: cannot open shared object file: No such file or directory

*[wrn] 19:57:05.0028 [no domain]:Error loading plugin: libhunspell-1.7.so.0: cannot open shared object file: No such file or directory

*[wrn] 19:57:05.0993 folks:backend-store.vala:435: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
![crt] 19:57:08.0938 GLib:Did not see expected message GLib-GObject-WARNING **: g_object_weak_unref: couldn't find weak ref *
![crt] 19:57:08.0939 geary:accounts_name_row_construct: assertion 'default_name != NULL' failed

EDIT: it actually crashes when choosing any of the options (google, yahoo, outlook, other ..)

[p1trson]

Additional info: the above problem is affecting geary-mobile only. standard geary doesn't suffer from this
another EDIT: uninstalling geary-mobile -> installing standard geary -> configuring account via standard geary -> uninstalling standard geary -> installing geary-mobile does the trick, since apparently settings are shared, meaning that after this, when launched the geary-mobile, my account enabled via standard geary was already available

[bvbfan]

I have a question, in Arch builds you use Gnome by default or only option?

[dukla2000]

I have a question, in Arch builds you use Gnome by default or only option?

Phosh is the default option. There is also a bare bones alternative.

[Juergen]

Incoming calls do work reliably now, this is really great!
Calls from the landline (FritzPhone) are always shown twice resp. several times in the "missed-calls-list".
No problems with incoming calls from other mobile phones.
Can anyone confirm?

EDIT:
Yesterday I flashed ArchLinux to the internal storage. Up to now, everything works perfectly.