Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,690
» Latest member: Noah Waverly
» Forum threads: 16,258
» Forum posts: 117,181

Full Statistics

Latest Threads
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
2 hours ago
» Replies: 0
» Views: 23
Cannot install spotify, l...
Forum: Mobian on PinePhone
Last Post: Noah Waverly
6 hours ago
» Replies: 4
» Views: 5,948
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
10 hours ago
» Replies: 0
» Views: 22
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: Harleydogisich
Yesterday, 10:51 PM
» Replies: 4
» Views: 2,055
Battery Life on Latest In...
Forum: General
Last Post: ouglastam
Yesterday, 08:47 AM
» Replies: 1
» Views: 1,911
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
Yesterday, 07:49 AM
» Replies: 0
» Views: 51
Second screen mirroring
Forum: General
Last Post: andrekyler
Yesterday, 01:06 AM
» Replies: 3
» Views: 1,878
7 inch touch panel patche...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: mkjmkj
Yesterday, 12:57 AM
» Replies: 0
» Views: 52
Pine64 LTS v1.2 not turni...
Forum: P64-LTS / SOPINE Hardware, Accessories and POT
Last Post: in_sympathy
11-16-2025, 08:09 PM
» Replies: 0
» Views: 41
I think you can try compi...
Forum: General Discussion on Pinebook Pro
Last Post: wangyukunshan
11-14-2025, 05:27 AM
» Replies: 1
» Views: 267

 
  Defective? PCI-E -> SATA card no work good
Posted by: unregisteredidiot - 08-22-2018, 08:58 PM - Forum: General Discussion on ROCKPRO64 - Replies (11)

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:


Code:
Jul 26 08:43:40 rockpro64 kernel: [    0.504648] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
Jul 26 08:43:40 rockpro64 kernel: [    0.504700] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    0.504739] vcc3v3_pcie: supplied by dc_12v
Jul 26 08:43:40 rockpro64 kernel: [    0.504804] vcc3v3_pcie: 3300 mV
Jul 26 08:43:40 rockpro64 kernel: [    0.504959] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
Jul 26 08:43:40 rockpro64 kernel: [    2.854241] vcc3v3_pcie: disabling
Jul 26 08:43:40 rockpro64 kernel: [    3.185787] phy phy-pcie-phy.9: Looking up phy-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    3.185794] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
Jul 26 08:43:40 rockpro64 kernel: [    3.242826] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
Jul 26 08:43:40 rockpro64 kernel: [    3.242833] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
Jul 26 08:43:40 rockpro64 kernel: [    3.242849] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
Jul 26 08:43:40 rockpro64 kernel: [    3.242997] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    3.243058] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    3.243063] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
Jul 26 08:43:40 rockpro64 kernel: [    3.243081] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
Jul 26 08:43:40 rockpro64 kernel: [    3.246321] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    3.246332] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
Jul 26 08:43:40 rockpro64 kernel: [    3.246349] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
Jul 26 08:43:40 rockpro64 kernel: [    3.249224] rockchip-pcie f8000000.pcie: invalid power supply
Jul 26 08:43:40 rockpro64 kernel: [    3.297572] PCI host bridge /pcie@f8000000 ranges:
Jul 26 08:43:40 rockpro64 kernel: [    3.312065] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
Jul 26 08:43:40 rockpro64 kernel: [    3.396326] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
Jul 26 08:43:40 rockpro64 kernel: [    3.399224] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
Jul 26 08:43:40 rockpro64 kernel: [    3.404688] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
Jul 26 08:43:40 rockpro64 kernel: [    3.404779] aer 0000:00:00.0:pcie02: service driver aer loaded
Aug 23 01:44:21 rockpro64 kernel: [  854.222319] Modules linked in: zram lz4_compress rockchip_saradc ip_tables x_tables autofs4 phy_rockchip_pcie midgard_kbase dw_hdmi_i2s_audio
Aug 23 01:48:14 rockpro64 kernel: [    0.502604] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
Aug 23 01:48:14 rockpro64 kernel: [    0.502653] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    0.502693] vcc3v3_pcie: supplied by dc_12v
Aug 23 01:48:14 rockpro64 kernel: [    0.502758] vcc3v3_pcie: 3300 mV
Aug 23 01:48:14 rockpro64 kernel: [    0.502914] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
Aug 23 01:48:14 rockpro64 kernel: [    2.926112] vcc3v3_pcie: disabling
Aug 23 01:48:14 rockpro64 kernel: [    3.390905] phy phy-pcie-phy.9: Looking up phy-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    3.390914] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
Aug 23 01:48:14 rockpro64 kernel: [    3.479972] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
Aug 23 01:48:14 rockpro64 kernel: [    3.479988] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
Aug 23 01:48:14 rockpro64 kernel: [    3.480049] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
Aug 23 01:48:14 rockpro64 kernel: [    3.480441] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    3.480703] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    3.480717] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
Aug 23 01:48:14 rockpro64 kernel: [    3.480757] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
Aug 23 01:48:14 rockpro64 kernel: [    3.489203] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    3.489223] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
Aug 23 01:48:14 rockpro64 kernel: [    3.489259] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
Aug 23 01:48:14 rockpro64 kernel: [    3.497732] rockchip-pcie f8000000.pcie: invalid power supply

