| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,964
» Latest member: gesav72643
» Forum threads: 16,334
» Forum posts: 117,438
Full Statistics
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
Yesterday, 08:44 AM
» Replies: 0
» Views: 47
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,494
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 117
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 66
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 215,656
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 115
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 185
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,017
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 894
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 574
|
|
|
| About the next ARM-based macbook.... |
|
Posted by: walterego - 06-24-2020, 04:20 PM - Forum: General Discussion on Pinebook Pro
- Replies (34)
|
 |
Hello! I recently received a Pinebook pro and I love the aestetichs and the idea of an arm-based laptop. However I see lag of support regarding most Distros that could do wonders in this machine.
Meanwhile the rumors of a new arm-based Macbook Air are real and I was wondering if somebody would be brave enough to eventually port arm-MacOS to the Pinebook pro. that would be the ultimate Operative System goal IMO. Any thoughts?
|
|
|
|
| New Pinephone No Audio |
|
Posted by: rohtua - 06-24-2020, 03:40 PM - Forum: PinePhone Hardware
- Replies (1)
|
 |
Hi
Just received my brand new pinephone ub edition. Booted up to find no audio from speaker, headphone jack or Bluetooth headphones. All the kill switches are set to on and im getting nothing. I've booted up the postmarketos factory test to see if it was just an issue with the UBPorts install and I'm getting nothing from the earpiece/speaker tests.
Does anyone have any ideas/suggestions as to what's happened and if there's anyway I can fix it?
|
|
|
|
| Not booting , Black screen backlight is on |
|
Posted by: pokemanearth - 06-24-2020, 03:27 PM - Forum: General Discussion on PinePhone
- Replies (17)
|
 |
I got my pinephone today. Switched on, it worked , did some setting changes, rebooted several time. After a few hours rebooted, then it stop booting up. The LCD backlight is on, the led flashes red green white in the beginning and nothing. Screen goes to sleep, if I press power the backlight comes on but the screen is black. Cannot go into recovery mode. Flashed other OS in SD same problem. Flashed fedora , lcd backlight does not even come up, after 30 sec led light next to camera switches on .Strange issue , any idea? Thanks.
|
|
|
|
| UBports CE: No sound or vibration? |
|
Posted by: ajdunevent - 06-24-2020, 12:17 PM - Forum: General Discussion on PinePhone
- Replies (3)
|
 |
Woohoo! DHL dropped off my phone a little bit ago.
Quick testing has revealed some problems. I can't seem to get sound or vibration to work. I tried some corded headphones but also didn't get any sound that way. Bluetooth won't stay off. The cameras don't seem to be working. My nano SIM was recognized and I was able to connect to the towers but I wasn't able to make or receive phone calls or send and receive SMS.
I know this is more of a development device and a service to the community so I'm not expecting a white glove roll out or anything. I am just looking for some reassurance that the issues I'm having are software and not hardware related and thus might be solved instead of my particular device being doomed to uselessness.
Thanks!
|
|
|
|
Simulator issue |
|
Posted by: pratyush049 - 06-24-2020, 05:28 AM - Forum: General Discussion on PineTime
- Replies (3)
|
 |
sir,
simulator is working fine but when i go to keyboard interrupt and do following the commands as you mentioned to check other application it does not update in the screen. what would be the issue?
thank you.
|
|
|
|
wasp simulation error |
|
Posted by: pratyush049 - 06-24-2020, 04:01 AM - Forum: General Discussion on PineTime
- Replies (1)
|
 |
sir,
while using simulator of wasp os am getting some error as mention below:-
raise UnsupportedError(pixels2d, "numpy module could not be loaded")
sdl2.ext.compat.UnsupportedError: 'numpy module could not be loaded'
can you share something about this error. what should i do further to overcome this error ! thankyou
|
|
|
|
| Installing latest version of crust |
|
Posted by: davegermiquet - 06-24-2020, 01:14 AM - Forum: General Discussion on PinePhone
- No Replies
|
 |
