Hopefully Bullet64 will be along shortly - he has played with the PCIe/SATA card AFAIK. You are correct, with a v2.1 board you shouldnt need your soldering iron.
I thought the symptoms you have were common with Ubuntu LXDE and Debian release, but were avoided by using Ubuntu minimal - unclear whether the minimal you tried was Debian or Ubuntu?
Those pcie power errors are indeed worrying, but in fact "normal" at the moment! I suspect a bit more tuning of the DTB will help but FWIW here is mine:
Up to 3.303s all kinds of noise while initialising the PCIe itself. From 3.375s it finds my NVMe card and drive, stuff in log is far more convincing and of course the NVMe is working fine.
I thought the symptoms you have were common with Ubuntu LXDE and Debian release, but were avoided by using Ubuntu minimal - unclear whether the minimal you tried was Debian or Ubuntu?
Those pcie power errors are indeed worrying, but in fact "normal" at the moment! I suspect a bit more tuning of the DTB will help but FWIW here is mine:
Code:
chris@rpro64:~$ uname -a
Linux rpro64.dukla.net 4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee #1 SMP Thu Aug 9 20:29:55 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
chris@rpro64:~$ dmesg | grep pcie
[ 0.505926] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[ 0.505975] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[ 0.506012] vcc3v3_pcie: supplied by dc_12v
[ 0.506077] vcc3v3_pcie: 3300 mV
[ 0.506234] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[ 2.746029] vcc3v3_pcie: disabling
[ 3.212576] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[ 3.212580] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[ 3.290021] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[ 3.290037] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[ 3.290098] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
[ 3.290367] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[ 3.290534] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[ 3.290543] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[ 3.290577] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[ 3.296888] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[ 3.296908] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[ 3.296943] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[ 3.303085] rockchip-pcie f8000000.pcie: invalid power supply
[ 3.375546] PCI host bridge /pcie@f8000000 ranges:
[ 3.404009] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[ 3.479670] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[ 3.485299] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[ 3.497076] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
[ 3.497282] aer 0000:00:00.0:pcie02: service driver aer loaded
Up to 3.303s all kinds of noise while initialising the PCIe itself. From 3.375s it finds my NVMe card and drive, stuff in log is far more convincing and of course the NVMe is working fine.
- ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Arch (6.2 kernel, Openbox desktop) for general purpose daily PC.
- PinePhone Pro Explorer Edition, daily driver, rk2aw & U-boot on SPI, Arch/SXMO & Arch/phosh on eMMC
- PinePhone BraveHeart now v1.2b 3/32Gb, Tow-boot with Arch/SXMO on eMMC