Is there a guide/ explanation of the boot sequence for dummies?

I can see "Image" and "Image.bak" in /boot/. I want to build a custom kernel based on mrfixit2001's code (with changed configuration), but I haven't found out yet to recover as painless as possible when things go south.

Is there a boot menu in u-boot or something?

During the discussion about the upcoming pinebook and phone on hackernews the report of a severe issue with the batch of eMMCs shipped with the A64-LTS came up. Namely that the eMMCs apparently ignore the first read instruction which leads to not being able to boot from the eMMCs.

https://news.ycombinator.com/item?id=21454573

The originial report is on the pine subreddit from a month ago.

https://www.reddit.com/r/PINE64official/...from_emmc/

The author added a bunch of information in the HN post, namely that he tried the different images from the etcher fork and not just armbian and

>I then was able to order a usb3->eMMC adapter, and was able to debug the USB and determine my assertions were correct: those eMMC chips ignored the first read operation.

Unfortunately,  I am not familiar with the issue myself, but thought it would be beneficial to collect the information here.

Cheers

Hey all! I just uploaded a quick video on opening the Pinebook Pro and some basic usage. Nothing too interesting here (besides some Doom II!), but since I had the recordings and edited it on the Pinebook Pro itself I am compelled to share it. :}

I've noticed that my Pinebook Pro immediately wakes up from a suspend-to-RAM state whenever external power is connected or disconnected. I find this concerning, because this is approximately the last time I would ever want it to wake from sleep mode automatically - particularly since it does this even if the lid is closed at the time, and it's very hard to tell from the outside if the device is asleep or awake with the lid down.

What will it take to change this? I'm bracing myself for the worst, because I can't imagine the OS is involved at all in wake conditions - hence my posting in the hardware section. Is this something that could be fixed in the firmware with a straightforward method, or is it going to require attaching debugging clips to an IC in there somewhere, or what?

It's puzzling to me how this behavior was established in the first place. Is it affecting other units as well, or is ours somehow a fluke?

Looks like mine is #375.

Has anyone tried the Debian 'auto-build'   ?
  ( It appears to have 'rock-pro' support)

I use a cloud service to store configuration files and use owncloud-client to access the files.  Unfortunately the Debian version of ownCloud client is too old to interface to the cloud server I'm using.  I tried to download the source and compile it but could not make the compilation proceed.  Has anyone else tried and succeeded in compiling the armhf version of this software?  I know that version 2.5.4 works (on an intel processor) and 2.4.1 does not (on the pinebook pro).

So far everything else I need works on this laptop.  This is the one thing that will make the device useable for my work, so am keen to get it going.  But I have not been able to successfully make the package compile, because it needs QT5.12 and inotify.

I think I have installed every library to do with inotify, but have not yet tried to install QT5.12, as the installation looks to be very hardware-specific.

Has anyone successfully compiled QT5.12 and ownCloud, and if so would you mind stepping me through the process?

Hi all,

I've built a true mainline Linux Kernel for the Pinebook Pro. It does only have a minimal amount of patches required to support

• the eDP panel Mainlined
  
• the battery fuel gauge (Mainlining in progress)
  
• the Pinebook Pro devicetree (Mainline starting 5.7) Mainlined in 5.7
  
• USB-C DP altmode
  
• Rockchip SIP driver
  
• Ultra low power sleep
  

• WiFi seems to be unstable, possibly due to issues with the Broadcom firmware and power management Fixed
  
• Bluetooth is untested Works through hciattach, actual native support through hci_uart would be great though Migrated to hci_uart and stable
  
• PCIe is untested PCIe works just fine
  
• Sound does not work (wip) Fixed though pinctrl
  
• Bootup takes a long time (~ 3 minutes) since the kernel hangs twice for quite some time during boot Workaround through new defconfig
  
• Charging via USB-C does not work Fixed though some devicetree adjustments
  
• Device does not power down fully Workaround in the rk808 driver, proper support in the ATF would be nice
  
• USB-C DP altmode does not work Fixed, with USB 3.1 gen 2 support
  
• Suspend to RAM is not working Fixed through forward port of SIP driver. Works only with BSP U-Boot, gives > 200 h standby
  

So, yeah... Deep in the documentation reads, and I'm paraphrasing, "Don't mess with the Chromium browser." I didn't see this until AFTER I had already borked the Chromium install by messing with the flags in the settings tab.

Not happy with my initial round of customizations, I downloaded the Debain image, flashed it to my SD Card so I get back to factory settings. When I place the SD Card in the bootable slot and boot up, nothing happens. Blank screen. 

Since I have the Pinebook and have reinstalled that OS plenty of times, I figured this would work the same way.

Can someone offer any suggestions on how to get my machine back to the factory install?

Thanks

I'm wondering if there is a repo/howto/something to build your own custom mrfixit image (as it seems to be the 'official' one). I want to encrypt the whole disk and I think the best approach will be to create my own image based on the official one.
Thanks!