Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,547
» Latest member: loveyou
» Forum threads: 16,209
» Forum posts: 116,954
Full Statistics
|
Latest Threads |
Brand new sealed Pinetime...
Forum: General Discussion on PineTime
Last Post: elver
Yesterday, 06:41 AM
» Replies: 0
» Views: 576
|
Call recording?
Forum: PinePhone Pro Software
Last Post: biketool
09-09-2025, 04:14 AM
» Replies: 7
» Views: 7,097
|
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: Frank23t
09-08-2025, 10:30 PM
» Replies: 4
» Views: 2,311
|
Why projects like PinePho...
Forum: General Discussion on PinePhone
Last Post: biketool
09-08-2025, 12:51 PM
» Replies: 4
» Views: 4,314
|
more mobile linux on redd...
Forum: General Discussion on PinePhone
Last Post: biketool
09-08-2025, 12:03 PM
» Replies: 2
» Views: 2,131
|
Anyone selling a Pinebook
Forum: Pinebook Hardware and Accessories
Last Post: ams
09-08-2025, 09:26 AM
» Replies: 2
» Views: 2,404
|
Having trouble reading MP...
Forum: Getting Started
Last Post: Alex92
09-05-2025, 08:49 PM
» Replies: 1
» Views: 3,505
|
Special keys stopped work...
Forum: General Discussion on PineNote
Last Post: cheepeero
09-05-2025, 07:32 PM
» Replies: 0
» Views: 2,630
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
09-04-2025, 12:52 PM
» Replies: 20
» Views: 10,504
|
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
09-04-2025, 01:40 AM
» Replies: 11
» Views: 4,845
|
|
|
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_TEMP - Minimum 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_PWM - Min 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.
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
|
|
|
What do you actually use your Pinebook for? |
Posted by: frank-zappa - 12-10-2018, 06:55 PM - Forum: General Discussion on Pinebook
- Replies (5)
|
 |
Hello all.
I thought it would be interesting to ask what people use their Pinebook for?
There seem to be a fair few tech savvy people and coders. Are there any more casual users like myself?
I just wanted a cheap laptop that ran Ubuntu.
it will be interesting to get a feel of what people use their machines for.
|
|
|
Has anyone gotten HDMI output? |
Posted by: rpm - 12-10-2018, 01:51 PM - Forum: General Discussion on Pinebook
- Replies (1)
|
 |
I've tried the default KDE, Diet Pi, Armbian, and Manjaro LXQT and have not managed to get HDMI output. I'm able to detect that an HDMI monitor is connected but can not seem to get it to actually display. Any advice hugely appreciated!
|
|
|
Rock64 as hypervisor ? |
Posted by: jean_bruder - 12-10-2018, 10:19 AM - Forum: Linux on Rock64
- Replies (1)
|
 |
Dear All,
I'm using the Pine64 board since some months now to host my ownCloud and everything is working fine without any kind of issues !
As the Rock64 board seems to bring more power, I planned to use it as a virtualization board. But, I didn't found any tutorial that could help me to setup my board so far. I've read on the forum that some users managed installing Xen on the board, and other use Docker/Kubernete.
I realize that I first need to be clear with what I would like to do with this board : I have many other different boards used to achieve different tasks on my home network (multi-room audio system using MPD, home automation systems for my connected lights, connected heating systems, connected windows, garden water pumps ...), and would like definitively to use as less as possible boards ... Each board run either Debian or Ubuntu and hosts a dedicated application. I definitively would like to have only one Rock64 boards to hosts all that applications, BUT isolated the one from the other ... In case something goes wrong with one, I wouldn't have to others dead at the same time ... And because I do many tests on each systems to make them evolve sometime in "testing mode" (compiling from scratch, updating packages ...).
Any ideas to share with me ?
Many thanks in advance,
Best regards,
Jean
|
|
|
No sound output from 3.5mm jack |
Posted by: spatial_dreams - 12-10-2018, 06:05 AM - Forum: RockPro64 Hardware and Accessories
- Replies (3)
|
 |
