| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
Yesterday, 10:08 AM
» Replies: 0
» Views: 47
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 18,911
|
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,030
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,271
|
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 217
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,926
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 317
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 143
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 218,049
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 275
|
|
|
| Best distro for kodi with web browser |
|
Posted by: vecnar - 11-03-2019, 11:53 AM - Forum: General Discussion on ROCKPRO64
- No Replies
|
 |
Hello,
I have openmediavault nas running on one rockpro64 and i got second one as a backup but rather than laying on the shelf thought to use it as fire tv stick replacement in one room.
Below are the things i tried: - Libreelec is great but lack of web browser is a big disadvantage as i have wireless keyboard with touchapad.
- Tried android 9.0 in hope to find and install some type of ui installer for and be able to control with hdmi cec but failed due to ethernet not working and i do not have wifi adapter.
What linux distro would you recommend that has some ui for remote control, quick to boot, kodi compliant, chrome compaitble and microsd card safe?
|
|
|
|
| Pinebook Pro - No Audio |
|
Posted by: bebop_man - 11-03-2019, 09:01 AM - Forum: Pinebook Pro Hardware and Accessories
- Replies (13)
|
 |
After I finally got it powered on, I I tried playing both a short movie, a youtube video, and a local MP3 file. No audio from any source.
I did confirm the volume is 100%, not muted, and using the es8316-spk-sound device, output to the analog stereo output.
Test speaker buttons also make no noise.
I don't get anything from the onboard speakers or the headphone jack. I haven't played with the UART switch yet as my understanding is that only affects the output of the jack itself, and not the onboard speakers.
apt update and apt upgrade have been run from the root logon.
Any suggestions?
|
|
|
|
| Overclock past 1.8/2.2 |
|
Posted by: kolbycrouch - 11-03-2019, 01:20 AM - Forum: General Discussion on ROCKPRO64
- Replies (3)
|
 |
Hi everyone! I've been testing overclocking on the rockpro64 for some time now, and I've gotten a stable ( I think ) overclock of 1.8/2.2 for the little and big cores.
However, when trying to push them any higher than 1800000000 and 2208000000 in the dts for ayufan-linux-mainline it never works.
I can attempt to set the big core to anything I'd like ( 7.0ghz ) and I get no real warning, and the clock as reported by sysfs is still 2.208ghz
I had to crank the voltage up a good bit to get them stable at this freq anyways so I'm not sure how much further I could go, but I'd like to try.
The thermals with 20mm heatsink + fan are still well within reason too.
|
|
|
|
| Can I rewrite a non-bootable eMMC from the PBP itself? |
|
Posted by: Kicou - 11-02-2019, 03:35 PM - Forum: General Discussion on Pinebook Pro
- Replies (3)
|
 |
