After leaving my Pinebook, for over a month, I decided to fire it up and try out a new OS... Sadly however when I pressed the power key, I got a green light, then...everything went off.

I assumed the battery must have died and plugged it in for a charge...expecting it to power up while charging, but still nothing.

So I left it overnight....and this morning, nothing...no repose to the power key.

Is there a key combo needed to perform some kind of reset, or any other advice anyone has, it seems to be dead at the moment?

I registered for preorder July 25th and nothing came to my email. Its that wrong?
I checked all folders, including spam.

Thanks for help.

I'm running a little behind everyone else in getting one of these lovely machines (I'd like one after the first ones have gone and been tested) ;) , but the question I have is -- you have EU and US power supplies. What do those of us in NZ and Australia do? We are 240V 60 Hz.

Thanks, I know ther is probably a simple answer.

Hello

Do you know where I can find a generic box which can be fixed on a screen via vesa 7.5 cm ?
The idea is too put the rockpro board inside and maybe add a battery inside the box.

thank you

Is anybody on an up to date kernel? I am trying to stay current, rebasing ayufan's linux-kernel-mainline against Greg KH's stable branch. I ran into an issue with usb storage recently, though. Does anybody run a (mostly) mainline kernel? Care to share any tips?

After finding major stability issues with Manjaro, I'm back on Debian for my rockpro64 build. I'm trying auyfan's latest stable stretch minimal image. I installed Wayland-protocols and Weston, but I'm unsure what I'm supposed to do with the files from [color=var(--newCommunityTheme-linkText)]https://github.com/rockchip-linux/libmali/tree/master. I tried running what I think was the appropriate install script after installing dh-exec stuff but Weston doesn't appear. Instead, I get errors like "MESA DRIVER: failed to retrieve device information" "gbm: failure to open any driver"[/color]


I don't want to use x11. I'l like to try actually using wayland on an arm64 setup. I'd like to use panfrost, but because that's only in mainline so far, and the accompanying mesa 19.2 isn't ready for another few weeks, I can't. I have to use the Rockchip Mali binaries if I am to get a stable system.

I'm forgetting a step. What am I forgetting?

Moderators: can we add a Fedora subforum?

Fedora 30 installed on my Pinebook with only a few issues.  The main one being that brightness defaulted to 0 on the original aarch64 image.  :-P

I booted the SD on an rPi3 to do initial configuration, and updates.  Then used the dracut option to create a multi-platform initrd for the new kernel, and moved the SD card back to the Pinebook.  The newer kernel defaults to brightness 2 - so I took it into a dark bathroom to navigate /sys and set a higher brightness, and change the text console fonts to the biggest available.  :-)  Fedora uses upstream kernels, so it reflects the state of A64 support in the mainline kernel.  

I've been using it a few weeks now.  Here are the biggest issues:

 1) the biggest issue is lack of support for cpufreq on A64.  It feels like 500Mhz, but without any supported readout, that is subjective.  Bogomips is 48.0.  I don't know what the cpufreq actually defaults to, but let's just say I do aarch64 builds on a 1G rPI3...  What is needed to get that upstream?

 2) the second most annoying problem is lack of support for internal wifi.  This is worked around by adding one of those tiny EdiMax wifi dongles (the big long ones can pose a danger of geting caught on something and damaging the USB port). 

 3) the third problem is inability to read mic input.  The mics are active - because if you turn up the gain, they feed back.  And if you connect some speakers to the audio out, the pinebook becomes a megaphone.  However, ALSA doesn't know how to make the mic data available to apps like Sound Recorder, Linphone, etc.

 4) the internal bluetooth is also not supported.  It would be nice to connect decent speakers (the internal speakers are understandably tinny tiny ones) or headset without resorting to an audio cable or yet another dongle.

 5) the Mali GPU is not supported.  I just use LXDE, which doesn't require 3D, and video playback is fine (xorg reports video accel active).  So this is the least important unsupported feature for this user.

The forum emails provide only the classic HELO <fqdn> for authentication.  This is fine, and RFC correct, although only a few knowledgeable email admins actually check it (or configure it correctly).  Big Email providers like to insist on PTR (which is not RFC correct - that is what HELO is for).  There is also a valid IP4 PTR record at 207.136.193.31.in-addr.arpa for files.pine64.org.  But there is no IPv6 PTR record:

7.0.2.0.6.3.1.0.3.9.1.0.1.3.0.0.0.0.8.0.0.b.a.f.8.f.a.0.2.0.a.2.ip6.arpa not found: 3(NXDOMAIN)

Sending to Big Email providers that insist on PTR via IPv6 may fail.


The HELO for the forums emails is HELO files.pine64.org, and the DNS for files.pine64.org lists only an A record for 31.193.136.207.  This is fine for sending emails to IP4 servers.  files.pine64.org has entered the 21st century, and also sends emails via IPv6!  Great job!  Unfortunately, the IPv6 address is not listed in DNS, so the HELO authentication fails in that case.  (The FQDN in HELO must resolve to the connect ip.)  Since no other authentication is provided, my email server rejects the emails by default.  (I, of course, have overridden this by adding a local SPF record for files.pine64.org.)

To simplest solution is to simply add the missing AAAA record to DNS:

files.pine64.org  IN AAAA 2a02:af8:fab0:800:31:193:136:207

It would also be a good idea to add the PTR ("reverse DNS") for the IPv6 address to keep Big Email happy.


In addition, I could not find a button to resend the activation email.  My account had to be manually activated by an admin on IRC.

If I click on "View New Posts" or "View Today's Posts", it shows a table of new posts, with the columns "Thread / Author", "Forum", and so on. The "Forum" column shows the sub-forum which the post is in. As the sub-forum is often called something like "Linux" or "Hardware and Accessories", it's not always possible to tell which product the post relates to.

Is it possible to include the parent forum name in the Forum column, as well as the sub-forum?

I was wondering, is there a plan for the main board inside the PBP to be swappable with future boards ? In other words, a component upgrade vs replacing the entire machine ?

Thanks