Defective? PCI-E -> SATA card no work good
#1
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?
  Reply
#2
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:

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. Started Bionic minimal - now "focal", Openbox desktop for general purpose daily PC.
* PinePhone BraveHeart daily driver with Mobian
  Reply
#3
Hi,

my board v2.1 is running with bionic-minimal. I don't use any desktop systems atm, too many bugs. Please inform me, when its run well Big Grin


Code:
rock64@rockpro64v2_1:~$ uname -a
Linux rockpro64v2_1 4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee #1 SMP Thu Aug 9 20:29:55 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux


dmesg


Code:
rock64@rockpro64v2_1:~$ dmesg | grep -E pcie
[    0.506998] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[    0.507045] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[    0.507084] vcc3v3_pcie: supplied by dc_12v
[    0.507136] vcc3v3_pcie: 3300 mV
[    0.507304] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[    2.868298] vcc3v3_pcie: disabling
[    3.171478] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[    3.171482] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[    3.278691] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[    3.278715] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[    3.278812] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
[    3.279319] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[    3.279493] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[    3.279515] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[    3.279564] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    3.289691] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[    3.289716] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[    3.289776] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    3.299851] rockchip-pcie f8000000.pcie: invalid power supply
[    3.848058] PCI host bridge /pcie@f8000000 ranges:
[    3.875577] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    3.905032] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[    3.905397] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[    3.905408] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
[    3.905516] aer 0000:00:00.0:pcie02: service driver aer loaded


lspci

Code:
rock64@rockpro64v2_1:~$ sudo lspci -vvv
[sudo] password for rock64:
00:00.0 PCI bridge: Rockchip Inc. RK3399 PCI Express Root Port Device 0100 (prog-if 00 [Normal decode])
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ <TAbort+ <MAbort+ >SERR+ <PERR+ INTx-
    Latency: 0
    Interrupt: pin A routed to IRQ 238
    Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
    I/O behind bridge: 00000000-00000fff
    Memory behind bridge: fa000000-fa0fffff
    Prefetchable memory behind bridge: 00000000-000fffff
    Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
    BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
        PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
    Capabilities: [80] Power Management version 3
        Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
        Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME+
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable+ 64bit+
        Address: 00000000fee30040  Data: 0000
        Masking: 00000000  Pending: 00000000
    Capabilities: [b0] MSI-X: Enable- Count=1 Masked-
        Vector table: BAR=0 offset=00000000
        PBA: BAR=0 offset=00000008
    Capabilities: [c0] Express (v2) Root Port (Slot+), MSI 00
        DevCap:    MaxPayload 256 bytes, PhantFunc 0
            ExtTag- RBE+
        DevCtl:    Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
            RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
            MaxPayload 128 bytes, MaxReadReq 512 bytes
        DevSta:    CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
        LnkCap:    Port #0, Speed 5GT/s, Width x4, ASPM L1, Exit Latency L0s <256ns, L1 <8us
            ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
        LnkCtl:    ASPM Disabled; RCB 64 bytes Disabled- CommClk-
            ExtSynch- ClockPM- AutWidDis- BWInt+ AutBWInt+
        LnkSta:    Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
        SltCap:    AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
            Slot #0, PowerLimit 0.000W; Interlock- NoCompl-
        SltCtl:    Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
            Control: AttnInd Off, PwrInd Off, Power+ Interlock-
        SltSta:    Status: AttnBtn- PowerFlt- MRL+ CmdCplt- PresDet- Interlock-
            Changed: MRL- PresDet- LinkState-
        RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
        RootCap: CRSVisible-
        RootSta: PME ReqID 0000, PMEStatus- PMEPending-
        DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via message ARIFwd+
        DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
        LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
             Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
             Compliance De-emphasis: -6dB
        LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
             EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
    Capabilities: [100 v2] Advanced Error Reporting
        UESta:    DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
        UEMsk:    DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
        UESvrt:    DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
        CESta:    RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
        CEMsk:    RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
        AERCap:    First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
    Capabilities: [274 v1] Transaction Processing Hints
        Interrupt vector mode supported
        Device specific mode supported
        Steering table in TPH capability structure
    Kernel driver in use: pcieport

