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: 632)

Hi

after extensive testing of my newly arrived setup I pinned down the problem described earlier (https://forum.pine64.org/showthread.php?tid=8359 and https://github.com/ayufan-rock64/linux-build/issues/299) to the official PCI-e to Dual SATA-II Interface Card. As I'm pretty sure that the card is the culprit in this case, I'm re-posting the problem here.

My setup:
RockPro64 4GB
2x4TB Seagate IronWolf 3.5" HDD
PCI-e to Dual SATA-II Interface Card
NAS case with fan and Pine64 power supply (5A)

With two HDDs connected, the system does not boot or crashes frequently (power cycle required to reboot). Before the crash, I can hear the HDDs repeatedly "trying to spin up". I tried with different OS images, including ayufans openmediavault builds (version 0.9.14, armhf and arm64) and "vanilla" armbian buster server (kernel 4.4). Both HDDs are working (tested using an USB-to-SATA adapter) and both SATA cables are tested and OK. Powering the HDDs with a separate PSU didn't help, so the power supply is not the problem.

Connecting only one hard drive to either of the two SATA connectors works without problems. I also tried hot-plugging the second hard drive, which results in the following dmesg output (repetitive, for ata1 or ata2):

I got my PineTime dev kit this morning.  Very nice packaging.  When I unpacked everything I found that the case back had come off the watch.  I have been trying to get get the two parts of the watch together so I can charge it for over 30 minutes with no luck.  It looks like the case back should just snap onto the watch but no matter how hard I press this does not happen.  I have the back properly positioned, with the charging pins over the metal connectors on the circuit board.  Is there a trick to getting the case back onto the watch?

Will the PinePhone accept any Linux operating system.

Is it possible to install Arch Linux on the PinePhone.
I discovered [/url]Project Anakin 
 [url=http://wiki.pine64.org/index.php/Project_Anakin]

and wondered why it isn't listed as a primary operating system for the PinePhone, since this phone is an opensource project.

Like raspberry pi and lattepanda does pine64's rockpro64 has mechanism to automatically reboot or (boot as soon as power is plugged in )in case it shutsdown abruptly ?

It has become apparent to me that charging via USB-C only works properly (fast) when the PBP is on.
The suspicion is that this has to do with PD negotiation failing when the device is powered off. This results in slow standard USB charging.

The graph below shows the charging pattern with the device on (orange boxes) and off (between the two boxes).
I'll talk to the relevant people and ask about what can be done. In the meantime, if you want your PBP to charge at its optimal using USB-C, make sure that its turned on.

This doesn't affect charging via the barrel jack.
It may be a issue specific to the default Debian MATE or other OSs too - haven't checked. Please report below if you've got experience with other OSs.

What is/was the order deadline for the next production run?
General timetable information would be appreciated as well. (with the understanding that everything is estimates/plans, not promises)

This is probably in a thread somewhere, but I looked for 5 minutes, and didn't find it.
Also, I'm lazy/wondering why it's not a pinned thread.

Here is a guide of how I repartitioned my eMMC to allow for a physical swap partition, and used GPT partition layout, (instead of DOS).
Basically you need an 8GB or larger SD card you can over-write.

Note that both Linux experience and command line familiarity is required. Any mistake and you could accidentally overwrite your working OS. Last, backups, (preferably multiple), is recommended.

This copies the low level boot information: