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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,006
» Latest member: gillian933
» Forum threads: 16,337
» Forum posts: 117,450

Full Statistics

Latest Threads
The "Should I buy a Quart...
Forum: General Discussion on Quartz64
Last Post: kapqa
24 minutes ago
» Replies: 5
» Views: 20,280
Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: shinzuka
Yesterday, 09:02 AM
» Replies: 9
» Views: 16,808
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
05-03-2026, 07:07 AM
» Replies: 14
» Views: 15,178
Mobian image for the Pine...
Forum: Mobian on PinePhone
Last Post: Korfou
04-27-2026, 09:57 AM
» Replies: 2
» Views: 321
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 236
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 19,741
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,149
my pinecil v2 is not work...
Forum: General Discussion on Pinecil
Last Post: jagrav
04-17-2026, 06:28 AM
» Replies: 0
» Views: 169
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,531
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 358

 
  Fedora 37 installation
Posted by: gswatkins - 11-14-2022, 07:26 AM - Forum: Linux on Pinebook Pro - Replies (16)

I recently got a pinebook pro and have been playing around with distros to see what I like best. I found the existing instructions available for Fedora, but they didn't work for the 37 beta currently available. I had already installed Tow-Boot and that continued to work fine. Here's what I had to do:

  1. Boot from Fedora 37 live image. I used USB, but SD should also work.
  2. Run the 'Install to Disk' application
  3. Choose the install destination. I reclaimed all space on the emmc and installed there.
  4. There will be error boxes that pop up complaining about problems installing the boot loader. You can choose to continue with the installation.
  5. Once the installer has finished and before rebooting, you need to add a boot loader entry. I did this manually by creating a boot loader entry file here:
    Quote:/mnt/sysimage/boot/loader/entries/fedora37.conf

    With these contents based on the kernel and initramfs images I had present in /mnt/sysimage/boot:
    Quote:title Fedora 37
    options $kernelopts
    linux /vmlinuz-5.19.7-300.fc37.aarch64
    initrd /initramfs-5.19.7-300.fc37.aarch64.img


After rebooting, the system starts up with the newly installed Fedora 37. I also noticed running dnf upgrade created new boot loader entries for the updated kernel packages automatically and it starts up just fine.

Things I have noticed are not working correctly yet:

  1. Sound
  2. Does not wake up from sleep after either closing the lid or pressing the power button.


  Still No Calls or SMS
Posted by: AndyM - 11-14-2022, 03:55 AM - Forum: Arch Linux on PinePhone - Replies (3)

Sorry, but I have no idea how to fix this.

If some kind person could guide me through it....?

Here is the result from journalctl when trying to place a call:

Code:
$ sudo journalctl --follow

