Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,968
» Latest member: MichelleKonzack
» Forum threads: 16,334
» Forum posts: 117,438

Full Statistics

Latest Threads
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 166
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,705
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 256
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 118
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 216,981
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 210
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 298
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,086
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 939
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 605

 
Question PinePhone Build Environment
Posted by: grondinm - 01-21-2020, 12:21 PM - Forum: General Discussion on PinePhone - Replies (5)

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.


Big Grin k3os
Posted by: merquerio - 01-21-2020, 11:16 AM - Forum: Linux on RockPro64 - Replies (1)

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).

Code:
# Extract the image
unxz bionic-containers-rockpro64-0.9.16-1163-arm64.img.xz

# Burn the image to the eMMC
dd if=bionic-containers-rockpro64-0.9.16-1163-arm64.img of=/dev/sdc bs=10M

I don't have any external monitors, so SSH access was key for me. This image starts a SSH server that I found easily on my network (eth access).

Code:
# pass: rock64
ssh rock64@192.168.1.20

Once inside I tested that Docker was running correctly, that the PCIe Dual SATA-II Interface Card was correctly detected and that the 2x HDD 1TB drives were there. In fact I found out that one of the drives is dead (but replacement is on it's way). I prepared the drive, but I will go in more details as soon as I receive the replacement.

Getting k3os to work was surprisingly easy. They provide a takeover installation that works like a charm. First you need to create the configuration file `config.yaml` that will set all the necessary stuff for the host OS. In fact, all the host OS should be done here. The details about this file are available here. In my case, for now, mounting the HDD was enough.

Code:
ssh_authorized_keys:
 - "ssh-rsa <the content of your id_rsa.pub"
hostname: nucloud
write_files:
 - content: |-
     /dev/sda1      /var/k8s-storage      ext4    auto      0 0
   owner: root
   path: /etc/fstab
   permissions: '0644'
k3os:
 labels:
   whatever: you-want
 dns_nameservers:
   - 192.168.1.1 # update this to your local or public DNS server if needed
 ntp_servers:
   - hora.rediris.es
 password: <pass>
 token: <token>

Then we download the rootfs and place in the root of our fresh install:

Code:
curl -sfL https://github.com/rancher/k3os/releases/download/v0.8.0/k3os-rootfs-arm.tar.gz | tar zxvf - --strip-components=1 -C /
cp myconfig.yaml /k3os/system/config.yaml
sync
reboot -f

And now our system will boot into k3os. This method places k3OS on disk and also overwrites `/sbin/init`. On next reboot the bootloader and kernel should be loaded, but then when user space is to be initialized k3OS should take over.


2. Access the Kubernetes node

Now that we have our system up and running, further access to the RockPro64 is not mandatory. k3os install k3s, a kubernetes lightweight distribution, and from now on we can operate the single node "cluster" remotely. To gain access from your laptop/desktop using kubectl, you just need to copy the access credentials and add the to your `~/.kube/config`:

Code:
scp rancher@192.168.1.20:/etc/rancher/k3s/k3s.yaml .

# Edit your ~/.kube/config to add the content of k3s.yaml or extend your $KUBECONFIG:

mv k3s.yaml ~/.kube
echo "export KUBECONFIG=$KUBECONFIG:~/.config/kube/k3s.yaml" >> .bashrc


ø. (WIP)

- Launch all the Helm charts
- Encrypt local data.
- RAID (software?) vs LVM vs ZFS, suggestions are more than welcomed
- Backup data locally and to a remote node (encrypted)
- Provide DDNS access to the kubernetes ingress


  [GUIDE] ArchLinuxARM on Pinebook Pro
Posted by: hku2 - 01-21-2020, 10:13 AM - Forum: Pinebook Pro Tutorials - Replies (10)

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!

[Image: EOr8IRyWsAIhGG5?format=jpg]

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).

Code:
sudo -i
pacman -S arch-install-scripts

Next, get the Generic AArch64 ArchLinuxARM image from here.


2) Prepare the eMMC (or NVMe)

We will have to prepare our eMMC (or NVMe) for the installation.
I initially installed mine on an NVMe, but even though its power consumption was 2.5W, the maximum supported by the pinebook pro, it would keep crashing at peak draws from the drive, so I ended up installing to the emmc instead.
The following guide applies to the emmc, but if you're installing to an nvme, simply replace /dev/mmcblk2 with /dev/nvme0n1.

Code:
fdisk /dev/mmcblk2
g # to create a new GPT
n # to create a new partition
1 # partition mumber
65536 # as the starting sector (we will need this space to flash Uboot in)
<ENTER> # for the last sector (auto)
w # to write the changes to disk

# create a filesystem
mkfs.ext4 /dev/mmcblk2p1

# mount the partition
mount /dev/mmcblk2p1 /mnt

# extract the image to the mounted partition
bsdtar -xpf ArchLinuxARM-aarch64-latest.tar.gz -C /mnt

# generate the fstab entry for your emmc partition
genfstab -U /mnt >> /mnt/etc/fstab

# switch to the arch chroot
arch-chroot /mnt


3) Configure the installation

We will now need to configure the installation, and make some necessary changes to make it work with the pinebook pro's SoC.
For this, I have used the Manjaro packages for the kernel, uboot and wifi firmware.
I imagine these packages will soon be backported from manjaro to arch, although I am not quite sure how this process works.
If I am mistaken, and they do not make it to the arch repos, then I'll try and create AUR packages for them, so we can get updates.

Code:
# initialize the pacman keyring
pacman-key --init
pacman-key --populate archlinuxarm

# install wget
pacman -S wget

