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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,455
» Latest member: ysaito
» Forum threads: 16,190
» Forum posts: 116,848

Full Statistics

Latest Threads
Full desktop Surfing and ...
Forum: General Discussion on Pinebook Pro
Last Post: Pattienner
11 hours ago
» Replies: 2
» Views: 379
Any recommended brands/mo...
Forum: Pinebook Pro Hardware and Accessories
Last Post: fnfgopro
Yesterday, 08:38 PM
» Replies: 2
» Views: 810
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: tantamount
Yesterday, 02:25 PM
» Replies: 3
» Views: 569
Upgrading Armbian from v2...
Forum: Linux on Pinebook Pro
Last Post: Sb2024
08-09-2025, 06:53 AM
» Replies: 1
» Views: 704
Hello from Ukraine
Forum: P64-LTS / SOPINE Projects, Ideas and Tutorials
Last Post: Dendrocalamus64
08-08-2025, 07:13 PM
» Replies: 1
» Views: 56
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
08-08-2025, 04:48 PM
» Replies: 5
» Views: 330
PulseAudio dropouts after...
Forum: Linux on Pinebook Pro
Last Post: Dendrocalamus64
08-08-2025, 02:39 PM
» Replies: 2
» Views: 181
Simple Outdoor Weather St...
Forum: General Discussion on PineTab
Last Post: aria22
08-08-2025, 12:47 PM
» Replies: 0
» Views: 69
Armbian fix, current vers...
Forum: Linux on Pinebook Pro
Last Post: Sb2024
08-08-2025, 08:49 AM
» Replies: 0
» Views: 58
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
08-08-2025, 05:39 AM
» Replies: 2
» Views: 179

 
  Where to find older Mobian image?
Posted by: guenther - 10-29-2024, 05:46 AM - Forum: PineTab Software - Replies (2)

Hi folks, I managed to kill my PineTab (older one) with the last update. After boot no Login screen appears, only serial console available.
Where to find old Mobian pinetab-image with u-boot? On mobian website there is no image with u-boot available anymore.

Last working image according to mobian wiki is "mobian-pinetab-phosh-20220327.img.gz".


  Problem
Posted by: Arnur - 10-28-2024, 03:55 AM - Forum: General Discussion on Pinecil - No Replies

Why can't I order pinecil v2 in Kazakhstan


  Another one boots to black screen
Posted by: Sb2024 - 10-27-2024, 09:26 PM - Forum: General Discussion on Pinebook Pro - Replies (7)

I got my pine book pro back in march, put towboot on the spi and ran armbian from the emmc. Happy! After a period of disuse including full battery discharge, it started booting to a black screen. Sad! 

I put a new image of armbian on an SD card and it does the same thing. I opened the case and turned off the emmc switch and tried a fresh SD card. No change. I tried the long press hard reset. Same. 

Tow boot is still working. When it boots to the black screen, the power light is green and the caps lock and num lock lights work. 

I’m not sure what to do next.


  multithreading issue / SIGSEGV under InfiniSim
Posted by: lmamane - 10-26-2024, 09:57 AM - Forum: Development Discussion on PineTime - No Replies

I get various crashes/SIGSEGV/SIGFPE/uncaught exceptions/"mutex released when not held"/... when running InfiniTime under InfiniSim.

I opened the discussion for one of the reproducible ones at https://github.com/InfiniTimeOrg/InfiniSim/issues/160

Another reproducible one seems too subtle / incomprehensible for me, and it seems to me that different threads get mixed up. I was hoping someone here would have more clue than me.

The backtrace looks like:


Code:
Thread 5 "displayapp" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe29fe6c0 (LWP 642677)]
0x00005555555cf26b in lv_refr_obj (obj=0x7ffff79f1c, mask_ori_p=0x7fffe29fdb2e) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:892
892        if(obj->hidden != 0) return;
(gdb) bt
#0  0x00005555555cf26b in lv_refr_obj (obj=0x7ffff79f1c, mask_ori_p=0x7fffe29fdb2e) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:892
#1  0x00005555555cf1d6 in lv_refr_obj_and_children (top_p=0x555556bb96c8, mask_p=0x7fffe29fdb2e) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:867
#2  0x00005555555cef04 in lv_refr_area_part (area_p=0x7fffdc0017c2) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:773
#3  0x00005555555ce3d6 in lv_refr_area (area_p=0x7fffdc0017c2) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:515
#4  0x00005555555cdf7a in lv_refr_areas () at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:405
#5  0x00005555555cd9ba in _lv_disp_refr_task (task=0x7fffdc001918) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:204
#6  0x00005555555e53e4 in lv_task_exec (task=0x7fffdc001918) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_misc/lv_task.c:386
#7  0x00005555555e4e6f in lv_task_handler () at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_misc/lv_task.c:134
#8  0x00005555555af57a in Pinetime::Applications::DisplayApp::Refresh (this=0x5555556a4ae0 <displayApp>) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/displayapp/DisplayApp.cpp:251
#9  0x00005555555af208 in Pinetime::Applications::DisplayApp::Process (instance=0x5555556a4ae0 <displayApp>) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/displayapp/DisplayApp.cpp:149
#10 0x0000555555609dec in sdl_function_wrapper (instance=0x5555556a5bf8 <displayApp+4376>) at /home/master/src/pinetime/InfiniSim/sim/task.cpp:61

Note that according to gdb, in frame 1 lv_refr_obj_and_children is called with top_p=0x555556bb96c8 in thread LWP 642677. I have modified this function to make debug outputs to a file, one file per thread, as follows:

Near the top of the file:

Code:
#include <stdio.h>
#define __USE_GNU
#include <unistd.h>
#undef __USE_GNU
then in the function:
Code:
    char buf[40];
    snprintf(buf, sizeof(buf), "VERBOSE_DEBUG_lv_core_%d.txt", gettid());
    buf[sizeof(buf)-1] = (char)0;
    FILE* vdf = fopen(buf, "a");
and then I fprintf(vdf, ...), in particular I log the value of top_p. Now, the "funny thing" is according to the logs, lv_refr_obj_and_children is called with top_p=0x555556bb96c8 only in thread 642669!
Code:
$ grep -l 96c8 VERBOSE_DEBUG_lv_core_6426*
VERBOSE_DEBUG_lv_core_642669.txt
According to gdb, that thread is:
Code:
Thread 1 (Thread 0x7ffff6e22cc0 (LWP 642669) "infinisim"):
#0  0x00007ffff790d11f in __GI___poll (fds=0x7fffffffdac8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
29    ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb) thread 1
[Switching to thread 1 (Thread 0x7ffff6e22cc0 (LWP 642669))]
#0  0x00007ffff790d11f in __GI___poll (fds=0x7fffffffdac8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
29    in ../sysdeps/unix/sysv/linux/poll.c
(gdb) bt
#0  0x00007ffff790d11f in __GI___poll (fds=0x7fffffffdac8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007ffff71f0d12 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007ffff71f2d8f in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007ffff71f2f00 in xcb_wait_for_reply64 () from /lib/x86_64-linux-gnu/libxcb.so.1
#4  0x00007ffff743810c in _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
#5  0x00007ffff74336ff in XSync () from /lib/x86_64-linux-gnu/libX11.so.6
#6  0x00007ffff6498166 in ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0
#7  0x00007ffff648823b in ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0
#8  0x00007ffff7ecbbe6 in ?? () from /lib/x86_64-linux-gnu/libSDL2-2.0.so.0
#9  0x00007ffff7e2f276 in ?? () from /lib/x86_64-linux-gnu/libSDL2-2.0.so.0
#10 0x0000555555572074 in Framework::refresh (this=0x7fffffffdee0) at /home/master/src/pinetime/InfiniSim/main.cpp:609
#11 0x000055555556f5d5 in main (argc=1, argv=0x7fffffffe0c8) at /home/master/src/pinetime/InfiniSim/main.cpp:1145
Somehow the threads get mixed up???

