Okay -- now that the RockPro64 has shipped a batch (or two), is it too early to start asking about the -AI variant that was announced in January?  My understanding is that the only difference is an alternative version of the RK3399 SoC, there are no board changes required.  Thus it ought to be a separate production run, but little else.  Originally August had been suggested as the date, however since the non-AI version slipped a little I would imagine the whole plan slipped too.  Is there a new schedule that can be shared?

Good morning all.

I have Debian installed on my A64, trimmed down to be headless.  It only offers SSH connections with only TTY & SSH access.

It works fine but gphoto2 throws an error when attempting to access my Canon EOS 350d.  

gphoto2 --auto-detect re4cognises it:

ken@floki:~$ gphoto2 --auto-detect
Model                          Port
----------------------------------------------------------
Canon EOS 350D                 usb:002,003

gphoto2 -L or gphoto2 -l returns an error:

*** Error ***
An error occurred in the io-library ('I/O problem'): No error description available
*** Error (-7: 'I/O problem') ***

I also specified a port using --port and tried --summary.  Received the same error.

Last year on a Debian build and AMD X64 machine it worked fine.  My Win 10 machine sees the camera just fine.  Does anyone have any guidance?

Thanks!

-Ken
KC7RAD

I have tried debian, OMV and OMV64 and something is working.  The latest builds of OMV get me a SIP error every time I press a key on the keyboard.  None of the three can get a stable LAN connection.  The current debian build gets an IP address but I cant get any farther, even with an external USB network adaptor.  it'a always throwing me "destination host unavailable."

Do I just have a bad board?

My boot logs show chinese ip, anyway to prevent this?

I am using lastest ayufan's image

I'm running the ayufan bionic 0.6.44 image. I switched over to Rock64 from a libre ROC-RK3328-CC board running xenial because it too had some flaky usb3 support. I mounted a USB hard drive attached to a USB3 hub. From there I will load up to 8 microSD cards, each with video or photos and simlutaneously copy the data to the hard drive. 

My system runs flawlessly on the USB2 port with several different hubs. Once I plug it into the USB3 port, it will copy only a few hundred mb of data and the ports will disappear until i reboot. It is lost to the point that even plugging a mouse into the usb3 port does nothing. The symptoms on the ROC-RK3328 board were similar, but it occurred consistently after copying only a few mb of data. Syslog doesn't spit out anything meaningful from what I've seen. 

Although I haven't touched linux in many years, I wonder if this could be an issue at the driver level?


I was wondering if anyone encountered this problem, and what steps would be useful to narrow it down to finding a resolution

thanks

Hi all,

I was checking the logs on my rock64 - purchased in Feb 2018 and I see entries that look like there is a real time clock (RTC) on the board

May 31 09:03:04 rock64 kernel: [    2.263456] rk808-rtc rk808-rtc: rtc core: registered rk808-rtc as rtc0
May 31 09:03:04 rock64 kernel: [    3.225131] rk808-rtc rk808-rtc: setting system clock to 2016-01-21 08:50:11 UTC (1453366211)

Is this correct / possible?

Hi,

The subject says it all.  To be clear, the keyboard worked fine in 0.6.41 and now it does not. (I am running Stretch Minimal and the board has been running flawlessly for about a year.)  I am trying to sort out what changed.  Is anyone else seeing this?

I opened a case in github with a ton of details including screenshots and dmesg output.  However, as a quick summary, when I plug in my USB keyboard it is recognized fine, but every time I type a key, the following appears in the console:

rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]

This happens with every keypress and if I hold shift, it repeats rapidly. The Rock64 still accepts the characters normally though, but all this junk makes the physical keyboard unusable.  SSH access still works without an issue and everything seems to be running normally besides this.

Anyone else have this issue?  Any suggestions on how to address it?

Thank you!

Hi,

I've been running my Rock64 for about 4 months as an FTP/Samba server for my home network and it's been running great. Recently the red LED is constantly on. Previously it would only come on during processing activity. Everything seems to be working fine but I'm curious as to why the change in the LED status.

I am running 4.4.126-rockchip-ayufan-239 from a 16GB EMMC Chip.

I'm very interested in hearing your thoughts as to why this LED is now constantly on.

Best,
Tom

Hello,

I received this week my rock64 sbc and i installed ubuntu with etcher from image file: xenial-mate-rock64-0.5.5-136-arm64.img.xz. This gives a system version 16.04.3LTS with a kernel 4.4.77-rockchip-ayufan-136aarch64.

I also bought this wifi dongle (https://www.pine64.org/?product=usb-wifi...for-rock64), but i don't succed to make it working. It is well detected by the sbc (from lsusb output). Even after executing the command "sudo iw reg set FR" (i am in France), i don't succed to configure an internet connection with this wifi dongle.
Someone can help?

regards

Does the Rock64 have a real hardware random number generator that can be used as a source of entropy with rng-tools?