Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,966
» Latest member: Sergio Gus
» Forum threads: 16,334
» Forum posts: 117,438

Full Statistics

Latest Threads
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 115
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,618
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 197
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 93
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 216,712
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 167
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 249
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,054
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 914
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 592

 
Lightbulb [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes
Posted by: devrtz - 05-12-2020, 01:04 AM - Forum: PinePhone Hardware - Replies (108)

Hello all,

after having faced crashes on the latest (yet to be publicly released) debian+phosh image,
which troubled only me and none of the other team members, I have found out that the issue
had only occured after the patch increasing dram frequency had been incorporated.
pmOS had this patch for a while now and I remember when first getting the pinephone it also crashed on me.
At that time I thought that the build may not have been mature yet, but now it dawned on me that this was probably
also related to dram frequency.

So I have built a few different uboot images with varying frequencies (from 492MHz to 624Mhz) to see how high I can go,
while still having a reliable system.
I figured I can't be the only one having this problem, maybe someone else had the same problem without realizing what exactly the problem was, so thats why I'm calling for willing volunteers to try out different clock speeds and see if they have any problems.

TL;DR:
Had problems with crashes; turns out it had to do with dram clock speeds
Feel free to download my u-boot binaries or built them yourself and please report your findings.
Personally I had a stable system with 588MHz, but not with 600MHz!

LAST UPDATE: 26.07.2020
Flashable binaries (should work on all distros?)

https://fortysixandtwo.eu/upload/pinepho...pl-492.bin
https://fortysixandtwo.eu/upload/pinepho...pl-504.bin
https://fortysixandtwo.eu/upload/pinepho...pl-516.bin
https://fortysixandtwo.eu/upload/pinepho...pl-528.bin
https://fortysixandtwo.eu/upload/pinepho...pl-540.bin
https://fortysixandtwo.eu/upload/pinepho...pl-552.bin
https://fortysixandtwo.eu/upload/pinepho...pl-564.bin
https://fortysixandtwo.eu/upload/pinepho...pl-576.bin
https://fortysixandtwo.eu/upload/pinepho...pl-588.bin
https://fortysixandtwo.eu/upload/pinepho...pl-600.bin
https://fortysixandtwo.eu/upload/pinepho...pl-612.bin
https://fortysixandtwo.eu/upload/pinepho...pl-624.bin

Flashing the u-boot binaries onto your device (as root) - make sure to use the correct device (jumpdrive exposes both eMMC and the SD):

Code:
# dd if=u-boot-sunxi-with-spl-XXX.bin of=/dev/sdX bs=8k seek=1
This should work independent of which distro you are currently using.


Debian packages

https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb
https://fortysixandtwo.eu/upload/pinepho..._arm64.deb

As a debian package it will only work on debian based distros.

To install it you should
  • download the .deb
  • install with dpkg -i
  • run u-boot-install-pinephone

I am interested to see whether this issue is widespread or if I just had bad luck in the silicon lottery Smile


PS: From the datasheet it seems that the ram should be usable up to 800MHz?


  PCIe 12v power issue
Posted by: dlan17 - 05-11-2020, 09:30 PM - Forum: General Discussion on Pinebook Pro - Replies (1)

I'd like to supply vcc12v pcie from external power, is it possible to remove Q13 (page 27)? and where I can find the top/bottom silk file (to locate Q13 component).


http://files.pine64.org/doc/rockpro64/ro...21-SCH.pdf


  Free to a good home: Pinebook pro
Posted by: Watercourse - 05-11-2020, 08:55 PM - Forum: General Discussion on Pinebook Pro - Replies (7)

The case has a couple of small cracks in the thin strap under the USB ports, and the hinge is getting tight.
The fun part is that it does not currently have a working OS, as i fumbled an install.
So, i'm hoping someone with the chops and the inclination to see it through to working again will contact me.
It can be yours for the cost of shipping.


  Problems with customs clearance
Posted by: jacksondaniels - 05-11-2020, 06:10 PM - Forum: General Discussion on PinePhone - Replies (1)

Hi all

Customs says that my customs declaration doesn't conform to Australian customs regulations.

I hate it bec it will cost me more. any advice of a customs broker you can give?


  Booting from NVME
Posted by: ilovegentoo - 05-11-2020, 11:59 AM - Forum: Linux on RockPro64 - Replies (11)

Hi all,

I finally bit the bullet and ordered a Intel 660p 512GB NVME SSD for testing my RockPro64 on it.
I downloaded the latest Ayufan Debian Buster build from https://github.com/ayufan-rock64/linux-b...m64.img.xz

I originally installed it on an SD card, then decided to copy it over to an USB stick (supposedly faster).

After that I again copied it over to the NVME drive.

The script I used for the migration is:

Code:
#!/bin/bash

# Parameters
source="/dev/disk/by-id/usb-Samsung_Flash_Drive_xxxxxxxxxxxxxxxx-0:0"
destination="/dev/disk/by-id/nvme-INTEL_xxxxxxxxxxxxxxxxxxxxxxxxx"
partitions=(1 2 3 4 5 6 7)
backupFolder="./backup"
rootid=7 # Root ID partition number

# Generate timestamp
timestamp=$(date +%Y%m%d%H%M)

# Create folder if not exist
mkdir -p $backupFolder

# Save GPT disks
sgdisk --backup=$backupFolder/$(basename $source)_$timestamp.sgdisk $source
sgdisk --backup=$backupFolder/$(basename $destination)_$timestamp.sgdisk $destination

# Copy $source layout to $dest and regenerate GUIDs
sgdisk --replicate=$destination $source
sgdisk -G $destination

# Clone partitions
for partition in "${partitions[@]}"; do
   echo "Clone partition $source-part$partition -> $destination-part$partition"
   dd if=$source-part$partition of=$destination-part$partition bs=1M status=progress
   echo "Cloned partition finished!"
done

# Must be done manually for now ...
#yes "-1MiB" | parted $destination resizepart $rootid
#e2fsck $destination-part$rootid
#resize2fs $destination-part$rootid

I then included the following modules and regenerated the initramfs:

cat /etc/initramfs-tools/modules
Code:
# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax:  module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
pcie_rockchip_host
phy_rockchip_pcie
nvme


update-initramfs -k all -u


I cannot book from NVME at the present moment. The onboard red LED stays lighted up.
If I put back the USB stick it boots normally.

Is there something I am forgetting ? Thank you


  Ubuntu 18.04 Bionic LXDE Desktop
Posted by: karbon17 - 05-11-2020, 09:46 AM - Forum: General Discussion on ROCK64 - Replies (1)

hello everyone and sorry my bad english, I installed the Ubuntu 18.04 Bionic LXDE Desktop version on Rock64 and it works but not the remote control, I installed both Teamviewer Host and Anydesk but neither of them starts, is there any solution?

I'm new to Linux :-) thanks


  Faulty Microphone - BH
Posted by: valentin - 05-11-2020, 07:58 AM - Forum: PinePhone Hardware - Replies (7)

Hello,

Apparently I have a PinePhone with a faulty microphone (or some component on which the microphone depends on) - it never worked.

A few days ago, I have found out that the audio routing for the phone calls is finally working. I downloaded and imaged the SD card with the latest build of Ubuntu Touch (at that time #307) and made a call to my Mrs. I could hear her in the PinePhone's earpiece but she couldn't hear me. Then I tried with a pair of headphones with the microphone on the wire. This worked - I could hear her and she could hear me.

I have re-imaged the micro-SD card with other distros: Debian with Phosh, Manjaro, and a couple of other Ubuntu Touch builds, including #318.

I have also turned on and off the kill-switch for the microphone (3) - it made no difference.

Has anyone else had this issue? Any feedback?

Thank you,


  Firmware Update over Bluetooth LE
Posted by: lupyuen - 05-11-2020, 07:24 AM - Forum: Development Discussion on PineTime - Replies (2)

Hi All: Here's a proposed plan for supporting PineTime firmware updates over Bluetooth LE. If you're a firmware developer, please take a look...

https://lupyuen.github.io/pinetime-rust-...ticles/dfu

It covers everything we need to do to implement firmware updates in our firmware: Bootloader, Bluetooth Stack, Firmware Rollback, Flash ROM Layout, Firmware Format, Mobile Apps, ...

We need to adopt a common mechanism for firmware updates if we wish to allow PineTime Owners to switch firmware easily. It's more work for us developers... But it's a huge benefit for PineTime Owners!

Please lemme know what you think... While writing this article I have received really good feedback from firmware developers. Their suggestions have been documented in the "Upcoming Enhancements" section.

The most serious limitation in the proposed design is that the firmware size must not exceed 232 KB. Hence there will be an upcoming enhancement to increase this limit (by moving the Standby Firmware Image to External SPI Flash).

Thanks everyone for the awesome work on PineTime... Now let's make PineTime fun and easy to learn and explore! :-)


  Error when trying to install local package with pkcon
Posted by: koenigs - 05-11-2020, 03:22 AM - Forum: Linux on Pinebook Pro - No Replies

I'm a beginner with Linux so please understand my skills are quite limited for the moment.

I wish to install Open Store so I installed PackageKit

Code:
$ sudo apt install packagekit

Then downloaded the armhf package from this page: https://open-store.io/app/openstore.openstore-team and ran


Code:
$ pkcon install-local --allow-untrusted openstore.openstore-team_2.95_armhf.click


However I'm getting the following error


Quote:Installing files              [=========================]         
Testing changes               [=========================]         
Finished                      [=========================]         
Fatal error: Could not find package(s)


Same issue if I'm trying to install another application like OSM Scout Server

What am I missing? 
Thanks for your answers


  Failure to boot
Posted by: atcwells - 05-10-2020, 01:34 PM - Forum: General Discussion on ROCKPRO64 - Replies (1)

Hi all,

I'm looking for some assistance please, I received my RockPro64 (+NAS case, fan, heat sink, 2xSATA board, Pine power supply) and set everything up, using ayufan's OMV images, and everything worked great. Up and running in about 1 hour (including putting the fan in the wrong place/orientation 3 times).

However, after shutting down in linux, moving it to my server cab and trying to boot again, I am no longer able to get my device to run. I don't get into Linux, I get a stack trace, after which the device reboots, but then does not power on again (I have to remove the power in order to then boot again).

I have removed all devices, so I'm running with just the board, USB keyboard and DVI connected to my display (I've just tried removing the network connection) but get the same results each time.

I've used both the armhf and the arm64 variants on the same SD card.

I am a programmer, but my embedded days were limited and a long time ago.. Can anyone offer advice on how to investigate further? Do I need to go the UART route, or am I best trying to return my board?

Thanks