PINE64
Arch Linux ARM on PinePhone - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Arch Linux on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=159)
+---- Thread: Arch Linux ARM on PinePhone (/showthread.php?tid=10507)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

RE: Arch Linux ARM on PinePhone (2020/11/29) - antoyo - 12-07-2020

Hi.
I just installed ALARM on my PinePhone with this image and I wondered if full-disk encryption is supported.
If not, how can I build this image with encryption and what would it take to make it use osk-sdl ?
Thanks.

RE: Arch Linux ARM on PinePhone (2020/11/29) - Danct12 - 12-07-2020

(12-07-2020, 06:40 PM)antoyo Wrote: Hi.
I just installed ALARM on my PinePhone with this image and I wondered if full-disk encryption is supported.
If not, how can I build this image with encryption and what would it take to make it use osk-sdl ?
Thanks.

osk-sdl is currently WIP, I'm currently working on it.

RE: Arch Linux ARM on PinePhone (2020/11/29) - bcnaz - 12-08-2020

NOTE :

It appears the cellular modem wakes up MUCH faster from sleep state  if the wifi is turned off...

(Seems to me ? )

RE: Arch Linux ARM on PinePhone (2020/11/29) - dukla2000 - 12-10-2020

(06-30-2020, 08:08 PM)Danct12 Wrote: ...
What's not working (or not properly working)
  • You tell me.
...

20201204 f2fs version, up to date with pacman -Syu. Pretty sure this problem predates December though.

There is a sound "glitch" that stops playback when using lollypop: somehow mpv recovers. The irritating thing is it is not possible to listen to a long track using lollypop. The "glitch" happens at random positions in the same track - it seems more related to what the phone is doing rather than the demands of the track.

With lollypop:

Code:
$ lollypop night-raiders-22_10_2020-final.mp3
file:///home/alarm/Downloads/night-raiders-22_10_2020-final.mp3
[INFO] 2020-12-10 10:42:04 Scan started
[INFO] 2020-12-10 10:42:04 lollypop.collection_scanner::__get_objects_for_uris: execution time 0:0.008460
[INFO] 2020-12-10 10:42:04 lollypop.collection_scanner::__scan: execution time 0:0.382076
[INFO] 2020-12-10 10:42:05 Scan started
[INFO] 2020-12-10 10:42:05 lollypop.collection_scanner::__get_objects_for_uris: execution time 0:0.001318
[INFO] 2020-12-10 10:42:05 lollypop.collection_scanner::__scan: execution time 0:0.004950
[INFO] 2020-12-10 10:43:48 Player::_on_bus_error(): ../gst-plugins-good/ext/pulse/pulsesink.c(1750): gst_pulseringbuffer_commit (): /GstPlayBin:player/GstPlaySink:playsink/GstBin:abin/GstBin:bin0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse

This is the journal covering the above fail - I pressed the power key to get the screen active and:
Code:
Dec 10 10:43:43 dukla systemd-logind[3255]: Power key pressed.
Dec 10 10:43:43 dukla phoc[6091]: [backend/drm/drm.c:971] Skipping pageflip on output 'DSI-1'
Dec 10 10:43:43 dukla gnome-session[6107]: gnome-session-binary[6107]: WARNING: Could not get session path for session. Check that logind i>
Dec 10 10:43:43 dukla gnome-session-binary[6107]: WARNING: Could not get session path for session. Check that logind is properly installed >
Dec 10 10:43:48 dukla bluetoothd[3408]: Endpoint unregistered: sender=:1.812 path=/MediaEndpoint/A2DPSink/sbc
Dec 10 10:43:48 dukla bluetoothd[3408]: Endpoint unregistered: sender=:1.812 path=/MediaEndpoint/A2DPSource/sbc
Dec 10 10:43:48 dukla systemd[3398]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Dec 10 10:43:48 dukla systemd[3398]: pulseaudio.service: Failed with result 'signal'.
Dec 10 10:43:48 dukla systemd[3398]: pulseaudio.service: Scheduled restart job, restart counter is at 42.
Dec 10 10:43:48 dukla systemd[3398]: Stopped Sound Service.