I was playing with different OS images and decided that since I was able to successfully boot from SD card it would be OK to overwrite the eMMC module image.
I dd'ed a Rock64Pro (bionic-minal arm64) onto the eMMC and now it won't boot anymore, neither from eMMC nor SD.
I was able to eventually start from SD by disabling the eMMC via the internal switch, but since I can't see it I cannot write to it.
How can enable the eMMC but bypass it at boot in order to rewrite it from the PBP itself (I don't have any other equipment to which I can attach the eMMC).
I have enabled the serial connector and do have a serial console adapter that I can connect to a Linux box, and probably attach to via minicom.
|
|
|
|
| Horrible screen flicker/strobe on battery power |
|
Posted by: mattjb - 11-02-2019, 03:18 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (19)
|
 |
Moving my information to its own thread here from the General Discussions forum as it seems like at least one other person is having the issue too. I'm thinking it is hardware related as it happens on bootup before it hits any graphical intensive tasks or a desktop. I can only adjust the brightness when in desktop mode though, as it seems to be handled through the power management application.
Quote:I'm experiencing the exact same issue as Meatball regarding the flickering screen when on battery. When on AC power, it's fine, but as soon as I unplug it, any graphical related activity (even moving the mouse) causes random massive headache-inducing flickering. It seems to get worse as time goes on... It is still present with all dimming options off and happens at any brightness level as far as I can tell. I'm also hearing a high frequency whine when it switches to battery power though I haven't paid attention if it happens at different brightness levels. It's happening on both the default Debian install and on ayufan's rock64pro bionic-mate-pinebookpro-0.9.14-1159-armhf. I'll report back on other observations I make regarding this issue.
An update on the screen flicker:
Played around with the brightness a little to see the effect and here and these are my observations on brightness levels while on battery power only...
0: no coil whine, no flicker, but absolutely too dark to see anything worthwhile
1: bad coil whine, no visible flicker, usable, just a bit dim to liking
2: horrible continuous flicker/strobe - completely unusable
3: flicker but better than 2
4: a little better than 3
5: as bad as 2
6: better than 5
7: same as 6, just brighter
8: random flicker (1-2 per second), not continuous (fractions of a second) like levels 2-7
9: horrible flicker/strobe
10: worse than 9
11: worse than 10
12-22: same as 11, just brighter, completely unusable
The flicker/strobe is also visible in non-GUI applications, like when Ctrl+Alt+F1'd
For tracking purposes, battery level is being reported as 52%. I haven't had a full discharge yet.
I'm in the process of trying to drain the battery before a full recharge to see if that fixes it, just taking a while on brightness 1.
Could it perhaps be a defective battery? Any way to test this?
|
|
|
|
Pinebook Pro Fingerprint Magnet |
|
Posted by: neilman - 11-02-2019, 03:13 PM - Forum: General Discussion on Pinebook Pro
- Replies (28)
|
 |
I and a lot of other fine folks have noted that my/their beautiful black precious Pro seems to be a magnet for finger prints and smudges.
Only subtle mind, not blatant, however inquiring minds have to ask...
Any suggestions for the best and safest way to clean the case to remove fingerprints and smudges?
|
|
|
|
Manual: Howto cross-compile Upstream U-Boot for rock64 |
|
Posted by: rock7 - 11-02-2019, 02:59 PM - Forum: Rock64 Tutorials
- Replies (3)
|
 |
Step 1: Get the file bl31.elf
You can build ATF with Upstream arm-trusted-firmware repository to get the file “bl31.elf” (Way 1) or you use the rk322xh_bl31_vXXX.elf file from rockchip rkbin repository (Way 2)
Way 1 (build ATF with Upstream arm-trusted-firmware repository to get “bl31.elf”)
Install the required packages (Debian / Ubuntu):
Code: sudo apt-get install --no-install-suggests --no-install-recommends device-tree-compiler build-essential gcc make git libssl-dev
To cross-compile:
Code: sudo apt-get install --no-install-suggests --no-install-recommends cpp-10-aarch64-linux-gnu gcc-10-aarch64-linux-gnu gcc-10-aarch64-linux-gnu-base libasan6-arm64-cross libatomic1-arm64-cross libc6-arm64-cross libgcc-10-dev-arm64-cross libgcc-s1-arm64-cross libgomp1-arm64-cross libitm1-arm64-cross liblsan0-arm64-cross libstdc++6-arm64-cross libtsan0-arm64-cross libubsan1-arm64-cross cpp-aarch64-linux-gnu gcc-aarch64-linux-gnu binutils-aarch64-linux-gnu gcc-10-cross-base
Go into your Download folder and open Terminal there, then run:
Code: git clone https://github.com/ARM-software/arm-trusted-firmware
cd arm-trusted-firmware
Optional 4:
Verify code archive integrity (see also: https://restic.net/blog/2015-09-16/verif...-integrity ).
- Replace in the following Y.Y with the tag version number
Download pgp-key from the developer (you can find the gpg key ID on https://github.com/ARM-software/arm-trus...mware/tags) who has signed the tag, check fingerprints, import key and verify tag: Go into arm-trusted-firmware folder and run the following command and verify the fingerprint:
Code: git tag --verify vY.Y
Now create a archive that contain the same repository as the release with the tag version, run in arm-trusted-firmware folder the following command:
Code: git archive --format=tar --prefix=arm-trusted-firmware-Y.Y/ vY.Y | gzip -n > arm-trusted-firmware-Y.Y.tar.gz
Show the sha256 checksum from the archive that contain the repository from the release with the tag version and show sha256 checksum from the same archive https://github.com/ARM-software/arm-trus...Y.Y.tar.gz which belongs to the tag and compare the checksums:
Code: sha256sum arm-trusted-firmware-Y.Y.tar.gz
Code: curl -s -L https://github.com/ARM-software/arm-trusted-firmware/archiv/vY.Y.tar.gz | sha256sum
End of the optional section 4
Code: cd arm-trusted-firmware
make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3328 DEBUG=1 bl31 ERRATA_A53_836870 ERRATA_A53_1530924
Software Developers Errata Notice: developer.arm.com/documentation/epm048406/2100/
Go into your Download folder and open Terminal, then run:
Code: git clone git://git.denx.de/u-boot.git
or Download U-Boot source tree from https://ftp.denx.de/pub/u-boot/
(How to verify downloaded file with .sig file: https://stackoverflow.com/questions/1533...h-sig-file )
Search now the “bl31.elf” file in the arm-trusted-firmware build folder and copy it in the U-Boot folder.
Way 2 (use “bl31.elf” file from rockchip rkbin repository)
Go into your Download folder and open Terminal, then run:
Code: git clone git://git.denx.de/u-boot.git
or Download U-Boot source tree from ftp://ftp.denx.de/pub/u-boot/
(How to verify downloaded file with .sig file: https://stackoverflow.com/questions/1533...h-sig-file )
Go back into your Download folder and open Terminal, then run:
Code: git clone https://github.com/rockchip-linux/rkbin
cd rkbin
Search the file „rk322xh_bl31_vX.XX.elf“ in the rkbin folder (current version is v1.42, this file is in bin/rk33/) and change the name of this file to „bl31.elf“ and copy it in the U-Boot folder.
Step 2:
Compile U-Boot Install the required packages (for latest Debian):
Code: sudo apt-get install --no-install-suggests --no-install-recommends bison dh-python flex gcc-10 libexpat1-dev libmpdec3 make mime-support swig4.0 u-boot-tools cpp-10 libpython3.9-stdlib libpython3.9-dev libpython3.9-minimal libpython3.9 python3.9 python3.9-minimal python3-distutils python3-lib2to3 python3-pkg-resources python3-setuptools python-pip-whl python3-pip python3.9-dev device-tree-compiler build-essential git libssl-dev
To cross-compile:
Code: sudo apt-get install --no-install-suggests --no-install-recommends cpp-10-aarch64-linux-gnu gcc-10-aarch64-linux-gnu gcc-10-aarch64-linux-gnu-base libasan6-arm64-cross libc6-arm64-cross libgcc-10-dev-arm64-cross libgcc-s1-arm64-cross libgomp1-arm64-cross libitm1-arm64-cross liblsan0-arm64-cross libstdc++6-arm64-cross libtsan0-arm64-cross libubsan1-arm64-cross cpp-aarch64-linux-gnu gcc-aarch64-linux-gnu gcc-10-cross-base libatomic1-arm64-cross swig
Code: cd u-boot
make CROSS_COMPILE=aarch64-linux-gnu- BL31=bl31.elf rock64-rk3328_defconfig
Code: make CROSS_COMPILE=aarch64-linux-gnu- BL31=bl31.elf all
Flash U-Boot to microSD card Create partition with fdisk:
(replace sda1 with the name of your microSD card with number (you can find it with fdisk -l))
Code: sudo umount /dev/sda1
(replace sda with the name of your microSD card but now in the following without number (you can find it with fdisk -l))
Code: sudo fdisk /dev/sda
d
o
n
Enter
Enter
Enter
First sector (2048-62333951, default 2048): 32768
Enter
w
sudo mkfs.ext4 /dev/sda1 (with number!)
Code: sudo fdisk /dev/sda
p
Quote:At “Boot” must be a * if there is not a * then press “a” and then “w”
End of fdisk instructions.
Now run this command:
Code: sudo umount /dev/sda1
Quote:Replace sda1 with the name of your microSD (with number at the end)
Open Terminal in the U-Boot folder and flash U-Boot to microSD card with following commands (you can find the name of your microSD card with e.g. gparted, we search for example /dev/sda (without number! not /dev/sda1)):
Code: sudo dd if=./idbloader.img of=/dev/sda seek=64
sudo dd if=./u-boot.itb of=/dev/sda seek=16384
MIT License: https://avg7.de/forum/sicheres-alpine-li...pierrechte
Copyright © 2023 AVG7.de
|
|
|
|
| USB-C hub/dock/video |
|
Posted by: Corkonian - 11-02-2019, 10:29 AM - Forum: Pinebook Pro Hardware and Accessories
- Replies (2)
|
 |
Being a long time Windows Phone user, I still have a Microsuft USB-C Display Dock lying around.
My Lumia 950 is obsolete, but if possible, I would want to reuse the MS Display Dock.
It charges via USB-C, that's good, but as soon as I plug it in, the Pinebook display starts to blink. There is only the PB built-in display in the Control Centre/Displays dialog.
A keyboard connected to the USB hub won't work either. Strange.
|
|
|
|
| Disposeable? |
|
Posted by: Corkonian - 11-02-2019, 07:38 AM - Forum: Pinebook Hardware and Accessories
- Replies (3)
|
 |
Am I right to assume, that Pinebooks are disposeable items?
My 14" Pinebook died, when I tried to swap the LC unit with a 1080p one. The flat ribbon connector was held in place only by very flimsy soldering pads and the slight tug of releasing the flat ribbon was enough to lift a few connectors off the platter and breaking a few conductor tracks off the platter. No resoldering possible, no spares available, so it went into the stack of to-be-recycled parts. It's still there, if somebody has a 14" mainboard, I could make use of it.
The 11" Pinebook died today. As you remember, the keyboard wasn't registering the numeric row of keys (and "s", as I discovered later.). While dismantling the unit, two heatserts came lose and fell out, not to be seen again, the left display hinge cracked out of the plastic and the keyboard itself is not a serviceable item as it is welded in and removing all the plastic welds would be, given the "quality" of the case, a futile attempt. Still, if you happen to have an 11" Pinebook with a broken motherboard, but working keyboard, I could make use of it.
I know, they're only $99 computers, but still .....
|
|
|
|
|