I just got my rockpro64 and I am trying to get it setup to run kodi and retroarch.  I have it running on the bionic-lxde-rockpro64-0.7.9-1067-arm64.img.xz image.  But I have no sound in kodi.  Sound works in mplayer after removing pulseaudio, but it gives the "your system is too slow" warning when trying to play any 1080p videos.

I have read the threads on the 7” LCD that Pine sells.

I am looking to get this working on the Rock64Pro, but using the Bionic LXDE image.

1. No LCD by default. No power on, no backlight. HDMI works by default.
2. I tried setting the uEvb.txt lines, but that doesn’t existing in /boot/. Adding it had no effect.

Anyone able to help point me in the right direction?

Hi everyone

I'd like to change the setting value (resolution, format, porch, etc..) of DSI.

Therefore, do the following procedure.

1. edit /boot/uEnv.txt
 add disp_screen0=lcd

2. edit /boot/pine64/sun50i-a64-pine64-plus.dtb 

I'm excited about the RockPro64. It just arrived the other day. Sadly, I can't get the PCI-E -> Sata adapter card (also bought through Pine64) to work.

Symptoms:
System locks up hard when anything tries to touch a drive connected to the PCI-E SATA ports. Something as simple as `lspci -v` or `cfdisk /dev/sda` will lock the system and force a reset. Attempting to mount a partition has the same result.

Things I've ruled out:
It's not the drive. I tried multiple drives, all of which work fine in other systems. I was able to mount and use the same drives on my rockpro64 using an old usb2->sata adapter that I had lying around.
I don't think it's the OS images. I tried ayufan's lxde and minimal images, the latest stable 0.7.9 version.
I don't think it's this flaw: https://forum.pine64.org/announcements.php?aid=6 ... my board has a date stamp of 2018-06-06 and the schematics in that engineering notice do not match the power regulator design on my board.

Things I suspect:
I'm not an EE and it's likely that I don't know what I'm looking at, but I suspect there may still be a PCI-E power regulation defect in these boards. Yes, despite the hardware rev. `grep pcie /var/log/syslog` turns up lots of weirdness, including:

Hi,

I'm designing a camera board to interface with the rockpro64 CSI-2 connector. Here're some questions I have because I could not find a hardware user guide for this board.

 1. What DVP_PDN stands for?
Pin 12 on the connector DVP_PDN1 and DVP_PDN0_H are each connected to a GPIO. Since MIPI_RST already has a RC delayed pull up for reset. I'm not sure what's this for. Or this can be used for any purpose?

2. I2C multiplexing
It appears all three connectors share a single I2C interface. Thus I'm not sure how it will be used if both sensor has the same slave ID especially in a dual cam HDR application. And it appears many Sony sensors shared the slave ID across variety of chips based on driver code on github.

3. Power voltage
I'm getting confused by the power voltage. On the connector it has two separate rails of 2.8V. Then a 1.2V and a 1.8V. But there's a note in the LDO section that says 1.8 is replaced with 2.8V? However many sensor out there, IMX214 included has one 1.8V. Can some engineer clarify this for me? Then there's a VCC5 and I assume that's constantly powered on?

Additional questions related to rock3399
4. CSI lane swapping
I can't find documentation on this. But many D-PHY is capable of lane swapping with register setting that controls the input MUX. I'm not sure if rock3399 has this capability. This will facilitate board layout.

Thanks!

Hi guys. The Rock64 OMV box throws up an error and refuses to update, using the "check" button on the Update Management Menu. Has anyone come across this? Any help appreciated.


Linux rock64 4.4.77-rockchip-ayufan-136 #1 SMP Thu Oct 12 09:14:48 UTC 2017 aarch64 GNU/Linux

Release: 3.0.99

Codename: Erasmus


"Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; apt-get update 2>&1' with exit code '100': Ign file: InRelease Ign file: Release.gpg Ign file: Release Ign file: Translation-en Get:1 http://security.debian.org jessie/updates InRelease [44.9 kB] Get:2 https://openmediavault.github.io erasmus InRelease [14.8 kB] Hit http://packages.openmediavault.org erasmus InRelease Get:3 https://openmediavault.github.io erasmus-proposed InRelease [6125 B] Hit http://security.debian.org jessie/updates/main Sources Hit http://ppa.launchpad.net xenial InRelease Hit http://security.debian.org jessie/updates/contrib Sources Hit .........snip

When I plug any storage device into the USB3 port any ssh session is aborted.  Im using Ubuntu 64bit minimal = Ubuntu 18.04.1 LTS (GNU/Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 aarch64)

One device is an SSD that is using UAS, I know that is a problem but there is no /etc/modprobe.d/rk3328-usb-storage-quirks.conf file as in this thread: https://forum.pine64.org/showthread.php?tid=5137&page=2

Adding it does not solve the problem even when resarting twice (yes, I did!).

However even plugging a standard USB pen drive that does not use UAS still causes the SSH session to drop, and even when I manage to SSH back in, the terminal is really slow, as soon as the pen drive is removed, things go back to normal.

Putting any drive in the USB2 port, has none of these impacts, including the SSD.

I have spend a while configuring a bunch of stuff on this distro now, only to find this new quirk, can anyone give some pointers as to how I can get the USB3 working properly please?

EDIT: I forgot to say the network connection ison a WiFi USB donglein one of the USB2 ports.

I didn't even see this until today but I do understand why some would not like to go with Windows 10. It seems that Microsoft is working on a full version of windows 10 on arm/arm64 computers. People have even gotten it to work on the RPi 3b+, as sad as that is, very slow.

I'm setting up an ISO right now but not sure it will work.

downloaded the image. There is a utility they made to set it up for the RPi

you need a USB driver and a UEFI to set it up.

In theory, the USB driver the RPi is using might work already. The question then comes in to the UEFI file.

Hello everyone!

I am excited to announce the KDE Neon Pinebook remix edition release candidate image.

https://dot.kde.org/2018/08/22/kde-plasm...p-pinebook

Image includes the,

• KDE Neon packages for Ubuntu bionic (18.04)
  
• KDE Plasma 5.13.4
  
• KDE Frameworks 5.49.0
  
• Qt 5.11.1
  
• Linux kernel 3.10.105-bsp-1.2
  

• Resuming from sleep is fixed
  
• Broken audio after resuming from sleep
  
• Bluetooth
  
• Palm rejection (Disable "touchpad" while typing)
  
• Disable/enable speakers when plugging/unplugging headphones
  
• Disable accidental zoom invocation when scrolling in firefox
  

• Lack of real suspend, I believe this is due to choice of driver we are using, and currently turning lid off puts device to sleep and not suspend like mate image.
  
• Sleep inverts the brightness control, after waking up from sleep brightness control are inverted.
  

• Proper suspend support instead of just sleep
  
• Fix for the inverted brightness after waking up from sleep/suspend
  
• Support for 1080p 11' IPS LCD pinebook
  

• kcminit process is crashing in background continuously
  

Hi


Is there an official build environment construction method and build procedure for the following Linux environment?
If not, please tell me.

https://github.com/ayufan-pine64/linux-build

Thank you.