# for now, get the packages from the manjaro arm repos (feel free to use a mirror closer to you instead)
cd
mkdir manjaro-packages
cd manjaro-packages
wget http://ftp-nyc.osuosl.org/pub/manjaro-arm/repo/stable/aarch64/core/linux-pinebookpro-5.5.0-0.2-aarch64.pkg.tar.xz
wget http://ftp-nyc.osuosl.org/pub/manjaro-arm/repo/stable/aarch64/core/uboot-pinebookpro-2020.01-4-aarch64.pkg.tar.xz
wget http://ftp-nyc.osuosl.org/pub/manjaro-arm/repo/stable/aarch64/community/pinebookpro-post-install-20191121-1-any.pkg.tar.xz
wget http://ftp-nyc.osuosl.org/pub/manjaro-arm/repo/stable/aarch64/community/ap6256-firmware-2020.01-1-aarch64.pkg.tar.xz

# install the downloaded packages
pacman -U linux-pinebookpro-5.5.0-0.2-aarch64.pkg.tar.xz
pacman -U uboot-pinebookpro-2020.01-4-aarch64.pkg.tar.xz
pacman -U pinebookpro-post-install-20191121-1-any.pkg.tar.xz
pacman -U ap6256-firmware-2020.01-1-aarch64.pkg.tar.xz

# install uboot on the emmc
dd if=/boot/idbloader.img of=/dev/mmcblk2 seek=64 conv=notrunc
dd if=/boot/u-boot.itb of=/dev/mmcblk2 seek=16384 conv=notrunc

# generate the new initramfs (chances are it's already been generated by now, but no harm in doing it again)
mkinitcpio -P


4)  Final Steps

- Rename the alarm user, and change passwords for your new user and root
(Reference: https://wiki.pine64.org/index.php/Pinebo...ame.2C_etc)

Code:
usermod -l myself -d /home/myself -m alarm
chfn -o "John A Doe" myself
groupmod -n myself alarm

passwd myself
passwd

- Follow the archwiki installation guide and complete any missing steps, like editing /etc/hostname, /etc/hosts, /etc/locale.gen, /etc/locale.conf, etc:
https://wiki.archlinux.org/index.php/Installation_guide

- Install optional packages
Code:
pacman -S base-devel vim bash-completion networkmanager htop lsof strace

- Power off your pinebook pro, remove the SD card, and boot to your new ArchLinuxARM installation!
Code:
exit # exit the chroot
umount /mnt
sync
poweroff

- Install a WM/DE. I am currently testing out SwayWM, and it appears to be very stable and fast!


5) Potential ToDos

- Consider creating AUR packages for the packages we borrowed from Manjaro in Step 3, if they don't get backported soon.
- Perhaps create an image you can flash straight to your emmc, instead of having to do all of the steps above.


  Android 9 img 64gb and google (first post)
Posted by: user7654 - 01-21-2020, 10:07 AM - Forum: Android on Rock64 - No Replies

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


  [Default Debian] Issue with Wifi captive portal?
Posted by: Tazdevl - 01-21-2020, 07:33 AM - Forum: Linux on Pinebook Pro - Replies (9)

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?


  Trackpad Switch primary/secondary buttons and paste on double-tap?
Posted by: lowry - 01-21-2020, 07:21 AM - Forum: General Discussion on Pinebook Pro - No Replies

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 

Code:
xinput set-button-map 7 3 2 1

then the single-finger tap and the double-finger tap are also sending "button 3".

Is there a way to decouple double-tap, single-finger and double-finger tap in trackpad configuration?


  Pinebook Pro (ANSI) availability notification?
Posted by: MechanicalPirate - 01-20-2020, 06:33 PM - Forum: General Discussion on Pinebook Pro - Replies (5)

Hello all,

I came across the Pinebook Pro and realized it is what I've been waiting for in a laptop.

Is there somewhere I can sign up to be notified when the ANSI edition becomes in-stock?

If not, I don't mind checking periodically.

Thanks,
MP


  i3status issues reading battery status
Posted by: dummy - 01-20-2020, 04:08 PM - Forum: Linux on Pinebook Pro - Replies (9)

So, finally had the time to sit down and try to whip this thing into shape since getting it, so far solid hardware and no more issues than I would have expected with a product like this. But after getting i3 set up, I cannot get the status display to read the battery charge status. At first assumed it was just the normal issue with non-standard battery names, but after manually putting the path in the i3status.conf I'm now getting an error: 

no '%d' in battery path


Has anyone else had this issue/have a resolution? I've seen a lot of people playing with i3 setups on here, so hoping someone else's past struggles found the solution.


  Meet the PBP Tinkerer Housing early proposal
Posted by: 8jef - 01-20-2020, 02:23 PM - Forum: Pinebook Pro Hardware and Accessories - Replies (7)

Hello PBP enthusiasts,


This is a very early basic design idea for an upgraded PBP housing.

Main features:

A few mm thicker bottom
Front facing speakers
Expanded width for hardware upgrades
M.2 Door
Integrated USB 3 hub
Easy customization 
3D printed on demand
Durable, recyclable
Future proof



.pdf   pbp_th.pdf (Size: 19.62 KB / Downloads: 805)


  Widevine-flash on Chromium-SD Card
Posted by: mamboman777 - 01-20-2020, 01:18 PM - Forum: Pinebook Pro Tutorials - Replies (3)

I was able to get Amazon Prime video working today on Chromium booted from an SD Card.  I used this script: https://gist.github.com/ruario/19a28d98d...42e5f8bf29

Extracted the .tgz file.  and copied the contents into the /opt/google/chrome folder of the partition labeled Root-A of the SD card which I have Chromium OS.

I have tested with Amazon Prime, but I don't have a netflix account. I imagine all widevine streams would work now.