Hi all,
I'm not sure if this is really a linux / debian / whatever issue, or what, but it seems my /boot partition is read only. (let me know, or mods, feel free to move me).

I installed the original Debian version (not the "unofficial installer"), which installs Debian 9 or so, then upgraded that to Debian Sid (via the usual "update the releases file and apt-get update , apt-get update", and resolving some dependency issues). Then only recently, I realized that apt-get dist-upgrade doesn't actually upgrade the kernel like it does in ubuntu (been using xuubuntu for 12 years or so now, and not much else), so I went along with this to upgrade the kernel, but ran into an error where apt-get / dpkg said /boot was read-only. indeed, "cd /boot; sudo touch 'testing.txt'" shows it's read only, even to root, despite "sudo ls -l" from "/" telling me root ought to have read permissions. strange. This is linux installed on the eMMC module, which /boot and / (which includes home which i've been freely writing to for a while now) are partitions on.

it shouldn't be device dependent (both home (which I can write to) and boot (which I can't) are on the same device). it shouldn't be OS / mount dependent (nothing in fstab aside from swap, and "ls -l" says root is allowed to write to it). so what's up?

I did find this thread, but it appears to not really be resolved.

I'm also not exactly sure where else to look (what system logs, etc, and where?). (un)fortunately, xubuntu has served me extraordinarily well over the years and I spend more of my time doing daily computerly things than i do looking through logs files and troubleshooting things (so I may be a bit out of the loop, please bear with me).

EDIT: interesting. I was able to unmount /boot via gparted, then remount it (idk, an icon showed up on my desktop and i clicked on it), and then I was able to write to it, and "sudo apt-get install linux-image05.8...". I did see a few warnings appear, regarding drivers not found though. rebooting, I appear to still be in linux 4.4.207, per uname.

google tells me I'd want to update grub if i were on a more typical system which used grub, but otherwise i'm not sure how to get into the newer kernel which is supposedly installed. (also unsure if i even want to get into the newer kernel, given those driver errors it showed....)

Hi all! I'm trying to find where is the source code to build KDE Neon images of plasma-mobile for the Pinephone.

We have a bunch of images here: https://images.plasma-mobile.org/pinephone/. I presume these are built daily from *somewhere*. I've tried reading the developer guide for plasma mobile, browsed a bunch on the KDE neon website and looked for repos and all I can find is the source code for plasma-mobile, but not the source code to build the KDE neon images for the pinephone specifically.

What I'm specifically looking for is the uboot script source, so I can edit it and compile it back with some changes. AFAICT it's different from the PostmarketOS image that comes with the phone.

Thanks!

While I'm familiar with Linux (I've been using it since 1993), I'm not familiar with Linux on the PinePhone. How do I know if the PinePhone can see my SD card?

Hello - I just got my PinePhone today. I didn't expect it to compete with my Samsung S10 and I am understanding it as a Linux box that can be used to make phone calls, but .. well .. I can't. Calls can be placed and the other side can hear me well, but all I am getting is some modulated static. It's very quiet but the real problem is that the sound itself is garbage. I can't understand a single word. Can't even say if its a male or female on the other side.

I am running the pre-installed PostMarketOS.

Any ideas?

Michaela

I wanted to ask if anyone has used a 3,5 mm combination headset with mic and has the mic working on Arch Linux ARM. I have audio out but can't get the mic working. The headset works fine on other devices, so it is not the headset. I am not certain what specifically controls the headset mic in alsamixer. Mic shows up the settings in the OS settings.

I am using Arch Linux ARM and the BT is now working in the latest update. With my BT headset the same thing occurs: audio out, but no mic. However the mic does not show up in OS settings. If anyone has information about alsamixer settings (or some other setting), please let me know.

Interestingly, my USB headset works flawlessly on audio and mic without any adjustments.

Hey team PBP! I have loving this Pinebook Pro - it has really been everything that I'd hoped and a little more...

I have a question that I hope someone can steer me to an answer/how-to/wiki for:

I received a Pinebook Pro on 9/15/2020, installed with Manjaro ARM on the internal eMMC storage. I'm having a good time playing around with Manjaro, and really want to mess around with the build and see what I can get out of this hardware and how much compiling and building I can squeeze out of the PBP - however, when one does this it changes Manjaro - sometimes in ways that you don't want permanently....

