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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,105
» Latest member: kiwigoldfish
» Forum threads: 16,361
» Forum posts: 117,529

Full Statistics

Latest Threads
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
10 hours ago
» Replies: 0
» Views: 39
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 146
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 68
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,543
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,167
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 234
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 157
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,634
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
06-27-2026, 02:43 PM
» Replies: 13
» Views: 18,830
Android Gaming Image
Forum: Game Station Emulation
Last Post: Jacobgilbert
06-26-2026, 07:06 AM
» Replies: 52
» Views: 111,250

 
Question Build Linux OS with Yocto
Posted by: RuslanGennadievich - 09-10-2018, 05:15 AM - Forum: Linux on Rock64 - Replies (1)

Hello

Tell me please, how a can build by Yocto, Linux OS for PINE ROCKPRO 64?

I see only one instruction:
http://opensource.rock-chips.com/wiki_Yocto

But how set MACHINE for rockpro64 don't understud.

Help please


  Crypto wallets - rock64
Posted by: Vegeta - 09-10-2018, 01:49 AM - Forum: General Discussion on ROCK64 - No Replies

Hi guys,
I got a rock64 with the purpose of having a couple of wallets staking 24/7  (instead of keeping the laptop on all day).
Anyone tried this before? Is it straightforward?


  MS Office
Posted by: minhdomanh - 09-09-2018, 09:37 PM - Forum: News - Replies (2)

Does MS Office work on Android?


  Simple questions from a non tech guy.
Posted by: minhdomanh - 09-09-2018, 09:34 PM - Forum: Community and Events - No Replies

Here is a copy of a message I sent to the creators/developers... I was thinking that some of these things could be answered for me here and then others like me would be able to benefit from it.


This project really really fascinates me, but I am not knowledgable about computers. I don't know enough about some of the terms your using to know the full extent of the boards abilities. The idea of expanding with more boards could be the kick computers needs to jump to the next level. What can I do with the computer? I don't know any OS except Windows, and I stumble through android on my tablet (still using a flip phone here), with dozens of Apps I have no idea what they are. Will I be able to use the computer, with the proper interfaces of course.


I guess what I am asking is how can I, a not so computery person use and benefit from the computer?

I really love the idea and modular design of it.

oh and if someone gets say 10 is there a housing option, or do you have ideas for that?


Thanks all for responses.


  TV is not detected unless powered on first
Posted by: excelsi0r - 09-09-2018, 06:20 PM - Forum: General Discussion on ROCK64 - Replies (5)

Hello!

I noticed a small problem with my rock64 and I can't get to fix it.
So basically I installed LibreELEC on my Rock64 and I noticed that if I don't turn on my tv/monitor within the first minute then there is no output signal.
I tried searching for the problem however I could not find specifics.
The only solutions I found were for the RPi, which did'nt work.

Is this a known issue? Has anobody else noticed this? Suggestions?

Thanks!


  Any benchmarks for non-pine64 pci to NVMe adapters?
Posted by: crhawle - 09-09-2018, 04:19 PM - Forum: RockPro64 Hardware and Accessories - Replies (2)

I have two things I would like to find benchmarks/information for. I apologize ahead of time if they are in another thread. I couldn't find them via google or the search function on this forum.

1. Does using a higher quality pci to NVMe adapter improve the performance? Ideally, the PCI lanes should each be able to contribute 400 MB/s for a total of 1.6 GB/s. The only benchmarks i've seen cap out at 540 MB/s write and 1.3 GB/s read. The SSD being tested in those is rated to be able to achieve much higher performance in both areas. I don't know if the difference is due to internal limitations of the processor or the PCI adapter itself. Hence my question.

2. I would also like to know if using a USB type C to ethernet adapter improves the network performance compared to using the built-in ethernet port.


  node red gpio
Posted by: little owl - 09-08-2018, 09:20 AM - Forum: General - Replies (2)

Huh

Hi.

                 Having recently purchased several rock64 boards and a pine A64 , i am horrified to find it supports node red but has no GPIO nodes.( the main reason for using node red ).

     It either doesn't exist or i've got to take a linux degree to do it. ( unfortunately im a PLC engineer and my brain is fuddled as it is ).
ive scanned this forum and the internet for hours......no joy

please put me out of my misery, or shall i ebay the lot???

Little owl...


  Rockpro64 Sata Card kills itself
Posted by: jerry110 - 09-07-2018, 03:42 PM - Forum: RockPro64 Hardware and Accessories - Replies (33)

This card is not happy......Anyone know what is going on?? I have a RockPro64 V 2.1 ,ASMedia ASM1061 (THe one that Pine sells) and a, Samsung 860 EVO SSD 1TB

