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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,106
» Latest member: mecivietnam
» Forum threads: 16,362
» Forum posts: 117,531

Full Statistics

Latest Threads
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
Yesterday, 11:02 AM
» Replies: 0
» Views: 55
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,016
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
07-04-2026, 08:23 AM
» Replies: 0
» Views: 95
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 200
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 106
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,577
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,188
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 259
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 185
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,661

 
  so installed minimal then xubuntu, major screen tearing.
Posted by: Martronic - 12-14-2018, 09:31 PM - Forum: Linux on RockPro64 - Replies (3)

so i have installed the minimal ubuntu 18.04 image and then i installed the xubuntu-desktop metapackage with recommends. i have noticed some pretty crazy screen tearing.... there hasn't been anything that has much mention (i searched the forums and the irc logs and there is not a whole lot of concise information on the subject....... i just want to have a thread on this.... 


you can tell me to buzz off if needed but i have almost all i need other then the screen tearing.... its also an issue in my main linux laptop but i don't really care about that as its mostly for work but this is being used for media consumption...
Speak


  Can't get Rockpro to boot
Posted by: Crnppscls - 12-14-2018, 06:51 PM - Forum: General Discussion on ROCKPRO64 - Replies (4)

I've been on for a week or so when i've had time but i'm still unable to get anything from Hdmi.
Both lights on the ethernet are solid as well as the green light next to the psu in. I have never seen the white light behind the reset switch lit.
I have a 32GB emmc and a decent samsung sd card, i've written ubuntu minimal to both but have been unable to boot anything. Windows does throw a bit of a hissy after writing with etcher but the image appears to be valid, i've also tried other images. 

Psu is 12v @3000mA. I could possibly try another but don't have one to hand and that is probably now the only thing i have left to do, unless windows is botching the writing process.
I wondered if there was something i have missed, i don't have much experience with Sbc's and i'm really struggling with this one.


Star OMV-Remotedesktop-lag-disorder
Posted by: Neo2018 - 12-14-2018, 01:21 PM - Forum: Linux on RockPro64 - Replies (7)

Hello,
I desperately need a Remote Desktop in OMV OpenMediaVault.
Installed> OMV-Extras> Plugins> openmediavault-remotedesktop 4.0.1
Connected via Windows Remote Desktop Connection.
After a few clicks, no reaction, connection reboot few clicks and again lags / errors.

Code:
root@rockpro64:~# uname -a
Linux rockpro64 4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee #1 SMP Thu Aug 9 20:29:55 UTC 2018 aarch64 GNU/Linux
[Image: 2Pcg4.jpg] [Image: 2PchY.jpg]

Remote Desktop is very important to me.
Please help.


  RockPro64 and JustBoom DAC and AMP
Posted by: goranobradovic - 12-14-2018, 11:34 AM - Forum: Rock64 Hardware and Accessories - No Replies

I am interested in connecting JustBoom DAC and AMP HAT cards (compatible with RPI IO socket) or Allo Boss DAC and Allo Volt AMP to Pine RockPro64 board. Is that possible?

https://www.justboom.co/product-category...io-boards/
https://www.allo.com/sparky/boss-dac.html
https://www.allo.com/sparky/volt-amp.html


  Seedbox issues (rtorrent, rutorrent, autodl-irssi)
Posted by: va88 - 12-14-2018, 08:26 AM - Forum: Linux on Rock64 - Replies (5)

Hey guys, I received my Rock64 yesterday and started to setup my seedbox-NAS-gamebox setup.

I'm doing this in my raspberrypi pretty easily, but the networking is so limited that I decided to go with the Rock64.

However, I'm stuck pretty much at the beginning, since the seedbox part is not working.

I'm using the provided debian minimal image and I'm following debian tutorials for the rutorrent + rtorrent + autodl-irssi, but it's not working.
Example tutorials and tools I've used to this end before successfully: 
i) https://chooseneye.com/2018/03/install-r...-debian-9/
ii) https://github.com/arakasi72/rtinst
iii) https://jes.sc/kb/rTorrent-ruTorrent-Seedbox-Guide.php

Which guides are you following to setup a seedbox with rtorrent, rutorrent and autodl-irssi in the Rock64? 

Should I boot the bionic minimal image and follow Ubuntu guides?

Also, I noticed that some steps are extremely slow compared to the same procedures in the raspberry pi 3, such as the use of "make" command to build most recent versions of libtorrent and rtorrent. How can this be in a faster SoC?

If you guys have suggestions on a different approach I'm all ears. I haven't even got to the NAS part and I've read about in the forum that the samba performance is quite bad in Rock64. I'm considering going with OMV, but then I'd lose the gaming part and part of the the seedboxing advanced scriptiong.


  Pinebook 14" availability?
Posted by: Bitflogger - 12-13-2018, 03:37 PM - Forum: General Discussion on Pinebook - Replies (4)