With mpv:
Code:
$ mpv night-raiders-22_10_2020-final.mp3
[ffmpeg/demuxer] mp3: Estimating duration from bitrate, this may be inaccurate
(+) Audio --aid=1 (mp3 2ch 44100Hz)
File tags:
Artist: Bruce Crompton
Album: Amazing War Stories with Bruce Crompton
Date: 2020
Genre: Podcast
Title: The Night Raiders of Normandy
AO: [pulse] 44100Hz stereo 2ch float
A: 00:00:14 / 00:36:48 (1%)
[ao/pulse] pa_stream_cork() failed: Connection terminated
[ao/pulse] pa_stream_flush() failed: Connection terminated
Audio device underrun detected.
[ao/pulse] pa_stream_get_latency() failed: Connection terminated
[ao/pulse] pa_stream_get_latency() failed: Connection terminated
A: 00:00:14 / 00:36:48 (1%)
[ao/pulse] pa_stream_cork() failed: Connection terminated
[ao/pulse] pa_stream_flush() failed: Connection terminated
AO: [pulse] 44100Hz stereo 2ch float
A: 00:00:16 / 00:36:48 (1%)
[ao/pulse] pa_stream_cork() failed: Connection terminated
[ao/pulse] pa_stream_flush() failed: Connection terminated
Audio device underrun detected.
[ao/pulse] pa_stream_get_latency() failed: Connection terminated
[ao/pulse] pa_stream_get_latency() failed: Connection terminated
A: 00:00:16 / 00:36:48 (1%)
[ao/pulse] pa_stream_cork() failed: Connection terminated
[ao/pulse] pa_stream_flush() failed: Connection terminated
AO: [pulse] 44100Hz stereo 2ch float
A: 00:00:28 / 00:36:48 (1%)
mpv hiccups at each of the "glitches" but recovers/continues OK.

I can try dig out extra info if required but it sems to me pretty easy to replicate.

RE: Arch Linux ARM on PinePhone (2020/11/29) - moodroid - 12-13-2020

Hi,

I'm on the 20201204 image, and while I don't have any issues, LF had reported good success after updating to 2020/12/05. So, I've tried 'sudo pacman -Syu 2020/12/05', and after saying a few package are up to date, it errors with 'database not found: 2020'. Apologies if it's a stupid question, as I'm not a Linux expert by any means, and have never even used Arch before, but it's the one that works best for me so far.

Thanks,

Edit: I think I realised now that you can't 'sudo pacman -Syu' to a particular date, and LF was just saying that he'd done it on that date. So it's all or nothing, right?

RE: Arch Linux ARM on PinePhone (2020/11/29) - Lousy Fisherman - 12-13-2020

Actually you can roll forward and back if you configure pacman to use the cache. I believe (check this) the default is to store the files from the last update. So , if I am correct, run the standard all or nothing update, if you have problems you can revert to the original state before you started. I have done this more than once on my QA card.  Tongue

See https://wiki.archlinux.org/index.php/Downgrading_Packages

HTH
LF

RE: Arch Linux ARM on PinePhone (2020/11/29) - moodroid - 12-13-2020

(12-13-2020, 10:27 AM)Lousy Fisherman Wrote: Actually you can roll forward and back if you configure pacman to use the cache. I believe (check this) the default is to store the files from the last update. So , if I am correct, run the standard all or nothing update, if you have problems you can revert to the original state before you started. I have done this more than once on my QA card.  Tongue

See https://wiki.archlinux.org/index.php/Downgrading_Packages

HTH
LF
Thanks

RE: Arch Linux ARM on PinePhone (2020/11/29) - dukla2000 - 12-13-2020

I cant get megapixels to work anymore. Is it just me (completely up to date pacman -Syu) or has the device numbering changed with a recent kernel update?

Code:
alarm@dukla:~$ dmesg | grep video
[    0.102580] videodev: Linux video capture interface: v2.00
[    0.725833] cedrus 1c0e000.video-codec: Device registered as /dev/video0
alarm@dukla:~$ 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
Could not open /dev/video1


RE: Arch Linux ARM on PinePhone (2020/11/29) - Danct12 - 12-14-2020

(12-13-2020, 02:57 PM)dukla2000 Wrote: I cant get megapixels to work anymore. Is it just me (completely up to date pacman -Syu) or has the device numbering changed with a recent kernel update?

Code:
alarm@dukla:~$ dmesg | grep video
[    0.102580] videodev: Linux video capture interface: v2.00
[    0.725833] cedrus 1c0e000.video-codec: Device registered as /dev/video0
alarm@dukla:~$ 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
Could not open /dev/video1


That's weird, camera still works with 5.9.14-2

Can you please reboot and dump dmesg to paste.ubuntu.com?

RE: Arch Linux ARM on PinePhone (2020/11/29) - dukla2000 - 12-15-2020

(12-14-2020, 08:51 PM)Danct12 Wrote:
(12-13-2020, 02:57 PM)dukla2000 Wrote: I cant get megapixels to work anymore. Is it just me (completely up to date pacman -Syu) or has the device numbering changed with a recent kernel update?

Code:
alarm@dukla:~$ dmesg | grep video
[    0.102580] videodev: Linux video capture interface: v2.00
[    0.725833] cedrus 1c0e000.video-codec: Device registered as /dev/video0
alarm@dukla:~$ 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
Could not open /dev/video1


That's weird, camera still works with 5.9.14-2

Can you please reboot and dump dmesg to paste.ubuntu.com?

Done - I put a month expiry on it to try be a good citizen so anyone reading this thread after Jan 2021 it is to be expected it is no longer there!

I also had a thought overnight that there should be something about the cameras in the log - at 9.5s I can see links but for sure more is missing. In parallel I will try another release via the SDcard - it may be I borked the camera connections when installing the 1.2b board.

p.s. a boot of Mobian from the SDcard gets at least the rear camera working fine in Megapixels.