Code:
[  129.267142] ata2.00: exception Emask 0x10 SAct 0x7ffeffff SErr 0x400000 action 0x6 frozen
[  129.268423] ata2.00: irq_stat 0x08000000, interface fatal error
[  129.269429] ata2: SError: { Handshk }
[  129.270033] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.270841] ata2.00: cmd 61/00:00:00:40:05/08:00:01:00:00/40 tag 0 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.273136] ata2.00: status: { DRDY }
[  129.273696] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.274526] ata2.00: cmd 61/00:08:00:48:05/08:00:01:00:00/40 tag 1 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.276794] ata2.00: status: { DRDY }
[  129.277380] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.278209] ata2.00: cmd 61/00:10:00:50:05/08:00:01:00:00/40 tag 2 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.280473] ata2.00: status: { DRDY }
[  129.281056] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.281883] ata2.00: cmd 61/00:18:00:58:05/08:00:01:00:00/40 tag 3 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.284149] ata2.00: status: { DRDY }
[  129.284707] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.285535] ata2.00: cmd 61/00:20:00:60:05/08:00:01:00:00/40 tag 4 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.287800] ata2.00: status: { DRDY }
[  129.288382] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.289224] ata2.00: cmd 61/00:28:00:68:05/08:00:01:00:00/40 tag 5 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.291506] ata2.00: status: { DRDY }
[  129.292094] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.292924] ata2.00: cmd 61/00:30:00:70:05/08:00:01:00:00/40 tag 6 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.295190] ata2.00: status: { DRDY }
[  129.295747] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.296574] ata2.00: cmd 61/00:38:00:78:05/08:00:01:00:00/40 tag 7 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.298880] ata2.00: status: { DRDY }
[  129.299443] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.300289] ata2.00: cmd 61/00:40:00:80:05/08:00:01:00:00/40 tag 8 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.302572] ata2.00: status: { DRDY }
[  129.303174] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.304017] ata2.00: cmd 61/00:48:00:88:05/08:00:01:00:00/40 tag 9 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.306303] ata2.00: status: { DRDY }
[  129.306902] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.307704] ata2.00: cmd 61/00:50:00:90:05/08:00:01:00:00/40 tag 10 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.309994] ata2.00: status: { DRDY }
[  129.310553] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.311406] ata2.00: cmd 61/00:58:00:98:05/08:00:01:00:00/40 tag 11 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.313705] ata2.00: status: { DRDY }
[  129.314304] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.315145] ata2.00: cmd 61/00:60:00:a0:05/08:00:01:00:00/40 tag 12 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.348484] ata2.00: status: { DRDY }
[  129.364856] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.381189] ata2.00: cmd 61/00:68:00:a8:05/08:00:01:00:00/40 tag 13 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.414106] ata2.00: status: { DRDY }
[  129.430189] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.446413] ata2.00: cmd 61/00:70:00:b0:05/08:00:01:00:00/40 tag 14 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.479421] ata2.00: status: { DRDY }
[  129.495503] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.511769] ata2.00: cmd 61/00:78:00:b8:05/08:00:01:00:00/40 tag 15 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.544879] ata2.00: status: { DRDY }
[  129.560998] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.577260] ata2.00: cmd 61/78:88:00:d0:04/07:00:01:00:00/40 tag 17 ncq 978944 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.610366] ata2.00: status: { DRDY }
[  129.626509] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.642795] ata2.00: cmd 61/88:90:78:d7:04/08:00:01:00:00/40 tag 18 ncq 1118208 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.675914] ata2.00: status: { DRDY }
[  129.692046] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.708321] ata2.00: cmd 61/00:98:00:e0:04/08:00:01:00:00/40 tag 19 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.741493] ata2.00: status: { DRDY }
[  129.757654] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.773958] ata2.00: cmd 61/00:a0:00:e8:04/08:00:01:00:00/40 tag 20 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.807130] ata2.00: status: { DRDY }
[  129.823279] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.839587] ata2.00: cmd 61/c0:a8:00:f0:04/06:00:01:00:00/40 tag 21 ncq 884736 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.872762] ata2.00: status: { DRDY }
[  129.888950] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.905279] ata2.00: cmd 61/40:b0:c0:f6:04/09:00:01:00:00/40 tag 22 ncq 1212416 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  129.938537] ata2.00: status: { DRDY }
[  129.954734] ata2.00: failed command: WRITE FPDMA QUEUED
[  129.971063] ata2.00: cmd 61/00:b8:00:00:05/08:00:01:00:00/40 tag 23 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  130.004352] ata2.00: status: { DRDY }
[  130.020605] ata2.00: failed command: WRITE FPDMA QUEUED
[  130.037015] ata2.00: cmd 61/00:c0:00:08:05/08:00:01:00:00/40 tag 24 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  130.070357] ata2.00: status: { DRDY }
[  130.086643] ata2.00: failed command: WRITE FPDMA QUEUED
[  130.103079] ata2.00: cmd 61/00:c8:00:10:05/08:00:01:00:00/40 tag 25 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  130.136476] ata2.00: status: { DRDY }
[  130.152749] ata2.00: failed command: WRITE FPDMA QUEUED
[  130.169163] ata2.00: cmd 61/00:d0:00:18:05/08:00:01:00:00/40 tag 26 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  130.202614] ata2.00: status: { DRDY }
[  130.218923] ata2.00: failed command: WRITE FPDMA QUEUED
[  130.235351] ata2.00: cmd 61/00:d8:00:20:05/08:00:01:00:00/40 tag 27 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  130.268852] ata2.00: status: { DRDY }
[  130.285132] ata2.00: failed command: WRITE FPDMA QUEUED
[  130.301587] ata2.00: cmd 61/00:e0:00:28:05/08:00:01:00:00/40 tag 28 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  130.335076] ata2.00: status: { DRDY }
[  130.351393] ata2.00: failed command: WRITE FPDMA QUEUED
[  130.367817] ata2.00: cmd 61/00:e8:00:30:05/08:00:01:00:00/40 tag 29 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  130.401265] ata2.00: status: { DRDY }
[  130.417601] ata2.00: failed command: WRITE FPDMA QUEUED
[  130.434096] ata2.00: cmd 61/00:f0:00:38:05/08:00:01:00:00/40 tag 30 ncq 1048576 out
                       res 40/00:90:78:d7:04/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  130.467591] ata2.00: status: { DRDY }