Hey fellow Rockers,
I'm having some trouble getting sound to play from the 3.5mm port on my rockpro 64
Kernel: Linux rockpro64 4.4.132-1075-rockchip-ayufan-ga83beded8524 #1 SMP Thu Jul 26 08:22:22 UTC 2018 aarch64 GNU/Linux
Distro: Debain Stretch 9.6
This is my first time encountering an audio problem so I'm not 100% I went through the all basics, but here's what I've done so far: - Verified my user is in the audio group
- installed pulseaudio and pavucontrol
- changed my default sinks to every option available with pacmd change-default-sink
- verified my volume was turned up in alsamixer
- played a known good file with aplay as local user and su
- tried a new headset, and tried the same headset in a different device. The headset is good.
- Searched this forum and followed Longsleep's recommendations posted here
- rebooted multiple times after iterating through these steps
None of these steps remedied the issue, and I still don't have any sound output from the 3.5mm. I was able to get audio through the HDMI port one time, but that happened unintentionally.
Sinks:
Code: 3 sink(s) available.
* index: 0
name: <alsa_output.platform-es8316-sound.analog-stereo>
driver: <module-alsa-card.c>
flags: HARDWARE DECIBEL_VOLUME LATENCY FLAT_VOLUME
state: SUSPENDED
suspend cause: IDLE
priority: 9009
volume: front-left: 57659 / 88% / -3.34 dB, front-right: 57659 / 88% / -3.34 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 0
linked by: 0
fixed latency: 99.95 ms
card: 0 <alsa_card.platform-es8316-sound>
module: 6
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = ""
alsa.id = "ff890000.i2s-ES8316 HiFi ES8316 HiFi-0"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "rockchip,es8316-codec"
alsa.long_card_name = "rockchip,es8316-codec"
device.bus_path = "platform-es8316-sound"
sysfs.path = "/devices/platform/es8316-sound/sound/card0"
device.string = "hw:0"
device.buffering.buffer_size = "17632"
device.buffering.fragment_size = "4408"
device.access_mode = "mmap"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "rockchip,es8316-codec Analog Stereo"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card"
index: 1
name: <alsa_output.platform-hdmi-dp-sound.analog-stereo>
driver: <module-alsa-card.c>
flags: HARDWARE DECIBEL_VOLUME LATENCY FLAT_VOLUME
state: SUSPENDED
suspend cause: IDLE
priority: 9009
volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 2
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 0
linked by: 0
fixed latency: 99.95 ms
card: 1 <alsa_card.platform-hdmi-dp-sound>
module: 7
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = ""
alsa.id = "HDMI-DP multicodec-0"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "2"
alsa.card_name = "rk-hdmi-dp-sound"
alsa.long_card_name = "rk-hdmi-dp-sound"
device.bus_path = "platform-hdmi-dp-sound"
sysfs.path = "/devices/platform/hdmi-dp-sound/sound/card2"
device.string = "hw:2"
device.buffering.buffer_size = "17632"
device.buffering.fragment_size = "4408"
device.access_mode = "mmap"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "rk-hdmi-dp-sound Analog Stereo"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card"
ports:
analog-output: Analog Output (priority 9900, latency offset 0 usec, available: unknown)
properties:
active port: <analog-output>
index: 2
name: <alsa_output.platform-spdif-sound.analog-stereo>
driver: <module-alsa-card.c>
flags: HARDWARE DECIBEL_VOLUME LATENCY FLAT_VOLUME
state: SUSPENDED
suspend cause: IDLE
priority: 9009
volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 3
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 0
linked by: 0
fixed latency: 99.95 ms
card: 2 <alsa_card.platform-spdif-sound>
module: 8
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = ""
alsa.id = "ff870000.spdif-dit-hifi dit-hifi-0"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "1"
alsa.card_name = "ROCKCHIP,SPDIF"
alsa.long_card_name = "ROCKCHIP,SPDIF"
device.bus_path = "platform-spdif-sound"
sysfs.path = "/devices/platform/spdif-sound/sound/card1"
device.string = "hw:1"
device.buffering.buffer_size = "17632"
device.buffering.fragment_size = "4408"
device.access_mode = "mmap"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "ROCKCHIP,SPDIF Analog Stereo"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card"
ports:
analog-output: Analog Output (priority 9900, latency offset 0 usec, available: unknown)
properties:
active port: <analog-output>
I'm not sure what to do next, so here I am. Thanks in advance for any assistance.
PS. lspci produces no output. Is this normal?
|
|
|
USB fails to power device? |
Posted by: BackWoodsTech - 12-08-2018, 03:09 PM - Forum: RockPro64 Hardware and Accessories
- Replies (12)
|
 |
I have a small USB router. It has a USB powerc cable wirh an AC power adapter. It works just fine when using like one of those outlets that just has a usb port, but when I attempt to power the device off the rock pro USB it boots then shutsdown..boots, shutsdown repeat.
Is the USB port insufficient to power peripherals?
|
|
|
|