EDIT: installing https://github.com/righttoprivacy/rak_co...or_gateway sets the Pinedio gateway devices (concentrator/gps) listed below. (Leaving notes for context/reference).
See lower page for example image with fork installed.

Hello!

Post to share things that are found helpful/work, progress/Notes along Pinedio Gateway/modules/Kit.

(Pinedio uses Rak Wireless "LoRa"/Mesh related/compatible hardware).

Pinedio's Wiki has been started and can be found here: https://wiki.pine64.org/wiki/Pinedio

Thread for sharing some found to be working notes that can be edited out/posted to WiKi as wanted.

The Pine64 Gateway's underlying hardware runs on the A64-LTS (this looked the best place to post this - feel free to move).

Working SOPINE/Patched Armbian image can be found at:

*** Removed one of the images as users reported ethernet was not working- my working image is below this:

https://mega.nz/file/Wd5CGRhB#spBqSQrhLm...HopFs4Ho9o (576MB) (Uploaded this copy after patching it)

sx1302_hal compiles/installs on Armbian without issue.

EXPERIMENT: SET UP RAK_COMMON_FOR_GATEWAY (ORIGINALLY FOR RPI: SOME MOD REQUIRED - NOT QUITE FINISHED):

Run sudo armbian-config. Enter System to enable SPI/UART for sx1302/rak/GPS.

Then Add The Following Line To /boot/armbianEnv.txt:

Hi everybody,
I am currently testing intensively rockpro64 in a blockchain usecase on a testnet.
As it is higlhy transactionnal, zfs OLTP performances are very appropriate to this usecase.
Actually it is the case, some easy arc size tuning makes it very performant in extreme i/o conditions.
No I want to mode forward for production testnet and I want to make it as safe.
I have found many adapters for a single nvme SSD, and I am looking for a dual PCI SSD adapter to run mirrored zfs pool on rockpro64.
Has anyone of you already found such PCIe adpater (not looking for an USB aspater) ?
For more details, I am running armbian focal ubuntu server on a rockpro64 SBC with a 2GB arc size on a 1GB zfs pool on nvme.

Many Thanks

Hello,

I hope I'm right here. I experience a weird behaviour for some time now with my KDE Community Edition PinePhone:

As long as I touch the screen, the brightness goes to normal. As soon as I lift my finger, the screen dims down to minimum immediatly.
The problem does not appear, as long as the phone is charging. But if it is not connected to the charger, the Pinephone is unusable like this. Shortly everything was ok, maybe this has come from a recent update.

What could be the reason? System is up to date...

Not every time, but sometimes when trying to power the phone off, an error appears and I get a mouse pointer. But the screen is too dark to read the error message (even with flashlight). The phone stays in this state until powering it of the hard way.

I found this thread which might provide a solution. But I'd prefer not to touch system files.
Did anybody experience this and solved it?

I have had lots of issues trying to get Mobian to work and I am confused by my most recent problem.  Maybe one of you have resolved this issue.

Background: I could not get the latest installer (mobian-installer-pinetab-phosh-alpha5.img.gz) or the latest build (mobian-pinetab-phosh-20210314.img.gz) to work by flashing the eMMC using JumpDrive 0.7 with bmap or dd.  I tried both encrypted and unencrypted with the installer.  The installer finished, but both choices resulted in a system that did not boot.  With the latest build, it would resize, and then go to black.  Reboots would flash the Mobian logo and then be black.  I started flashing older builds using the same process with success.  I do not have the serial cable to investigate the black screen issue further.

Now I am having trouble updating the old builds (mobian-pinetab-phosh-20201215.img.gz) to the latest version.  If I use the Software app and try to update, I run into the "Gnome Software (gnome-software) unable to download updates" issue listed on the troubleshooting section of the Mobian wiki [1].

The wiki suggests running these commands using King's Cross app:

Read the blog entry by @JF002 discussing the release of InifiniTime 1.0 for the PineTime.

Read now

Hi all,

I received my pinepower desktop earlier this week, and seems to be working fine when just used for charging devices.

However, when using the pinepower to supply power to a Raspberry Pi 4 (or even to a Lattepanda Alpha) through the type-C port, I'm seeing that the output power just drops then returns randomly, resulting in the SBCs to reboot, and that even multiple times per day. 

Initially I thought this was because of me plugging and unplugging the usb cable to charge my pinephone on the quickcharge port, but apparently, after leaving the pinepower desktop on overnight, I figured that the SBCs had rebooted multiple times!

It is strange to see this behaviour, and I would like to know if anyone else is experiencing this issue.

I'm aware the device is promoted as a charger, but I would like to know if this is considered normal.

Thanks!

PS: Feel free to move this message to a different thread if needed, because apparently there is no dedicated forum for the PinePower desktop to this day.

Hello there,

I have a Rock64 4GB Board, powered by POE and running Ubuntu 18.04.5 LTS (by Ayufan), Booting from microSD, no eMMC installed.
With fresh installations everything works great (i mean bare OS and no other applications), My intention of buying this board is to move away from RPi3B
for my Home Assistant system. I believe Rock64 is much more powerful CPU and extra RAM can provide a better environment.

However after migrating my working Home Assistant from RPi-3B to Rock64, Rock-64 started crashing immediately after boot with kernel panic.

I was able to take a short video to read what's going on with system and below are few lines which hets printed on console at panic.
Note that I have a oversized fan constantly blowing air on Rock64 and Heatsink is also installed on CPU.

Any help to resolve this issue will be appreciated..  ( I believe this is not too unstable system and can at least handle load what RPi-3B was doing past 2 years)


---- ERROR LOGS ---
INFO: task systems:885 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Kernel panic - not syncing: hung_task: blocked tasks
----
----  few more lines here with exception stack... 
----
Kernel Offset: disabled
Memory Limit: none

rockchip-thermal ff250000:tsadc: channel 0: temprature(48 C)
THERMAL REGS:
<SOME ADDRESSES IN BINARY>
Rebooting in 10 seconds

Hi all,
  I try to boot over the network (PXE boot) and follow the tutorial https://forum.pine64.org/showthread.php?tid=6814 with the Armbian image. After some hours to understand at the end that iptables was blocking the tftp connection I was able to boot but I cannot login : it is stuck when I enter the login or new password.
Do you have an idea of how to solve this issue ? root mount error ? NFS problem ?

LMM

Hello!

I'm looking into buying a pinetime, but there are a few features I would need:
- Ability to sync time with a degoogled Android phone or a Linux desktop os 
- Alarms
- Count down timer
- Ability to write/install custom apps

Do infinitime and the 1.0 release include this?

Thanks!

hello
i would like get vpn or tor working. is there a way for an average user to do that?