| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,205
» Latest member: Karen68
» Forum threads: 16,384
» Forum posts: 117,596
Full Statistics
|
| Latest Threads |
Hardware Feature Suggesti...
Forum: Quartz64 Hardware and Accessories
Last Post: Independent Researcher
Yesterday, 07:19 PM
» Replies: 0
» Views: 40
|
Single-board computers an...
Forum: General
Last Post: Spaker
08-29-2026, 08:12 PM
» Replies: 0
» Views: 71
|
Pinephone visibly losing ...
Forum: General Discussion on PinePhone
Last Post: baptx
08-29-2026, 11:18 AM
» Replies: 9
» Views: 8,384
|
Fixing the Quartz64 USB3 ...
Forum: Quartz64 Tutorials
Last Post: mig
08-28-2026, 01:32 AM
» Replies: 1
» Views: 12,775
|
Pinecil as a Pocket-Sized...
Forum: General
Last Post: Arsen
08-27-2026, 09:15 AM
» Replies: 0
» Views: 131
|
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-24-2026, 08:00 AM
» Replies: 0
» Views: 198
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: Nambo
08-23-2026, 12:17 AM
» Replies: 18
» Views: 13,640
|
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 398
|
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 2,043
|
RAM-free SBCs with SODIMM...
Forum: General
Last Post: anchor
08-20-2026, 08:21 AM
» Replies: 0
» Views: 176
|
|
|
| Roadmap questions from a PinePhone owner |
|
Posted by: 3x5co - 06-26-2020, 09:46 AM - Forum: UBPorts on PinePhone
- Replies (1)
|
 |
Hi there, I recently received my PinePhone, and while I'm excited about the project, the phone itself is not totally usable, yet. I get that this has been established, while I admit I didn't read the fine print, my old phone still works for now and my PinePhone is something I'll ease into.
My questions are as follows:
- Is it safe to assume my hardware will not need to be upgraded? I'm assuming all the updates from here on out will be software, and sometime — maybe in a few months, maybe a year — I'll be able to use my PinePhone as my primary phone.
- Realistically, when do you think the PinePhone will be more or less ready for prime time? Are we thinking 6 months? A year? Just curious. sorry if this has been addressed elsewhere.
- If I'm going to dual boot, what other OS is the farthest along? I read that the next sound of PinePhones will ship with Postmarket OS, but PinePhone's position seems to be that UBports is the most stable right now. Someone on the forum said Mobian is working best for them.
- Is there any reason not to run the bleeding-edge repos? At this point, if the phone is semi non-functional anyway, It seems the fastest way to get stability would be to move to the dev channel.
Thanks for reading, and for creating this phone. I spent a lot of effort rooting my Android phone, installing lineageOS with no Google Play services, and somehow it still shows me ads based on things I've said in the room. I'm hoping with PinePhone, I'll finally have a phone that doesn't spy on me!
|
|
|
|
flickering vignette display? |
|
Posted by: plarkinjr - 06-26-2020, 08:54 AM - Forum: General Discussion on Pinebook Pro
- Replies (4)
|
|
Got my first PBP a couple weeks ago - Manjaro KDE ... did the steps in the wiki for it:
https://wiki.pine64.org/index.php?title=...KDE_system
Everything was running fine..... until: I got the debian image onto SD card and booted it. The screen was immediately over bright, flickering rapidly & steadily, and had a vignette effect (darker soft band around the outer edges). I booted Debian a couple more times and observed the same. then I removed microSD and booted back to manjaro KDE and the same video effect persists!
So, what do I do now? did booting Debian jack the firmware or something? Is this a coincidental manufacturers defect?
|
|
|
|
| Frequent segfaults etc. while compiling |
|
Posted by: mfritsche - 06-26-2020, 07:15 AM - Forum: Linux on Pinebook Pro
- Replies (13)
|
 |
Is it possible my pinebook pro suffers from a similar issue as mentioned in https://forum.pine64.org/showthread.php?tid=7387 ?
When I try to compile large projects (using Manjaro), i.e. GHC (Haskell Compiler), I suffer from segfaults and similar errors. Most of the time (if the previous object files weren't broken), just restarting helps.
I already extended the cooling pads. Using make -j 6 yields errors quicker, but single thread compiling doesn't fully fix the issue. Using different govenors yields the same observation - using powersave instead of the performance ones does lead to errors later, but don't fully fix them.
Anyone else seeing the same? Is there a way to limit the RAM clock on the pinebook pro?
Best regards, Markus
|
|
|
|
Pin configuration |
|
Posted by: pratyush049 - 06-26-2020, 05:38 AM - Forum: General Discussion on PineTime
- Replies (3)
|
|
sir,
i am working on wasp OS for pinetime want to check out the pin config of all protocols like spi, i2c, vibration motor pin, button pins etc. where can i find that file. i have been searching all day but didn't got. Can you help me out in this.
thankyou so much.
|
|
|
|
Cellular Data |
|
Posted by: vicky - 06-26-2020, 02:24 AM - Forum: UBPorts on PinePhone
- Replies (4)
|
|
I tried to enable cellular data on my UBports Edition. In stable (OTA-03 eMMC)as well as developement (Version 58 build number 2020-06-25/2 on SD card) I cannot switch cellular data on. The switch is a darker grey in the menu and seems to not let me activate it. I entered APN details myself. I tried it with two different SIM cards of different networks.
Am I missing a step? Any suggestions where my problem comes from?
|
|
|
|
| Cannot charge and NO Wifi? |
|
Posted by: jiapei100 - 06-26-2020, 02:02 AM - Forum: Getting Started
- Replies (3)
|
 |
I just received my PINE64 Community Edition: UBports Limited Edition Linux today. And it seems it got some issues:
1) It seems the power on my laptop's USB port is NOT powerful enough to power PINE64 up, PINE64 always restart after I see the PINE64 logo.
2) Therefore, I tried to power PINE64 up using USB power adaptor with the delivered Type C cable. Now, PINE64 boots into Ubuntu 16.04. However, it's NOT changing at all. the Battery Charge Level sticked to 0%, no matter how many hours I left PINE64 for charging. As long as I disconnect the Type C cable, PINE64 is out of power and shut down right away.
3) What'e even more weird. In Settings->Battery, there is even choices for Wi-Fi and Bluetooth? What's that for?
4) And in Settings->Wi-Fi, there is ONLY 1 option: Previous networks , PINE64 won't be able to show Wireless network around.
So, in sum: PINE64 ALWAYS stick to batter charge 0%, and Wi-Fi doesn't search wireless network at all.
Did anybody have those issue as well? Is there a way to let me reflash Ubuntu onto PINE64 from scratch ?? Say, how can I flash Ubuntu 20.04 onto PINE64 ?
Thank you very much. Looking foward to have some fun on PINE64.
Pei
|
|
|
|
| Creating a current armbian-Image with network-fix |
|
Posted by: clusterDude - 06-26-2020, 12:21 AM - Forum: Clusterboard
- Replies (15)
|
|
I recently got my sopine modules and my clusterboard only to notice that the network is not working. So I searched the forums and found a way to conveniently build an Armbian-Image which has the network fix applied (using Ubuntu):
I tested this with the current Armbian Focal release.
Thanks to @AZClusterboard who made an initial guide on how to setup the clusterboard which gave me confidence to buy my own cluster!
Step [b]Overview:[/b]
- Download current Armbian Focal release
- Mount the Image to make modifications
- Make changes to the .dtb file (allwinner network fix)
- Write the changed Image to as many sopines as you wish
- (Give each sopine a unique hostname by hand)
Step number 5 is not necessary but it helps in identifying sopine modules by name. So you can boot all modules at once, look at a "nmap" printout and can see each hostname and the corresponding ip-adress.
More thorough explanation of the steps:
1. Download current Armbian Focal release (https://www.armbian.com/sopine-a64/)
2. Mount the Image to make modifications (more informations here)
2.1. create a dir to mount the image to: e.g.
2.2. find the location of the partition within the image
Code: fdisk -l <armbian-image.img>
Code: 512 bytes/sector * 8292 sectors =4194304 bytes
2.3. mound the image at the correct sector to the created directory in /mnt/img
Code: sudo mount -o loop,rw,sync,offset=4194304 <armbian-image.img> /mnt/img
3. Make changes to the .dtb file
3.1. navigate to the correct .dtb file
Code: cd /mnt/img/boot/dtb/allwinner/
3.2. Now we need to translate the .dtb file. To do so we change it into a modifiable state using dtc. The file we want to change is sun50i-a64-sopine-baseboard.dtb (see here). I will name this modifiable file "temp.dts". This command will most likely throw some warnings but it will work.
Code: sudo dtc -I dtb -O dts -o temp.dts sun50i-a64-sopine-baseboard.dtb
3.3. apply the fix to temp.dts described here
go to the segment
and add
Code: allwinner,tx-delay-ps = <500>;
as described here [LINK]
It will then look similar to
Code: ethernet@1c30000 {
compatible = "allwinner,sun50i-a64-emac";
syscon = <0x2d>;
reg = <0x1c30000 0x10000>;
interrupts = <0x0 0x52 0x4>;
interrupt-names = "macirq";
resets = <0x2 0xd>;
reset-names = "stmmaceth";
clocks = <0x2 0x24>;
clock-names = "stmmaceth";
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <0x2e>;
phy-mode = "rgmii";
phy-handle = <0x2f>;
phy-supply = <0x30>;
phandle = <0x6f>;
allwinner,tx-delay-ps = <500>;
mdio {
compatible = "snps,dwmac-mdio";
#address-cells = <0x1>;
#size-cells = <0x0>;
phandle = <0x70>;
ethernet-phy@1 {
compatible = "ethernet-phy-ieee802.3-c22";
reg = <0x1>;
phandle = <0x2f>;
};
};
};
3.3. translate the modified .dts to and .dtb file and overwrite the old(faulty) .dtb-file. This command will produce some warnings, but it will work.
Code: sudo dtc -O dtb -o sun50i-a64-sopine-baseboard.dtb -b 0 temp.dts
3.4. remove the temp.dts
3.5. unmount the image, go to your home directory first, so the unmount process is successful
Code: cd ~/
sudo umount /mnt/img
4. The image is now ready to be written to a sd-card!
5. To change the hostname of each "sd-card"
After the sd-card is written, mount the sd-card and navigate
and change 2 files:
[1]In hostname, specify a hostname (old one is most likely "pine64so") you like (probaly something like "master" or "worker1" or "worker2" ...),
[2] in hosts, change every entry with the old hostname to your new hostname.
Save the changes made to both files, unmount you sd-card, put it in the sopine-module, wait for it to boot (may take some minutes), login with "root" and "1234" and enjoy your cluster!
If you have any questions, comments or suggestions for improvement let me know!
|
|
|
|
| CPU Configuration and Status Scripts for PBP/Linux |
|
Posted by: Syonyk - 06-25-2020, 10:28 PM - Forum: Linux on Pinebook Pro
- Replies (2)
|
|
https://github.com/syonyk/pinebookpro
I've created two halfway helpful utility scripts that are useful enough to share generally. They should work with any Linux, though I've only tested them on Ubuntu 20.04/mainline kernel 5.7.
The first is cpu-set.sh - which allows you to, as root, quickly toggle between all CPUs, big CPUs, little CPUs, see the status of the CPU, and set the governor across all the cores (the cpufreq-utils don't seem to get all the cores properly). Really, you shouldn't have to do much more than powersave, performance, or schedutil. I've not seen much power savings by turning cores off, but if you want to do hardware accelerated KVM work, you'll need to disable the little cores - they don't seem to support the hardware virtualization properly.
The second is pbp-status.sh - which shows the CPU status, temperature, and some basic battery stats (voltage, current, watts). Most of the battery stats will be zero while charging, as the only one you get out is the voltage. This doesn't need root.
Code: CPU0: 1 Freq: 1200 MHz (schedutil)
CPU1: 1 Freq: 1200 MHz (schedutil)
CPU2: 1 Freq: 1008 MHz (schedutil)
CPU3: 1 Freq: 1200 MHz (schedutil)
CPU4: 1 Freq: 600 MHz (schedutil)
CPU5: 1 Freq: 600 MHz (schedutil)
Temp 0: 35
Temp 1: 35
Voltage: 4077 mV
Current: 823 mA
Power: 3355 mW
Enjoy! Let me know if there are other things you'd like to see.
|
|
|
|
|
