| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 28,076
» Latest member: niggowai
» Forum threads: 15,667
» Forum posts: 114,488
Full Statistics
|
| Latest Threads |
Pinebook Pro Initial Impr...
Forum: General Discussion on Pinebook Pro
Last Post: dachalife
52 minutes ago
» Replies: 442
» Views: 583,376
|
[WIP] KDE Plasma Mobile 6...
Forum: PinePhone Pro Software
Last Post: u-kidjp
Yesterday, 08:08 AM
» Replies: 5
» Views: 551
|
Availability of the LoRa ...
Forum: PinePhone Pro Accessories
Last Post: zetabeta
Yesterday, 04:49 AM
» Replies: 1
» Views: 55
|
Pinephone Pro for a Debia...
Forum: General Discussion of PinePhone Pro
Last Post: zetabeta
Yesterday, 03:01 AM
» Replies: 2
» Views: 97
|
Where are the LoRaWAN dev...
Forum: General
Last Post: deuitpym
04-14-2024, 11:49 AM
» Replies: 14
» Views: 9,561
|
OpenBSD install on eMMC w...
Forum: BSD on RockPro64
Last Post: KC9UDX
04-12-2024, 02:06 AM
» Replies: 1
» Views: 78
|
PinePhone Pro and PinePho...
Forum: General
Last Post: Kevin Kofler
04-11-2024, 03:10 PM
» Replies: 2
» Views: 118
|
Case for Pinephone
Forum: PinePhone Accessories
Last Post: gramonyl
04-11-2024, 11:48 AM
» Replies: 13
» Views: 6,858
|
Phone powers off with hig...
Forum: PinePhone Hardware
Last Post: zetabeta
04-11-2024, 09:17 AM
» Replies: 7
» Views: 367
|
pinephone virtual keyboar...
Forum: General Discussion on PinePhone
Last Post: aular
04-10-2024, 03:45 PM
» Replies: 4
» Views: 261
|
|
|
| RockPro64 Official Kernel Support |
|
Posted by: ASIC - 10-31-2018, 09:15 AM - Forum: Linux on RockPro64
- Replies (23)
|
 |
When can we expect full support for the RockPro64 in the regular Linux kernel? I'm just curious because it would be kind of nice if it were possible to use an official distro image (i.e. Debian) instead of having to depend on Ayufan and others to keep making images for the RockPro64.
|
|
|
|
| Is there a guide somewhere how to upgrade Ubuntu on Pinebook? |
|
Posted by: dejan - 10-31-2018, 08:54 AM - Forum: Linux on Pinebook
- Replies (7)
|
|
Pinebook I bought not so recently has Xenial pre-installed. It is all working relatively well, but now I would like to upgrade it to the latest LTS Ubuntu (Bionic Beaver) and I need some guide to follow (if it exists)...
Alternatively, could someone refer to a Fedora installer for Pinebook (as I am predominantly RH/AL/CentOS/Fedora user)...
|
|
|
|
| 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.
|
|
|
|
|
