| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Slarm64 on PinePhone [Uno...
Forum: PinePhone Software
Last Post: donchurch
6 hours ago
» Replies: 35
» Views: 24,470
|
Bluetooth Handsfree Bount...
Forum: General Discussion on PinePhone
Last Post: conifera
Yesterday, 04:58 PM
» Replies: 23
» Views: 1,770
|
Install Tow-Boot on the S...
Forum: Pinebook Pro Tutorials
Last Post: alchemist
Yesterday, 12:20 PM
» Replies: 13
» Views: 7,975
|
Help needed to understand...
Forum: Mobian on PinePhone
Last Post: Pelecanus
Yesterday, 07:59 AM
» Replies: 2
» Views: 56
|
Helpful setup summaries
Forum: General Discussion on PineTab
Last Post: tophneal
04-18-2024, 09:48 AM
» Replies: 1
» Views: 46
|
After upgrade on 08.03.24...
Forum: General Discussion on PineTab
Last Post: Corkonian
04-18-2024, 01:22 AM
» Replies: 3
» Views: 620
|
how to use rk2aw-spi-flas...
Forum: General Discussion of PinePhone Pro
Last Post: Gooberpatrol66
04-17-2024, 10:23 PM
» Replies: 0
» Views: 56
|
GloDroid (Android-14)
Forum: PinePhone Software
Last Post: GaryM
04-17-2024, 08:39 AM
» Replies: 1
» Views: 104
|
Android images for RockPr...
Forum: Android on RockPro64
Last Post: tophneal
04-17-2024, 07:50 AM
» Replies: 1
» Views: 37
|
Pinebook Pro Initial Impr...
Forum: General Discussion on Pinebook Pro
Last Post: KC9UDX
04-16-2024, 07:29 PM
» Replies: 443
» Views: 585,294
|
|
|
| Rock64 as multiple server |
|
Posted by: Sputnik - 10-30-2018, 01:21 AM - Forum: General Discussion on ROCK64
- Replies (2)
|
 |
Hello -
I want to set up a Rock64 mini server with NextcloudPi and an extra web server for myself.
In front of both could be a a NGinX as a proxy server so that the subdomains can be reached without port information. My idea is to use Docker and set up NGinX, NextcloudPi and the web server in different containers. Does the setup make sense?Or how can it be better configured?
I don't know Linux very well yet. Are there any instructions or hints for this?
I want to learn and constantly improve the system but not run into a dead end...
Any help would be appreciated!
|
|
|
|
| apt --fix-broken install |
|
Posted by: KC7NOA - 10-29-2018, 06:33 PM - Forum: Linux on Rock64
- Replies (1)
|
|
rock64@rock64:~/Downloads/sdrangel/build$ sudo apt-get install dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
libgl1-mesa-dev : Depends: libglvnd-dev but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
im just a bit over my head in dealing with this .....
i would love suggestions ....
also need to install Qt5
|
|
|
|
| Not able to write u-boot to SPI |
|
Posted by: Jix0 - 10-29-2018, 11:08 AM - Forum: General Discussion on ROCKPRO64
- Replies (2)
|
|
Hello everyone.
I have a trouble flashing uboot to my RockPro64 4GB variant. I am trying to use rock64_write_spi_flash.sh script, but nothing is flashing.
I made all steps according to wiki, booted from SD card, used latest ubuntu image, but everything I get is following error:
Code: rock64@rockpro64:/dev$ sudo su
[sudo] password for rock64:
root@rockpro64:/dev# rock64_write_spi_flash.sh
Doing this will overwrite data stored on SPI Flash
and it will require that you use eMMC or SD
as your boot device.
Type YES to continue or Ctrl-C to abort.
YES
Writing /dev/mtd0 with content of /usr/lib/u-boot-rockpro64/rkspi_loader.img
Erasing 4 Kibyte @ 0 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 0 (mtd0)
error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 110 (Connection timed out)
Erasing 4 Kibyte @ 1000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 1 (mtd0)
error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 110 (Connection timed out)
Erasing 4 Kibyte @ 2000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 2 (mtd0)
error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 110 (Connection timed out)
Erasing 4 Kibyte @ 3000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 3 (mtd0)
error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 110 (Connection timed out)
Erasing 4 Kibyte @ 4000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 4 (mtd0)
error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 110 (Connection timed out)
Erasing 4 Kibyte @ 5000 -- 0 % complete ^C^C
I have even tried steps written here: https://forum.pine64.org/showthread.php?...e#pid40677 (,only changed the overlay address to "ff1d0000" to fit to RockPro64 dts).
I never flashed anything to SPI before, so it can't be messed up. I tried the SD card method with only ayufan uboot image and this don't work either. Nothing is written to it..
Output of "mtdinfo":
Code: root@rockpro64:/dev# mtdinfo
Count of MTD devices: 3
Present MTD devices: mtd0, mtd1, mtd2
Sysfs interface supported: yes
root@rockpro64:/dev# mtdinfo /dev/mtd0
mtd0
Name: loader
Type: nor
Eraseblock size: 4096 bytes, 4.0 KiB
Amount of eraseblocks: 1016 (4161536 bytes, 4.0 MiB)
Minimum input/output unit size: 1 byte
Sub-page size: 1 byte
Character device major/minor: 90:0
Bad blocks are allowed: false
Device is writable: true
root@rockpro64:/dev# mtdinfo /dev/mtd1
mtd1
Name: env
Type: nor
Eraseblock size: 4096 bytes, 4.0 KiB
Amount of eraseblocks: 8 (32768 bytes, 32.0 KiB)
Minimum input/output unit size: 1 byte
Sub-page size: 1 byte
Character device major/minor: 90:2
Bad blocks are allowed: false
Device is writable: true
root@rockpro64:/dev# mtdinfo /dev/mtd2
mtd2
Name: vendor
Type: nor
Eraseblock size: 4096 bytes, 4.0 KiB
Amount of eraseblocks: 64 (262144 bytes, 256.0 KiB)
Minimum input/output unit size: 1 byte
Sub-page size: 1 byte
Character device major/minor: 90:4
Bad blocks are allowed: false
Device is writable: true
Output of dmesg:
Code: root@rockpro64:/dev# dmesg | grep spi
[ 2.015555] rockchip-spi ff1d0000.spi: Failed to request TX DMA channel
[ 2.016160] rockchip-spi ff1d0000.spi: Failed to request RX DMA channel
[ 2.016778] rockchip-spi ff1d0000.spi: no high_speed pinctrl state
[ 2.017904] m25p80 spi32766.0: gd25q128 (16384 Kbytes)
[ 2.018394] 3 ofpart partitions found on MTD device spi32766.0
[ 2.018924] Creating 3 MTD partitions on "spi32766.0":
[ 164.537097] m25p80 spi32766.0: flash operation timed out
[ 204.537255] m25p80 spi32766.0: flash operation timed out
[ 244.537347] m25p80 spi32766.0: flash operation timed out
[ 284.537402] m25p80 spi32766.0: flash operation timed out
[ 324.537509] m25p80 spi32766.0: flash operation timed out
[ 364.537587] m25p80 spi32766.0: flash operation timed out
Thanks for any suggestions. This is really driving me nuts.. Any help will be appreciated.. :-)
|
|
|
|
| How to change DSI Clock |
|
Posted by: r.tanaka - 10-29-2018, 04:03 AM - Forum: LCD and Touch Panel
- No Replies
|
|
Hi everyone
How do I change the DSI clock?
The software and hardware used are as follows.
Hardware: PINE A64-LTS
Software: Armbian
Thank you.
|
|
|
|
New Pinebook releases (28.10.2018) - Ayufan |
|
Posted by: Luke - 10-29-2018, 03:34 AM - Forum: Linux on Pinebook
- Replies (5)
|
 |
