While Pinebook is not a very powerful machine, it's still quite capable. And while it's certainly not a "gaming laptop", it could still run graphically less demanding games quite well. Moreover, great battery life could keep you entertained throughout a long trip, for instance. What games do you play on your Pinebook?

One of best genres to play on a Pinebook in my opinion, is roguelike games. Great keyboard, optimal size and weight (for 11.6"), long battery life - all this makes Pinebook an ultimate portable roguelike machine. And as roguelikes are usually very modest with system requirements - it's a perfect kind of games to play on Pinebook. NetHack, Angband, Dungeon Crawl Stone Soup - all they can be played on a Pinebook, and it's a very enjoyable experience.

My personal favorite is NetHack, which I do play quite often on my Pinebook:



Many major roguelikes are already packed in most distros repositories.

Does anyone have any hints on how to get an NFS mount working?  I am using kernel 4.20 since it recently had rockpro64 support added.  My kernel parameters look like the following:

console=ttyS2,1500000 earlycon=uart8250,mmio32,0xff1a0000 root=/dev/nfs rw nfsroot=10.10.0.1:/export/sysroot,proto=tcp,vers=3 ip=10.10.0.2:10.10.0.1::255.255.255.0:rockpro64:eth0:off raid=noautodetect nfsrootdebug

and I am loading my kernel and kicking it off from u-boot with:

tftpboot 0x2000000 <kernel Image>
tftpboot 0x20000000 rk3399-rockpro64.dtb
booti 0x2000000 - 0x20000000

The NFS debug spits out:
NFS: nfs mount opts='vers=2,udp,rsize=4096,wsize=4096,proto=tcp,vers=3,nolock,addr=10.10.0.1'
NFS:   parsing nfs mount option 'vers=2'
NFS:   parsing nfs mount option 'udp'
NFS:   parsing nfs mount option 'rsize=4096'
NFS:   parsing nfs mount option 'wsize=4096'
NFS:   parsing nfs mount option 'proto=tcp'
NFS:   parsing nfs mount option 'vers=3'
NFS:   parsing nfs mount option 'nolock'
NFS:   parsing nfs mount option 'addr=10.10.0.1'
NFS: MNTPATH: '/export/sysroot'
NFS: sending MNT request for 10.10.0.1:/export/sysroot
NFS: failed to create MNT RPC client, status=-101
NFS: unable to mount server 10.10.0.1, error -101

I am not convinced that the network interface is coming up.  For starters, I never see anything like the following on the console:

IP-Config: Complete: 
      device=eth0, addr=192.168.1.100, mask=255.255.255.0, gw=255.255.255.255, 
    host=myboard, domain=, nis-domain=(none), 
    bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath= 

which is what I thought using the ip= parameter was supposed to do and when I turn on:
rpcdebug -m nsfd all
rpcdebug -m rpc all

and watch /var/log/messages on my server, nothing happens - it looks like my devices aren't talking.

I assumed that the in kernel realtek drivers would be sufficient, but I noticed that in the 4.4 kernel, there is an actual rockchip ethernet driver - does that need to be used in the 4.20 kernel?  I tried copying it and adding it to my config, but some of the timer interfaces changed, so it does not compile.

Any hints would be helpful.

Thanks!

I had a 2.5 HDD on the USB3 connector without a separate power supply. It worked any weeks. Then the rockpro dies during work on it. The Kernel can't find the filesystem. After then boot hangs on initilize the USB stack.

Good day,

When I login Ubuntu desktop, the OS hanged and the PCIe slot power seemed turned off (NVMe SSD LED was off ).
If I unplug the NVMe SSD from the PCIe slot and boot into OS, it was successfully login into desktop and all was normal.

The NVMe SSD can be recognized and normally operated under Ubuntu OS without desktop.
The system would hang during booting or login after installing desktop (I have tried gnome、mate、lxde、xfce...).
 
I want to use NVMe SSD as my storage under desktop environment (GUI).
If any setting is necessary for installing desktop environment I lost ?
Any one has the same issue or can help with your experience ?

PS. The OS image is the latest release in wiki. The board is ROCKPro64 V2.1.

Thanks!

Hi all

Does anyone have any hints on how to get an NFS mount working?  I am using kernel 4.20 since it recently had rockpro64 support added.  My kernel parameters look like the following:

console=ttyS2,1500000 earlycon=uart8250,mmio32,0xff1a0000 root=/dev/nfs rw nfsroot=10.10.0.1:/export/sysroot,proto=tcp,vers=3 ip=10.10.0.2:10.10.0.1::255.255.255.0:rockpro64:eth0:off raid=noautodetect nfsrootdebug

and I am loading my kernel and kicking it off from u-boot with:

tftpboot 0x2000000 <kernel Image>
tftpboot 0x20000000 rk3399-rockpro64.dtb
booti 0x2000000 - 0x20000000

The NFS debug spits out:
NFS: nfs mount opts='vers=2,udp,rsize=4096,wsize=4096,proto=tcp,vers=3,nolock,addr=10.10.0.1'
NFS:   parsing nfs mount option 'vers=2'
NFS:   parsing nfs mount option 'udp'
NFS:   parsing nfs mount option 'rsize=4096'
NFS:   parsing nfs mount option 'wsize=4096'
NFS:   parsing nfs mount option 'proto=tcp'
NFS:   parsing nfs mount option 'vers=3'
NFS:   parsing nfs mount option 'nolock'
NFS:   parsing nfs mount option 'addr=10.10.0.1'
NFS: MNTPATH: '/export/sysroot'
NFS: sending MNT request for 10.10.0.1:/export/sysroot
NFS: failed to create MNT RPC client, status=-101
NFS: unable to mount server 10.10.0.1, error -101

I am not convinced that the network interface is coming up.  For starters, I never see anything like the following on the console:

IP-Config: Complete:
      device=eth0, addr=192.168.1.100, mask=255.255.255.0, gw=255.255.255.255,
    host=myboard, domain=, nis-domain=(none),
    bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath= 

which is what I thought using the ip= parameter was supposed to do and when I turn on:
rpcdebug -m nsfd all
rpcdebug -m rpc all

and watch /var/log/messages on my server, nothing happens - it looks like my devices aren't talking.

I assumed that the in kernel realtek drivers would be sufficient, but I noticed that in the 4.4 kernel, there is an actual rockchip ethernet driver - does that need to be used in the 4.20 kernel?  I tried copying it and adding it to my config, but some of the timer interfaces changed, so it does not compile.

Any hints would be helpful.

Thanks!

I tried to compile firefox via pkgsrc and I can’t because rust isn’t avalaible on aarch64 arch.

Any suggestion to fix it? I’ll keep doing some research... Looking for rust compile instructions...

arm64# pwd
/usr/pkgsrc/lang/rust
arm64# cd ..
arm64# ls rust*
CVS           DESCR         Makefile      buildlink3.mk cargo.mk      distinfo      files         patches
arm64# ls ru
ruby/                      ruby-gherkin/              ruby23-base/               runawk/
arm64# pwd
/usr/pkgsrc/lang/rust
arm64# make install
=> Bootstrap dependency digest>=20010302: found digest-20180917
ERROR: This package is not available for these platforms: NetBSD-8.99.26-aarch64.
ERROR: This package has set PKG_SKIP_REASON:
ERROR: rust-1.30.1nb1 is not available for NetBSD-8.99.26-aarch64
*** Error code 1

Stop.
make: stopped in /usr/pkgsrc/lang/rust
arm64# 

I'm using the RP64 with the dual SATA board to run two drives in a RAID 1 configuration. This is using OpenMediaVault 4.

The drives were seen as /dev/sda and /dev/sdb.

It was running fine for a while. And then I found that the Raid was showing as 'degraded' and only sda was showing in the Raid config. When I looked at the Disks section I found that sdb had disappeared and sdc had appeared. Using lsblk showed sdc as not having a partition.

Looking through syslog, I found this:

Dumb question but is it possible to install the OS to another laptop?

Hello. I'm just waiting for my Pinebook. But I have some disappointment after I have read about hardware support. One linux distro doesn't support one of component, another distribution doesn't support another one.

As I see in this table, the most usable distro is KDE neon. But HDMI is not supported and GPU acceleration is marked with "?". Is there any solution to fix HDMI output on KDE Neon? Does GPU work? If yes what driver does it use: from ARM or reverse-engineered?

Great news everyone, Armbian images are now available for RockPro64.

Download Here