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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,272
» Latest member: PrinterSolvedTeam
» Forum threads: 16,394
» Forum posts: 117,654

Full Statistics

Latest Threads
Printing from Mobian
Forum: Mobian on PinePhone
Last Post: PrinterSolvedTeam
Yesterday, 06:01 AM
» Replies: 3
» Views: 4,875
Satellite antenna
Forum: Community and Events
Last Post: biketool
10-26-2026, 02:46 PM
» Replies: 2
» Views: 438
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
10-25-2026, 04:11 AM
» Replies: 5
» Views: 14,872
Booting Issues
Forum: PineNote Software
Last Post: vlagged
10-23-2026, 12:14 PM
» Replies: 25
» Views: 26,040
Alpha One - no connectivi...
Forum: Getting Started
Last Post: Dabdarklighter
10-22-2026, 03:51 PM
» Replies: 1
» Views: 1,156
Article: The Advantages o...
Forum: General
Last Post: zetabeta
10-20-2026, 02:38 PM
» Replies: 2
» Views: 358
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
10-19-2026, 12:27 PM
» Replies: 22
» Views: 21,460
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
10-19-2026, 10:01 AM
» Replies: 25
» Views: 16,225
Article: Will Linux phone...
Forum: General
Last Post: amosbatto
10-19-2026, 09:52 AM
» Replies: 11
» Views: 1,464
Login issues
Forum: PineTab Hardware
Last Post: Corkonian
10-17-2026, 02:34 AM
» Replies: 2
» Views: 457

 
  Has anyone gotten cpuminer running yet?
Posted by: jenkinsmitchell - 08-10-2018, 01:26 PM - Forum: General Discussion on ROCKPRO64 - No Replies

I've been trying to get veriumminer cpuminer to run on my 2gb rockpro64 but with no luck. Has anyone been able to get it working on theirs?

Sent from my VS996 using Tapatalk


  getrusage(2) time precision is 1 ms, not 1 μs
Posted by: lucho - 08-10-2018, 12:54 PM - Forum: Linux on RockPro64 - No Replies

The ru_utime.tv_usec member of the rusage structure for the getrusage(2) system call with RUSAGE_SELF manifest constant returns times that are multiple of 1000 with the Ayufan's kernel. That is, their precision is 1 ms, not 1 μs as for example for the BCM2708, A10, H3, BCM2837 and EX5422 SoC. I haven't studied the manual of the RK3399, but it seems very unlikely that it doesn't have a high-precision timer (counter), if all these SoC's have one. Is it possible to support it in the future kernel releases in order to obtain the aforementioned microsecond time precision? Thanks in advance!


  usb-c devices don't always power up
Posted by: steamiestoyster - 08-10-2018, 10:47 AM - Forum: Linux on RockPro64 - No Replies

I am running lxde 0.7.9. I have an external hd that is mounted during boot via fstab and plugged into the USB-C port. The raid has LED that come on when it is connected to a system. On initial boot up the external raid never seems to turn on so the boot sequence just sits there waiting for it. It will come on after I 1) unplug and replug the rockpro64 power supply or 2) unplug and replug the usb-c (at this point, I have to reboot the rockpro64 anyways). It is a consistent 100% reproducible issue. I switched the hd over to the USB3 port and did not have any issues.


  kodi and /dev/rkdev
Posted by: catalinii - 08-09-2018, 10:38 PM - Forum: Linux on RockPro64 - No Replies

I tried to compile kodi for ubuntu 18.04 (minimal) and everything seems to be workign, however the only thing missing seems to be hardware acceleration for the video. I used mostly all the patches from LibreELEC to make it work in Ubuntu.

I checked the error messages and used mpp both from github and from librockchip-mpp-dev and it seems the failure is caused by the fact that /dev/rkdev is not present on my system. I suppose that some driver (RK related) is not loaded. Does someone have any idea what is missing on the kernel side ?

Thanks


Information First usable Armbian image!
Posted by: Luke - 08-09-2018, 09:53 AM - Forum: Linux on Pine H64 - Replies (19)

Current nightly from Armbian is pretty darn usable with DVFS, temperature sensor, Ethernet and HDMI on mainline: https://dl.armbian.com/pineh64/Debian_st...nightly.7z

[edit] Apart from Armbian (Igor, et al) credit making this build happen goes to MoeIcenowy; Jernej; and Wink from BU3


  OpenBSD: GPIO with the I2C device PCF8574(A)
Posted by: krjdev - 08-09-2018, 06:41 AM - Forum: BSD on Rock64 - No Replies

Currently the ROCK64 GPIO cannot used in userland. (I currently working on it.)

So I have written a driver for the good old PCF8574 from NXP.
You can find the driver on my Github page:

Additional drivers for OpenBSD

To use the PCF8574, add this to the device trees (Example):