...halp? What do? I'm not sure how to troubleshoot this further. I'm 90% sure this is hardware related. If there is a known fix, I'm a steady hand with a soldering iron or a rework station. If there's not a known fix, is there a way to return this whole setup?


  CSI-2 MIPI
Posted by: astronomer - 08-22-2018, 04:18 PM - Forum: RockPro64 Hardware and Accessories - Replies (1)

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!


  OpenMediaVault fails to update
Posted by: S265 - 08-22-2018, 03:09 PM - Forum: Linux on Rock64 - Replies (3)

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


  USB3 problems
Posted by: scalextrix - 08-22-2018, 10:47 AM - Forum: Linux on Rock64 - Replies (2)

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.


  Windows 10 on ARM
Posted by: Firesped - 08-22-2018, 06:30 AM - Forum: General Discussion on ROCKPRO64 - Replies (3)

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.


  KDE Neon Pinebook remix edition RC image
Posted by: bshah - 08-22-2018, 02:04 AM - Forum: Linux on Pinebook - Replies (67)

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
Initially username/password is live/live

You can download .img.gz from,

https://files.kde.org/neon/images/pinebo...0821-1118/

New image 20180917-1726:

https://files.kde.org/neon/images/pinebo...0917-1726/

There are several fixes included,
  • 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
Errata:
  • 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.
New release: https://files.kde.org/neon/images/pinebo...1028-1500/

Fixes included
  • 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
Errata
  • kcminit process is crashing in background continuously
Looking forward to your feedback in comments section.

In general images are rolling model, so you can find most recent image from this URL: https://files.kde.org/neon/images/pinebook-remix-nonfree/useredition

[edit Luke]: For those of you looking for detailed instructions, please see this post further on in the thread.

Thanks.


  Official build procedure of ayufan pine64
Posted by: r.tanaka - 08-21-2018, 10:54 PM - Forum: Linux on Pine A64(+) - No Replies

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.


  How to change DSI setting value from DTS
Posted by: r.tanaka - 08-21-2018, 08:05 PM - Forum: Ubuntu - Replies (8)

Hi

I would like to customize DSI settings value (resolution, format, pouch etc.).
Therefore, I am planning to change the setting value from DTS.

Is there any document that describes how to change DTS and how to build it?
If it does not exist, I would like to know how to change DTS and build DTS.

The software and hardware used are as follows.
 software : https://github.com/ayufan-pine64/linux-build (xenial-minimal-pine64-bspkernel-0.7.19-118.img.xz)
 hardware : PINE A64+ 1GB

Thank you.


  How to control the SOPINE UART and SPI pins as GPIO?
Posted by: Pine - 08-21-2018, 05:55 PM - Forum: General Discussion on PINE A64-LTS / SOPINE - Replies (1)

The StackOverflow community took a look at the schematic for the 20-pin header beside the SOPINE modules on the clusterboard and said that it should be possible to configure the SOPINE hardware to use the UART and SPI pins as GPIO. One user commented:

"Most MCUs and SoCs have multiple functions on each pin. The SPI 'pins' are just one of those alternative functions. As long as you're not using SPI, and don't have it configured, those pins are just plain GPIO pins"

I'd like one of them to operate a simple low-power LED that is either on or off, controlled by software, to indicate busy status (not if the board is powered on or off). Any ideas how to get started?


  rock64 hdd from usb3.0
Posted by: baszek - 08-21-2018, 07:35 AM - Forum: General - Replies (4)

Hi, 
I would like to ask is it possible to power some HDD from USB 3.0 on Rock64 sbc ? 
I mean without external power - just from usb - probably it should run fine with some external enclosure and 2.5" 5400rpm HDD or SSD ?