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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,081
» Latest member: fxkl47BF
» Forum threads: 16,357
» Forum posts: 117,512

Full Statistics

Latest Threads
"USB access to SD" disapp...
Forum: General Discussion of PinePhone Pro
Last Post: jebez
Yesterday, 06:40 PM
» Replies: 0
» Views: 50
Girls In Your Town - No S...
Forum: General
Last Post: savvas48
Yesterday, 12:07 PM
» Replies: 0
» Views: 42
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: dave3294
06-17-2026, 03:16 AM
» Replies: 11
» Views: 9,211
Girls In Your Town - Anon...
Forum: General
Last Post: wilsonmatt
06-16-2026, 11:16 PM
» Replies: 0
» Views: 94
Girls In Your City - Anon...
Forum: General
Last Post: publishers
06-16-2026, 06:44 PM
» Replies: 0
» Views: 82
Girls From Your City - An...
Forum: General
Last Post: publishers
06-16-2026, 04:32 PM
» Replies: 0
» Views: 73
asterisk or FreePBX on pi...
Forum: PinePhone Software
Last Post: vanja
06-16-2026, 09:24 AM
» Replies: 0
» Views: 126
Jami on Pinephone [ IM an...
Forum: PinePhone Software
Last Post: marlboro1950
06-16-2026, 05:02 AM
» Replies: 15
» Views: 22,094
Thread management hurdles...
Forum: General
Last Post: reyohi4392
06-15-2026, 05:12 AM
» Replies: 0
» Views: 118
Let's get the PPP and Mob...
Forum: General Discussion of PinePhone Pro
Last Post: Rsquared
06-15-2026, 12:01 AM
» Replies: 0
» Views: 167

 
  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/


  Rkvdec memory leak?
Posted by: Abhinav - 06-01-2023, 06:02 PM - Forum: Linux on Pinebook Pro - Replies (2)

Anyone else seeing high memory usage with rkvdec/rockchip_vdec? I am seeing high memory usage with both GStreamer and FFmpeg (https://github.com/jernejsk/FFmpeg) clients so, if other people are also having issues, it seems like it might be an issue in the kernel driver. Performance is quite good until it starts swapping however. I see 3.5 GiB of shared memory usage before it hangs/starts swapping. I'm using kernel 6.1. It's also possible that it is somewhere else like Panfrost or Mesa and I guess I would need to use Kmemleak to confirm but I'd like to know if this is a known issue before I test further.


  Python programme for a vibration signal from Raspberry Pi 4 via bluetooth connection
Posted by: Tria91 - 06-01-2023, 01:33 AM - Forum: Development Discussion on PineTime - Replies (1)

Hi,
please, I need some help to make a vibration signal, if possible with adjustable vibration-length, out from a Python programme from a Raspberry Pi 4 via bluetooth connection.

Best regards,
Gerald


  OpenCL on pinebook Pro
Posted by: Bram - 05-31-2023, 01:01 PM - Forum: Linux on Pinebook Pro - Replies (2)

I am running Armbian 23.02.2 and I am trying to use OpenCL.

Using clinfo, it turns out that there are no installed driver.



Code:
$ clinfo

Number of platforms                              0



Where can I obtain an OpenCL driver for the Pinebook PRO?


  Star64 booting up Armbian video
Posted by: tantamount - 05-31-2023, 07:07 AM - Forum: General - Replies (1)

Here's my Star64 booting up Armbian for the first time on a 2GB microSD. https://youtu.be/3L0rNewF0QE
This Armbian image is based on Fishwaldo's kernel & device tree and this release of Armbian: Armbian_23.5.0-trunk.275_Star64_lunar_edge_5.15.0.img from here: https://www.armbian.com/star64/
I made an image of my 2GB drive in case anyone wants to write it to a microSD and try booting it. I'd recommend writing it to a larger microSD, maybe 16GB or more, because my 2GB quickly filled up. Armbian should automatically resize itself to fill your larger microSD.
You can find the compressed disk image on google drive: https://drive.google.com/file/d/1zIOl9xU...sp=sharing The shasum for the xz file is 4a1dc00d0ac27c690a04546c4447f6f96fe5f38f.


  Emergency Mode Boot Hotkey?
Posted by: jiacovelli - 05-30-2023, 05:21 PM - Forum: Linux on Pinebook Pro - Replies (20)

Is there an equivalent for the RHEL/Fedora emergency shell boot for Pine Pro/Manjaro ARM/Plasma?

I've tried various key combinations including ctrl-shift-F2. Inserting a USB having burned a downloaded Manjaro-ARM-kde-plasma-pbpro-20.12.img.xz image onto it does nothing.

Been using linux (mostly RH, Fedora and Ubuntu) for nearly 30 years; ARM (Chrome OS) for six months. I can't say I'm terribly impressed with the Pinebook. And this from a guy who's partial to KDE/Plasma.

System is stuck, by the way, on (not) mounting a 2TB sd disk whose PARTUUID I'd inserted in fstab. Meant to comment out the line when a manual test mount didn't work, but must have somehow not saved the file after inserting the hash character. Stuck on it whether the sd is in or out.

Oh well. Appreciate any help. A search on the forum turned up no results that I could see.