Update (08/07/2020):
Now there's also an option to use mainline U-Boot (v2020.07) with reference ARM Trusted Firmware, no need to use Rockchip blobs anymore.
You can build it yourself using this repository and flash the image as usual (flash_erase + dd works for Manjaro):

https://github.com/pcm720/u-boot-build-scripts

The build script uses patches from dhivael, sigmaris and Manjaro.
v2020.07 binaries for SD/eMMC and SPI Flash are available as well, you can find them on Releases page of the repo.
The resulting SPI image works on my PBP and boots from NVMe just fine.
Boot priority is SD -> eMMC -> NVMe -> USB, and there's no need to destroy U-Boot on SD card anymore.

---------
While it's possible to place the boot partition on eMMC and use NVMe as rootfs, the lack of NVMe support in stock U-Boot kept bugging me, so I decided to do something about it.

So, by porting Rockchip PCIe patches from Radxa and backporting some NVMe patches from upstream U-boot, I was able to get NVMe support going on mrfixit2001's fork and now can successfully boot from my NVMe drive:



You can find binary images for SD/eMMC/SPI flash and source code here.
Note that the current SPI image has issues when booting pre-made images from SD card.

For some reason Rockchip's SPL tries (and fails) to initialize trust mode with the microSD, so you'll have to zero out the bootloader, U-Boot and ATF on your SD card with the following commands:

Quote:dd if=/dev/zero bs=32k seek=1 count=1 of=<microSD>
dd if=/dev/zero bs=64k seek=128 count=64 of=<microSD>
dd if=/dev/zero bs=64k seek=192 count=64 of=<microSD>

As I was exploring Chromium settings, I stumbled across the connected devices tab, with the setting to connect your android phone to the laptop underneath it. It is, however, greyed out, saying "This setting is enforced by your administrator." Is that just its way of saying that isn't supported right now? As far as I know the administrator of my PBP is me...

I'm trying to attach a video file screen capture of how my wifi reception decreases when I move away from the gateway. I've tried several files with sizes under the attachment limit (under 2 MB), with ogv and mkv formats but get an error message

"Please correct the following errors before continuing:

• The type of file that you attached is not allowed. Please remove the attachment or choose a different type."
  

Ubuntu mate, during boot (the fast text command scrolling):
7613770 fixing recursive fault but reboot is needed.

I have to hold the power button down for longer time to reboot.

Hi,

Maybe I'm getting old and senile, but I keep forgetting the keyboard shortcuts to disable/enable the camera, microphone, and WiFi. On future iterations of the keyboard, it might be an idea to place symbols on the bottom left of the F10-12 keys.

Ben

   ***
 Now that the Pinebook Pro is being perfected,

   How about a :   'Pinebook Pro Extreme'   ?

  1) a 19" Wide screen
  2) Maybe dual batteries
  3) Able to boot from the NVMe
  4) Larger Speakers that point up from the palmrest
 
   That would likely attract a lot of attention,
    
        Of Course it would cost a bit More,,,
 
   but it likely attract even more potential high end customers.

               
                   Just a thought  ?

I wanted to share this, after trying so many different forks. For anyone interested in using crouton to install Arch, refer to this fork of chroagh. I tried/edited about 4 other forks, but this buried beauty has actually allowed me to install aarch64 Arch within Chromium.

Since it's outdated, you'll likely need to run sudo enter-chroot -n [chroot name] -u root in order to be able to login/finish setup.

  2434230-40.jpg (Size: 11.22 KB / Downloads: 775) Hello,

I'm wondering if anyone has installed and configured a Piface2 Digital Input Output board on a A64 Pine 1GB board?
The Piface2 was originally designed for the Raspberry Pi A+ and B+ models.


Here's a link to the Piface datasheet:  
http://www.farnell.com/datasheets/188155...1574787277

Any help would be appreciated.
Dave

When I connect a monitor via hdmi port (which resides on a USB-C hub), the Pinebook Pro decides to choose a wrong resolution. dmesg shows, that the monitors resolution of 1680x1050  is announced, but the set to a lower resolution of 1024x768. What can I do to keep the monitors resolution? I append the dmesg's output:

I bought an USB-C from Amazon. It's maker is Andobil. While ethernet and display port are working fine, it seems the sd card slots and usb ports are not recognized. dmesg prints a lot of lines when plugging in the USB-C hub. I add the output to this post. Any ideas what is going wrong here?

Attached Files

  usb_dmesg.txt (Size: 4.34 KB / Downloads: 597)