However, I know this isn't an issue because I can just reinstall Manjaro as if it were brand new in the box - as I received it on day 1.

I know that there is a NOOBS SDcard creation application.... but what is the proper way to revert a modified Pinebook Pro system to back to stock/vanilla Manjaro?

Is there a wiki or how-to on this? I want to reinstall Manjaro to the state it was brand new.

Thanks in advance, I really appreciate the help as I begin to learn about Pine64 products. (I am not a beginner, but am brand new to Pine64 products and the Pinebook Pro.)

I updated to 20.08. I have a couple of issues:

Soft reboot: If I do a reboot from the command menu, the system will shut down, then restart where I get a full screen image (looks like the manjaro logo stretched from top to bottom). The image will change a couple of times. The restart does not happen. I have to do a hard power down. If however I do a shutdown or power off the machine, and then restart (via the power key), the system boots just fine.

Boot from SD: Doesn't work on Manjaro images, but does on Debian. ??

Wi-Fi: No longer worked after an update. I think the update took the system to 20.09. If I toggle Wi-Fi off and on, then reboot (can only do this with hard power down), wi-fi is not available. Nothing worked. I had to re-flash the emmc with 20.08, then after login do an update to 20.09. Now it works. Soft reboot is still broken.

Now sure if it matters, but I upgraded the emmc from 64GB to 128GB. 

Strange.

I've searched the forums, but can't find an answer. When I first activated my Pine Phone, I selected full disk encryption to see how it behaved. Now, after deciding that it was a mistake, and getting tired of having to enter my password so much, I want to get rid of it. However, I can't find any instructions on how to do that.

Can anyone point me to instructions on how to start over from scratch? I'm looking for a factory reset.

Hi All, 
I'm just wondering if there are any software-based hardware testing tools available to verify that all pinephone hardware components are performing correctly?

I just received my pmOS pinephone; every feature I've tested works so far except for the earpiece during phone calls (i only get an unintelligible buzzing noise when the other person speaks).  Overall I'm very impressed with the pinephone's capabilities but I'm concerned about the possibility of this being a hardware fault rather than a software issue so I would like to rule out that possibility to put my mind at ease.

I commanded my PBP with extra eMMC module of 128 GB and unfortunately without eMMC USB adapter to flash it. I face the problem: when initial 64 GB eMMC module is replaced by new 128 GB eMMC, the PBP does not boot from either SD or USB stick. When I place initial and bootable 64 GM eMMC back, it can boot from either SD or USB. In this situation I am unable to actually install something to brand new 128 GB eMMC.

I found the solution to this problem. In all my initial attempts I carefully followed the instruction from Wiki https://wiki.pine64.org/index.php?title=Pinebook_Pro, where at subtitle eMMC information, we can read: "The eMMC appears to be hot-pluggable... Best practice is probably to turn the eMMC switch to off position before changing modules." So, the procedure was:
- Switch off eMMC,
- Remove eMMC module,
- Place another eMMC module,
- Switch on eMMC.

But in the following situations, the PBP does not boot (power lid remains off):
1. Bootable SD/USB is inserted, but no eMMC is present (regardless of the switch),
2. Bootable SD/USB is inserted and eMMC is present, but its switch is off,
3. Bootable SD/USB is inserted, brand new (read: not bootable) eMMC is present and its switch is on.

Then I observe that by switching off/on the eMMC something is reset in PBP, which is not reset by replacing eMMC module without switch it off/on. After the 3rd not bootable situation, I replaced eMMC module back to old bootable 64 GB one without touching the switch. This configuration normally results in booting from SD/USB device. But this time it didn't boot (the power lid is off). Somehow the PBP keeps track of not bootable eMMC and doesn't know it is already changed to bootable one.

So I use this supposition in opposite way. I install old bootable eMMC, insert bootable SD/USB stick and boot from the removable device without problems. Now I shutdown the PBP and while keeping bootable removable device, change bootable eMMC with new not bootable eMMC without touching its switch. The system believes its eMMC is still bootable, so I can power on the PBP. The system boot from SD/USB and after that I can install whatever to new eMMC, which is now bootable.

Does this situation happens only to me, or somebody faced the same problem?