[June 20] Manjaro KDE (micro SD to eMMC Boot) 19.04 -1080P Pinebook | [June 20] Stock Android 9.0 - Rock64 v2/v3 | [June 19] NextCloudPi 03-10-19- RockPro | [June 19] Debian Minimal by mrfixit2001 190531- RockPro | [June 19] NextCloudPi 03-10-19- Rock64 | [June 19] Debian Minimal by mrfixit2001 190531- Rock64 v2/v3 | [June 17] Stock Android 9.0 - Pine H64 | [June 13] Armbian Ubuntu Bionic Desktop 5.88 / Armbian Ubuntu Bionic Minimal 5.88 - Rock64 v2/v3 | [June 13] Stretch OpenMediaVault OS Image arm64 / armhf 0.8.0rc14-1134 - ROCK64 v2/v3 (Testiing version)

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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 12,398
» Latest member: vladk
» Forum threads: 5,543
» Forum posts: 43,747

Full Statistics

Latest Threads
Rock64 Seafile Installati...
Forum: General Discussion on ROCK64
Last Post: klaus_nase
2 hours ago
» Replies: 0
» Views: 6
Pinewatch ?
Forum: General
Last Post: Kochise
2 hours ago
» Replies: 0
» Views: 5
PinePhone, PineTab and Pi...
Forum: News
Last Post: mattcfox
7 hours ago
» Replies: 17
» Views: 1,582
Make Wiki Great Again
Forum: General
Last Post: fire219
Yesterday, 05:52 PM
» Replies: 11
» Views: 3,484
Pine64 E-ink screen - And...
Forum: Projects, Ideas and Tutorials
Last Post: clamum
Yesterday, 07:31 AM
» Replies: 3
» Views: 1,636
Hardware Status Monitorin...
Forum: Linux
Last Post: PopcornMaker
Yesterday, 04:04 AM
» Replies: 5
» Views: 2,472
10mm Low Profile Heatsink...
Forum: Hardware and Accessories
Last Post: evilbunny
Yesterday, 02:45 AM
» Replies: 1
» Views: 26
Android 9 for Rock64?
Forum: Android
Last Post: Vanbesem
Yesterday, 12:39 AM
» Replies: 37
» Views: 4,560
how to keep MAC address a...
Forum: Android
Last Post: AlexS
06-24-2019, 11:52 PM
» Replies: 0
» Views: 24
Android Images (ROCK64)
Forum: Android
Last Post: totalgaara
06-24-2019, 11:01 PM
» Replies: 58
» Views: 31,595

 
  Udev rule for gpios for non root access
Posted by: dkebler - 06-11-2019, 09:06 AM - Forum: Pi2, Euler and Exp GPIO Ports - Replies (2)

Using armbian bionic mainline kernel on A64-v1.1 board
Linux pine64 4.19.38-sunxi64 #5.83 SMP Fri May 3 21:02:31 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux

Need to allow non-root access to gpio pins (i.e. gpio group with access to export and unexport etc) via udev.  I've done this successfully before on an RPI but no matter what I try the gpio group and permissions are not set.   Maybe it's something specific to Pine64 so asking here.  

here is one version of rules I've tried.   using udevadm I've confirmed the file is read and loaded but the changes are not made

Code:
SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c 'find -L /sys/class/gpio/ -maxdepth 2 -exec chown root:gpio {} \; -exec chmod 770 {} \; || true'"


Any suggestions?  Anyone have a successful udev rules for this board?  If so please share


  Request for new Open Source Driver
Posted by: khaosgrille - 06-11-2019, 07:20 AM - Forum: Linux - Replies (1)

Hi,

there is a new driver coming to the 5.2 linux kernel called Panfrost https://gitlab.freedesktop.org/panfrost. Afaik Rockpro6 has a Mali GPU and maybe it could use these drivers. Are there any plans to backport them to the current kernel or to jump to a newer kernel in the near future?
Kodi for example supports Panfrost and should be running much better with it.

Greetings,
Khaosgrille


  SPI support in GPIO
Posted by: mr_rabbit - 06-11-2019, 05:07 AM - Forum: General Discussion on ROCKPRO64 - No Replies

Hi!

I recently bought a RockPro64 with 4GB and would like to control a 1.8 LCD screen with SPI interface using the pins on the GPIO header.

The system is running ayufan's Ubuntu minimal. 

I had success in simple GPIO switching by using the RP64-GPIO library:
https://forum.frank-mankel.org/topic/292...-rp64-gpio

However, I was not able to access SPI. I could not find any help or documentation on the internet, not even on the Wiki.

Anyone had success with this?


  Failure in setting the display backlight with Armbian 5.86 [SOLVED]
Posted by: wlad - 06-11-2019, 03:36 AM - Forum: Linux - No Replies

I tested both current Armbian mainline images (Armbian_5.86_Pinebook-a64_Ubuntu_bionic_next_4.19.38_desktop and Armbian_5.86_Pinebook-a64_Debian_stretch_next_4.19.38) with my Pinebook 11.6" shipped in May '19 and both images have issues with the display brightness settings. 

