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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,772
» Latest member: d2minik
» Forum threads: 16,285
» Forum posts: 117,304

Full Statistics

Latest Threads
Booting Issues
Forum: PineNote Software
Last Post: d2minik
5 hours ago
» Replies: 22
» Views: 16,078
Window Maker Live for Pin...
Forum: Linux on Pinebook Pro
Last Post: vajak
12-24-2025, 06:00 AM
» Replies: 2
» Views: 379
Rrkisp issue with CSI cam...
Forum: Linux on Quartz64
Last Post: lystar
12-24-2025, 02:34 AM
» Replies: 1
» Views: 3,753
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: Kevin Kofler
12-24-2025, 12:11 AM
» Replies: 80
» Views: 45,620
Fedora + Phosh for PinePh...
Forum: PinePhone Software
Last Post: shanehill@mail.com
12-23-2025, 09:12 PM
» Replies: 75
» Views: 200,968
Trixie - bring up the On ...
Forum: Mobian on PinePhone
Last Post: grump_fiddle_reinstall
12-23-2025, 04:34 AM
» Replies: 0
» Views: 76
On-Screen Keyboard Arrow ...
Forum: Mobian on PinePhone
Last Post: grump_fiddle_reinstall
12-23-2025, 04:25 AM
» Replies: 11
» Views: 6,071
Armbian has been released...
Forum: News
Last Post: ArmbianForSBCs
12-23-2025, 01:36 AM
» Replies: 21
» Views: 32,311
Alarm clock doesn’t work
Forum: Mobian on PinePhone
Last Post: biketool
12-23-2025, 12:12 AM
» Replies: 14
» Views: 24,442
Diagnosing and fixing fai...
Forum: PinePhone Pro Software
Last Post: biketool
12-22-2025, 11:59 PM
» Replies: 7
» Views: 623

 
  Another stuck watch!
Posted by: Ralpharama - 06-05-2023, 03:48 AM - Forum: General Discussion on PineTime - Replies (11)

