Hello everyone,

We now have a utility to flash eMMC. Many thanks go out to @MartijnBraam @Danct12 and others who contributed to making this happen.


Here's how it works:
1) download the Jumpdrive image
2) flash the Jumpdrive image to a SD card
3) boot from the SD card
4) connect the PinePhone to your computer using USB-A -> USB-C cable.
5) flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card
6) once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card
7) boot into your OS of choice on eMMC


Download Jumpdrive

The store is one big sprawling page with some products shown multiple times. Could the store be converted into several pages or somehow better organized for a better experience?

Hey!

I installed PmOS with Phosh a couple of days ago. I was planning to install pmos+phosh on the emmc, so I already installed pmbootstrap and run the init command. After a reboot the terminal application in the app drawer was gone. I can't provide details to the installation or log files (it must have been the phosh release from two days ago). pmOs 1.17.0.


Settings / Applications show the terminal app as installed.

Without the terminal app you're stuck. I tried to use a keyboard shortcut to start the command prompt, but it's not working with the software keyboard. Next I will try to access the phone via ssh and reinstall the terminal app (when I've found out how it is called).

Before this happened I installed python-pip3, gparted (which is not working) and gnome-disk-utilitiy. I don't think that this bug is related to these installations, but who knows.

Maybe someone has an idea. At the end I will flash the sd card again.

Absolutely lovely computer and booting to the already installed system on eMMC works really well.
Its snappy and boots fast. I tried installing Manjaro/Plasma, but if feels very sluggish in comparison.
A few questions.

1) Is this something that can be fixed (or will be) in the future (sluggishness)? if anyone knows

2) I read in the March update news that Pine will be using Manjaro as the default moving on. Does this mean the (I guess its) Debian which comes pre installed will not be supported anymore, or not have as much support as Manjaro?

3) I was not presented with any installation to eMMC when booting Manjaro from SD, are there any tutorials available for installing to eMMC with encryption for the drive? Or at least just installing to eMMC?

4) This might be a stupid question, but when the Pinebook is booting there are no option for BIOS. This is normal for these SOC computers, correct?