Indication: After boot up, the backlight is set to maximum brightness and resetting it to other values in /sys/class/backlight/backlight/brightness (or via desktop power manager tool) shows no effect. The brightness level stays the same, although 'cat  /sys/class/backlight/backlight/brightness' returns changed values.

Solution: I managed to work around the issue by modifying the sun50i-a64-pinebook.dtb in /boot/dtb/allwinner/ in the following way:

(You can convert the dtb file to human-readable dts-format with 'dtc -I dtb -O dts /boot/dtb/allwinner/sun50i-a64-pinebook.dtb > converted.dts')

Initial content was:

Code:
[...]
backlight {
compatible = "pwm-backlight";
   pwms = < 0x43 0x00 0xc350 0x01 >;
brightness-levels = < 0x0 0x5 0xa 0xf 0x14 0x1e 0x28 0x37 0x46 0x55 0x64 >;
default-brightness-level = < 0x2 >;
  enable-gpios = < 0x22 0x03 0x17 0x00 >;
phandle = < 0x98 >;
};
[...]

After I removed the line with "phandle = < 0x98 >;", setting backlight brightness worked again. Unfortunately, the levels were reversed (1 meaning brightest, 9 meaning darkest, 0 and 10 turned off the backlight completely). Thus, I have changed the line with "brightness-levels" with inversed level values.

Overall, the final content of the dts file is:
Code:
[...]
backlight {
  compatible = "pwm-backlight";
   pwms = < 0x43 0x00 0xc350 0x01 >;
  brightness-levels = < 0x64 0x55 0x46 0x37 0x28 0x1e 0x14 0xf 0xa 0x5 0x0 >;
  default-brightness-level = < 0x2 >;
  enable-gpios = < 0x22 0x03 0x17 0x00 >;
};
[...]

In order to apply the changes, you have to compile the dts file back to dtb format and overwrite the original file in /boot/dtb/allwinner/. We will backup the original file before overwriting, in case after the reboot you end up with a dark display and need to boot from sd-card in order to undo the changes.
Code:
sudo cp /boot/dtb/allwinner/sun50i-a64-pinebook.dtb /boot/dtb/allwinner/sun50i-a64-pinebook.dtb.bac
sudo dtc -I dts -O dtb converted.dts > /boot/dtb/allwinner/sun50i-a64-pinebook.dtb

Please note, that this is only a shallow workaround. I do not know, what the effect of the phandle line was and why it works to set brightness without it. All I can say is that until now, I saw no negative side effects of this "solution".


  Pine hangs up on boot if I add my exFAT USB drive to /etc/fstab
Posted by: pqueiro - 06-10-2019, 12:07 PM - Forum: Ubuntu - No Replies

I can mount it manually fine off the CLI but if I add it to /etc/fstab it hangs the entire system when booting. I've got it on fstab as

Code:
/dev/sda2    /mnt/verbatim    exfat    defaults    0    1

Am I missing something in the options? Is it just checking something on boot and taking a long time? (it's a 2TB drive)

Given that it works if I mount it manually, I'm not sure what I'm doing wrong here  Sad

EDIT: setting pass to 0 and changing defaults to rw,auto,user,gid=1000,uid=1000 seems to have fixed it. I'm not 100% sure but I suspect it may have been the pass going to 0 that did it (as noted earlier in my original post, it's a 2TB USB3.0 drive and checking that filesystem would certainly have taken a long time). This means I have to be more hands-on about checking and maintaining the file system, but at least it now boots and mounts it correctly.


  how to upgrade?
Posted by: skipper - 06-10-2019, 02:07 AM - Forum: Linux - No Replies

I have several rock64 boards running bionic-containers-rock64-0.7.9-1067-arm64.img.xz
I now see there's a new pre-release/upgrade available bionic-containers-rock64-0.8.0rc14-1134-arm64.img.xz
My question is:
Is it enough to do
sudo apt-get update -y
sudo apt-get install linux-rock64 -y
..would that upgrade the 0.7.9 version to the 0.8.0 version? ..and how do I see that it's the 0.8.0 version?
..or do I need to take out the SD card, format it and install 0.8.0 from scratch?
I wouldn't like to re-format and re-install all the boards, as I have them all modified and fine-tuned with many features, settings and programs.

After having tried the install linux-rock64 command I now see this when logging in:
Welcome to Ubuntu 18.04.2 LTS (Gnu/Linux 4.4.167-1201-rockchip-ayufan-g74fa6c44ee39 aarch64)
Is that the 0.8.0 version linked above?

Krgds.


  Unable to boot any armbian linux
Posted by: vicsanca - 06-10-2019, 12:43 AM - Forum: Linux - No Replies

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


  MicroSD and MATE Desktop slow on AOSC
Posted by: vicsanca - 06-10-2019, 12:39 AM - Forum: Linux - No Replies

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 Sad. This microSD is capable of much more speed.

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

Any tuning tips?


Thanks.


  Sometimes no power to SATA PCIe controller
Posted by: rble - 06-09-2019, 06:07 PM - Forum: Hardware and Accessories - Replies (4)

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 /[email protected] 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.


  System freeze...
Posted by: Faradn - 06-09-2019, 08:30 AM - Forum: Linux - No Replies

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