| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
10 hours ago
» Replies: 20
» Views: 9,759
|
LCD DSI pine a64
Forum: General Discussion on PINE A64-LTS / SOPINE
Last Post: shinzuka
05-26-2026, 11:27 PM
» Replies: 0
» Views: 57
|
Raudio for Rock64 V2
Forum: Linux on Rock64
Last Post: shinzuka
05-26-2026, 02:34 PM
» Replies: 4
» Views: 448
|
Girls From Your Town - An...
Forum: General
Last Post: georgegohl888
05-26-2026, 06:07 AM
» Replies: 0
» Views: 66
|
Pinebook pro bricked?
Forum: General Discussion on Pinebook Pro
Last Post: Anthona
05-26-2026, 02:20 AM
» Replies: 4
» Views: 5,634
|
Boot Order in Pinebook Pr...
Forum: Linux on Pinebook Pro
Last Post: finmark
05-25-2026, 08:28 AM
» Replies: 12
» Views: 12,876
|
RockPro64 automatically r...
Forum: General Discussion on ROCKPRO64
Last Post: g2t
05-25-2026, 04:57 AM
» Replies: 0
» Views: 98
|
Volumio 3 Pine A64+ unoff...
Forum: Linux on Pine A64(+)
Last Post: shinzuka
05-23-2026, 03:26 PM
» Replies: 5
» Views: 522
|
Power button not being ig...
Forum: PostmarketOS on PinePhone
Last Post: wintercactus
05-21-2026, 04:44 AM
» Replies: 1
» Views: 214
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: Rodery
05-21-2026, 02:27 AM
» Replies: 1
» Views: 330
|
|
|
| RockPro64 automatically run after power recovery - my solution |
|
Posted by: g2t - 05-25-2026, 04:57 AM - Forum: General Discussion on ROCKPRO64
- No Replies
|
 |
Motivation
Since some years my system (Rockpro64 V2.1 2018-07-02) is not starting properly after a power loss, with increasing occurrence. It seems after some hours of power loss (e.g. over night) it is working more reliable, but when waiting only a few minutes this is not working anymore at all. Only the power button can be used for startup my system reliable.
In the forum there can be find a similar thread with some general information about the schematic and some measurements with a new system. Many thanks to @Nikolay_Po for his investigations on a new board. This was the base for my investigations and I solved it finally. I will describe my work step by step now, so others can repeat it and hopefully fix there system. If someone can give me an advice how to add/upload pictures, I will add my photos, so you can see what I have done.
Repeat the same measurement
"PMIC" is measured on C205 (right side) and "VCC5V0_SYS" is measured on C2006 (left side). Both can be found on top of the circuit board. The measurement results nearly equal the results from "Nikolay_Po" (the colours yellow and blue are interchanged in my measurement). So, perhaps, not the discrete components has changed its behavior but something inside RK808 changes over time. Or, the original values of the discrete components are chosen very close to the borders of the PMIC-system. No matter what it is, we can only change the discrete components - C204 catches my attention first.
Measure around and modify C204
The capacitor C204 can be found on the bottom of the circuit board (SD card slot at bottom left), in the area between C164 and C168, left of the resistor R89 and over the resistor R88. Another description: between the both big capacitor (C164 and C168) there are 4 small components in a flipped L-shape. C204 is the one in the corner of the "L".
The measurement was done with 2 channels, connected left and right of the C204 component. This means one is "VCC5V0_SYS" and the other one is the connection between C204, R89, D5 (soldered on the top side) and R88.
Try to increase the capacitor C204
Because it was working with a brand new board, most likely some aging process has changed the timings a bit. A second capacitor will increase the peak and the time a bit and maybe this can fix the problem. I added two connectors with wires left and right besides C204 and was able to add a second capacitor in parallel with an alligator clip.
1. choose 1uF --> working 100%
2. choose 100nF --> working 100%
Fix by soldering a SMD capacitor on top of C204
I disassembled some small SMD capacitors from a old circuit board and found one with around 150nF. This part I soldered on top of the C204 capacitor and this really fixed the problem for now.
|
|
|
|
| Power button not being ignored by init |
|
Posted by: forestcreature - 05-17-2026, 05:08 PM - Forum: PostmarketOS on PinePhone
- Replies (1)
|
 |
Hello, my pinepone is booting into pmOS with sxmo on sway, and the power button is acting literally: i.e. immediately it is pressed once, shutdown is initiated.
What I'm expecting to happen is that it will work as bound to Return in sxmo menus, that it will wake from suspend, or turn on the display when off, etc. (as it was doing previously).
I guess that I am missing some config to tell init to ignore the power button. Can someone please let me know e.g. which package would set that up on the pinephone? I reckon I might have accidentally deleted something in the fix of a messed up apk world.
|
|
|
|
| Screen size issues after update with diederik script |
|
Posted by: pine-user - 05-13-2026, 10:18 AM - Forum: PineNote Software
- No Replies
|
 |
