This may be a too general question, but what additional font package(s) must be installed in order for Firefox to display the CJK characters properly in web pages? Not that I can read them, but I prefer to see the real symbols instead of rectangles
This explains how to connect a serial console to the ROCKPro64. In this example I'm using the console sold by the Pine64 folks, but probably works for other serial consoles as well.
Parts/software needed
1) ROCKPro64 (I'm using the Rockpro64_V2.1 2018-06-06, 2GB version)
2) Serial console (I'm using a CH340G chipset based console, the one from Pine64)
3) Three F/F jumper wires (4 are included in the serial console from Pine64 and are 15 cm long)
4) Screen, Minicom or Picocom installed on a Linux distro
Steps
Connect the serial console to the PI-2-bus on the ROCKPro64
Set the yellow jumper on the serial console to 3V3 (see the picture below)
Connect a F/F jumper cable to the ground (GND) on the serial console and the other end to pin#6 of the PI-2-bus (black cable in the picture)
Connect a F/F jumper cable to RTX on the serial console and the other end to pin#8 of the PI-2-bus (brown cable in the picture)
Connect a F/F jumper cable to TXD on the serial console and DO NOT connect it to the ROCKPro64 (I'll explain below)
The reason for not connecting that last jumper cable to the ROCKPro64 is that in my case the ROCKPro64 doesn't boot when it is connected. When the cable is disconnected it boots fine. It is not really a problem because this connection is for sending. Receiving works just fine (and that is usually the reason why people use the serial console in the first place). Nevertheless, once the system is booting (or finished booting) you can connect the jumper cable and send commands to the ROCKPro64.
Connect the serial console to another computer and establish a connection
[1] Plug in the console into an USB port. I'm using a MacbookPro running Arch Linux:
Code:
[root@mbp_arch ~]# uname -a
Linux mbp_arch 4.17.13-arch1-1-ARCH #1 SMP PREEMPT Mon Aug 6 23:06:31 UTC 2018 x86_64 GNU/Linux
[2] Figure out how to access the serial console:
Code:
[root@mbp_arch ~]# dmesg | tail
[ 70.843501] usb 3-1: new full-speed USB device number 2 using ohci-pci
[ 71.071013] usb 3-1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.62
[ 71.071023] usb 3-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 71.071028] usb 3-1: Product: USB2.0-Serial
[ 71.103892] usbcore: registered new interface driver usbserial_generic
[ 71.103903] usbserial: USB Serial support registered for generic
[ 71.105335] usbcore: registered new interface driver ch341
[ 71.105348] usbserial: USB Serial support registered for ch341-uart
[ 71.105374] ch341 3-1:1.0: ch341-uart converter detected
[ 71.119050] usb 3-1: ch341-uart converter now attached to ttyUSB0
[3] The way to access the console is through ttyUSB0 (in my case, it could be different for you)
[4] Open a terminal and start screen, minicom or picocom with the following parameters:
This will start the application with a baud rate of 1.5M on ttyUSB0 (which we have just established is the serial console)
[5] Connect the power cable to the ROCKPro64 and enjoy the boot messages that will show. At this point you can connect the last jumper cable to pin#10 on the PI-2-bus which will allow you to send as well (and be able to login).
[6] To quit screen press 'ctrl-a' first followed by 'k'. Answer 'y' to the question to kill the current connection. To quit minicom press 'ctrl-a' followed by 'x' and select 'yes'. For picocom press 'ctrl-a' first and then 'ctrl-q'.
My Pinebook has been working nicely but a few days ago, several keys started generating spurious characters. I don't know of anything that triggered it.
The misbehaving keys have changed over time and are currently (using a Dvorak layout): 'x' (keycode 56) generates a spurious 'w' (keycode 59), 'm' (keycgode 58) generates a spurious 's' (keycode 47) and space (keycode 65) generates a spurious 'z' (keycode 61). In all cases, the autorepeat repeats only the second (spurious) character.
I've tried multiple reboots and power cycles (including disconnecting the battery to force a hard power power cycle) to no avail. Has anyone else seen anything like this or have any suggestions for what to try.
I'm seeling my 2GB PineA64 with RTC Clock, Wifi Module, Serial Console Adapter & Case. No SD-Card or Power Brick. Fully Functional but I was never satisfied with device.
Price: $20 + shipping..
If you're interested PM me or reply. For shipping please tell me the destination country.
I'm using Xenial Mate image on Sopine.
My goal application is use Sopine with OpenCV.
I have ported my software from desktop and I'm facing huge lags during video recongition. CPU load is 99-100%.
On my desktop same software runs with ~20-40 CPU load on AMD-A4-4000 (2 cores).
After I have run glmark2 benchmark most of tests shows FPS very low.
Attached full log.
I'm not advanced user on linux, so give me advice what can I do with it. Maybe I need to enable some acceleration or something like this...
So i got my EMMC to USB adapter today....flashed the image stretch-minimal-rockpro64-0.7.9-1067-arm64.img onto the emmc
And no joy.....Am i missing something?
Do i have to use a special image? set a jumper?
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!
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.
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 ?
![[Image: EfJ0JhP.jpg]](https://i.imgur.com/EfJ0JhP.jpg)
