Hi All,

I received my PBP last week, all working fine out of the box, love the device so far!

The only issue I've had so far is that the image on the EMMC seems to be corrupted, I can boot from SD cards just fine, posting this from the standard Debian.

What's strange, once I've booted from a SD I can boot the device from the EMMC once or twice but after it will just loop through the boot process. Sometimes it will get to the logon screen but it will hang there and after a period of time it will power cycle again.

Is there a straight forward way to flash the Debian image to the EMMC storage when booted from a SD? So far it seems my only option is to get the USB adapter and do it that way.

Tried different dist isos and SD cards with both dd and etcher, not booting.

Tried dd from another computer, booting.

this post is to document the minor differences to run and
install the pinebookpro trackpad/keyboard firmware update
while running netbsd.

please see the original post for details about the issue:
  https://forum.pine64.org/announcements.php?aid=23


for me i had to do this beyond the normal instructions:

- install libusb1 from pkgsrc
- install vim-share from pkgsrc (this provides xxd)
- patch the Makefile to use these cflags:
      -I/usr/pkg/include -R/usr/pkg/lib -L/usr/pkg/lib
- use gmake not make

and i had to power-cycle between step-1 and step-2.

The "simple" way I restored the OS using the eMMC adapter and was up and running.

I ran into issues getting the OS installed from the SD card  
 Since the SD card method failed, I used the eMMC adapter instead. If you don't have an adapter, here are a few links where you can purchase one. 

I purchased mine from the Pine64 store which took a while to arrive.

• Pine64 store https://store.pine64.org/?product=usb-ad...mmc-module 
  
• Amazon https://www.amazon.com/ODROID-eMMC-Adapt...B01LHJ2O38
  
• Amazon https://www.amazon.com/ODROID-USB3-0-eMM...B07BHQ615Q
  
• Amazon https://www.amazon.com/SmartFly-info-eMM...B08229QKV3
  

1. Download the OS on a separate computer. https://wiki.pine64.org/index.php/Pinebo...an_Desktop
   
2. You'll need to flash the eMMC. I recommend using Balena Etcher https://www.balena.io/etcher/
   

1. Turn off your PBP, open the back, and remove the eMMC flash memory from the motherboard. See here for where to find it and other specs: https://wiki.pine64.org/index.php/Pinebo...Reassembly
   
   
2. Attach the eMMC to the eMMC adapter and place the adapter in an open USB slot within the separate computer.
   
   
3. Open Etcher on the separate computer and follow the instructions on how to flash the eMMC you have plugged into the USB slot. It's the same process as flashing an SD card.
   
   
4. Once Etcher is complete, reinstall the eMMC in the PBP and close it up.
   
   
5. Power up!
   
   
6. After your PBP boots up (you'll see the OS logo screen twice), log in using the rock/rock username/password combo.
   
   
7. Make sure the PBP has internet access so you can run the updates.
   
   
8. When the updates finish, follow the instructions on how to update the trackpad firmware. https://forum.pine64.org/showthread.php?tid=8407
   
   
9. After the second reboot, during the trackpad upgrade, you should be good to go   
   

I'm interested to see if someone else has got Hangover running on the Pinebook Pro.

Theoretically, Hangover should provide better performance than using just qemu for running windows programs.
More about Hangover on it's GitHub page and WineHQ's documentation.

Hangover requires 64bit userspace which excludes the default Debian and Ubuntu builds.

The Unofficial Debian installer , @jannik2099 's Gentoo instructions and Manjaro ARM should be the easiest way to get 64bit userspace systems.

The unofficial Debian installer appears to have several perks in terms of getting the requirements fulfiled for Hangover. Namely, gcc-ada should be available.

You can follow my progress on getting gcc-ada and mingw on Manjaro ARM (had to bootstrap gcc-ada using Debian packages) here.

I've installed Debian testing (bullseye) from Daniel Thompson's unofficial Debian installer:
https://github.com/daniel-thompson/pineb...-installer

Does it work to upgrade this to unstable?  I see the installer installs a Kernel from a "Debian_Testing" folder at the OpenSuse build service, and there is also a "Debian_Unstable" folder in the same location.  But I don't know whether this will be sufficient.

If it works to upgrade, how would I go about it?  Just the normal process of updating the sources list and then "apt full-upgrade"?  Or are there special steps?

So, reading through the wiki, if my reading comprehension is where it should be, it appears to me that is
1. the RK3399 searches to boot from SPI flash first
2. there is spi flash presentt
3. it is unused or it's use is undocumented

I ask, because this would be the obvious place for a more complex bootloader (i.e. coreboot) instead of relying on the hardcoded boot order, potentially adding support for SSD boot without any hacky drive leapfrogging stuff.

Apologies if this has been talked about before, couldn't quite find anything though.

EDIT: I was so eager to be helpful I didn't even look at the pinned posts, lol.

Hi,

I'm sure that I'm in the same boat as other folk that made orders, but is there a place to check order-update status? Or should just wait until the end of the month before doing anything like contacting the sales people directly?

I placed an order in early December for an ANSI Pinebook Pro and only received the the paypal transaction email, no kind of direct Pine64 confirmation email.  I don't even remember what the particular email address I used for the order, so I don't even know how to look that up.

Thanks!

To adjust the brightness in i3w on Manjaro or Arch:

1. 
   
   Code:

   sudo pacman -S brightnessctl
   
   
2. Add this keybindings to your config:
   
   Code:

   #Adjust Brightness with brightnessctl
bindsym XF86MonBrightnessUp exec --no-startup-id brightnessctl -q s  +1
bindsym XF86MonBrightnessDown exec --no-startup-id brightnessctl -q s  1-

I did this to have battery-status on the i3bar: