Just to ask is there a package for the network manager that adds support for VPN's like L2TP and others like that?

This is the second time i've had this issue running nextcloudpi on my rock64.  It runs fine for about a month and then my SD card shows that it's full and I have no room left.  This prevents my nextcloud server from running correctly and I can't connect.

Created Stretch evironment with `qemu-debootstrap` (Buster seems to have a bug with QEMU), ran with qemu-i386-static , entered chroot with `schroot` and installed Wine. This will only work on aarch64 / ARM64 kernels.

Game extracted from my Linux x86_64 (Ubuntu 19.04) installation.

Followed this Tutorial.

Game extracted from my Linux x86_64 (Ubuntu 19.04) installation.
Followed this Tutorial.

Extracted from my Steam account, followed tutorial at https://magazine.odroid.com/article/play...-platform/

Hi, I just received my PineBook Pro yesterday and I am using the default OS with Debian 9 (32bit user space, 64bit kernel). I would like to recompile the kernel to enable the KVM module. I want to test containers and possibly Windows 10 on ARM. I have seen the images on the wiki, but I am not sure where the sources are to build an image myself, although ideally I just want to update the kernel on my existing OS. Since there are so many repos and distros for the PineBook Pro, I am not sure where to start. I don't want to lose all the great driver support, like the Mali drivers, I am hoping someone could share simple instructions to clone the repo of the kernel, build a .deb and install a kernel upgrade. Or in any case, this could possibly be a feature request for @Mrfixit2001  or @ayufan to include in the official image?

The Panel built in color looks washed out. I don't know what's panel does it has.
So is it possible to replace with a better one?

Bought a new RockPro64, downloaded some linux images, flashed them to eMMC: no boot.
The white light goes on, stays on for a while, goes off for half a second, goes on again for a while, repeat.
No HDMI output.

OK, turns out: new RockPro64's come without a uboot, or with a seriously old uboot.

What does boot, is ayufan's images:
https://github.com/ayufan-rock64/linux-b...tag/0.9.14
Download for example the
bionic-mate-rockpro64-0.9.14-1159-armhf.img.xz

That should work. It takes a while to load, first run, but it does work.
Boot from there.

From Ayufan's bionic Mate there you can install a uboot.
Download a uboot from here:
https://github.com/ayufan-rock64/linux-u-boot/releases

Now, it says you should download an flash SPI image, flash that image to an SD or eMMC and boot from that.
Well, with an old / missing uboot, the flash SPI image won't load.

So, download the .deb:
u-boot-rockchip-rockpro64-2017.09-rockchip-ayufan-1065-g95f6152134.deb

Open a terminal, and install the deb.
sudo dpkg -i u-boot-rockchip-rockpro64-2017.09-rockchip-ayufan-1065-g95f6152134.deb

Then flash the uboot to spi with
sudo rock64_write_spi_flash.sh

Enter YES with capitals to confirm that this is a scary thing to do.

After it stops scrolling you are done.
You can now boot other images.

This probably goes into the 'goes without saying'  category, because this information is nowhere to be found.
This took me a day, so let's hope this post saves someone else a day.

Also, please correct/reply if I made some errors in this description, I'm only doing this for one day now.

OK, bought a new RockPro64, downloaded some linux images, burned some of them to eMMC, didn't boot.
The green light comes on (power) and the white light comes on  and stays on. Then for about half a second the white light goes off, then goes on again for a couple of seconds. Repeat.
No HDMI output whatsoever.

Tried a couple of images, like the MrFixIt and Manjaro ARM images, no go.
Then happened upon Ayufan's fine work here:
https://github.com/ayufan-rock64/linux-build/releases

His image actually booted!
Specifically: https://github.com/ayufan-rock64/linux-b...tag/0.9.14
Progress. The RockPro64 isn't DOA!

Did some more reading, some searching the forums, nothing turns up but for an almost random mention somewhere that a uboot might be old.

Turns out, on new RockPro64 boards you have to install the u-boot / uboot, if you actually want to run some linux images.

Uboot is the ARM bootloader. There is a storage chip (SPI) on the RockPro64 board that holds the bootloader software.
The bootloader software is ran during boot, and if it finds a correct image, it boots that image.

Also: no information anywhere on how to actually install a new uboot.

New RockPro64 boards, it turns out, they come without a working uboot loader, or with a seriously old version that just doesn't load Linux images.

Luckily Ayufan also has images that flash to the SPI a newer (somewhat) uboot.
https://github.com/ayufan-rock64/linux-u-boot/releases

Now the information says you download an image, flash the image to an SD-card or eMMC and then boot it. When it boots, it flashes the SPI with the new uboot, and we should see a blinking white light. Which would be nice, if it actually loaded that image to start the flashing. Which it didn't. Because: no working uboot.

OK, so, the solution: download the ayufan linux image, flash that to a eMMC or SD.
E.g.: bionic-mate-rockpro64-0.9.14-1159-armhf.img.xz
Boot from that, and yes: this takes ages. But it's all good stuff.

Then from the working Bionic Mate, download the ayufan uboot .deb, this one:
https://github.com/ayufan-rock64/linux-u-boot/releases
u-boot-rockchip-rockpro64-2017.09-rockchip-ayufan-1065-g95f6152134.deb

Then open a terminal to install the .deb with:
sudo dpkg -i u-boot-rockchip-rockpro64-2017.09-rockchip-ayufan-1065-g95f6152134.deb
(make sure you are in the download folder)

Then you can install the uboot to the SPI:
sudo rock64_write_spi_flash.sh
You have to type YES with capitals to agree that this is a risky move. Then: be patient

There is a lot of scrolling... and then it's done.

Reboot, and you should be able to load images other than ayufan's.

Oh, yeah, this software works wonders for burning images:
https://www.balena.io/etcher/
You don't have to 'unxz'  the images, you can burn the .xz images right to an SD card or an eMMC.

This took me the better part of a day, so let's hope this post saves someone a day or an unnecessary RMA.

Also: please correct / reply if any of the above is wrong. I've only been at it for a day now.