| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,695
» Latest member: mkelty
» Forum threads: 16,260
» Forum posts: 117,185
Full Statistics
|
| Latest Threads |
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: brb78
4 hours ago
» Replies: 0
» Views: 21
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11 hours ago
» Replies: 5
» Views: 532
|
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: KelsonV
Yesterday, 02:20 PM
» Replies: 0
» Views: 53
|
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 111
|
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 458
|
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,109
|
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 60
|
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 79
|
Second screen mirroring
Forum: General
Last Post: andrekyler
11-17-2025, 01:06 AM
» Replies: 3
» Views: 1,900
|
7 inch touch panel patche...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: mkjmkj
11-17-2025, 12:57 AM
» Replies: 0
» Views: 87
|
|
|
| Assembling the premium aluminum case |
|
Posted by: mlefevre - 01-01-2019, 02:22 PM - Forum: Rock64 Hardware and Accessories
- Replies (14)
|
 |
I just purchased another Rock64 to build another NAS using OMV and I decided to get the premium aluminum case this time. It arrived with no instructions and I have a couple of questions:
1) The kit includes 2 pieces of blue thermal tape and a little packet of thermal compound. Am I supposed to use all three (stacked) in the assembly?
2) There is a little acrylic light pipe that looks like it should go in a hole near the white and red LEDs but it is too big. Do I just need to drill the hole in the case out a little?
Thanks for any help from those who've gone before me.
Marc
|
|
|
|
| 10 bit HEVC support on Rock64? |
|
Posted by: Bowser - 01-01-2019, 07:19 AM - Forum: General Discussion on ROCK64
- Replies (3)
|
 |
Does the Rock64 support 10 bit HEVC 1080p and 4K content?
I've heard that LibreELEC for Rock64 does support it, but it's in alpha and seemingly not very reliable. The other option is ayufan's ATV build, but I'm not sure if HEVC 10 bit is supported on this.
Will I be able to play HEVC 10 bit content on ayufan's ATV build? Also, what is the extent of HDR support on it? I currently only have a 1080p TV but plan to upgrade to a 4K HDR TV in the near future.
|
|
|
|
| Battery powered rock64 |
|
Posted by: omer811 - 12-31-2018, 03:07 AM - Forum: General Discussion on ROCK64
- Replies (2)
|
 |
Hello, I'm working on a project and I want to power the rock64 board off an external USB battery,
I was thinking about soldering the plus and minus wires from the USB port to the plus and minus of the barrel power jack.
I know I won't get charge information or anything, but will the battery recognize that it's being used and won't automatically shut down?
does anyone have any experience with running the board on battery?
Thanks a lot,
Omer.
|
|
|
|
Does the Rock64 single board computer (1, 2 or 4 GB ram) have a PCie slot? |
|
Posted by: IP_Proxy - 12-29-2018, 09:02 PM - Forum: General
- Replies (5)
|
 |
Hello everyone I'm thinking of getting a Rock64 single board computer and I'm wondering if it has any type of PCie slot (slot for external gpu) because apparently it's GPU is not that good and I'm getting the 4gb variant of the Rock64 SBC because I want to use it as a mini pc when I'm out and about so please can someone answer?
--Thanks in advance
Prox
|
|
|
|
| 4 better solutions than DD Images |
|
Posted by: cfriedt - 12-29-2018, 06:15 PM - Forum: General
- Replies (1)
|
 |
Hi forum,
I guess this is more of a suggestion to the release manager for pine64 and less of a question.
While I appreciate the dd image format's simplicity, it would make a lot more sense to distribute images lest wastefully.
Part of the reason I mention that is because the dd image that is distributed has a corrupt partition table, so it can't be copied to an SD card via more efficient means.
I run into this problem regularly and I myself am a fan of a couple of methods:
1) the bash binary
https://www.linuxjournal.com/content/add...ll-scripts
This is more useful if you want to add obscurity (not security) to the images you distribute
2) a zip file, along with 2 bash scripts that implement *an API*
This method is a bit more complex.
script 1: flash.sh
usage: flash.sh [--device|-d <device>] [--tmpdir|-t <tempdir>]
device - a block device e.g. a default could be /dev/mmcblk0, exported as $DEVICE
tempdir - a temporary directory e.g. see man mktemp, exported as $TMPDIR
in turn, script 1 sources script 2, and script 2 exposes a few shell functions.
script 2: details.sh
fetch(): fetches all source files to $TMPDIR specified by script1
urls are encoded in the details.sh file
small files (e.g. patch files) can be stored in the .zip file locally
large files can be fetched from the internet
prepare(): applies patches
partitions device
resizes partitions as appropriate
a really compact and scriptable way to specify a partition layout that can fill up space to the end of the disk (so you don't need to have 8GB, 16GB, and 32GB files) is using sfdisk
https://linux.die.net/man/8/sfdisk
http://download.vikis.lt/doc/util-linux-...k.examples
flash(): could use dd, or not
a more efficient means for Pine64 would be to distribute .ext4 files or .vfat files that can be mounted as loop devices (using losetup)
3) fastboot
This is arguably the standard way of distributing Android factory images and is described in detail at the link below
https://source.android.com/setup/build/running
4) There is always yocto too.. ¯\_(ツ)_/¯
Really, there must be a better alternative than sitting here, waiting for 26 billion zeros to be written to an sd card.
Cheers,
C
|
|
|
|
| Forcing u-boot to detect USB3 storage |
|
Posted by: jandastroy - 12-29-2018, 11:27 AM - Forum: Linux on Rock64
- Replies (8)
|
 |
So I've still been having some intermittent boot issues with my USB3 SATA drive. Every now and then u-boot randomly gives me this result during the usb startup process:
Code: Hit any key to stop autoboot: 0
resetting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: Core Release: 3.10a
USB3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... cannot reset port 1!?
1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Usually calling reset a few times fixes the issue, which is fine if I'm at home but when this happens remotely I can't do anything about it. Until now!
I've been playing with the u-boot environment a bit and decided to try a custom bootcmd to keep trying the usb until it magically just works. Doing this bypasses the default distro_bootcmd which calls into the sd, mmc, usb, and PXE boot options, so if you use any of these alternate boot options you may not want to do this. I'm only interested in the usb boot device, so this setup just repeats the usb boot attempt until it succeeds or the sun burns out.
If you're having intermittent problems with your usb bootup and want to try this, you can type the following in at your u-boot console:
Code: env set bootcmd 'itest 0 == 1; while itest $? != 0; do run usb_bootretry; done'
env set usb_bootretry 'setenv devnum 0; usb reset; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi'
env save
It's not a perfect solution, but it hasn't failed me yet so far. It seems to get the storage device properly on the 2nd attempt every time (unless the 1st attempt works of course), but I've only been running this for a little bit. I think this problem stems from the usb controller being in a bugged state which is why the forced retry manages to get it to start properly by resetting the adapter into a valid state.
In case you try this but want to restore the system default boot sequence, just type the following at the u-boot console:
Code: env set bootcmd 'run distro_bootcmd'
env save
|
|
|
|
| Port REQUEST |
|
Posted by: NightCrawler504 - 12-29-2018, 09:55 AM - Forum: Android on RockPro64
- No Replies
|
 |
Would somebody be so kind as to port android to rp64 from any of these tv boxes H96 Max, X99, Ebox r99, RKM M39 they all work great as tv box, all use rk3399?
|
|
|
|
|