After updating a fresh PineNote there are now problems with the sizing of the display. The battery percentage is cut off on the right, and the on screen keyboard is partially cut off on the bottom. The application icons in the application view are small and harder to see now than they were before, and there is no text description under them.
The steps I took were the following:
I just got a new PineNote. It was working fine out of the box. I tried running apt upgrade:
Code: sudo apt update
sudo apt upgrade
and I got the following error message:
Code: ******************************************************************************
*
* The base-files package cannot be installed because
* /lib64 is a symbolic link and not pointing at usr/lib64 exactly.
*
* This is an unexpected situation. Cannot proceed with the upgrade.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
******************************************************************************
I tried deleting the symbolic link as suggested here. The upgrade proceeded. During the upgrade, I was asked about updating the /etc/plymouth/plymouthd.conf config file. I chose to keep the current version. The upgrade finished without error. Over 800 packages were upgraded, and 17 packages were left unupgraded.
When I rebooted, the PineNote got stuck in a loop saying "booting". I was still able to ssh in. I followed the advice in the last post in the link above and ran the suggested script from diederik. (I downloaded the tar.gz labeled v0.0.4.) After running the script over ssh, the boot loop exited to the desktop screen on the PineNote. I rebooted again, and the PineNote booted normally and showed the desktop screen after booting.
However, at this point I noticed the screen size and icon size/label issues which I described above.
I have screenshots, but I'm not sure how to attach them.
|
|
|
|
| Star64: All listed distros don't boot |
|
Posted by: tantamount - 05-08-2026, 08:56 AM - Forum: Getting Started
- No Replies
|
 |
Here an overview of what Star64 distros work or don't.
TL;DR: None listed in the wiki boot
Irradium 3.8, kernel 6.12:
Doesn't boot. The power light stays green forever, no HDMI signal.
Irradium 3.8, kernel 7.0:
Doesn't boot. The power light stays green forever, no HDMI signal.
DietPi Trixie:
Doesn't boot. The power light stays green forever, no HDMI signal.
Armbian:
They dropped the Star64 some time ago.
NixOS v2023.11.26:
This one doesn't decompress: "unexpected end of file"
NixOS 23.11.20230827:
Doesn't boot. The power light stays green forever, no HDMI signal.
NuttX RTOS:
Doesn't boot. The power light stays green forever, no HDMI signal.
What does boot:
1. I still have an ancient copy of Armbian from when it did support the Star64, which does boot (non-graphical).
2. I see that Fishwaldo's old images from 2023 are still available here: https://pine64.my-ho.st:8443/
Thus I think the "Software releases" section should be updated to remove the entries for the distros that don't even boot.
Of Fishwaldo's 3 images (version 2.1), I get the following results: - The minimal distro does not boot. I get the green light that never blinks blue. This is a pity because text-only could be useful.
- The Weston distro boots and provides a fast GUI, however it doesn't provide anything else, like a menu or a way to launch apps or settings.
- The Plasma distro boots and provides a fast but more laggy GUI, but it does almost fully work.
Just now, with the Fishwaldo Plasma distro I was able to do the following which is pretty impressive:
- Boot up and log in as pine64 (password pine64).
- Set up Wifi, which works fine.
- Run Firefox, which is somewhat slow but it works.
- Download a FOSS program, compile it and run it.
- Su as root (password pine64) and run "apt update" but there are no new packages. (e.g. GCC is version 11 but the current version is 14).
- Install ffmpeg. This runs fine, however ffplay crashes with a segmentation fault.
- Mount a USB thumb drive from the command line (it wasn't seen by Dolphin file manager).
- Convert an MP3 to WAV and play it with `aplay`, which sounded like there was interference.
Regarding Weston, when I tried to force a text-only startup (systemctl set-default multi-user), this was ignored.
I think for some people, the text-only startup option could be necessary for projects.
|
|
|
|
| Updated Pinebook Pro? |
|
Posted by: tantamount - 05-07-2026, 08:51 AM - Forum: General Discussion on Pinebook Pro
- Replies (1)
|
 |
Hi,
I know there's a RAM crisis ongoing but is there ever going to be a new Pinebook Pro2 with more RAM?
Some chips are easier to get than others, for instance the 1.5GB chips are easier to get than 1/2/4 GB.
Therefore maybe a Pinebook with 6GB or 12GB RAM would be doable.
Cheers.
|
|
|
|
| Unresponsive / inaccurate touchscreen |
|
Posted by: PerfectJam - 05-07-2026, 03:37 AM - Forum: General Discussion on PineTime
- No Replies
|
 |
Hello,
I have a PineTime purchased in March 2023. When I first used it, the touchscreen was working perfectly.
I then left the watch unused for approximately 2 years. When I powered it back on, the touchscreen was no longer responding correctly, it feels like it is miscalibrated: inputs are not registered where I tap, or swipes are not recognized reliably.
I just updated the firmware to 1.16.0 (from 1.11.0), but the issue persists.
My assumption is that this may be a hardware degradation issue (deep discharge during storage) rather than a firmware problem, but I wanted to check here before concluding.
Has anyone experienced a similar issue after long-term storage? Is there any known fix or workaround short of hardware intervention?
Thanks and cheers !
|
|
|
|
|