Nov 14 09:08:16 pinephone dbus-daemon[3779]: [session uid=1000 pid=3779] Activating service name='org.gnome.Contacts' requested by ':1.90' (uid=1000 pid=13275 comm="gnome-calls")
Nov 14 09:08:16 pinephone dbus-daemon[3779]: [session uid=1000 pid=3779] Successfully activated service 'org.gnome.Contacts'
Nov 14 09:08:18 pinephone gnome-calls[4149]: Unexpected error response to netlink request while trying to fetch local IP address
Nov 14 09:08:28 pinephone gsd-media-keys[4005]: Unable to get default sink
Nov 14 09:08:28 pinephone gsd-media-keys[4005]: Unable to get default source
Nov 14 09:08:28 pinephone ModemManager[12626]: <info>  [modem0/call0] user request to start call
Nov 14 09:08:28 pinephone ModemManager[12626]: <info>  [modem0/call0] call state changed: unknown -> dialing (outgoing-started)
Nov 14 09:08:28 pinephone gsd-media-keys[4005]: Unable to get default source
Nov 14 09:08:28 pinephone ModemManager[12626]: <info>  [modem0/call0] call is started
Nov 14 09:08:33 pinephone gnome-calls[4149]: Unexpected error response to netlink request while trying to fetch local IP address
Nov 14 09:08:48 pinephone gnome-calls[4149]: Unexpected error response to netlink request while trying to fetch local IP address
Nov 14 09:08:53 pinephone nmbd[3306]: [2022/11/14 09:08:53.565089,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Nov 14 09:08:53 pinephone nmbd[3306]:   *****
Nov 14 09:08:53 pinephone nmbd[3306]:
Nov 14 09:08:53 pinephone nmbd[3306]:   Samba name server PINEPHONE is now a local master browser for workgroup FDSERVICES on subnet 192.168.1.22
Nov 14 09:08:53 pinephone nmbd[3306]:
Nov 14 09:08:53 pinephone nmbd[3306]:   *****
Nov 14 09:09:03 pinephone gnome-calls[4149]: Unexpected error response to netlink request while trying to fetch local IP address
Nov 14 09:09:07 pinephone ModemManager[12626]: <info>  [modem0/call0] call state changed: dialing -> terminated (unknown)
Nov 14 09:09:07 pinephone gsd-media-keys[4005]: Unable to get default sink
Nov 14 09:09:07 pinephone gsd-media-keys[4005]: Unable to get default source
Nov 14 09:09:07 pinephone gnome-calls[4149]: Error deleting call `/org/freedesktop/ModemManager1/Call/0' on MMModemVoice `QUECTEL Mobile Broadband Module': GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.27 was not provided by any .service files
Nov 14 09:09:07 pinephone gnome-calls[4149]: Error deleting call `/org/freedesktop/ModemManager1/Call/0' on MMModemVoice `QUECTEL Mobile Broadband Module': GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.106 was not provided by any .service files
Nov 14 09:09:07 pinephone gsd-media-keys[4005]: Unable to get default source
Nov 14 09:09:18 pinephone gnome-calls[4149]: Unexpected error response to netlink request while trying to fetch local IP address
Nov 14 09:09:26 pinephone ModemManager[12626]: <info>  [modem0] 3GPP registration state changed (home -> searching)
Nov 14 09:09:26 pinephone ModemManager[12626]: <info>  [modem0] state changed (registered -> searching)
Nov 14 09:09:26 pinephone ModemManager[12626]: <warn>  [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
Nov 14 09:09:26 pinephone ModemManager[12626]: <warn>  [modem0] couldn't load operator name: Current operator id is still unknown
Nov 14 09:09:26 pinephone mmsdtng[3770]: ../mmsd-1.12.1/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 8 New State: 7, Reason: 0
Nov 14 09:09:26 pinephone mmsdtng[3770]: ../mmsd-1.12.1/plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 7
Nov 14 09:09:26 pinephone mmsdtng[3770]: ../mmsd-1.12.1/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY

I don't know what to do about these errors:
Code:
gnome-calls[4149]: Unexpected error response to netlink request while trying to fetch local IP address
Code:
gsd-media-keys[4005]: Unable to get default sink/source
Code:
gnome-calls[4149]: Error deleting call `/org/freedesktop/ModemManager1/Call/0' on MMModemVoice `QUECTEL Mobile Broadband Module': GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.27 was not provided by any .service files
gnome-calls[4149]: Error deleting call `/org/freedesktop/ModemManager1/Call/0' on MMModemVoice `QUECTEL Mobile Broadband Module': GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.106 was not provided by any .service files
Code:
ModemManager[12626]: <warn>  [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
ModemManager[12626]: <warn>  [modem0] couldn't load operator name: Current operator id is still unknown

I have googled all of them endlessly but I still have no idea how to fix then. I have updated geoclue2 to make sure that the polkit rules are up to date (I hope)

If I check the modem state I can see the Operator id and name:
Code:
$ mmcli -m 0
  -----------------------------------
  General  |                    path: /org/freedesktop/ModemManager1/Modem/0
           |               device id: b526365d8a8c8ebb23bbb0995d36796c19ab76a3
  -----------------------------------
  Hardware |            manufacturer: QUALCOMM INCORPORATED
           |                   model: QUECTEL Mobile Broadband Module
           |       firmware revision: EG25GGBR07A08M2G
           |          carrier config: ROW_Generic_3GPP
           | carrier config revision: 05010820
           |            h/w revision: 10000
           |               supported: gsm-umts, lte
           |                 current: gsm-umts, lte
           |            equipment id: 867698046452572
  -----------------------------------
  System   |                  device: /sys/devices/platform/soc/1c1b000.usb/usb2/2-1
           |                 drivers: option, qmi_wwan
           |                  plugin: quectel
           |            primary port: cdc-wdm0
           |                   ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB1 (gps),
           |                          ttyUSB2 (at), ttyUSB3 (at), wwan0 (net)
  -----------------------------------
  Status   |                    lock: sim-pin2
           |          unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
           |                   state: registered
           |             power state: on
           |             access tech: umts
           |          signal quality: 4% (cached)
  -----------------------------------
  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: 4g
  -----------------------------------
  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: 867698046452572
           |           enabled locks: fixed-dialing
           |             operator id: 20810
           |           operator name: SYMA
           |            registration: home
  -----------------------------------
  3GPP EPS |    ue mode of operation: csps-2
           |     initial bearer path: /org/freedesktop/ModemManager1/Bearer/0
           |  initial bearer ip type: ipv4v6
  -----------------------------------
  SIM      |        primary sim path: /org/freedesktop/ModemManager1/SIM/0

and yet if I look at the ModemManager Service I see this:

Code:
$ sudo systemctl status ModemManager
● ModemManager.service - Modem Manager
     Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled; preset: disabled)
     Active: active (running) since Mon 2022-11-14 07:19:32 CET; 3h 33min ago
   Main PID: 12626 (ModemManager)
      Tasks: 5 (limit: 3273)
     Memory: 6.1M
        CPU: 2.877s
     CGroup: /system.slice/ModemManager.service
             ├─12626 /usr/bin/ModemManager --test-quick-suspend-resume
             └─12639 /usr/lib/qmi-proxy

Nov 14 09:13:35 pinephone ModemManager[12626]: <info>  [modem0] state changed (enabled -> registered)
Nov 14 09:29:32 pinephone ModemManager[12626]: <info>  [modem0] 3GPP registration state changed (home -> searching)
Nov 14 09:29:32 pinephone ModemManager[12626]: <info>  [modem0] state changed (registered -> searching)
Nov 14 09:29:32 pinephone ModemManager[12626]: <warn>  [modem0] couldn't load operator code: Current operator MCC/MNC is still unkn>
Nov 14 09:29:32 pinephone ModemManager[12626]: <warn>  [modem0] couldn't load operator name: Current operator id is still unknown
Nov 14 09:30:05 pinephone ModemManager[12626]: <info>  [modem0] 3GPP registration state changed (searching -> idle)
Nov 14 09:30:05 pinephone ModemManager[12626]: <info>  [modem0] state changed (searching -> enabled)
Nov 14 09:30:06 pinephone ModemManager[12626]: <info>  [modem0] 3GPP registration state changed (idle -> registering)
Nov 14 09:30:06 pinephone ModemManager[12626]: <info>  [modem0] 3GPP registration state changed (registering -> home)
Nov 14 09:30:06 pinephone ModemManager[12626]: <info>  [modem0] state changed (enabled -> registered)
lines 1-21/21 (END)

as you can see, I have no idea what I am doing, but some advice would be really helpful now  Huh

Thanks


  Not connecting to cellular network
Posted by: car46999 - 11-14-2022, 12:06 AM - Forum: Mobian on PinePhone - Replies (18)

Just bought a new Pinephone (non pro) and I am trying to get it setup and working. Out of the box with Manjero I tried my SIM and it would not connect to cell service, IIIRC it would give constant GSM error and a timeout. I then updated Manjero, with the same result of not connecting to cell service.

So today I switched to Mobian, the latest weekly build (mobian-pinephone-phosh-20221113.img). But I still appear to still have an issue with registering on the cell network.

My SIM is Puretalk, I am in the US. And it works in my Android phone. I checked before ordering the phone and saw several posts where people said PureTalk works fine. One said just slap the SIM card in and voice is good, setup the APN and mobile data is good.

I have tried the following:

  • Cycling through all of the network types 2g-4g, and disabling and re-enabling the mobile network.
  • Switching the Network (selection) from Automatic to off, most of the time this results in "Timeout was reached" or GDBus.Error:org.freedesktop.libqmi...
    But after a several tires I usually get a list of carriers, and I select PureTalk.com. I can exit and go back in and it still shows PureTalk is selected. If I close the settings and re-open it it is back to Automatic.
  • Multiple reboots, complete power off and battery removal
  • Switching the modem hardware switch on and off.
  • I am connected to WiFi and did update after installing.
  • Tried disabling mobile data
  • Tried a couple variations for APN (currently using PureTalk / RESELLER)
  • Tried texting and calling. Texts to not send, calls just immediatly just say "call ended"
  • SIM card has been in and out a few times, is installed correctly (since it sees my phone number)


Modem status:
Carrier (blank)
Network Type - Unknown
Signal - 20-55%
Network Status - Searching or Not registered
Own Number - ***-***-****  (Is Correct)



Any help on this would be great. I am liking Mobian, and would like to keep it.


  How well does Rock64 deal with HDR and Atmos on Kodi?
Posted by: drvlikhell - 11-13-2022, 10:11 PM - Forum: General Discussion on ROCK64 - Replies (3)

I'm looking to use the Rock64 for emulation and media playback. I will be running RetroPie, Batocera, Recalbox, Lakka, or RetroArch. Which ever one runs the best, or is easiest to set up will be fine. I plan to install Kodi into which ever OS I go with. One of them even has Kodi preinstalled. The emulation capabilities of the Rock64 are just fine for my expectations but I'm curious about how well it handles HDR video and also passthrough audio with Atmos. I searched around to see what people had to say but most of the posts are from two years ago or more, and I know that development usually moves along pretty quickly so issues from two years ago may have been solved by now.

I will be playing media locally with Kodi. Files will be in h.265 10 bit with HDR and most will have Dolby Digital Plus with Atmos, some will be Dolby TrueHD with Atmos. Output will be via HDMI into a home theater receiver that fully supports the above audio codecs.

Does anybody have any recent experience with this type of setup? Any problems with either HDR or Atmos passthrough?


  Armbian VPU decoding support coming soon
Posted by: LivingLinux - 11-13-2022, 02:32 PM - Forum: Linux on Pinebook Pro - No Replies

Announced on Twitter: https://twitter.com/armbian/status/1591873408694120448


  Woodpecker 3.3V not recognized
Posted by: z3bra - 11-13-2022, 07:05 AM - Forum: Rock64 Hardware and Accessories - Replies (1)

Hello,

I bought a fresh now rock64 along with the woodpecker USB to serial adapter. However, when I plug in the adapter to my computer in 3.3V, it is not recognized by the computer, and "dmesg" output remains silent, even though the led is lit. I tried multiple distros, kernel options and even Windows. The device just doesn't show up.

The adapter is correctly recognized in 5V mode, and the /dev/ttyUSB0 device gets created as expected. But apparently I should not use this mode to access my Rock64 console or I'll damage it.

What can I do ?

Thanks


  DietPi OS for Quartz64
Posted by: MichaIng - 11-13-2022, 05:06 AM - Forum: Linux on Quartz64 - Replies (47)

[Image: dietpi-logo_192x192.png]

DietPi is an extremely lightweight Debian-based OS. It is highly optimised for minimal CPU and RAM resource usage, ensuring your Pinebook always runs at its maximum potential.

Use dietpi-software to quick and easy install a desktop and lots of other Ready to Run & Optimised applications for your system. DietPi will do all the necessary configurations, including starting the services.

DietPi images are available for PINE A64PINE H64PinebookPinebook Pro, ROCK64 and ROCKPro64 and all Quartz64 models.

Our Quartz64 images use latest upstream kernel and U-Boot builds based on Peter Geis' work.
Kernel config: https://github.com/MichaIng/DietPi/blob/..._defconfig
U-boot sources: https://gitlab.com/MichaIng/u-boot


Website: https://dietpi.com/
Download images: https://dietpi.com/#download
Documentation: https://dietpi.com/docs/
Blog: https://dietpi.com/blog/
Forum: https://dietpi.com/forum/
GitHub repository: https://github.com/MichaIng/DietPi

DietPi is a free and open-source project. We are be happy if you consider to contribute or donate: https://dietpi.com/contribute.html


  Manjaro Plasma busted
Posted by: Chief - 11-12-2022, 09:00 PM - Forum: Manjaro on PinePhone - Replies (2)

I have noted that Evolution crashed and also Libreoffice on Manjaro Plasma.
I was able to reinstall Evolution but Libreoffice remains busted, can't install.
I also noted numerous issues with updating in the terminal. After several tries
I was able to update. However Libreoffice remains busted and that is essential.


  I think my PBP blew a fuse...
Posted by: pineymousepad - 11-12-2022, 07:23 PM - Forum: General Discussion on Pinebook Pro - No Replies

I plugged in usb c charger and heard my PBP making a chirping noise like a bird, I unplugged it and the USB C metal end felt really hot, tried using my simple pocket sized portable battery and my battery percentage LED turned off (that never happened before, bricked my portable battery), it seems to be sending current back towards whatever is supposed to be charging it. PBP was working until it ran out of battery (had no way of charging it, so PBP works, but now no way to add power)...
I tried the barrel charger, nothing (where before this incident it was working)...

I tried searching for threads related to my problem and found nothing. Will I have to open the PBP and change a fuse? USB-C port? Every month I use this thing it seems to pose me with a new engineering challenge.


  My PBP blew a fuse?
Posted by: pineymousepad - 11-12-2022, 07:20 PM - Forum: Pinebook Pro Hardware and Accessories - No Replies

I plugged in usb c charger and heard my PBP making a chirping noise like a bird, I unplugged it and the USB C metal end felt really hot almost burned my finger, tried using my simple pocket sized portable battery and my battery percentage LED turned off (that never happened before, bricked my portable battery), it seems to be sending current back towards whatever is supposed to be charging it. PBP was working until it ran out of battery (had no way of charging it, so PBP works, but now no way to add power)...
I tried the barrel charger, nothing (where before this incident it was working)...

I tried searching for threads related to my problem and found nothing. Will I have to open the PBP and change a fuse? USB-C port?