Code:
/dts-v1/; /include/ "rk3328-rock64.dts" &i2c0 {    status = "okay";    pcf8574: gpio@20 {        compatible = "nxp,pcf8574";        status = "okay";        reg = <0x20>;        #gpio-cells = <2>;        gpio-controller;    }; };

Configuration of the Kernel (add the following):

Code:
pcfgpio*    at iic? gpio*       at pcfgpio?

Compile the kernel.

dmesg output from my driver:

Code:
pcfgpio0 at iic0 addr 0x20 gpio0 at pcfgpio0: 8 pins



Use the driver with gpioctl:

Code:
$ gpioctl /dev/gpio0 0 on
Turns pin 0 to on.



Use the driver with ioctls (simple running light example):

Code:
#include <unistd.h> #include <fcntl.h> #include <stdio.h> #include <errno.h> #include <string.h> #include <sys/types.h> #include <sys/gpio.h> #include <sys/ioctl.h> int main(int argc, char *argv[]) {    int i, fd;    int ret;    struct gpio_info ginfo;    struct gpio_pin_op gop;        if (argc < 2) {        printf("usage: gpio [DEV]\n");        return 1;    }    fd = open(argv[1], O_RDWR);    if (fd == -1) {        printf("error: couldn't open file (%s)\n", strerror(errno));        return 1;    }    ret = ioctl(fd, GPIOINFO, &ginfo);    if (ret == -1) {        printf("error: ioctl GPIOINFO failed (%s)\n", strerror(errno));        close(fd);        return 1;    }    printf("gpio: Number of pins: %d\n", ginfo.gpio_npins);    while (1) {        for (i = 0; i < ginfo.gpio_npins; i++) {            gop.gp_pin = i;            gop.gp_value = GPIO_PIN_HIGH;            ret = ioctl(fd, GPIOPINWRITE, &gop);            if (ret == -1) {                printf("error: ioctl GPIOPINWRITE failed (%s)\n", strerror(errno));                close(fd);                return 1;            }            sleep(1);            gop.gp_value = GPIO_PIN_LOW;            ret = ioctl(fd, GPIOPINWRITE, &gop);            if (ret == -1) {                printf("error: ioctl GPIOPINWRITE failed (%s)\n", strerror(errno));                close(fd);                return 1;            }        }    }    close(fd);    return 0; }


  Wireless Module Driver Source code
Posted by: mido2018 - 08-08-2018, 04:26 PM - Forum: Wifi/BT Module - No Replies

Hi, 
I am trying to find the source code of the Wireless module's driver. I could find the driver's source code for the Bluetooth part but not for the WiFi part of the module. Can someone help me with that?


  PCIe-Bus not initialized, no devices detected
Posted by: seiji - 08-08-2018, 01:07 PM - Forum: General Discussion on ROCKPRO64 - Replies (10)

Hey guys,

I bought one of those beauties (v.2.1 2018-06-06) and flashed a micro SD-Card with the latest image of debian stretch minimal (0.7.9).
I had to notice however, that not even the pcie bus is showing up. (The output of lspci is empty, no matter if a card is in the slot or not)

When a card is in the slot, it does not seem to get any power. (No lights turn on, neither do they get warm)
The cards I tested:
- Logilink Dual LAN-Card with two Realtek chips on it http://www.logilink.com/media/datasheets/PC0075.pdf
- Intel Ethernet LAN Card D33025

- Varius graphics cards (wasn't expecting them to work, really)

I tested multiple versions and images. Did not work with either BSP nor mainline kernel.
The last image I tried was (0.7.8) of minimal Ubuntu with Kernel (4.4.132-1072-rockchip-ayufan-ga1d27dba5a2e).
I attached the boot-log (dmesg output) on that one.

Have I forgotten something?
I already crawled through the entire forum of Frank Mankel, unfortunately to no avail.
I read something about setting jumpers for a similar problem somewhere, but for a solution, the post links to an entry on Frank Mankel's deleted blog.  Confused



Attached Files
.log   dmesg.log (Size: 63.01 KB / Downloads: 601)

Video ARMBand an easily configured Home Media Server
Posted by: gabrielsr - 08-08-2018, 06:47 AM - Forum: RockPro64 Projects, Ideas and Tutorials - Replies (2)

Hi all, 

I'm working on a Home Media Server project for automate the process of downloading series and movies and organize your media library. 
The project will easy the process of deployment a lot of great existing projects out there for a home server / personal cloud such as Plex, Emby, Radarr, CouchPotato, onwCLoud, ...

If you're interested in making a RockPro64 a Media Server, say hello to ARMBand. Big Grin

The underling Bits:

ARMBand is a fork of Cloudbox for the arm64 architecture. Cloudbox can configure a impressive list of services for home media server without much user work envolved but only supports amd64 architecture. Cloudbox uses Ansible to configure media server related services using Docker containers.  Ansible is an infrastructure automation technology (like Puppet and Chef, but much more easily to start playing with).

Porting Cloudbox to arm64 basically envolves changing Ansible recipes to use arm64 based docker images, fork docker images and adapt scripts to download arm64 packages.
 
If anyone is interested in contributing in development or testing drop me a msg, ok? 

Thanks.

Main Project:
https://github.com/dibrz/ARMBand

Cloudbox Wiki:
https://github.com/Cloudbox/Cloudbox/wiki


  How to do hardware decoding of video?
Posted by: SuperSaiyanCaleb - 08-08-2018, 04:30 AM - Forum: Linux on Rock64 - Replies (9)

So I have a Rock64 board and I want to leverage its hardware decoding and encoding abilities in an Emby server.  But for a start I'd be happy just to get any sort of hardware decoding working.  I tried out Armbian Stretch and wasn't able to get either of my HEVC test files to play smoothly out of the box.  (vainfo returned an error when trying to get a driver name, so evidently something needs to be installed that's not, but I'm not sure what...)  And there's very little instruction out there that I can find, so I'm not sure if this is an Armbian shortcoming or just a matter of me not knowing how to get all the pieces in place.

I'm interested in ayufan's images, but don't know if it's any easier to get hardware decoding working there than on Armbian...  Has anyone gotten hardware decoding working on these boards?  What OS works best and what needs to be installed/configured to get it working properly?