[  130.483918] ata2: hard resetting link


  cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Posted by: kuerious - 09-06-2018, 01:36 PM - Forum: Linux on RockPro64 - Replies (10)

I began this thread (mistakenly?) on the release GitHub page for ayufan-rock64, found here:

https://github.com/ayufan-rock64/linux-build/issues/270

After a few days of no answer there, I figured I should post what's been going on over here in the forums.

Hello all. Big, big fan of your hard work and determination, ayufan.

The following occurred using both of these images:
1: stretch-openmediavault-rockpro64-0.7.9-1067-arm64.img.xz
2: stretch-openmediavault-rockpro64-0.7.9-1067-armhf.img.xz

The title says it all. On first boot, the console shows the following error more than once (at least twice):


Code:
cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2

and


Code:
cdn-dp fec00000.dp: [drm:cdn_dp_request_firmware] *ERROR* Timed out trying to load firmware


The first few times I attempted to get to the IP, the screen loaded blue but nothing else. After it timed-out, I tried a Ctrl+F5 (clean refresh), and it loaded even less this time. I did the usual troubleshooting: let it run for awhile, then reboot - no change; tried the other image for OMV on Rock64Pro - no change.

So I decided to give it some time, see if I could think of anything I missed. I unplugged the power (why, oh why, did the Pine64 team NOT include a power button on the power supply? There's no chance to press the small board button after you plug it in - it just boots.)

I just came back, again, plugged it in. Nothing different. Nothing at all. The SAME error messages occur, but this time the web interface works. It even times me out (as it should) when I'm not active. So, that's weird. But is it functional?

My issue is, if the unit says the firmware isn't loading, should I try using it? As well, did I choose the incorrect images? Did I miss a step?

1: Built the unit (Pine64 storage case + Rock64Pro + 2x 6TB drives + 12V/6A power supply)
2: Used Etcher to load images (above) to 16GB Class 10 microSD
3: Booted

Please tell me what to try next ...


  Problem with connection timeouts
Posted by: Dratcha - 09-06-2018, 10:53 AM - Forum: General Discussion on ROCKPRO64 - Replies (11)

Hi,

I have a RockPro64 with the sata drives being used for a file server. It serves my movies to my three kodi boxes running on Raspberry Pi 3.


the problem I face is when I try to stream a movie, every kodi box freezes at around 51 seconds. The error is a connection timeout with the RockPro64 box.

I have tried OpenMediaVault and a plain Debian install with NFS on my Rockpro64 box, and both experience the exact same issue. I have also tried multiple hard drives. I know the problem is not with the Kodi boxes because it is happening to all three of them, and my original Windows PC that is acting as a file server now does not have this issue.

What could be the problem here? The RockPro64 should have plenty of resources to do this. Did I just get a lemon?

Thanks!