I have Manjaro installed on both eMMC and NVME in my Pinebook Pro. 

At some point in the last few weeks or month maybe, networking stopped working on both installs. I get the box with the red icon on the bottom.

I plug in a known good USB WiFi dongle, but it doesn't show up in ifconfig or "ip a". 

Dmesg does show the device connecting.

I assume something broke in Manjaro.

I have Armbian on a MicroSD card and there are no network problems with it.

Has anyone seen this?

I hadn't realized but I had spent an inordinate amount of time on a project for my rockpro64 NAS. So much so, that I thought it maybe of use to others since, through its many iterations, it has become nicely refined, maybe to the extent of a viable product.

I designed it out of a block of aluminium.
it had to be passive cooled to be in a heavily dusty environment.
it would be working hard, and in a hot workshop. As a result it had to have ample cooling, for chips and ram.
It turned out rather sleek like, apple esc due to the nature of how I chose to passively cool it.
Had to house and protect 3 SSD's.

 Do I have to host pics to post them here?

can someone tell me how to revert to an older version of U-Boot or upgrade to a working version?  I am currently running version 2023.07+dfsg-1.  It will no longer boot from an SD card.   I put a screen shot with the errors then after it flashes like it is adjusting video then boots.  I does then same on reboot but get stuck at the flashing screen.

Attached Files

Thumbnail(s)
       

Hello there,

I am new here and owner of PinePhone pro, As far as i know that Pine64 products are made in Taiwan, but when received my phone and checked the shipping tracking it was originated from Hong Kong China, even my shipment was designated to Taiwan, can someones shed the light on this.

Thanks

I'm trying to setup an LED indicator using the gpio pins on a Quartz64 model A. I've installed libgpiod, which comes with a number of  tools, like gpiodetect and gpioinfo. With these tools, I can detect a five gpio chips (0-4). However, I don't think that any of these are linked to the main gpio pins since each of the chips has 32 lanes, but there are only 20 gpio pins on the Model A. Also, very few of the 5x32 lanes are named, and the few names are things like "fan" or "restart", not the names listed in section 3.8 of the wiki

wiki.pine64.org/wiki/Quartz64


This is an excellent tutorial on gpio programming, which originally led me to libgpiod

plebian.org/running/gpio/


However, all the examples are for the Model B. I'd hoped that the setup and naming convention for the Model A would be similarly easy, but it seems not. Does anyone have insight for the Model A?

For context, I've tried this while running armbian and gentoo, and the results are the same.

Hey there Pinephone Community!

I received my Pinephone Pro roughly a week ago. I installed Tow-boot, then Mobian, then PostmarketOS then the 2024. 01. 07. Mobian weekly on the eMMC. I am aware that this is a highly experimental device, but this amount of malfunctions make me worried.

In all three of the installations, the phone is able to boot without a Micro SD-card, so I'm sure the installation itself is fine. What I'm about to describe is my experience running the aforementioned Mobian weekly release. The phone worked fine for about three days before these came up two days ago:

1. The phone sometimes is not able to be turned on. Pressing and holding the power button only turns on the device 20% of the time (even though the battery is charged and since it's using Tow-boot, the bootloop problem from a few years ago doesn't apply here as far as I know). After holding the power button for 4-5 seconds and the red LED doesn't turn on, I pick out the battery, put it back in, pop the case in and try again. After two, three, sometimes four of these tries, the red light showed up, the LED would shortly turn white and Mobian's disk encryption password screen prompts me to enter the encryption password.
   
2. After entering the lockscreen digit code, the screen is black for a few seconds, then Phosh's menu drawer greets me and the phone is usable for one or two minutes. After that, the screen turns back, the phone itself doesn't get colder, the backlight is noticeably still on, so I guess the screen lost its connection for some reason. This makes me hold the power button for a few seconds, then to be sure that it's powered down, I pick out the battery, put it back in again, and GOTO 1.
   
3. If at any point while the device is turned on, I manage to lightly tap/hit the phone on the back near the modem (even by putting it on a table or sometimes even just resting my hands on the back), the black screen problem occurs. This happens even if the modem is turned off via the appropriate hardware switch.
   
4. There were some rare cases in point 2. where the screen would freeze. It would still be turned on, but doesn't refresh and doesn't register any inputs
   

I am using pine book pro with kali and i get screen flashes on boot with all different colors like it's trying to adjust then it does it again on reboot but gets stuck.  Seems like I need to configure something in the video settings.  Does anyone have any ideas?

Hello

The internal speaker no longer works on my Pinephone, even after rebooting. I haven't updated it for several days. I assume that I broke something after trying to use an external speaker through bluetooth. The internal earpiece and the headset still work.

How can I solve my problem, preferably without reinstalling the whole system as I use my phone daily?

Pinebook Pro Recover with Void Linux (xbps)

Hello all!

I recently received my Pinebook Pro and, as I have gathered has happened to quite a few people, broke the system with an initial Manjaro update. I thought I'd do my part to help anyone else having the same problem by documenting what I've figured out over the last few days. This will basically be a compilation of a bunch of different articles and tutorials from across the internet, with application specific advice. I'll try to link all major sources. I chose to use Void Linux just 'cause it's what I'm used to, and xbps makes building a system onto the SD card super easy.

While I've learned a lot through this process, I'm by no means an expert. I would appreciate any input, correction, or elaboration the topics discussed.

Just to account for any hardware differences, this was on a PBP received on Jan 11 2024. I haven't checked into this, but if there's any where I can find a hardware revision number or anything like that, let me know.

Some preamble:
The PBP can boot directly from, in order:
- the onboard SPI module,
- the onboard eMMC module, or
- a microSD card.

By default, nothing is written to the SPI. The factory Manjaro ARM system is installed on the eMMC. From what I understand, the system breaks after a Manjaro update because the system updates the bootloader package without properly configuring it. The result is that the PBP boots from the eMMC, but the user gets nothing but a black screen.

Fortunately, the PBP mainboard has a hardware switch to block access to the eMMC, so we can turn that on and boot instead from a microSD card.

Regarding the bootloader, I to use Tow-Boot. I don't have experience any with alternatives, but it was simple to flash and is flexible at boot-time, which is what I was looking for.

So this was my strategy:
1. Disable the eMMC
2. Boot from SD card
3. Flash Tow-Boot to the SPI
4. Re-enable the eMMC
5. Boot again from the SD card
6. ???
7. System repaired.

If I wanted to, I think I could have skipped a couple steps by re-enabling the eMMC while the system was running and flashing Tow-Boot to the eMMC's boot partition. However, I like having the bootloader on the SPI and didn't want to keep Manjaro anyways. Furthermore, this method lets me use GPT and EFI; this probably doesn't matter but it just feels right.

# Setup
To start off with, we're gonna want an existing Void Linux system, though you should be able to follow the same process on any Linux system using a statically-linked XBPSThis can be from a live image, though depending on your setup that might present some issues with memory and device throughput when writing to the SD card.

First off, we're gonna want to make sure all our repositories and packages are up to date:

Hi,
I just bought the LCD panel for my pine a64 and I was wondering where I can find the android os that supports the screen? or else can anyone tell me how to find and edit the uEnv.txt file to make it display on the LCD?