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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,004
» Latest member: shinzuka
» Forum threads: 16,337
» Forum posts: 117,448

Full Statistics

Latest Threads
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
3 hours ago
» Replies: 14
» Views: 15,131
Mobian image for the Pine...
Forum: Mobian on PinePhone
Last Post: Korfou
04-27-2026, 09:57 AM
» Replies: 2
» Views: 264
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 222
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 19,681
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,140
my pinecil v2 is not work...
Forum: General Discussion on Pinecil
Last Post: jagrav
04-17-2026, 06:28 AM
» Replies: 0
» Views: 156
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,505
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 343
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 9,371
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 480

 
  USB-C connector Overheated and melted
Posted by: nickbenjones - 05-25-2023, 10:08 AM - Forum: PinePhone Hardware - Replies (2)

Hello, Postmarket os 22, pinephone daily driver now for over a year now. Plugged in my phone, while the phone was running, this morning to a USB-A to USB-C charge cable and the usb connector started melting down. Melted the back cover, the battery is ok, but the cable and usb-c side board is toast. The cable and power brick are both anker brand. Voltage and ripple on power brick seems more than reasonable, so I am ruling that out. Is this a common failure? Any idea on cause? I have never had anything like this happen before with any phone. Any guidance would be great

Cheers!

[Image: BPvRnyc]

[Image: BPvRnyc]


  Very slow GbE when receiving, fast sending
Posted by: unixpoet - 05-25-2023, 09:51 AM - Forum: General Discussion on Quartz64 - Replies (3)

I received my Quartz64 a little while ago and have been experimenting a bit. The network is extremely slow when receiving data, but does the usual 940 Mbit/s full saturation for 1 gigabit when sending. Please see below iperf3 outputs. 10.0.0.201 is my Quartz64 model A and 10.0.0.4 is a pretty powerful amd64 Linux workstation.

