| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,034
» Latest member: DanneA
» Forum threads: 16,346
» Forum posts: 117,489
Full Statistics
|
| Latest Threads |
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: Rodery
3 hours ago
» Replies: 1
» Views: 253
|
PinePhone community poll
Forum: Community and Events
Last Post: Andrey Ivanchenko
11 hours ago
» Replies: 1
» Views: 4,142
|
Raudio for Rock64 V2
Forum: Linux on Rock64
Last Post: shinzuka
Yesterday, 02:02 PM
» Replies: 3
» Views: 271
|
pinephone keyboard
Forum: Pinebook Pro Hardware and Accessories
Last Post: zetabeta
Yesterday, 09:19 AM
» Replies: 1
» Views: 139
|
Window Maker Live for Pin...
Forum: Linux on Pinebook Pro
Last Post: vajak
Yesterday, 06:55 AM
» Replies: 9
» Views: 3,086
|
Shipping to Canada extrem...
Forum: Shipment Related Discussion
Last Post: xerafaw813
05-19-2026, 04:07 AM
» Replies: 4
» Views: 7,953
|
Fitting new case
Forum: Pinebook Pro Hardware and Accessories
Last Post: fnfgopro
05-19-2026, 03:45 AM
» Replies: 1
» Views: 500
|
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
05-18-2026, 02:11 PM
» Replies: 4
» Views: 12,937
|
PinePhone Game Thread
Forum: General Discussion on PinePhone
Last Post: elinkser
05-18-2026, 01:33 PM
» Replies: 29
» Views: 78,361
|
Has someone tried USB-C s...
Forum: PinePhone Pro Accessories
Last Post: elinkser
05-18-2026, 01:16 PM
» Replies: 4
» Views: 4,083
|
|
|
| Power button not being ignored by init |
|
Posted by: forestcreature - 05-17-2026, 05:08 PM - Forum: PostmarketOS on PinePhone
- No Replies
|
 |
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 !
|
|
|
|
| Unresponsive / inaccurate touchscreen |
|
Posted by: PerfectJam - 05-07-2026, 03:36 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 !
|
|
|
|
| Mobian image for the PinePhone |
|
Posted by: Korfou - 04-27-2026, 04:06 AM - Forum: Mobian on PinePhone
- Replies (2)
|
 |
Hello,
I have a PinePhone 64. I’m desperately trying to figure out which Mobian image to use for the PinePhone.
I can’t find the image for the PinePhone on the Mobian website. And I don’t want to make a mistake.
Thank you for your help.
|
|
|
|
|