Using a SanDisk Extreme V30 128GB. Also tring with samsung Evo+

AOSC working without problems.

Each time I boot different errors, usually mounting /tmp, zram or other similar. Sometimes stack trace and automatic reboot.

Latest dev builds are broken?

Thanks

Hello

Using a SanDisk Extreme V30 128GB, max read and write speed with AOSC is 22MB/s...the same like my old Raspberry Pi 2 . This microSD is capable of much more speed.

The same with desktop performance in Mate. Slow as hell.

Any tuning tips?


Thanks.

I'm hoping someone can help with a problem I have with a new NAS build using OMV.

I have a RockPro 64, Pine64 NAS case, two ST8000DM004-2CX1 drives, 16 GB eMMC boot, Pine 5A supply. I am running Open Media Vault stretch-openmediavault-rockpro64-0.7.9-1067-armhf.img.xz (Linux rockpro64 4.4.132-1075-rockchip-ayufan-ga83beded8524 #1 SMP Thu Jul 26 08:22:22 UTC 2018 aarch64 GNU/Linux) with all updates listed in OMV applied.

Sometimes during boot, the SATA PCI board does not get power and thus OMV sees no data drives. I have confirmed with a DVM there is no 12VCC on the SATA controller chip pin 48 when this happens. About half the time it boots up correctly and OMV seems to work OK. I get ~100 MB/s over gigabit Ethernet from a PC to the NAS, so the performance is good.  I have checked the +12V input to the RockPro64 and it ramps up monotonically when the power supply is connected, and only sags to 11.8V while the drives are spinning up.

When it's working, lspci -vvv says:

00:00.0 PCI bridge: Device 1d87: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 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: -6dB, 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 01) (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 <512ns, L1 <2us
            ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
        LnkCtl:    ASPM Disabled; RCB 64 bytes Disabled- CommClk-
            ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
        LnkSta:    Speed 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: -6dB, 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

When it's not working lspci -vvv says nothing.

Looking at dmesg in both cases, I see suspicious entries about power configuration, but they are the same in both the working and no PCI power case:



    0.502678] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[    0.502716] vcc3v3_pcie: supplied by dc_12v
[    0.502740] dc_12v: could not add device link regulator.2 err -2
[    0.502781] vcc3v3_pcie: 3300 mV
[    0.502937] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[    0.502989] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc1v8-s0[0]'
[    0.503005] vcc1v8_s0: 1800 mV
[    0.503152] reg-fixed-voltage vcc1v8-s0: vcc1v8_s0 supplying 1800000uV

[    2.053627] vcc3v3_pcie: disabling


The key difference in the dmesg outputs is the one that has no PCI power says:

 rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
 rockchip-pcie: probe of f8000000.pcie failed with error -110

The one that works has a long section of status messages that begins:

 PCI host bridge /pcie@f8000000 ranges:
   MEM 0xfa000000..0xfbdfffff -> 0xfa000000
    IO 0xfbe00000..0xfbefffff -> 0xfbe00000
 rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00

This failure mode is easily observable during boot. If there is power to the SATA controller card, you can see it's LED blink through the case grille. If there is no power to the board, no LED of course.

Does anyone have any ideas about what I could do to troubleshoot this? I don't want a file server that only boots 1/2 the time.

SBC: RockPro64 v2.1
OS: DietPi v6.24.1 aarch64
DE: Mate

After several hours of running, I noticed the system has frozen.
Remote access with ssh also fails.

Going through the DIetPi forumns, I did not find any posts related
to a RoskPro64.

I've got DietPi v6.24.1 running on an Odroid XU4 and that OS is
not freezing up.

Any suggestions/recommendations will be greatly appreciated.

/Faradn
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Odroid XU4 2Gb
Pine64 RockPro64 4Gb

Hi everybody,

I just want to know if my rockpro64 is able to stream games through Shadow?

https://shadow.tech/int

There is a client for ubuntu. Does anybody have any experience so far?

Thanks in advance.

Hi

Is it just Android 6 that runs on the 1080P Pinebook or does Android 7 run on 1080P Pinebook too?

Many thanks
toca180

So, I'm still trying to get some stuff to work. I'm running Manjaro-ARM LXQT 19.04 from the SD card on the Pinebook 11". 