-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 10.0.0.4, port 32952
[  5] local 10.0.0.201 port 5201 connected to 10.0.0.4 port 32954
[ ID] Interval          Transfer    Bitrate
[  5]  0.00-1.00  sec  110 MBytes  926 Mbits/sec                 
[  5]  1.00-2.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  2.00-3.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  3.00-4.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  4.00-5.00  sec  112 MBytes  942 Mbits/sec                 
[  5]  5.00-6.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  6.00-7.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  7.00-8.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  8.00-9.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  9.00-10.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  10.00-10.00  sec  308 KBytes  885 Mbits/sec                 
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval          Transfer    Bitrate
[  5]  0.00-10.00  sec  1.09 GBytes  940 Mbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201 (test #2)
-----------------------------------------------------------
Accepted connection from 10.0.0.4, port 54688
[  5] local 10.0.0.201 port 5201 connected to 10.0.0.4 port 54704
[ ID] Interval          Transfer    Bitrate        Retr  Cwnd
[  5]  0.00-1.00  sec  1.17 MBytes  9.81 Mbits/sec  41  2.83 KBytes     
[  5]  1.00-2.00  sec  827 KBytes  6.78 Mbits/sec  23  2.83 KBytes     
[  5]  2.00-3.00  sec  1.37 MBytes  11.5 Mbits/sec  48  2.83 KBytes     
[  5]  3.00-4.00  sec  2.42 MBytes  20.3 Mbits/sec  53  2.83 KBytes     
[  5]  4.00-5.00  sec  1.24 MBytes  10.4 Mbits/sec  37  2.83 KBytes     
[  5]  5.00-6.00  sec  2.25 MBytes  18.9 Mbits/sec  102  2.83 KBytes     
[  5]  6.00-7.00  sec  1.12 MBytes  9.42 Mbits/sec  95  2.83 KBytes     
[  5]  7.00-8.00  sec  3.08 MBytes  25.9 Mbits/sec  234  2.83 KBytes     
[  5]  8.00-9.00  sec  3.11 MBytes  26.1 Mbits/sec  73  2.83 KBytes     
[  5]  9.00-10.00  sec  3.48 MBytes  29.2 Mbits/sec  72  2.83 KBytes     
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval          Transfer    Bitrate        Retr
[  5]  0.00-10.00  sec  20.1 MBytes  16.8 Mbits/sec  778            sender


Look at all those retransmits! I've verified that the cable and switch port and everything else in the setup are otherwise fine. This happens in both Arch and Plebian. Did I receive a bad board, should I submit an RMA? Or is there something else going on here?


  PineTab2 shipping
Posted by: GloriousCoffee - 05-25-2023, 03:06 AM - Forum: General Discussion on PineTab - Replies (17)

Hi!

I've ordered a PineTab2 a few days ago. The article title says shipping will occur mid-may, which we've passed. Will the order be included in the next planned shipment, or would I have to wait until next batch is produced? And if so, what time frame should I be expecting?


  PD resets during heat up tip [Pinecil V2]
Posted by: Neitron4ik - 05-24-2023, 12:27 PM - Forum: General Discussion on Pinecil - Replies (2)

Strange power behaviour of chain: Baseus 100W GAN Charger + Pinecil V2(+short tip).
After pressing button to heat up the solder tip, Pinecil starts heating, and in some moment Charger resets TypeC output, I press again it tries to heat up again and resets again, and after several tries, it reach threshold temperature and after that I can solder easily. Seems not enough power, and charger detects power peaks and resets output.
This is 100W charger from Baseus:  https://www.aliexpress.com/item/1005003117435688.html , I am using 100W TypeC cable.
I tried other cables, doesnt help. I tried to limit power in Pinecil's "advanced seting" to 65 to 50 W to 40W - doesnt help.
I tried to disconnect all other consumers, and remain only Pinecil connected to this Charger - doesnt help.
This Baseus charges my 65W Lenovo laptop easily.

Is there ideas what to check? Maybe some other advanced settings to try? Huh


  How To Access the Pine Phone Auxillary microSD Without Removing Card
Posted by: pinephoneuser22 - 05-23-2023, 07:01 PM - Forum: General Discussion on PinePhone - Replies (2)

I would like to use the Pine Phone auxiliary microSD slot with a memory card as external storage for data files. I would like to access the auxiliary microSD card from a laptop to transfer and manage files. Is there an easy way to do this with the card in the phone? I can take the card out and use a card reader, but from a typical user perspective that is not good workflow. When i use the tow-boot like functionality in Mobian at boot i only see the internal eMMC memory as a storage device from a Mac or Windows laptop, the auxiliary microSD is not shown. The Mobian Phosh Portfolio app can see the auxiliary microSD which is formatted as FAT to be compatible with Mac and Windows. I am unable to connect the phone to a Linux virtual machine so cannot evaluate things using Linux. Any help is appreciated.


  Star64 apps crashing constantly
Posted by: tantamount - 05-23-2023, 05:56 AM - Forum: General - Replies (8)

Hi folks,

I'm using the latest 1.2 version of the Plasma distro provided by Fishwaldo.
I'm finding that many applications crash within a few seconds of launching them, or simply do not work.

- The web browser, maybe called something fishAngel? I forget the name. It crashes within seconds of visiting any web page.
- The web browser Konqueror is unable to bring up any web page. It just remains a blank page.
- The Settings app frequently crashes within 1 minute of launch.
- The "unicode" terminal app (not Konsole, the other one), has extreme graphics corruption and is unusable.
- After some hours of running, the window manager completely crashed, leaving only the Konsole running.

Is this just me (which might indicate a bad board) or is everyone seeing these problems?

Thanks.


  Getting started for developers
Posted by: lagrang3 - 05-22-2023, 04:20 AM - Forum: General Discussion on PinePhone - Replies (5)

Hello,

I am looking for information about developing applications for the pinephone.

As far as I understand, from the software layer point of view,
the Pinephone should behave like any multipurpose desktop computer.

But I wonder if there is a development kit for accessing the pinephone's devices:
cameras, microphone, gravity sensor, etc.

Thanks for any information,
Lagrang3


  How to enable CoreSight ETM trace on RockPro64
Posted by: shpark - 05-21-2023, 11:34 PM - Forum: Linux on RockPro64 - No Replies

Hi,

I am trying to reproduce coresight-trace, a CoreSight ETMv4 trace decoder utility, on RockPro64 running vanilla 6.3.1 Linux kernel and dtbs (https://github.com/RICSecLab/coresight-trace).

The utility depends on a library called CSAL (upstream: https://github.com/arm-software/CSAL, fork: https://github.com/RICSecLab/CSAL/tree/f...dd5e7a744e) which is used to configure CoreSight registers.

I found that the helper script, csscan.py (https://github.com/ARM-software/CSAL/blo.../csscan.py), is supposed to print the topology of CoreSignt components given the address of the ROM table, but it ends up halting the whole machine when trying to access CoreSight components within Big core cluster. Here are the failing output:

Code:
sudo python3 coresight-tools/csscan.py --topology 0xfe400000
@0xfe400000    0x000 0x000 r0.0                        ROM table
@0xfe401000    0x23b 0x908 r2.0  CS Funnel             funnel         <no arch>        in-ports:6
@0xfe403000    0x23b 0x906 r4.0  CS CTI                CTI            <no arch>        channels:4 triggers:8
@0xfe404000    0x23b 0x101 r1.0  TM101 Timestamp       CoreSight timestamp generator
@0xfe405000    0x23b 0x912 r4.0  CS TPIU               port           <no arch>        TPIU
@0xfe420000    0x23b 0x4a3 r4.0                        ROM table
@0xfe430000 - device excluded from scan
@0xfe431000    0x23b 0x9d3 r4.0  Cortex-A53 PMU        PMU (core)     Arm PMUv3 rev0   aff=0x80000000 not acessing
@0xfe432000 - device excluded from scan
@0xfe433000    0x23b 0x9d3 r4.0  Cortex-A53 PMU        PMU (core)     Arm PMUv3 rev0   aff=0x80000001 not acessing
@0xfe434000 - device excluded from scan
@0xfe435000    0x23b 0x9d3 r4.0  Cortex-A53 PMU        PMU (core)     Arm PMUv3 rev0   aff=0x80000002 not acessing
@0xfe436000 - device excluded from scan
@0xfe437000    0x23b 0x9d3 r4.0  Cortex-A53 PMU        PMU (core)     Arm PMUv3 rev0   aff=0x80000003 not acessing
@0xfe438000    0x23b 0x9a8 r4.0  Cortex-A53 CTI        CTI            Arm CTI rev0     aff=0x80000000 channels:4 triggers:8 gate
@0xfe439000    0x23b 0x9a8 r4.0  Cortex-A53 CTI        CTI            Arm CTI rev0     aff=0x80000001 channels:4 triggers:8 gate
@0xfe43a000    0x23b 0x9a8 r4.0  Cortex-A53 CTI        CTI            Arm CTI rev0     aff=0x80000002 channels:4 triggers:8 gate
@0xfe43b000    0x23b 0x9a8 r4.0  Cortex-A53 CTI        CTI            Arm CTI rev0     aff=0x80000003 channels:4 triggers:8 gate
@0xfe43c000    0x23b 0x95d r4.0  Cortex-A53 ETM        ETM            Arm ETMv4 rev0   aff=0x80000000 pdsr=0x00000023 ETMv4.0 ts:64 bb cc min-ccit:4 retstack stall events:4 resources:16 addrcomp:4 ssc:1 pecomp:0 counters:2 seqstates:4 extin:30 extinsel:4
@0xfe43d000    0x23b 0x95d r4.0  Cortex-A53 ETM        ETM            Arm ETMv4 rev0   aff=0x80000001 pdsr=0x00000023 ETMv4.0 ts:64 bb cc min-ccit:4 retstack stall events:4 resources:16 addrcomp:4 ssc:1 pecomp:0 counters:2 seqstates:4 extin:30 extinsel:4
@0xfe43e000    0x23b 0x95d r4.0  Cortex-A53 ETM        ETM            Arm ETMv4 rev0   aff=0x80000002 pdsr=0x00000023 ETMv4.0 ts:64 bb cc min-ccit:4 retstack stall events:4 resources:16 addrcomp:4 ssc:1 pecomp:0 counters:2 seqstates:4 extin:30 extinsel:4
@0xfe43f000    0x23b 0x95d r4.0  Cortex-A53 ETM        ETM            Arm ETMv4 rev0   aff=0x80000003 pdsr=0x00000023 ETMv4.0 ts:64 bb cc min-ccit:4 retstack stall events:4 resources:16 addrcomp:4 ssc:1 pecomp:0 counters:2 seqstates:4 extin:30 extinsel:4
@0xfe600000    0x23b 0x4a4 r0.0                        ROM table
@0xfe610000 - device excluded from scan
@0xfe620000    0x23b 0x906 r4.0  CS CTI                CTI            <no arch>        channels:4 triggers:8

(halt)

Based on the TRM, the address it starts to fail seems to be around the CLUSTERB_CTI0 or CLUSTERB_PMU0, implying that there are some issues with accessing CoreSight components on the Big core cluster.

I'd like to ask if you have any recommendations on what should I do to resolve this issue.

Any information would be deeply appreciated.

Best Regards,
Seonghyun


  Basic question: KDE apps on GNOME and vice versa
Posted by: jojuma - 05-21-2023, 03:16 PM - Forum: General Discussion on PinePhone - Replies (4)

So I have this very basic question:

Is it kind of "blasphemy" to run KDE apps in a GNOME environment and vice versa? Is there something like an unwritten law that says KDE apps belong to KDE only and GNOME apps to GNOME only?

I understand this is possible since everything ends up at the X server (or Wayland), but since I have to install large packages like e.g. "org.gnome.Platform" etc. to use GNOME apps in a KDE environment, I just wonder, if that is legit...?

Thanks for clarification for a non pro Smile


  Error: Device rejected by app
Posted by: jojuma - 05-21-2023, 03:49 AM - Forum: General Discussion on PineTime - Replies (1)

Hi,

I'm not sure if this is the right place to ask, maybe it's the KDE subforum or the developer site.
On my Pinephone (KDE Community Edition) I installed Watchmate to manage and update my Pinetime.
The Pinetime is found by the app but when I try to connect it I get the error "device rejected by app".
I had Watchmate running on other distros on the Pinephone without any problems. What could be the reason for this behaviour?

Thanks!