01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
    Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Interrupt: pin A routed to IRQ 239
    Region 0: I/O ports at <unassigned> [disabled]
    Region 1: I/O ports at <unassigned> [disabled]
    Region 2: I/O ports at <unassigned> [disabled]
    Region 3: I/O ports at <unassigned> [disabled]
    Region 4: I/O ports at <unassigned> [disabled]
    Region 5: Memory at fa010000 (32-bit, non-prefetchable) [size=512]
    [virtual] Expansion ROM at fa000000 [disabled] [size=64K]
    Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Address: fee30040  Data: 0000
    Capabilities: [78] Power Management version 3
        Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [80] Express (v2) Legacy Endpoint, MSI 00
        DevCap:    MaxPayload 512 bytes, PhantFunc 0, Latency L0s <1us, L1 <8us
            ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
        DevCtl:    Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
            RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
            MaxPayload 128 bytes, MaxReadReq 512 bytes
        DevSta:    CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
        LnkCap:    Port #1, Speed 5GT/s, Width x1, ASPM not supported, Exit Latency L0s unlimited, L1 <2us
            ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
        LnkCtl:    ASPM Disabled; RCB 64 bytes Disabled- CommClk-
            ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
        LnkSta:    Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR-, OBFF Not Supported
        DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
        LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
             Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
             Compliance De-emphasis: -6dB
        LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
             EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
    Capabilities: [100 v1] Virtual Channel
        Caps:    LPEVC=0 RefClk=100ns PATEntryBits=1
        Arb:    Fixed- WRR32- WRR64- WRR128-
        Ctrl:    ArbSelect=Fixed
        Status:    InProgress-
        VC0:    Caps:    PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
            Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
            Ctrl:    Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
            Status:    NegoPending- InProgress-
    Kernel driver in use: ahci



I am using three HDD/SDD's


Code:
rock64@rockpro64v2_1:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            992M     0  992M   0% /dev
tmpfs           200M  484K  199M   1% /run
/dev/sda7       235G  106G  120G  47% /
tmpfs           996M     0  996M   0% /dev/shm
tmpfs           5,0M  4,0K  5,0M   1% /run/lock
tmpfs           996M     0  996M   0% /sys/fs/cgroup
/dev/sda6       112M  4,0K  112M   1% /boot/efi
/dev/sdb1       932G  128G  803G  14% /mnt
/dev/sdc3       1,2G  1,2G     0 100% /media
tmpfs           200M     0  200M   0% /run/user/1000


sda = USB3 SSD Samsung Pro 256GB
sdb = SATA 1TB HDD
sdc = SATA 250GB SSD (ipfire image = 2GB - i know)

uptime


Quote:rock64@rockpro64v2_1:~$ uptime
 16:55:05 up 20:08,  1 user,  load average: 0,00, 0,00, 0,00

Only problem i know is that usb3 isn't stable atm.
Sorry for any mistakes. English is not my native language

1. RP64 v2.1 / PCIe SATA Marvell 88SE9230 Chipsatz / sd-card / 2 * 3,5 Zoll 4TB HDD (raid1) / using as NAS / Kernel 4.4.202-1237-rockchip-ayufan-gfd4492386213 / Booting from an USB3 SSD

2. RP64 v2.1 / testing.....testing....testing 

https://forum.frank-mankel.org/category/14/rockpro64
  Reply
#4
Oh ... ah ... HA!
You guys set me on the right track, thanks! Solved!!!

The problem has little to do with minimal vs lxde. The main problem with the lxde build is that it only comes with a single processor architecture: ARM64. I was able to replicate the same symptoms on the minimal bionic image, but I was using the arm64 build. I switched to armhf and everything worked fine.

Moral of the story: If you want to use PCI-E attached SATA, you must use a build that targets the ARMHF architecture. I'm trying to figure out why installing a desktop environment on top of the armhf build fails. It seems like an unrelated problem; it seems to boot (and I can see it detect my sata drive in the process) all the way to the text login screen, then freeze instead of properly starting x.

I'm still working on that and will report back if I find anything interesting. Until then, my apologies to Pine64 for misdiagnosing this as a hardware problem. If it is a hardware problem, it's not the voltage regulator. Maybe a bus conflict in 64-bit mode?
  Reply
#5
I am using only


Code:
https://github.com/ayufan-rock64/linux-build/releases/download/0.7.9/bionic-minimal-rockpro64-0.7.9-1067-arm64.img.xz

without an problem.

Code:
rock64@rockpro64v2_1:~$ dpkg --print-architecture
arm64


But nice if you could solve the problem. And there are certainly still some problems in ayufans images.
Sorry for any mistakes. English is not my native language