This is just a bog standard install from Etcher to the SD card, and booted from the Pinebook.
First things first: running some updates. Had some errors on one of the dependencies being install after the program relying on it... and some generics errors, and afterwards when my system was 'up to date' it wouldn't reboot or shutdown anymore. Had to hard-power down because even through the CLI "reboot" or "shutdown -hP now" would just give me a blank cursor and no response.

Sound.... I tried both running a youtube video and a local WAV file, no luck. I keep reading everywhere there is a wrong audio device selected or something muted... but when I run alsamixer and enable everything, I still have no sound! Stupid thing is, when I enable the microphone and boost it high enough, I will get horribly loud feedback, so the hardware is at least working... it must be a software issue. 

In the GUI, I have tried both 'volume mixer' settings: controlling ALSA or Pulseaudio. I have both and all to 100%.

When I start the "Pulseaudio Volume Control" from the menu, I get a small 'pop' from the speakers upon starting the app. No sound after that, however. The only option displayed under 'output devices' with "built-in audio stereo" is "analog output" and it's already at max (even 153% now) volume. The same for the "headphones" below that. At the bottom, it displays that I'm already showing "all output devices".

What am I doing wrong?

My pinebook 11" 1080p crashed and failed to boot - and how i recovered it.

In may 2019 I received my new 11" pinebook 1080p laptop with the default ubuntu bionic 18.04 and kde neon 5.14 desktop. I used it only a few times and after installing some seemingly innocuous packages using the software manager "discover" and also python pip it failed to boot. It displayed the circle splash screen on startup, but then remained blank and did not display the login request. (I had previously set it to NOT auto boot to the desktop).
I was able to get a console login using  CTRL-ALT-F2 and login as root. I use a wired lan connection via a usb ethernet adaptor and I had "automatic" internet access from the console.(May be more difficult using wifi). I ran startx, but it failed and "could not connect to server". "X -configure" did not fix the x server either. I used apt-get update (or upgrade, I forget which) and it downloaded about 100Mb of updates. This took a while and you need to press the shift key occasionally or the system goes into screen shutdown and cannot be woken-up. Shift does nothing and seems to prevent inactivity-shutdown.
Now the system would boot to the login screen, but this would only flash briefly and you could not login and the screen remained blank. I downloaded the current distribution image (20190428) from the pine64 website https://wiki.pine64.org/index.php/Pinebook_Main_Page  . Be careful to get the 1080p version or standard version for your laptop screen resolution. I put this on a flash-memory card but this would not boot at all, not even the circles splash screen at startup.

I returned to using the console, booting off the internal MMC and tried to use apt-get again. This gave a message to use pkcon instead on this ubuntu version! I used 'pkcon update' which was messy, but downloaded more updates and installed them. (use the shift key trick above to avoid inactivity sleep blanking!)

The system now booted correctly. It had updated KDE neon to 5.15. It was able to boot from the flash disk that previously failed to boot.

Main points:
1) use CTRL-ALT-F2 to get a console. (It must partially boot to do this)
2) use "pkcon update" to update the entire system. its not the same as apt-get update! There are many updates to the factory supplied version
3) Booting from a flash-memory card can apparently be disabled by some unknown software issues on the MMC disk.
4) Use a USB-LAN adaptor and wired network if wifi does not work from the console.

Despite the recommended changes to "settings", "desktop behaviour", "screen locking" it still suffered unrecoverable inactivity shutdowns. (perhaps closing and opening the lid works - i did not try that) I have changed the shutdown time to maximum allowable 99 mins, but this does not help either! To prevent unrecoverable sleep events I have used the forum comments to use a separate profile, not the default, and set this to never sleep. This works. (settings > power management > activity settings > *define special behaviour, *never shutdown screen, *never suspend )

as root or sudo, shutdown -r now does not reboot the board. It looks like the board correctly shutdowns but it does not reboot. You have to press the Reset button or unplug/plug back the PSU.

Hello,

(1) Beside splicing the SATA power cable (which comes with the SATA card) is there another place on the board where one can pick up the 12v line (for the 80mm fan I'm adding to the Pine64 NAS case)

(2) If I were to use 4 drives (2 x 3.5" and 2 x SSD) in the Pine64 NAS case, with a Marvell 88SE9230 4-PORT, is using a PSU 12v 8A OK to power the board OK? Otherwise what is the Amp limit?