+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=98)
+--- Forum: Linux on RockPro64 (https://forum.pine64.org/forumdisplay.php?fid=101)
+--- Thread: Sata/PCI-E problems? (/showthread.php?tid=6595)
Sata/PCI-E problems? - Takenover83 - 09-26-2018
I am currently running Ubuntu 18.04 Bionic minimal 0.7.9, with a custom 4.18.9 kernel. Although I have tried others kernels as well. My board is in the NAS enclosure with the 30mm heatsink and a 80mm fan (5-amp power supply). I am running it as a server for Plex, Radarr, Sonarr, Jackett, Deluge, Ombi, and Tautulli.
I am currently experiencing a strange problem with the sata drive, a Western Digital 8TB Red Drive. Or perhaps the problem is with the pci-e card, not sure. I often have quiet a few torrents downloading via deluge. Usually about once or twice a day, I come back to see all of my torrents have error'ed out. Likely, because the drive is somewhat disconnected? Doing a df -h shows it is still mounted, but the drive will not function properly until I do a complete power down. Just curious if anyone else has experienced any troubles similar to this. Either way I am documenting the problem here just in case someone else experiences the problem in the future and can chime in.
RE: Sata/PCI-E problems? - mocara - 09-30-2018
I've not had a happy experience with the Pine64 supplied PCI-e card either. Same as you, I have the NAS Case, etc, etc. In my situation, though I have just a single SSD and I get a load of dump type messages as it boots. I have seen the blue LED on the PCI-e card just once but then couldn't access the SSD card at all. I have tried a couple of different SSDs with no better success. Even just the PCI-e card on its own causes problems at boot time with some odd messages, leading me to believe that I have somehow killed the card.. Using the same Linux build as yourself as well. Also tried using the OMV build with much the same results.
I'm nearly to the point of giving a 3rd party card a try!! In the mean time I'm using a USB3 to SATA cable to connect the SSD, which of course works just fine. Not good though if I want to add another drive.
RE: Sata/PCI-E problems? - Bullet64 - 09-30-2018
With pin64 nvme adapter no m.2 sata card will work. You must use an m.2 nvme card.
My Samsung 960 EVO 256GB NVMe SSD works fine
RE: Sata/PCI-E problems? - jja2000 - 10-15-2018
I've been having trouble getting my Pine bought PCIe SATA card to work aswell.
It used to show up before but then totally disappear. The HDD spins up but does not show up in lsblk or in dmesg. There's no LED burning on the card. The HDD works aswell.
Doing a dmesg | grep pci gives me this:
Code:
rock64@rockpro64:~$ dmesg | grep pci
[ 0.498071] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[ 0.498129] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[ 0.498167] vcc3v3_pcie: supplied by dc_12v
[ 0.498232] vcc3v3_pcie: 3300 mV
[ 0.498386] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[ 1.177078] ehci-pci: EHCI PCI platform driver
[ 2.656712] vcc3v3_pcie: disabling
[ 3.114214] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[ 3.114218] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[ 3.292837] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[ 3.292852] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[ 3.292902] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
[ 3.293278] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[ 3.293470] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[ 3.293483] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[ 3.293518] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[ 3.302175] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[ 3.302195] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[ 3.302230] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[ 3.313324] rockchip-pcie f8000000.pcie: invalid power supply
[ 3.820353] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 3.830861] rockchip-pcie: probe of f8000000.pcie failed with error -110RE: Sata/PCI-E problems? - xtract - 10-15-2018
Have you guys tried with mainline kernel? I have a marvell sata card and I haven't noticed any problem, all my torrents complete and docker containers either.
RE: Sata/PCI-E problems? - jja2000 - 10-15-2018
(10-15-2018, 11:23 AM)xtract Wrote: Have you guys tried with mainline kernel? I have a marvell sata card and I haven't noticed any problem, all my torrents complete and docker containers either.
I haven't tried it yet no, though it would be weird if this SATA card doesn't work since it's the one Pine sell in their store.
RE: Sata/PCI-E problems? - jja2000 - 10-20-2018
(10-15-2018, 05:28 AM)jja2000 Wrote: I've been having trouble getting my Pine bought PCIe SATA card to work aswell.
It used to show up before but then totally disappear. The HDD spins up but does not show up in lsblk or in dmesg. There's no LED burning on the card. The HDD works aswell.
Doing a dmesg | grep pci gives me this:
Code:rock64@rockpro64:~$ dmesg | grep pci
[ 0.498071] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[ 0.498129] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[ 0.498167] vcc3v3_pcie: supplied by dc_12v
[ 0.498232] vcc3v3_pcie: 3300 mV
[ 0.498386] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[ 1.177078] ehci-pci: EHCI PCI platform driver
[ 2.656712] vcc3v3_pcie: disabling
[ 3.114214] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[ 3.114218] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[ 3.292837] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[ 3.292852] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[ 3.292902] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
[ 3.293278] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[ 3.293470] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[ 3.293483] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[ 3.293518] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[ 3.302175] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[ 3.302195] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[ 3.302230] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[ 3.313324] rockchip-pcie f8000000.pcie: invalid power supply
[ 3.820353] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 3.830861] rockchip-pcie: probe of f8000000.pcie failed with error -110
Okay so I installed mainline and I get a similar error:
Code:
rock64@rockpro64:~$ dmesg | grep pci
[ 1.709157] vcc3v3_pcie: supplied by dc_12v
[ 2.994902] ehci-pci: EHCI PCI platform driver
[ 3.051118] ohci-pci: OHCI PCI platform driver
[ 3.468181] vcc3v3_pcie: disabling
[ 6.753355] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[ 6.753416] rockchip-pcie f8000000.pcie: Linked as a consumer to regulator.3
[ 6.753431] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[ 6.753441] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[ 7.308970] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 7.309707] rockchip-pcie f8000000.pcie: Dropping the link to regulator.3
[ 7.309778] rockchip-pcie: probe of f8000000.pcie failed with error -110But it happens a lot less consistently, mostly reboots and a bit of reseating of the cables makes it function again.