1. RP64 v2.1 / PCIe SATA Marvell 88SE9230 Chipsatz / sd-card / 2 * 3,5 Zoll 4TB HDD (raid1) / using as NAS / Kernel 4.4.202-1237-rockchip-ayufan-gfd4492386213 / Booting from an USB3 SSD

2. RP64 v2.1 / testing.....testing....testing 

https://forum.frank-mankel.org/category/14/rockpro64
  Reply
#6
That's strange and interesting. If I do not use the pci-e slot and leave it empty, my rockpro64 is consistently stable on either arm64 or armhf builds. When I have the sata controller and a sata drive plugged in, it consistently crashes on any arm64 build but is consistently stable on the armhf build.

Out of curiosity, what is the date stamp on your board? I wonder whether there is a difference between hardware revisions 2.0 vs 2.1.
  Reply
#7
Date stamp on my v2.1 is 2018-06-06
Sorry for any mistakes. English is not my native language

1. RP64 v2.1 / PCIe SATA Marvell 88SE9230 Chipsatz / sd-card / 2 * 3,5 Zoll 4TB HDD (raid1) / using as NAS / Kernel 4.4.202-1237-rockchip-ayufan-gfd4492386213 / Booting from an USB3 SSD

2. RP64 v2.1 / testing.....testing....testing 

https://forum.frank-mankel.org/category/14/rockpro64
  Reply
#8
Thanks. I'll test again, making sure to check the md5's of my .img files to be sure I don't have a bad copy.
  Reply
#9
Well, color me embarrassed. I downloaded fresh copies of the bionic minimal 0.7.9 images and everything works on both arm64 and armhf architectures. This must have all been caused by either a corrupt download or a bad 'dd'. For future reference in case anyone else with similar symptoms finds this thread, the valid checksums appear to be:

Code:
5db9865d01da5370d9d1b8c11945df53  ./bionic-minimal-rockpro64-0.7.9-1067-armhf.img

7856fe0e0c0d162cbbc08d6e2070e97d  ./bionic-minimal-rockpro64-0.7.9-1067-arm64.img

The system lockup from the bionic lxde image is still sort of a thing. There's nothing in the syslog because it technically isn't a lockup -- lspci will cause 100% CPU usage. I'll see if I can dig into this further to find why, but it's a separate topic. Unfortunately, I probably won't have time to work on it again for a couple of days.

Thanks for the input, all.
  Reply
#10
Nice that you could fix the error
Sorry for any mistakes. English is not my native language

1. RP64 v2.1 / PCIe SATA Marvell 88SE9230 Chipsatz / sd-card / 2 * 3,5 Zoll 4TB HDD (raid1) / using as NAS / Kernel 4.4.202-1237-rockchip-ayufan-gfd4492386213 / Booting from an USB3 SSD

2. RP64 v2.1 / testing.....testing....testing 

https://forum.frank-mankel.org/category/14/rockpro64
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Mainline U-Boot with SPI, NVMe and SATA boot support sigmaris 35 4,956 06-18-2020, 05:20 AM
Last Post: sivar93
  4pin Connector for dual SATA m.ekstrom 2 198 05-14-2020, 02:33 AM
Last Post: mabs
  micro SD Card Slot Spring not working, Cant boot mjembd 1 140 04-16-2020, 12:30 AM
Last Post: mjembd
  Spotify - work arround with librespot-java Helium75 0 246 12-08-2019, 06:53 AM
Last Post: Helium75
  for what purpose Pine64 added PCIEx4 card on this sbc ? seaurchin 4 478 11-25-2019, 11:33 AM
Last Post: dukla2000
  Shadow Game streaming - does it work? korn2017 1 254 06-13-2019, 07:30 PM
Last Post: tllim
Sad RockPro64 with OpenMediaVault - Ethernet card is not recognized eduapof 8 968 04-18-2019, 08:28 AM
Last Post: g_t_j
  Usb3 to sata and USB C to sata / openmedia RockPro64Newbie 1 429 01-19-2019, 04:45 PM
Last Post: oreggin
  SD Card UHS speed hopkinskong 5 1,061 12-06-2018, 05:52 PM
Last Post: z4v4l
  Good advances in Panfrost Open Source driver tuxd3v 1 534 10-23-2018, 08:14 PM
Last Post: tllim

Forum Jump:


Users browsing this thread: 1 Guest(s)