handy-dandy post at the top of the forum says we should change keyboard layout.
Doesn't say how.

(my preference would be for a command-line method)

This thread is to post that, in my experience, migrating from the default Debian to Devuan works without issue. I will note that you need to use Devuan ASCII, Beowulf will not let you upgrade properly. I have not extensively gone through to test features, I will post if I run into any issues.

Steps:
1. Install sysv init system
2. Reboot
3. Install WICD (this is temporary, and unnecessary if you know how to use wpa_supplicant)
4. Stop NetworkManager, and start WICD (or wpa and dhcpcd)
5. Change /etc/apt/sources.list from the default debian repo to deb.devuan.org/merged and change Jessie to ASCII
6. Purge systemd (this will also remove mate, lightdm, and networkmanager)
7. Apt update and install devuan keyring, by running 'apt-get --allow-unauthenticated' (there must be a better way to do this, but I don't know it)
8. Apt upgrade
9. Install NetworkManager, lightdm, eudev, elogind, and whatever de or wm you want

I just received my pb64 and liking it so far. When signing into chrome to sync my accounts I noticed that after I sign into my first about then go into settings to add another the aw snap page pops up. I checked that my internet was connected and confirmed it while a previous page was loading without issue but the settings page keeps going to the error screen. Not sure what's happening, does anyone running the default Debian that has signed into their Gmail can you go to settings and see if it happens to you and report back? At least I'll know if it's a bug or just me.

Currently I am using the default debian image provided by @Mrfixit2001 . It seems to me, that the image, as every other downloadable image from the download section, contains a lot of modifications and extensions to the standard kernel and drivers. I  am wondering if I have to stick to these customized images for the lifetime of the PBP.  Are there plans to propagate these modifications to the standard debian repositories? Are there plans to create a PBP (or pine64) specific distro, like Raspbian for the rpi. As I am new to this, can anyone explain to me, how FOSS OS development generally happens and how it will be in this specific case.

I am interested in setting up a build environment for pinephone. I plan on using Manjaro/Arch. I'm thinking it would be nice to be able to build packages either from AUR or just source on a faster CPU.

I'm not sure the best way to set this up. I was thinking qemu but i have had no luck getting qemu-system-aarch64 to boot anything. Obviously i'm doing something wrong. What's a good guide on running say Arch arm using qemu?

I've tried just issuing this command

sudo qemu-system-aarch64 -machine virt -machine type=virt -m 2048 -cpu cortex-a57 Manjaro-ARM-plasma-mobile-pinephone-alpha2.img

is there another machine/type/cpu i should specify. All i get is a black screen with a qemu prompt. Maybe i need to specify other devices? Maybe i need to extract the image somehow and specify the kernel separately?

The other thing i thought of was using a chroot but that would not work since the host and target do not share the same architecture correct?

any help/kick in the right direction would be appreciated.

Hi there, first post here, so any recommendations are more than welcomed.

0. Context

I wanted a home server as minimalist as possible, to lower the maintenance burden, so I bought the RockPro64 and it arrived January 20th.

We use Kubernetes at work so I wanted something similar that is easy to operate and maintain. I found k3os a Linux distro that it's single purpose is to run Kubernetes. This will allow me to focus on deploying the Helm charts we need at home and keeping the data safe (redundancy, backups ...).

I open the thread to share my experience as I go through the process of getting everything up and running.

1. Installing k3os

As far as I understand the RockPro64 cannot be run using the upstream kernel (please correct me if I'm wrong.). So I decided to look for a distro that supported Docker out of the box (just in case). Thanks to @ayufan, there is a Ubuntu (Bionic) image with Docker support available here. So I decided to test it, burning it into the eMMC (the microsd card boots too).

Hello!
I just got my Pinebook Pro (ANSI) a couple of days ago.
I tried a few of the various OS images out there, and was really impressed with the performance.

I do like to run ArchLinux on my machines though, and since I am relatively new to the ARM architecture, I felt like I owed it to myself to at least try and get arch running on my pinebook pro!



Below is the process I used. There's probably a better way of going about this, but like I said, this is my first attempt at bringing arch up to an unsupported device.


1) Environment Setup

Boot from your SD card to any Manjaro image (I used the Manjaro XFCE one).

Hey all, I've just got Android 9 on my rock64 v2 up and running via burning it to sdcard. For some reason the 32gb img didn't agree with the board...

Anyway, is there perhaps a tutorial somewhere about getting Google services and stuff into the ROM?

Sent from my Pixel 3 XL using Tapatalk

I'm a but stuck at the moment, wifi at work uses a captive portal to signin (or onboard to BYOD).

After some google-research, it looks like I need to do something with resolvconf but at present this is missing on my machine.
Did the trick with networkmanager & creating some [connectivity] settings... but no luck.

Any idea how to fix this?

Hello,

I am left-handed and an old-time Linux user.

As a left-handed, I'd like to switch primary and secondary button.

As an old Linux user, I'd like to have the select on single-finger double tap and paste on double -finger tap. The default configuration seems to link the single-finger tap and the double-finger tap to the primary button (button 1), and the triple-finger tap to the middle button (button 2). Once I invert primary and secondary buttons with