According to the logs, that function is called in thread 642677 only with values top_p = 0x7fffdc001958, 0x7fffdc001c58 or 0x7fffdc001d58 and each time it is called, lv_obj_get_parent(top_p) == NULL (this is the value with which par is initialised), meaning the function exits without entering the while(par != NULL) loop, and never enters the lv_refr_obj call where the SIGSEGV happens, which is the one in the loop.

Still according to the logs, in thread 642669, all calls where top_p == 0x555556bb96c8 return, and the last call has another top_p value and has lv_obj_get_parent(top_p) == NULL.


  A big Incentive to choose RISC-V, when Dinosaurs Die Mammals Emerge
Posted by: biketool - 10-23-2024, 03:49 AM - Forum: PineTab Hardware - No Replies

https://www.windowscentral.com/microsoft...e-oct-2024
"A new report suggests that Arm Holdings PLC is ending its contract with Qualcomm Inc. which allows the firm to build chip designs based on Arm technology."
While Qualcom and ARM fight will we see an opening forRISC-V emerge as a safer option for large businesses?
Can RISC-V and open source hardware became the low risk option like Linux and other FOSS has?
The Qualcom vs ARM dispute will end up settled in court, this is a legal chess manuver between ARM and it's largest customer who in an IP license 'legal hack' attempt acquired another company to use a more favorable license, but this is an opportunity in a time of instability for CPU hardware alternatives to be discussed not unlike how Crowdstrike outage darkened the reputation of Microsoft windows vs FOSS alternatives as platforms for business.


  used ppp ee on sale
Posted by: giorez - 10-22-2024, 03:08 PM - Forum: General Discussion of PinePhone Pro - Replies (1)

I want to sell my ppp ee + uart cable + soft cover + external charger + extra battery + docking hub for about 200 euros. shipping from italy. Camera flash led has just died. Anyone is interested?


  CIrcuitry inside Battery Casing?
Posted by: rotdrop - 10-21-2024, 02:59 AM - Forum: Quartz64 Hardware and Accessories - Replies (1)

Hi there,




I purchased one of those aluminum battery casing:




https://pine64.com/product/lithium-battery-casing/




My question is: there is a small PCB inside with 3 ICs on top of it, does this PCB compose a battery protection circuit? That would be a very welcome feature, but I could not find any information about this in the shop or in this forum.




Best



Claus


  MMS Carrier Settings
Posted by: biketool - 10-20-2024, 09:19 AM - Forum: Mobian on PinePhone - No Replies

There are four fields in Mobian Trixie SMS/MMS settings
Phone Number - Your Modem's Phone Number ????
MMSC - correct
APN - correct
Proxy - correct

I have not seen a modem phone number on any GSM phone I have ever used.
I ask because I am still not able to view 9 MMSs even though the APN, MMSC, and proxy are verified correct.
I have tried my phone number with local area code and international country code too, phone number is not mentioned on my carrier's internet nor MMS settings.


  Inexpected reboot during watching youtube video
Posted by: regivanx - 10-18-2024, 02:14 AM - Forum: Linux on Pinebook Pro - Replies (1)

Good morning,

I was quietly watching a video on YouTube with Firefox when suddenly my pinebook pro restarted. The problem recurred three times.

The computer is not hot and restarts ~20 minutes after the start of the video.

The battery is charged and the computer plugged in.

Here are some diagnostic elements:

Code:
root@mmc-pbp2 /h/regivanx# journalctl -k -b -1
-- No entries --
root@mmc-pbp2 /h/regivanx# journalctl -b -1 | grep shutdown
root@mmc-pbp2 /h/regivanx [0|1]# dmesg | grep -i error
[    1.355108] rockchip-pcie: probe of f8000000.pcie failed with error -110
[   23.905498] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.pine64,pinebook-pro.bin failed with error -2


Do you know what this could be and how to fix the problem?


  Delivery within China
Posted by: Zdorenko - 10-16-2024, 10:20 PM - Forum: Shipment Related Discussion - Replies (2)

Hello. I would like to order a Pinecil V2 with a delivery to an address within China. Wrote an email to "Sales" 2 days ago, but no any response.
Anyone knows how I can manage with that?