New Pinebook releases from ayufan - including Bionic with LXDE, Xenial with Mate and Stretch minimal.
Do note that that OS images designated for Pinebooks with 1080p IPS panel are designated accordingly. N.B. The new images are also available for Pinebooks from previous batches with non-1080p ISP screens.
Download here
|
|
|
|
| WIFI driver compilation |
|
Posted by: wsk - 10-28-2018, 04:34 AM - Forum: Rock64 Hardware and Accessories
- Replies (1)
|
|
Hello everyone,
I have a Rock64 board and have two USB wifi adapters, one with rtl8192SU chip and the other with rtl8192EU. I have spent several days trying to compile the drivers for both and changed the system from debian to ubunto and back. I cannot get the system to compile the drivers. I followed the threads here and the readme on github for several versions. Nothing is working. Can anyone direct me to a tutorial about the preparation of the system for compiling the drivers that would be enough to get this to work? I now have armbian. I successfully installed the .deb driver but it cannot identify the hardware and the driver does not show in the sysotem.
Any help is appriciated.
|
|
|
|
| Smooth playback of 4K videos working under Ubuntu / mpv |
|
Posted by: danboid - 10-27-2018, 01:15 PM - Forum: General Discussion on ROCK64
- Replies (2)
|
 |
One of the main reasons I bought my rock64 was in the hope of being able to use it to play 4K videos. Although I have achieved that previously with libreelec, libreelec/kodi would always crash or reboot on me after a while plus I'd prefer to run a regular/proper Linux distro and mpv is a much more powerful video player than kodi is.
Today I finally got 4K videos to play back smoothly using mpv under ayufan's bionic/lxde Ubuntu image. The secret, as disclosed by @fcoulombe on github, was to edit /usr/local/bin/rkmpv and add:
--drm-mode=21
To the mpv options, which fixed the green lines and very jerky playback I was experiencing without. A lot of my videos require that I also use the switch
--video-aspect=1.3333 (and --video-rotate=no)
as using that rids of the letterboxing.
https://github.com/ayufan-rock64/linux-build/issues/249
|
|
|
|
| Odd HDMI issues |
|
Posted by: jman005 - 10-26-2018, 09:15 PM - Forum: General Discussion on ROCK64
- No Replies
|
|
Hey there,
I've been trying to set up the rock64 with an HDMI LCD (this one) for a while now. HDMI output works fine with regular monitors - however, when I try to connect to the LCD oddities follow. When using Ubuntu Mate, the LCD briefly flashes on (to a black screen) and off. I was told this may be an issue with resolution size, so I tried to use another monitor to change it; however, connecting to the LCD seemed to have broken the HDMI output. I re-flashed the MicroSD with an LXDE distro which seemed to fix the issue, then decreased the resolution before connecting to the LCD, but the same results occurred with the only difference being that the LCD displayed a 'no signal' message rather than flashing on and off.
Any suggestions? Thanks in advance.
|
|
|
|
|