Hi all,
I just got my sealed PineTime a month ago, it was all up to date and working fine, then I left it in a bag and it discharged its battery. When I put it on the cradle to charge I get the pinecone in green, then it freezes on the InfiniTime logo. After reading other posts on the forum I tried various things.
- reset it - same thing happens
- reset it to blue pinecone - same thing happens
- reset it to red pinecone - same thing happens
- gadgetbridge was already disconnected, but I also turned off my phone and left it off and tried the above again
- allowed the watch to discharge its battery again then tried the above again with phone off (so there's no chance of any connection)
So I'm stuck, no matter what I do I can't seem to get past the InifiTime logo.
Any other suggestions?
Thanks!
Ralph


  Separate ISO keyboard for PBP
Posted by: Besouro - 06-04-2023, 02:51 PM - Forum: Pinebook Pro Hardware and Accessories - No Replies

Hello,

It's been some time already that Pine stopped selling PBP's with an ISO keyboard.

I couldn't find any separate ISO keyboard in the Pine shop nor something similar on Aliexpress. I'm not interested in a used PBP.

Anybody knows if the ISO keyboard can be purchased separately and if so where?


  SD Card has wrong capacity
Posted by: AndyM - 06-04-2023, 07:27 AM - Forum: General Discussion on PinePhone - Replies (11)

After flashing an OS to my 16GB micro SD I find that it erroneously reports in, for example, parted as 4GB.


Code:
$ lsblk
NAME  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 465.8G  0 disk
├─sda1  8:1    0    2M  0 part
├─sda2  8:2    0  39.1G  0 part /
├─sda3  8:3    0  7.8G  0 part [SWAP]
└─sda4  8:4    0 418.9G  0 part /home
sdb      8:16  1    15G  0 disk
└─sdb1  8:17  1    15G  0 part

Code:
$ sudo parted /dev/sdb
GNU Parted 3.6
Using /dev/sdb
[menu]
(parted) print all                                                       
Model:  (file)
Disk /dev/sdb: 4092MB

I have googled endlessly but cannot find a way of fixing this.
I would like to use the 16GB SD card for data.

Any help would be appreciated as usual.


  Star64: SATA
Posted by: Der Geist der Maschine - 06-03-2023, 09:21 PM - Forum: Getting Started - Replies (1)

From the Star64 wiki

Quote:The 4-pin 12 volt JST-XH-4A connector found on the Star64 is incompatible with the dual SATA power adapter intended for the ROCKPro64. The connector on the Star64 is rotated 180 degrees to the one on the ROCKPro64, resulting in the cable receiving +12V where GND is expected and vice versa. The cable's internal circuitry ends up shorting in this configuration."


@tllim will the Pine Store eventually sell a cable for the Star64?


PS: Isn't it time to have a Star64 subforum (and move all star64 post into that subform)?


  Fixing the Quartz64 USB3 Port with the soldering iron
Posted by: Hemi03 - 06-03-2023, 06:43 PM - Forum: Quartz64 Tutorials - No Replies

In this tutorial I will document what components i desolderd, to fix the flaky USB3 Port on the Quartz64.

To fix the issues with USB3 you need to disconnect the sata connector, it is messing with the USB3 connection.
This will disable the sata connector and you will only be left with a USB3 Connector (a working one tho).



WARNING: THIS CAN BREAK YOUR DEVICE AND THAT WILL BE YOUR FAULT
Only proceed if you have advanced soldering skills, the components are very small.



You need: 

  • A hight power soldering iron (my Pinecil strugglet a faire bit)
  • A fine tip for the iron
  • Flux Paste



First locate the 4 resistors that connect the sata connector, i numberd them in this picture:

[Image: Quartz-USB3-fix.jpg]


I simply applied flux paste on to the resistors and pushed them of there pads with the hot soldering iron.
After that USB3 should just work fine.


  Star64: GPU firmware loading on Armbian
Posted by: Der Geist der Maschine - 06-03-2023, 01:01 PM - Forum: Getting Started - Replies (15)

GPU firmware loading fails on armbian:

Code:
[    0.698528] PVR_K:(Fatal):    1: All RGX Firmware image loads failed for 'rgx.fw.36.50.54.182' (PVRSRV_ERROR_NOT_FOUND) [1599]
[    0.698565] PVR_K:(Error):    1: RGXInit: InitFirmware failed (275) [1556]
[    0.698592] PVR_K:(Error):    1: RGXInit() failed (PVRSRV_ERROR_NOT_FOUND) in PVRSRVCommonDeviceInitialise() [2156]
[    0.698626] PVR_K:(Error):    1: PVRSRVDeviceFinalise() failed (PVRSRV_ERROR_NOT_INITIALISED) in PVRSRVCommonDeviceInitialise() [2170]
[    0.698664] [drm:pvr_drm_load] *ERROR* device (____ptrval____) initialisation failed (err=-19)

This is probably a first step in having GPU support in Xorg and Wayland.

Apply this kernel patch

Code:
schaecsn@pc:~/risc/linux# git diff drivers/gpu/drm/img/img-rogue/Kconfig
diff --git a/drivers/gpu/drm/img/img-rogue/Kconfig b/drivers/gpu/drm/img/img-rogue/Kconfig
index 5b793bb9da0e..6f84a2643e02 100644
--- a/drivers/gpu/drm/img/img-rogue/Kconfig
+++ b/drivers/gpu/drm/img/img-rogue/Kconfig
@@ -1,5 +1,5 @@
config DRM_IMG_ROGUE
-      bool "DRM support for PowerVR GPU"
+      tristate "DRM support for PowerVR GPU"
        select DRM_IMG
        default n
        help


Configure the gpu driver as a module

Code:
schaecsn@pc:~/riscv/linux$ scripts/config -m CONFIG_DRM_IMG_ROGUE


Rebuild the kernel and modules and install them.

The driver needs to be compiled as a kernel module. Unsophisticated guess: that moves out the initialization of the gpu from initrd into systemd-land. That is why the firmware does not need to be in initrd but can reside on the /-filesystem.

The two firmware blobs rgx.fw.36.50.54.182  rgx.sh.36.50.54.182 need to be moved into /lib/firmware/ directory. They come from starfive-'s github repro https://media.githubusercontent.com/medi...866.tar.gz

Code:
schaecsn@star64:~$ sudo mv img-gpu-powervr-bin-1.17.6210866/target/lib/firmware/* /lib/firmware/


A reboot shows successful firmware load

Code:
[  26.414834] PVR_K:  362: Read BVNC 36.50.54.182 from HW device registers
[  26.414879] PVR_K:  362: RGX Device registered BVNC 36.50.54.182 with 1 core in the system
[  26.422574] PVR_K:  362: RGX Firmware image 'rgx.fw.36.50.54.182' loaded
[  26.442903] PVR_K:  362: Shader binary image 'rgx.sh.36.50.54.182' loaded


Th next step in having GPU support in Xorg and Wayland is probably installing the libs, bin, and headers from said img-gpu-powervr-bin-1.17.6210866.tar.gz "[this] is a GPU library packages from Imagination and provide GPU firmware, libOpenCL, vulkan, gles2, gles3. This library is not open source, only provide with binary library." I have not tried that.


  Any suggestions for USB audio devices?
Posted by: unixpoet - 06-03-2023, 11:11 AM - Forum: RockPro64 Hardware and Accessories - No Replies

I'm looking for suggestions for good USB audio interfaces for the RockPro64. I'm encountering clipping at low volumes with the 3.5mm jack and would like something more capable. I won't be connecting a TV or anything like that to the RockPro64, so HDMI isn't an option. I'd love something like the Focusrite Scarlett Solo I have connected to my workstation, but without the ports I don't need :)


  Can't get the feet to stay on!
Posted by: elix - 06-03-2023, 10:32 AM - Forum: General Discussion on Pinebook Pro - Replies (3)

I always make sure there is no residue or anything but for the life of me I can not get any feet to stay on the pinebook pro. Anyone have any tips?


  2TB SD Card Write Errors
Posted by: jiacovelli - 06-02-2023, 02:18 PM - Forum: Linux on Pinebook Pro - Replies (3)

Per the booklet, I got the largest SD card compatible with the Pinebook Pro. I can successfully format, check it for errors and mount it. As soon as a write attempt is made, even just a mkdir, errors occur (invalid block bitmap). I've tried both ext4 and ext3.

Has anyone had success mounting and using that large an SD card? Thanks.


  pinephone no longer receiving calls or texts
Posted by: jyoung - 06-01-2023, 07:13 PM - Forum: General Discussion on PinePhone - Replies (3)

Hi,

My pinephone is no longer getting calls or texts, and I'm trying to understand why. A while back I had a similar problem, wherein the model seemed clogged:

forum.pine64.org/showthread.php?tid=16939&page=2

But, I never actually got the bottom of that. I've tried using mmcli to see the stored messages:

mmcli -m 0 AT+CPMS?


But it just returns information about the modem (copied below). Does anyone know what might be going on?

-----------------------------------
  General  |              dbus path: /org/freedesktop/ModemManager1/Modem/0
          |              device id: b6df770f2cdf2a32fe9b70af378e85fcc9b3e3b8
  -----------------------------------
  Hardware |            manufacturer: QUALCOMM INCORPORATED
          |                  model: QUECTEL Mobile Broadband Module
          |      firmware revision: EG25GGBR07A08M2G
          |          carrier config: hVoLTE-Verizon
          | carrier config revision: 05010141
          |            h/w revision: 10000
          |              supported: gsm-umts, lte
          |                current: gsm-umts, lte
          |            equipment id: 860195051746581
  -----------------------------------
  System  |                  device: /sys/devices/platform/soc/1c1b000.usb/usb3/3-1
          |                drivers: qmi_wwan, option1
          |                  plugin: quectel
          |            primary port: cdc-wdm0
          |                  ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB1 (gps),
          |                          ttyUSB2 (at), ttyUSB3 (at), wwan0 (net)
  -----------------------------------
  Numbers  |                    own: --------
  -----------------------------------
  Status  |                    lock: sim-pin2
          |          unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
          |                  state: connected
          |            power state: on
          |            access tech: lte
          |          signal quality: 52% (recent)
  -----------------------------------
  Modes    |              supported: allowed: 2g; preferred: none
          |                          allowed: 3g; preferred: none
          |                          allowed: 4g; preferred: none
          |                          allowed: 2g, 3g; preferred: 3g
          |                          allowed: 2g, 3g; preferred: 2g
          |                          allowed: 2g, 4g; preferred: 4g
          |                          allowed: 2g, 4g; preferred: 2g
          |                          allowed: 3g, 4g; preferred: 4g
          |                          allowed: 3g, 4g; preferred: 3g
          |                          allowed: 2g, 3g, 4g; preferred: 4g
          |                          allowed: 2g, 3g, 4g; preferred: 3g
          |                          allowed: 2g, 3g, 4g; preferred: 2g
          |                current: allowed: 2g, 3g, 4g; preferred: 2g
  -----------------------------------
  Bands    |              supported: egsm, dcs, pcs, g850, utran-1, utran-4, utran-6, utran-5,
          |                          utran-8, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5,
          |                          eutran-7, eutran-8, eutran-12, eutran-13, eutran-18, eutran-19,
          |                          eutran-20, eutran-25, eutran-26, eutran-28, eutran-38, eutran-39,
          |                          eutran-40, eutran-41, utran-19
          |                current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-6, utran-5,
          |                          utran-8, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5,
          |                          eutran-7, eutran-8, eutran-12, eutran-13, eutran-18, eutran-19,
          |                          eutran-20, eutran-25, eutran-26, eutran-28, eutran-38, eutran-39,
          |                          eutran-40, eutran-41, utran-19
  -----------------------------------
  IP      |              supported: ipv4, ipv6, ipv4v6
  -----------------------------------
  3GPP    |                    imei: 860195051746581
          |            operator id: 311480
          |          operator name: Verizon
          |            registration: home
  -----------------------------------
  SIM      |              dbus path: /org/freedesktop/ModemManager1/SIM/0
  -----------------------------------
  Bearer  |              dbus path: /org/freedesktop/ModemManager1/Bearer/