Hi,

I'm looking to buy my second Pinebook.  When will a 14" be available again?

My first one is a little old.  Moving the screen when the back is unscrewed broke a hinge.  It still holds together with the back screwed on, but its only a matter of time.

Earl


  WiringPi support for Rock64
Posted by: CristianM - 12-13-2018, 04:08 AM - Forum: General Discussion on ROCK64 - Replies (1)

Hello! I want to use the GPIO, I2C and SPI ports of a Rock64 board. However, I cannot find software support to do this. I have seen a R64.GPIO library, but it does not have interrupt support and is only for GPIO.

So, is there a software library for Rock64 that offers access to GPIO (including interrupts), I2C and SPI (similar to wiringpi)? If no, how can I gain access to these functions?


  Tutorial:How to Configure ATS Fan control
Posted by: tuxd3v - 12-12-2018, 09:13 AM - Forum: RockPro64 Projects, Ideas and Tutorials - Replies (26)

Hello all,
I told you that I would create a tutorial about ATS Configuration, and here it is( sorry for the late on this.. ).

You need a supported Kernel for this to work( at least you need kernel 4.4.132-1083 ).
But the one bellow will work for sure:

Code:
apt-get update
apt-get install linux-image-4.4.138-1097-rockchip-ayufan-gb5128c0a1684 linux-headers-4.4.138-1097-rockchip-ayufan-gb5128c0a1684 linux-firmware-image-4.4.138-1097-rockchip-ayufan-gb5128c0a1684
reboot

This tutorial is about the version 0.2.0 ( Install Point 2. or 3.  ), it is updated with the status of the project..

So please refer only to this first comment,
Some of comments below could be outdated( as the project is been updated.. )..



1) ATS, has a configuration file '/etc/ats.conf'

Code:
SYSTEM = {
    BOARD = {
        NAME    = "ROCKPRO64",
        CPU    = "RK3399"
    },

    THERMAL0_CTL    = "/sys/class/thermal/thermal_zone0/temp",
    THERMAL1_CTL    = "/sys/class/thermal/thermal_zone1/temp",
    PWM_CTL        = "/sys/class/hwmon/hwmon0/pwm1",

    MAX_CONTINUOUS_THERMAL_TEMP    = 60,
    MIN_CONTINUOUS_THERMAL_TEMP    = 40,

    MAX_PWM                = 255,
    MIN_PWM                = 40,

    ALWAYS_ON            = false,

    PROFILE_NAME            = "profile0",
    PROFILE_NR            = 0
}
return SYSTEM

This File will define when ATS is active or not,
IF fan is always on, and the max power applied...

The values above are the default ones..

THERMAL0_CTL - CPU Thermal SysFs Control
THERMAL1_CTL - GPU Thermal SysFs Control
PWM_CTL      - Power Control

