| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,998
» Latest member: Dada
» Forum threads: 16,337
» Forum posts: 117,447
Full Statistics
|
| Latest Threads |
Mobian image for the Pine...
Forum: Mobian on PinePhone
Last Post: Korfou
04-27-2026, 09:57 AM
» Replies: 2
» Views: 125
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
04-19-2026, 12:56 PM
» Replies: 13
» Views: 14,913
|
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 190
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 19,461
|
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,123
|
my pinecil v2 is not work...
Forum: General Discussion on Pinecil
Last Post: jagrav
04-17-2026, 06:28 AM
» Replies: 0
» Views: 119
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,443
|
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 309
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 9,264
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 433
|
|
|
| rock64 bonnie results with patriot burst ssd |
|
Posted by: edwinbmiller - 04-13-2018, 06:07 AM - Forum: Rock64 Hardware and Accessories
- No Replies
|
 |
using xenial-minimal 156 with the ssd on usb3 port.
Version 1.97 ------Sequential Output------ --Sequential Input- --Random-
Concurrency 1 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
rock64 4G 168 99 100785 59 53812 50 976 99 100715 53 11664 371
Latency 59015us 194ms 2397ms 29160us 28069us 19886us
Version 1.97 ------Sequential Create------ --------Random Create--------
rock64 -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 11424 71 +++++ +++ 18450 87 11717 73 +++++ +++ 12908 67
Latency 905us 2012us 2598us 1277us 20313us 1545us
1.97,1.97,rock64,1,1523581505,4G,,168,99,100785,59,53812,50,976,99,100715,53,11664,371,16,,,,,11424,71,+++++,+++,18450,87,11717,73,+++++,+++,12908,67,59015us,194ms,2397ms,29160us,28069us,19886us,905us,2012us,2598us,1277us,20313us,1545us
|
|
|
|
| pine LTS with openBSD |
|
Posted by: sean - 04-12-2018, 10:56 PM - Forum: General Discussion on PINE A64-LTS / SOPINE
- Replies (4)
|
 |
Hi All,
I received the pine64 LTS board today and would like to load openBSD on to it. I have openBSD current snapshots running on a much older (from February 2016ish) pine64 board without any issues.
I did what I did last week to install openBSD on the working board:
Code: sudo dd if=miniroot63.fs of=/dev/sdf bs=1M
Hooked up the serial connection, applied power and all I receive in the terminal is this:
Code: U-Boot SPL 2018.03 (Mar 20 2018 - 04:43:06 -0600)
DRAM: 0 MiB
### ERROR ### Please RESET the board ###
So what's it mean? Do I need to have the spi flashed with something? Does openBSD need to add support for this u-boot? Do I need an eMMC thing?
Here's the installation instructions for arm64:
https://ftp.openbsd.org/pub/OpenBSD/snap...TALL.arm64
https://www.openbsd.org/arm64.html
LTS is missing, but I do see this: "Pine64 Pine 64/64+" Is this separate from LTS?
Thanks,
sean
|
|
|
|
Looking for donor board to replace voltage regulator or any other ideas? |
|
Posted by: ansic - 04-12-2018, 10:57 AM - Forum: Rock64 Hardware and Accessories
- Replies (1)
|
 |
My Rock64 have a faulty voltage regulator. The breakdown happened from a faulty power supply adapter. It can still boot up a Linux OS but there are a few complications.. HDMI is not working and Its very slow to execute programs. The error messages are about voltage regulator not responding to the I2C messages so I figured replacing the RK805 voltage regulator might fix it.
The problem is that I don't have a spare RK805 and Pine64 does not want to sell me one, it's understandable but a bummer since there are is nobody else with these chips. That is why I am asking here for advice.
|
|
|
|
| I could not start ROCK 64. |
|
Posted by: pine3228 - 04-12-2018, 07:08 AM - Forum: Linux on Rock64
- No Replies
|
 |
Google Translate :
axel -a -n 5 https://github.com/ayufan-rock64/linux-b...m64.img.xz && xz - dv bionic - minimal - rock 64 - 0.6.31 - 209 - arm 64. img. xz && sudo dd if = bionic - minimal - rock 64 - 0.6.31 - 209 - arm 64. img of = / dev / sda
I tried starting up ROCK 64 using such a command, but unfortunately I could not start it. (White lamp, green lamp and red lamp are in a state of lighting) I suspected that the image file was damaged, but I will not change how many times. However, writing 0.5.15 xenial and artful images on the micro sd card, I was able to launch it. The same problem occurred in the images of bionic (arm64) of 0.6.25, 0.6.26, and 0.6.27. What should I do?
Also, I have another question.
https://dl.armbian.com/rock64/
Although it is an image of armbian distributed here, it was also impossible to start up here. Apparently, there seems to be no boot partition, but how do you start it?
原文
axel -a -n 5 https://github.com/ayufan-rock64/linux-b...m64.img.xz && xz -dv bionic-minimal-rock64-0.6.31-209-arm64.img.xz && sudo dd if=bionic-minimal-rock64-0.6.31-209-arm64.img of=/dev/sda
私はこのようなコマンドを使い、ROCK64の起動を試しましたが、残念ながら起動することができませんでした。(白のランプと緑のランプと赤のランプが光りっぱなしの状態)私は、イメージファイルの破損を疑いましたが、何度やっても変わりません。しかし、マイクロsdカードに0.5.15のxenialとartfulのイメージを書き込んだところ、起動することができました。この問題は、0.6.25、0.6.26、0.6.27のbionic(arm64)のイメージでも同じことが起きました。どうすればいいのでしょうか?
それと、もう一つ質問があります。
https://dl.armbian.com/rock64/
こちらで配布されてるarmbianのイメージですが、こちらも起動することができませんでした。どうやら、bootパーティションなどが無いようなのですが、どのようにして起動するのですか?
|
|
|
|
| Clusterboard i2c and Linux |
|
Posted by: jgullickson - 04-11-2018, 09:45 AM - Forum: Clusterboard
- Replies (3)
|
 |
