Hello all!

Just really wanted to ask a quick and simple question really. Does anyone know what os the pinephone/community edition os will be based on? I only ask as I was looking at a video on youtube ;

https://www.youtube.com/watch?v=-MXOgb-U2jI

but as I watched something didn't quite seem right. Sure the phone is running ubuntu touch but something just well - it looked just a little bit "android-ish" if you can see what I mean. And lo and behold about 4 mins into the video I see in the file manager a directory called "Android". So .... is the pinephone similar to the Aquaris E5? That old phone ran ubuntu touch but you couldn't use it in the same way as "normal" ubuntu (you couldn't even run apt-get update was one of the comments I heard back at that time - !). And in the end it was revealed that "ubuntu" was just a re-jigged "ubuntu" running in an android chroot. It was pretty ..... terrible. :-( and you're still tied in to google spying and survellience.

https://ubuntu.com/blog/bq-launches-the-...tu-edition

So is the pinephone just running "ubuntu" in a chroot but quitely running android below that? Only reason I ask is I don't want yet-another android spy device and really don't want to get stung a second time (I did buy the E5 back in the day x.x ).

ljones

There're waterproof ratings out there that don't imply it will come back from sinking like Titanic. It would be nice to know if some kind of submergion is planned. Also how hard is glass and what's the type used or how easily it can be replaced?

Hello, I searched for an answer but I'm not finding anything.  Apologies if this has been asked and answered already.

My Pinebook Pro boot order was behaving as expected for quite some time.  It was booting from the SD card when a bootable card was inserted, and then from the eMMC otherwise.

After flashing Ayufan's Chromium OS build to the eMMC, now for some reason the PBP always boots from the eMMC card unless I disable the hardware switch for it.  This effectively makes the eMMC worthless since it can't be re-enabled without rebooting, but then the boot happens from the eMMC (which is currently in a totally broken state and needs to be re-installed).  I've now got a real chicken and egg problem going here.

I had read that the boot order was fixed (possibly hardcoded) but given my experience here, I'm wondering how true that actually is.

Is there any way to change the boot order?  How can I restore it to factory settings?

Hi,

I am trying to install opensuse on my pinebook pro and feel stupid for asking this ... but how ?

I downloaded the iso from https://github.com/smithmcgriff/openSUSE-on-pinebookpro
and then I put it on an sd card.

My pbp boots from it but all I get is a terminal. I think it just boots from the sd card but how do I get the image to install on the internal drive in the pinebook pro?

Also a small side question:
How bad of an idea is it to simply get the aarch64  image from opensuse (https://software.opensuse.org/distributions/tumbleweed) and install that on the pbp?

One of the issues that comes up is that we can't easily select what device to boot during startup.
U-Boot does not have that option for us, yet. During testing, I've had to remove and insert the
MicroSD card far too many times. It would be nice if I could leave it installed and force booting
something else.


So, how about something like this?

U-Boot selectable device target:
        - Pause & blink LED, (which one?), for a short time, (5 seconds?)
        - During this time, accept keyboard input
        - Select boot device of:
                - eMMC, (number 1?)
                - MicroSD card, (number 2?)
        - Timeout default using current scheme, MicroSD if installed, eMMC otherwise.

The exact keys for which devices are not really important. And if NVMe or USB booting works fine
then those could be added as well. Plus, allow changing the default boot order at install time, (so
people with NVMes could be a priority over eMMC).

Plus, perhaps having the ESC and Enter keys immediately jump to the default action. So a way to
skip the pause.

As time goes one, perhaps we can add a primitive text menu on the screen.


At present, this idea does not care where U-Boot is installed, (SPI, eMMC, MicroSD card). For
testing, it probably easiest to have it on a eMMC or MicroSD card. This idea is to address which
device we use for "/boot".

So, what does anyone else think?

Perhaps someone has a better idea?

Does using Grub as a target allow boot chaining?
(Meaning a grub menu entry can say go to another device.)

Hi

I'm not sure why this happens, although I've not noticed any issues so far, but every time I run apt-upgrade on debian on my PBP, the upgrade runs fine but always end with:
update-initramfs: Generating /boot/initrd.img-5.5.0-1-pinebookpro-arm64
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory
find: ‘/lib/modules/5.5.0-1-pinebookpro-arm64/kernel/arch/*/crypto’: No such file or directory

Thoughts?

Help please!

Attached Files

  photo_2020-05-16_17-51-15.jpg (Size: 120.39 KB / Downloads: 636)

Hello,

I am extremely interested in getting a PinePhone. I have this wild dream to use my PinePhone with external peripherals to remote into a desktop PC so I can use all of my juicy desktop applications on the go! One PinePhone to rule them all. Genius, right? I am imagining something like Teamviewer with the lowest latency possible.

Nothing special but I wanted to set up Fedora Server on this Pine64 v2 from here.

https://getfedora.org/en/server/download/


This did not work so I downloaded and installed Armbian_20.02.1_Rock64_buster_current_5.4.20. The OS booted up and is working ok.

My question is - will this work just as well for some server type work? Initially I want to set up an email server and will require postfix and other dependecies to be in the repository.

Going back to Fedora, they have a raw image download. Can this be made to work on the Rock64?

A script modification I made to make it easier to flash different boot images.
Based upon lupyuen's scripts and requires openocd-spi.

https://github.com/jlukanc1/pinetime-boot-flasher/

I HAVE NOT TESTED THIS ON A DEVICE YET
USE AT YOUR OWN RISK

It should be fine however.

Look at the repo for more info. 

Good luck!