MAX_CONTINUOUS_THERMAL_TEMP - Maximum Temperature were ATS adjust Fan power [ -20, 70 [,
                              Above this, power is always Maximum..
MIN_CONTINUOUS_THERMAL_TEMPMinimum Temperature were ATS adjust Fan power [ -20, 70 [,
                              Bellow this, power is always Off.

MAX_PWM - Max PWM Fan Power ] 0, 255 ], above 255 ATS will automatically assign value 255, and bellow 0, the same.
MIN_PWMMin PWM Fan Power [ 0, 255 [, bellow 0 ATS will automatically assign value 40, and above 254, the same.

ALWAYS_ON - Tell ATS when Fan should be ON/OFF { true, false },
          - true, if you want the Fan always ON.
          - false,if you want the Fan Cycling ON/OFF,
            In this case, the algorithm works always in a 2 steps way( Time for Fan on, and Time for Fan off ):
            - Timer for Fan ON, will increase with temperature rising, or decrease when temperature fall..
            - Timer for Fan OFF, will decrease with temperature rising, or increase when temperature fall.. 


The values bellow( introduced in version 0.1.8 ), probably will be scratched out, because its almost impossible to create profiles with so different configurations any one has( different heatsinks, different Fans, different Humidity/Temperatures around the globe... ).

Instead, the controls above, would be better,( don't delete them because the code needs to be adjusted first for that..) 

PROFILE_NAME - The name of the profile
PROFILE_NR   - Profile number


2) A Practical Case..

Imagine you want max power at 100, the Fan always ON, and max power( 100 ) to be reached at 65°C:

Code:
SYSTEM = {
    BOARD = {
        NAME    = "ROCKPRO64",
        CPU    = "RK3399"
    },

    THERMAL0_CTL    = "/sys/class/thermal/thermal_zone0/temp",
    THERMAL1_CTL    = "/sys/class/thermal/thermal_zone1/temp",
    PWM_CTL        = "/sys/class/hwmon/hwmon0/pwm1",

    MAX_CONTINUOUS_THERMAL_TEMP    = 65,
    MIN_CONTINUOUS_THERMAL_TEMP    = 40,

    MAX_PWM                = 100,
    MIN_PWM                = 40,

    ALWAYS_ON            = true,

    PROFILE_NAME            = "profile0",
    PROFILE_NR            = 0
}
return SYSTEM



3) Stop ATS, and start it again( new values will be read ).

Code:
service ats stop && service ats start



4) Check values applied,
   Start ats in test mode:

Code:
root@rockpro64:~# ats -t
info:'SYSTEM' Table
info:    'BOARD' Table
info:        'NAME' = ROCKPRO64
info:        'CPU'  = RK3399
info:    'THERMAL0_CTL' = /sys/class/thermal/thermal_zone0/temp
info:    'THERMAL1_CTL' = /sys/class/thermal/thermal_zone1/temp
info:    'PWM_CTL'      = /sys/class/hwmon/hwmon0/pwm1
info:    'MAX_CONTINUOUS_THERMAL_TEMP' = 65
info:    'MIN_CONTINUOUS_THERMAL_TEMP' = 40
info:    'MAX_PWM' = 100
info:    'MIN_PWM' = 40
info:    'ALWAYS_ON' = true
info:    'PROFILE_NAME' = profile0
info:    'PROFILE'      = 0
info:'Pratio' timers
info:    'Pratio[ -20 - 40 [' = 0
info:    'Pratio[ 40 ]'       = 40
info:    'Pratio[ 41 ]'       = 42
info:    'Pratio[ 42 ]'       = 44
info:    'Pratio[ 43 ]'       = 47
info:    'Pratio[ 44 ]'       = 49
info:    'Pratio[ 45 ]'       = 52
info:    'Pratio[ 46 ]'       = 54
info:    'Pratio[ 47 ]'       = 56
info:    'Pratio[ 48 ]'       = 59
info:    'Pratio[ 49 ]'       = 61
info:    'Pratio[ 50 ]'       = 64
info:    'Pratio[ 51 ]'       = 66
info:    'Pratio[ 52 ]'       = 68
info:    'Pratio[ 53 ]'       = 71
info:    'Pratio[ 54 ]'       = 73
info:    'Pratio[ 55 ]'       = 76
info:    'Pratio[ 56 ]'       = 78
info:    'Pratio[ 57 ]'       = 80
info:    'Pratio[ 58 ]'       = 83
info:    'Pratio[ 59 ]'       = 85
info:    'Pratio[ 60 ]'       = 88
info:    'Pratio[ 61 ]'       = 90
info:    'Pratio[ 62 ]'       = 92
info:    'Pratio[ 63 ]'       = 95
info:    'Pratio[ 64 ]'       = 97
info:    'Pratio[ 65 ]'       = 100
info:    'Pratio[ 65 - 70 ['  = 255
Stop ATS Service first [ service ats stop ]..

Here you can see at end:
'Stop ATS Service first [ service ats stop ]..'

No problem,
When you started ats in test mode, it detected that Service launched in 3) was already running..

So it report the config, and exit from test mode( The Service launched in 3) continues running, as expected )..
Its nice when you wanted to know what values are configured for example..

That's it!!
Hope you find a good tuning for your Fan/Cooler. Shy

Best Regards,


  Boinc issue
Posted by: Fabien - 12-12-2018, 03:08 AM - Forum: Android on RockPro64 - Replies (7)

Hello everybody,

I just purchased one ROCKPRO64 2GB. I installed Android 7.1 (20180809) and the board run well.
In order to test the performance of the board, I run some benchmark without issue and finally I tried to run BOINC. On this board BOINC is running very badly. In this software you can select the number of CPU core you would like to use and also the CPU time of computation. I tried to select 2, 4 or 6 CPU core and I saw that the 2 big core are never used. Only the LITTLE core are used.

I already run BOINC on other SBC and I never saw this issue. Do you think the issue came from BOINC or on this version of Android? What could I do to try to solve this issue?

Thanks for your help
Best regards


  PCIe port specifications
Posted by: MisterA - 12-11-2018, 02:55 AM - Forum: RockPro64 Hardware and Accessories - No Replies

Hi,

I read that a lot of people have problems getting PCIe cards to work with the rockpro64.

However I'm starting to wonder if the board respects the PCIe standards in the correct way.
I can understand some drivers are not ready yet to support every card out there.

However what I noticed in my case, that my SATA PCIe card which I'm trying to get to work, get extremely hot.
To the point you can 'smell' the card due to the heat and you can't touch the heatsink on the different chips of the card.
After just a few seconds I need to shutdown the board because I'm afraid it would damage the card (or eventually catch fire?).

In my opinion this just shouldn't happen, putting the card in a regular PC doesn't lead to this kind of heat problems.
Has anyone else have similar experiences?

Best regards,
Jan