Hello all,
I'm trying to connect an MCP23017 to the i2c bus on one of the Clusterboard's headers (J4) and I'm unable to see it from Linux using i2cdetect:
Code: jjg@pine64so:~$ sudo i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
jjg@pine64so:~$ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
I had the same problem interfacing this same chip to a full-size A64 board and resolved it by adding some pull-up resistors to the i2c pins (connecting them to the 3.3v supply as suggested in this thread: https://forum.pine64.org/showthread.php?tid=2079&page=2). However the Clusterboard doesn't supply 3.3v at this header.
I'm not sure how best to proceed. Assuming the pull-ups are required on the Clusterboard as they are on the A64, do I need to provide a 3.3v supply (perhaps stepping the 5v supply down to 3.3v) or is there a better way to achieve the same thing?
It seems weird to me that the header would supply the i2c pins if they couldn't work without external regulation but then again I'm pretty new to working with i2c and maybe this is normal?
Any pointers are appreciated, thanks!
|
|
|
|
| Help pls~Desktop (xfce4/lxde/gnome/i3) installation problem. Install_desktop.sh faild |
|
Posted by: yours_david - 04-10-2018, 11:41 PM - Forum: Linux on Rock64
- No Replies
|
 |
Hi Pine64 community,
I have been very happy to have Rock64 running openmediavault to manager my 3 HDDs for share, 2 HDDs sitting on USB3 HDD dock for non-raid share, 1 HDD USB2 running cold backup. Now I would like to install desktop, e.g. xfce4/lxde/gnome/i3, on top of my OMV image. I run "install_desktop.sh" script from "/usr/local/sbin/" after searching through forum and internet.
The installation progress get stuck while fetch plex, the error code is in below. The full details list at bottom for better reading.
Code: E: Failed to fetch https://downloads.plex.tv/repo/deb/dists/./public/InRelease Unable to find expected entry 'main/binary-armhf/Packages' in Release file (Wron g sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
My firmware based on 0.6.31: jenkins-linux-build-rock-64-209, which was upgraded from 0.6.28: jenkins-linux-build-rock-64-197 by running "sudo apt-get update -y & sudo apt-get install linux-rock64 -y".
As a linux noob, I tried what I can but still failed to install xfce4 then run KODI while running OMV at background.
I checked install_desktop.sh trying to comment off fetch plex in order to continue such installation, but I can't find anything.
I also run "apt-get install xfce4", but don't know how to run xfce4.
Can anyone help me to run OMV+HTPC Kodi solution on my rock64 NAS build? Two questions.
Q1, how to fix install_desktop.sh?
Q2, without that .sh strip, how can I install xfce4 and kodi then run based on OMV rock64 firmware? Thank you for any advise.
Cheers,
David
Full log which run install_desktop.sh
Code: root@NAS-David:/usr/local/sbin# install_desktop.sh xfce4
Get:1 file:/var/cache/openmediavault/archives InRelease
Ign:1 file:/var/cache/openmediavault/archives InRelease
Get:2 file:/var/cache/openmediavault/archives Release
Ign:2 file:/var/cache/openmediavault/archives Release
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Hit:5 http://security.debian.org stretch/updates InRelease
Hit:6 http://ppa.launchpad.net/ayufan/rock64-ppa/ubuntu bionic InRelease
Get:7 https://download.docker.com/linux/debian stretch InRelease [39.1 kB]
Get:11 https://downloads.plex.tv/repo/deb ./public InRelease [3408 B]
Hit:12 http://packages.openmediavault.org/public arrakis InRelease
Ign:14 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch I nRelease
Ign:15 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing s tretch InRelease
Ign:16 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-plex stre tch InRelease
Get:17 http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases InRelease [1253 B]
Ign:18 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-sync stre tch InRelease
Hit:19 https://openmediavault.github.io/packages arrakis InRelease
Ign:20 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker st retch InRelease
Hit:9 https://apt.syncthing.net syncthing InRelease
Get:21 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch R elease [4389 B]
Hit:21 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch R elease
Hit:8 http://cdn-fastly.deb.debian.org/debian stretch-backports InRelease
Ign:10 http://cdn-fastly.deb.debian.org/debian stretch InRelease
Hit:13 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
Hit:22 http://cdn-fastly.deb.debian.org/debian stretch Release
Get:24 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing s tretch Release [4389 B]
Hit:24 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing s tretch Release
Get:26 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-plex stre tch Release [3540 B]
Hit:26 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-plex stre tch Release
Get:29 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-sync stre tch Release [3540 B]
Hit:29 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-sync stre tch Release
Get:31 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker st retch Release [3540 B]
Hit:31 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker st retch Release
Fetched 43.8 kB in 8s (5031 B/s)
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0xf6ca1468>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0xf6ca1468>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Reading package lists... Done
E: Failed to fetch https://downloads.plex.tv/repo/deb/dists/./public/InRelease Unable to find expected entry 'main/binary-armhf/Packages' in Release file (Wron g sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
|
|
|
|
|