I installed the latest version of crust , by doing the following on my Mac:
This was using the Mobian stable and Mobian Nightly build:
used a docker Debian image, latest
make sure git/build-essential/cross compiler is installed
Downloaded the following and placed in /opt folder
https://musl.cc/or1k-linux-musl-cross.tgz
git clone https://github.com/crust-firmware/meta.git
edit the Makefile
update cross compiler folders
update board to say pine phone
make
(makes images)
grabbed the following afterwards:
u-boot-sunxi-with-spl.bin
copied this file to Mac book host file
booted up with jump drive on my sdcard
now I can see all drives
unmount all drives
bash-3.2# gpt -r show disk3
start size index contents
0 1 MBR
1 1952
1953 248048 1 MBR part 131
250001 7171874 2 MBR part 131 MBR part 131
7421875 23363661
See (1 1952) is not assigned, but 1
and 2 are so I zeroed out 1 - 1952 just in case left overs (This is where uboot resides be careful your deleting boot now)
bash-3.2# dd if=/dev/zero of=/dev/disk3 bs=512 seek=1 cou
sync && sync && syncnt=1952
then I did the following:
bash-3.2# dd if=u-boot-sunxi-with-spl.bin of=/dev/disk3 bs=1024 seek=8
the above can be found at SUNXI sites=
sync && sync && sync
1024 seek=8
Try at your own risk but it worked for me
Output on UART:
DRAM: 2048 MiB
Trying to boot from MMC2
NOTICE: BL31: v2.3(release):v1.4-5069-ga4b8b9dba
NOTICE: BL31: Built : 1592882082
NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE: BL31: Found U-Boot DTB at 0x40647b8, model: Pine64 PinePhone (1.2)
NOTICE: PSCI: System suspend is available via SCPI
U-Boot 2020.07-rc4-18358-g139397e64e (Jun 23 2020 - 03:14:42 +0000) Allwinner Technology
CPU: Allwinner A64 (SUN50I)
Model: Pine64 PinePhone (1.2)
DRAM: 2 GiB
MMC: Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000'
mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:2... In: serial@1c28000
Out: serial@1c28000
Err: serial@1c28000
starting USB...
No working controllers found
Hit any key to stop autoboot: 0
|
|
|
|
| Need help updating comparison of the PinePhone vs Librem 5 specs |
|
Posted by: amosbatto - 06-24-2020, 12:42 AM - Forum: General Discussion on PinePhone
- Replies (6)
|
 |
I'm trying to update my comparison of the PinePhone vs Librem 5 specs:
https://forums.puri.sm/t/comparing-specs...hones/6827
Can anyone tell me: - What RAM chip is used in the PinePhone (or at least what speed of RAM)?
- What Flash memory chip is used in the PinePhone?
- Is the A64 on the PinePhone running at 1.2 GHz or 1.152 GHz?
- Can anyone weigh the PinePhone to verify that it is 185 grams?
- What is the specific Goodix touchscreen controller chip?
- Can the battery be replaced just using fingers (no tools)?
- Is there a list of the apps available in Ubuntu Touch?
- Are there any other chips on the PinePhone that I missed?
- Has anyone benchmarked the performance of the PinePhone?
- Will both DisplayPort and HDMI Alt Mode work over the USB-C port?
- Does anyone know the clock speed of the Mali-400 MP2 GPU?
And of course, is there anything inaccurate in the table or that needs to be added?
Thanks in advance for your help.
|
|
|
|
| Manjaro 20.06 Step-By-Step Installation Guide |
|
Posted by: nathanielwheeler - 06-23-2020, 07:24 PM - Forum: Linux on Pinebook Pro
- Replies (19)
|
 |
