Hi there,

I am interested in using Fedora on my Pinebook pro. However, I suspect Fedora Workstation would be a bit heavy for the specs. So, I am hoping to setup a lightweight Fedora from the minimal image. I came across a few problems with this:

1. What is the default username and the password for the login to the Fedora minimal?
2. How to connect to a wireless network from the Fedora minimal?

I want to setup Fedora with either LxQT or xfce. If there is good documentation, I would consider i3 or sway too.

Any help would be appreciated.

I was thinking that I might be more interested in blackberry style qwerty keyboard, than keyboard that is being worked on for Pinephone right now. Is there more people interested? How dificult would be to make specific version of pinephone with this design? Or maybe DIY kit with necessary parts? Now when Blackberry no longer makes phones only other option with this design is chinesse Unihertz Titan which is not suitible from many reasons (screen size, heavines, software support, etc.)

Regarding an old thread, has someone done measurments e.g. with a microwave leak detector?

I recently received the PineTime I ordered and it's nice! I managed to upgrade the firmware without issues (InfiniTime 1.7.1) using siglo on the PinePhone (Mobian), but now I am stuck! I can't find any information on how to use siglo with the PineTime. So here are a few possibly dumb questions:

- Is siglo supposed to do more than flashing the OS or is that it's purpose?
- If siglo does more: do I need to keep it running in order to receive notifications?
- I seem to be able to pair on siglo and pair in the PinePhone bluetooth options, is both required for notifications?
- If siglo is not intended to deliver notifications, are there instructions somewhere on how to install amazfish on the PinePhone?

Hello, everybody.

My Rock64 bricked after I incorrectly booted a SD card loaded with an unknown OS (I have many boards, lost track of which OS I put in).
Now it just won't boot anymore, just two solid LEDs.

I tried following instructions from these posts with no avail:
https://forum.pine64.org/showthread.php?tid=6508
https://forum.pine64.org/showthread.php?tid=5008
https://forum.pine64.org/showthread.php?tid=8668

To summarize the things I have done so far:

• stretch-minimal-rock64-0.8.3-1141-arm64.img
  
• u-boot-flash-spi-rock64.img
  
• u-boot-erase-spi-rock64.img
  
• And many different OS images ...
  
• Shorted pin 20/21 or 23/25 to disable boot into SPI
  
• Unplug UART TX line prior to boot up
  
• Connect USB OTG to computer but computer do not recognize such hardware even with driver installed
  

Quote:DDR version 1.13 20180428
ID:0x805 Y
In
LPDDR3
786MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB
ddrconfig:6
OUT

So I have searched around without much luck. I am looking to go daily driver with or without MMS but it seems the newest version of Manjaro has MMS support in chatty, I have filled out the MMS settings with T-Mobiles recommended settings but no luck. Is this not supposed to be working or am I doing something wrong?

I have noticed the ~/.mms/moddemanger/mms/ folder is holding files that seem to be my MMS mesages but i have no way to view them?

Excuse my ignorance I have been away for a while and have not followed development to closely but does the modem still get clogged if I do nothing with missed MMS?

Thanks in advanced.

I am sure the PinePhone is a great little phone and lot's of fun to experiment with but I will never have the opportunity to experience it.
PinePhone shipped it promptly. Within three days of purchase. It was sent via DHL and arrived in Miami on October 30, 2021 and that is where it was lost. I notified PinePhone and no answer, no response. You cannot contact them till the phone is missing for THIRTY DAYS and then they promptly respond stating they will not send another phone or give a full refund till DHL declares the phone is lost. Well Good Luck with that. I have to do all the work and it's very dismal dealing with DHL.

I have sent numerous emails to DHL which they state someone will call me within two hours and I never receive the call. Few days go by and I contact them again receiving the same response. It has been a month since I notified DHL and asked them to declare the phone LOST and now they want package details, size, weight, model of the phone, serial number, color, etc. I do not have this information. PinePhone does and THEY should contact DHL but they don't. I am their customer!

Why doesn't PinePhone get involved and communicate with DHL? They shipped it through them. PinePhone,org is not helping me at all and I have a lost phone and out of $225.00 and paid extra shipping expense to ensure the package would arrive.

Pine Phone has dropped the ball on this big time. I was patient for thirty days thinking PinePhone will come through but I do not see that happening. Really disappointed.

so my spacebar was stuck, I tried to clean it with some isopropyl, but it looks like i killed the whole keyboard. is there another way to try to turn on the PBP to see if it's just the onboard keyboard? this thing has beeen a good sidekick, would be nice if I can just replace the keeb

edit: short power and gnd pins on the motherboard's keyboard connector
https://files.pine64.org/doc/PinebookPro...ematic.pdf

Hi all,

I am a beginner with all this, so please, excuse the lack of knowledge.  Just opening the books up as I'm fed up with google and the stalking.

I have my pinephone, went through the set up, but it wont unlock? 
Used the 123456 and loads of other combinations. Read a post that 147147 worked tried it and it failed.

Any one got any thoughts? 

Or any suggested literature in getting started?

I just got booked on Jason Cannons linux course as a starter to get started.

I'm working on SMBIOS support for the Quartz64, and the CPU reports that it supports the Arm64SocID SMC call.
But it's returning invalid values: 

Jep106 code: 0xFFFFFAE0
SoC revision: 0xFFFFFB18

According to the SMC Calling Convention, the top bit of both should be zero:

SoC_ID_type == 0
JEP-106 code for the SiP
Bit[31] must be zero
Bits [30:24] JEP-106 bank index for
the SiP (see [9.])7
Bits [23:16] JEP-106 identification
code with parity bit for the SiP (see
[9.])7
Bits [15:0] Implementation defined

SoC ID

Bit[31] must be zero
Bits [30:0] SoC revision


How would I go about reporting this problem to Rockchip? I don't know if this is a problem they can fix in their rkbin repo, or if it's a hardware bug.