So, I have a RockPro64 running OMV that I purchased last year some time.  It's in the NAS case with 2 4TB HDDs, running as separate drives.  It's been working great, with Emby plug in.  I had an issue where I lost power (hadn't bought a UPS yet), and the main media drive crapped out.  That's all solved.  Now, however, I'm looking at using a SBC to run a VPN server, and pi hole to remove ads from my network.  I was looking at an Odroid N2 to run this.  However, after some research, I'm thinking maybe I can run all 3 services on the RP64...  It seems to be powerful enough for it.  Is it wise to do an all in one, or should I keep them separated?

Hello,
 
     While the rest of the world may have moved on to the Pinebook Pro, I personally still love my Pinebook 1080P.  Yes, it is a bit quirky, but not so quirky as to be unusable.  In fact, most of the quirks have simple workarounds that teach you about how Linux works, so I see it as a fun and interesting challenge.

     I have been making Slackware work on my Pinebook in one way or another since I first received it.  For a long time, I was using Anarsoul's ArchLinux with XFCE as the base, then I would strip everything out except /boot and /lib/modules and /lib/firmware.  Then I would copy over a root filesystem, and build it up from there.

   Wanting a newer kernel than 4.20.0 (despite the appeal of the number itself), and after many failed attempts to build my own kernel (these ARM devices sure can be tricky...), I finally reached out on LinuxQuestions.org, and got help from sndwvs there.  If you would like to follow that thread, here is the link:

https://www.linuxquestions.org/questions...175669005/

    The build script at gitlab is not currently working, but I can still build fresh images using a commit from a few weeks ago, details are on the link above.  If you are interested in following the build script development, that his happening here:

https://gitlab.com/sndwvs/slackware_arm_build_kit

   And if you would like to skip all of that and just grab the latest working image, you can find those here:

https://3space.xyz/pineslarm/

   I will put up a full image there soon, so that you do not have to do any downloading after installation to get a GUI desktop.  Stay tuned for that, it should be uploaded sometime this week.

   Note that this last link also contains a directory of the SlackBuilds that I have built for Slarm64.  Not all of them work, some I have built for testing purposes only.  Some might be outdated, sometimes I build a package, try it out, and never update it after that.  So, there are no guarantees here, I just provide them in case you want to use them instead of building them yourself.

   A build of note is LibreOffice with a single dependency (libfreehand), which I am currently building an update for, hopefully with no dependencies at all.

   FWIW, I am finding that this image with JWM as the window manager (see my builds above) is the snappiest and smoothest image I have ever tried on the pinebook, and I have tried all that I can find, including everything on the Wiki (even the BSDs).  Your mileage may vary.  And, "nostalgic" is not the word that I would use when referring to Slackware-current.  Yes, you can go retro with it, but it is just a base to build from, so I see it as basically the same thing as Anarsoul's ArchLinux without systemd and easier to build your own packages on, more or less.  This only has to be as "nostalgic" as you want it to be.

   Oh, and I believe this script supports Pinebook-Pro as well, but since I do not have one of those, I cannot comment on how that one is working.

   One last note:  I do not think that Slarm64 has received the official blessing from either Pat Volkerding or Stuart Winter, so I do not think this is "official" Slackware in that sense. But nothing has been added beyond boot files and kernel modules needed to make the Pinebook work.  This is a true Slackware experience on the Pinebook, regardless if it has been Blessed By "Bob" ™ or not.

Enjoy.

Hi, wanting to try another OS (the new Manjaro) I downloaded the emmc installler image and flashed it to a 16GB SanDisk microSD with the PINE64 INSTALLER utility.

However, my Pinebook Pro refuses to boot from the SD card as long as the internal eMMC drive is swithced on. After switching it off with the little toggle under the hood, I can boot from SD card but then... How to install to the internal drive?

Can anyone point me to some clear instructions either on the wiki or these forums? For a noob it's completely confusing...

Thanks!

Excited to hear that Manjaro KDE will be the default OS on new PBPs. 
I got my PBP in January with Debian though. Which is the official link for the new default Manjaro build? I'd like to install it on my MMC.

I'm tempted to try the link in the wiki, but the page still mentions Debian as default.
https://wiki.pine64.org/index.php/Pinebo...MC_Boot.5D

Dear Pinebook Pro fans,

I have a PBP and it has Debian with Linux 4.4.213 on it. I have installed i3wm beside the MATE

I have a problem with powering off the machine though. In MATE if I press the power key a dialog appears and if I press shutdown the machine shuts down and power offs as expected. However, if I run `sudo poweroff` or `sudo systemctl poweroff` the system shuts down but does not poweroff. The screen goes black and a pointer keeps blinking forever. It does not matter if I run this command inside MATE or i3, the result is the same.


According to this thread I configured the power key for i3wm and also used systemd-inhibit to prevent systemd from handling the power key when i3 is running. I think it has nothing to do with the above mentioned problem though, since that problem happens in MATE too.

The question is, what MATE does differently that its shutdown dialog can poweroff the PBP properly? Doesn't MATE use systemd to poweroff the machine?

I appreiciate any of your comments.

Update
Adding `--force` to the poweroff command solved the issue, i.e. `sudo systemctl --force poweroff`. However, I don't know what prevents the poweroff without the force flag.

I am very sorry to report that my PBP has suddenly and inexplicably locked me out, it will Not recognize my passwords for any ID I have created, nor for the default rock ID.  

My guess is I will simply need to make a new boot stick and reload the OS?  

My daily use has just been to boot up, enable any machine and the Debian OS updates, and then proceed with using the machine.  Last session was trying out Geany as an IDE, and using the web to help with that.  I have not been pursuing any assembler coding, nor any similar thing that may have interfered with the OS password operations.  

So, I am here to ask for guidance, where do I download an ISO file of the default Debian OS please, and where are there instructions on making up a new OK install?