My PinePhone worked great until (I think – this was quite some time ago because it wasn't urgent to get fixed, so I don't perfectly remember it anymore) it crashed and I had to force a reboot (taking out the battery).  Now the SIM card related stuff doesn't work (great) anymore.  To make or receive a phone call I now have to run `mmcli -m any -e` (found on the internet) to activate the modem (which isn't great, but also not a big problem) and (more importantly) I can't configure an APN (the option in the settings GUI is grey out, and I don't know how to do it in the terminal), which means I have no mobile internet (which wasn't a problem, because I'm usually somewhere with WiFi, but soon will be a problem).

It might (or might not) be worth mentioning that I somewhat damaged the SD/SIM card slot, but I don't think this is related, because it still worked for some time with this damaged slot and because after running this command making phone calls still works.

Memory Management Unit (MMU) is the hardware inside our Single-Board Computer (SBC) that implements Memory Protection and Virtual Memory.

Sv39 is the RISC-V MMU inside the Pine64 Ox64 SBC, based on Bouffalo Lab BL808 SoC.

In this article, we boot Apache NuttX RTOS on Ox64 SBC to find out how Sv39 MMU works with:
(1) Memory Protection (for our Kernel)
(2) Virtual Memory (for the Applications)
As we record everything that happens when NuttX configures the Sv39 MMU.

Check out the article:
RISC-V Ox64 BL808 SBC: Sv39 Memory Management Unit

Lup
   

I am a newby to Linux and have the Pinephone and Pinephone Pro.  I have installed PMos on the PP and Mobian on the PPP.  I have to admit that switching to different OSs is lots of fun.  I have a lot of issues trying to make one of them my daily driver device. (Beyond sick of Google and Apple among many other big tech life drainers)  I am just wondering why a Linux open source device has to have a Google protocol in the firmware of the modem in both phones. (com.google.fastboot) Is it communicating to Google in any way? If so, then this defeats the purpose of what I am personally trying to accomplish and not sure how to proceed from here.  Like I said, I am new to Linux and need some guidance if you would be so kind.

Thank you in advance.

I'm assuming I've missed something ?

Wondering is there a (Correct) way to shutdown or reboot the PPP once it's TowBoot "Volume Up" booted into USB Readable Drive mode ?

I've tried just holding the power button down but I don't appear to be shutting down / rebooting after unplugging USB Cable / Connection ?

Sorry couldn't figure out if this should go under "Hardware" or "Software" ?

Ta for help in advance.

Which tablet screen protector is compatible with PintTab 2?

bookworm vs trixie discussion for mobian in pinephone regular.

this is a discussion of bookworm vs trixie and maybe staging. so like possible problems and how to fix them. which one is better, and how well it works. here are some generic arguments. this is for pp regular, here is for pp pro https://forum.pine64.org/showthread.php?tid=18839 .

arguments for bookworm:
- stable.
- basics work.
- do not have dependency problems, or broken packages.
- smooth security updates.

arguments against bookworm:
- gets outdated.
- some features are missing, because pinephone is a beta product.
- stuck to the older kernel.

arguments for trixie:
- newer packages.
- features, which are missing in older versions.
- newer kernel, see serious point below.

arguments against trixie:
- dependency problems, broken packages.
- some thing do not work, because of unstable packages.

it seems that pipewire is required and default. package is "pipewire-audio".

practically speaking users should go for trixie, unless users can tolerate basic features. i recently updated to trixie, seems to be ok. but moving into trixie from bookworm wasn't straightforward though. pp regular is stuck to 6.1 kernel for now.

it seems that bluetooth mic does not work, headset seems to work.

i put more information when i encounter them.

My Pine a64 Lts runs fine, but when I plug in the ethernet cable, after about a few seconds of having internet, my board shuts down and won't fully reboot. It just shows a black screen. I am running Ubuntu. Any Ideas what the problem could be? I am very new to this sort of stuff so I apologize for my lack of knowledge.

Hi all,

I'm working on installing another operating system from MicroSD and have been working off of "Getting started"
https://wiki.pine64.org/wiki/Getting_sta...roSD_Cards

I've successfully reached my MicroSD card having the operating system I want on it

I don't yet know how to boot from MicroSD. 

How do you boot from MicroSD on Pinebook Pro?

There appears to be some kind of real-time clock on the SOQuartz Model A Baseboard, maybe even two, but I can't seem to get them to work. I bodged together a CR2032 holder and a JST-PH 2mm header which fits the connector on the board that is labelled "RTC". Verified with a multimeter that the battery has 3V across the terminals so it seems like it's plugged in properly, but I'm still getting "rtc rtc0: Power loss detected, invalid time, rtc-pcf85063 1-0051: hctosys unable to read the hardware clock" in dmesg. There seems to also be a /dev/rtc1 (rk808-rtc) that seems responsive to hwclock but on every reboot it reverts to August 5, 2017 09:00 UTC for some reason.

Anyone know the correct way to provide power to the RTC?

I have an SOQuartz and a Pine64 Model A carrier board, and I'm slowly getting it to work. After CPU temperatures soared to 71°C on moderate CPU load, I found a CM4 heatsink from Waveshare with a 12V fan, apparently this model:

https://www.waveshare.com/product/cm4-fan-3007-b.htm

I was able to get the fan running by using a couple of DuPont wires to plug it into the 12V power header beside the power jack on the Model A board, and while thermal problems are now no longer an issue (temperatures peak at 54°C even when doing a make -j4 compile of the Linux kernel) I'm wondering if I could plug the other two pins on the fan somewhere and get the fan speed adaptively controlled instead of having it on all the time. It seems to be a typical PWM fan with the standard colours for the wires. I can see from the Model A schematic that there's apparently a PWM to I2C chip that is probably suitable for this purpose, but it is unclear where it actually terminates. The Model A board picture on the Pine64 Wiki shows a four-pin unshrouded header on the top left , but I instead have a two-pin JST header there with + and - indicators printed beside it on the board. Any help on how I can do this, including any software I might need to do fan control?