I've found that the information needed to replace the default OS on Pinebook Pro is scattered all over the place, and in some places, contradictory. To help newbs like me avoid the trial-by-error that I went through, I've made the following guide based on a successful replacement of Mate/Debian with XFCE/Manjaro.
Update: extended introduction to clarify the structure of the guide
First, an overview of the guide. First, to replace the eMMC distro, we need to make an ARM-compatible OS on a microSD. For the purposes of this guide, we will be using the same OS on the microSD as we are on the eMMC, but theoretically any ARM-compatible OS could be used on the microSD.
Once we have the working OS on the microSD booting on the PBP, we will use that system to use 'dd' to transfer an image of manjaro directly onto the eMMC, bit by bit.
0. Get the proper images and signatures.
First, download the images and checksums you need.
KDE Plasma
- Download
- Torrent
- sha256
XFCE
- Download
- Torrent
- sha256
I3
- Download
- Torrent
- sha256
1. Verify checksums
It's very important to verify that the compressed image you downloaded isn't corrupted or anything. To do that, we will be running sha256sum on our image and checking it against the checksum we downloaded.
Make sure you are in the directory containing the images, usually `~/Downloads`
Code: $ sha256sum <target image>.img.xz
For mac, use:
Code: $ shasum -a 256 <target image>.img.xz
This will print a string of characters followed by the name of the file. Check that checksum against the .img.xz.sha256 file. There are many ways to do this, but the simplest way is to print the file:
Code: $ cat <target image>.img.xz.sha256
Ideally, the output will look exactly the same as the sha256sum function. If it isn't, then your image is corrupted and you need to redownload the image.
2. Decompress the image
Get xz-utils if you don't already have it installed.
Code: $ # On Arch:
$ sudo pacman -Syu xz-utils
$ # On Debian/Ubuntu:
$ sudo apt-get install xz-utils
Then, extract the image.
Code: $ # I like to use the -v flag so I can watch the progress of the extraction
$ unxz -k -v <target image>.img.xz
The mac equivalent is a bit different:
Code: $ # Get xz package if you don't already have it
$ brew install xz
$ # Decompress image
$ xz -d -k -v <target image>.img.xz
3. Flash to microSD using Etcher
I recommend using balena Etcher to flash the image to microSD. Simply select the image, then the drive to flash to, and then wait for etcher to finish. It will likely take good while, so make some tea or something.
4. Boot from microSD.
Once the microSD has been flashed, pop it into the microSD drive on your Pinebook Pro and turn it on. If all has gone well, it will boot to Manjaro's desktop.
NOTE: this system is not our final OS, this is simply the environment in which we will install Manjaro the internal eMMC memory.
You will get a few setup questions:
- keyboard layout
- username
- additional groups (there's a bug here: leaving this field empty will not add the default groups, so you will have to type them in manually separated by commas)
- full name
- password
- root password
- timezone
- locale (en_US.UTF-8 if you are located in the United States)
- hostname
At this point, we still need to put Manjaro on the internal eMMC memory, so we have a few more steps to run.
5. Repeat steps 0-2
As much as I wish to tell you that the Manjaro ARM installer works, it is incredibly buggy at the moment, so this is where we will have to get technical and dangerous. Download a new image of Manjaro, verify its checksum, and decompress it, just like we did in Steps 0-2.
EDIT: To clarify, this image should be on the freshly booted microSD portion of the PBP. This cannot be done on the eMMC portion of the PBP, because we are using this image to to replace the operating system on the eMMC. It has to be done from the microSD.
6. Using dd
EDIT: First, make sure that you are booted on the microSD card. This will not work if you are working on the eMMC portion of the PBP.
At this point, I'm afraid we have to resort to the tool of last resort: dd. Jokingly, it is short for "disk destroyer", because it is incredibly literal and the slightest misspelling could destroy all data on the target.
What dd does is it does a direct bit-by-bit transfer from a target to a destination in the form of:
Code: $ dd if=<target> of=<destination> bs=4M status=progress
EDIT 2020-11-03: I have added a few arguments that make dd a little faster. `bs=4M` makes the byte copy go way faster, and is just as reliable as the default (512 bytes). I also added in the `status=progress` argument, which will show the byte copy progress in real time.
So, for our pinebook pro, we are targeting our freshly downloaded image, likely at '/home/<user>/Downloads'. The destination will be '/dev/mmcblk2', but you should use `fdisk -l` to verify that your eMMC internal storage is located there.
For my own pinebook pro, I ran:
Code: $ dd if=/home/<user>/Downloads/<target>.img of=/dev/mmcblk2 bs=4M status=progress
7. Reboot
Shutdown your system, remove the microSD card, and if all went well, you should be prompted for the same information as you were prompted for in Step 4.
8. Rejoice!
Congratulations, you have now successfully replaced the default OS on the Pinebook Pro!
|
|
|
|
|