| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Mobian image for the Pine...
Forum: Mobian on PinePhone
Last Post: Korfou
04-27-2026, 09:57 AM
» Replies: 2
» Views: 145
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
04-19-2026, 12:56 PM
» Replies: 13
» Views: 14,952
|
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 193
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 19,485
|
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,123
|
my pinecil v2 is not work...
Forum: General Discussion on Pinecil
Last Post: jagrav
04-17-2026, 06:28 AM
» Replies: 0
» Views: 125
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,455
|
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 315
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 9,283
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 443
|
|
|
| Mods need help |
|
Posted by: aular2 - 07-29-2024, 08:38 AM - Forum: General
- Replies (2)
|
 |
I need help recovering my old password to my other account. Same name minus the 2 at the end of it. I cant recieve the recovery emails and i tried multiple times.
|
|
|
|
| Battery life suggestion |
|
Posted by: aular2 - 07-29-2024, 08:08 AM - Forum: General Discussion on PinePhone
- Replies (2)
|
 |
Since my other account is unable to recieve recovery emails since somebody blocked it i had to create a new account and start over.
So what i wanted to ask or suggest is is it possible for somebody to create 2 versions of an os. What i mean by that is since android and ios do all this stuff that reserves battey life like shutting down processes and other stuff to drastically improve battery life, is there a developer willing to copy that same model to improve battery life but have 2 os versions where 1 has what we have now and the other has the clone of the android ios battery life but for the pine phone?
|
|
|
|
| A way to view or log the splash screen on Pinephone Pro running ArchLinux (Danctnix) |
|
Posted by: PHLEMON - 07-29-2024, 06:26 AM - Forum: General Discussion of PinePhone Pro
- Replies (4)
|
 |
Good day!
I've been using Pinephone Pro as a daily driver for 7 months now. Mainly with Arch Linux Danctnix OS. Recently, I'm having problems with connecting to the wifi. It can scan available SSIDs but could not connect after a 90 second timeout.
I've tried manually connecting the wifi via nmcli, manually installing the firmware for brcmfmac from github repos and rebuilding the initramfs. But it doesn't seem to fix my problem.
I'm thinking whether this is a hardware problem (given that I charge it with a 5v:3000ma charger overnight) or a software problem (since I usually update with yay first then sudo pacman -Syu. The updates could've messed with the firmware.)
SInce I use the phone almost always for online activities, I can't use it and I usually reboot it often following the wifi connectivity error. While doing so, I read something in the splash screen at boot-time stating something along the lines of "Failed to read chip id 258" Hopefully anyone here could point me to a way to log or view the messages at the splash screen, or a more appropriate forum or discussion board to bring up my concern.
Help a bro out, links or advice would be greatly appreciated.
|
|
|
|
| tow-boot, just bought pinephone pro |
|
Posted by: stratofall - 07-29-2024, 05:30 AM - Forum: PinePhone Pro Software
- Replies (4)
|
 |
My pinephone pro came with sailfish and I believe U-boot ...
I've been trying to try different OS's from the wiki using sdcard.
Some work, some don't.
I assume a lot of the ones that don't work I need to install tow-boot.
My issue is...
I have the tow-boot spi on an sdcard.
I push in the re button and then the power button. (I have tried plugging in power via usb as well).
But, nothing happens. It never boots to the spi install screen.
Is there something I am doing wrong in this regard?
Also, if I ever do get tow-boot installed, how do I revert to a stock U-boot? I have not seen instructions for doing so with the reading I have done yet.
Any help is appreciated. I am just tired of iOS and android and tired of throwing away phones. I am hoping pine64 and its open nature can satiate my basic needs.
|
|
|
|
| Disable MicroSD reader for extra GPIO |
|
Posted by: mxruben - 07-27-2024, 10:08 PM - Forum: General Discussion on ROCK64
- No Replies
|
 |
Hello! I am working on a project that requires nearly all of the GPIO pins on the rock64. 7 of the GPIO pins are unusable while the microSD card reader is in use. To fix this, I installed armbian onto a usb drive and am booting from it now instead. However, I am still unable to set the GPIO pins that were in use by the microSD card reader. My guess is that it is still active, even though it is not reading anything. I think I need to do something to disable it. Has anyone found a way to access these GPIO pins?
|
|
|
|
| Desktop ready? |
|
Posted by: eiger3970 - 07-27-2024, 07:49 PM - Forum: General
- No Replies
|
 |
Hello, I'm new to RISC-V and would like to try a desktop board (no gaming needed).
I would like:
1. **Audio connection** for speakers (unless there's some wireless way I don't know about?)
1. **Bluetooth** for mouse or keyboard
1. **Display connections** x3, perhaps micro HDMI or USB-C (AOC 22B2H or similar)
1. **CPU**: RISC-V
1. **Graphics** integrated
1. **Mobo**: SBC
1. **NIC** x2 (run a VM router)
1. **Power**
1. **Ram**: 16-32GB preferred
1. **Storage**: NVMe PCIe, probably 32GB-256GB, nothing large like 1TB
1. **USB** x2 for spare stuff
1. **Wi-Fi** for Internet hotspot, mouse or keyboard
|
|
|
|
| Enhancing Privacy with additional hardware killswitches |
|
Posted by: Substing - 07-24-2024, 10:24 PM - Forum: General
- Replies (2)
|
 |
I've been following the discussions on the need for more hardware killswitches to enhance privacy and security. Inspired by the suggestions in this thread, I wanted to gather more insights and ideas from the community. basket random
1. What additional hardware components do you think should have killswitches to prevent potential privacy breaches?
2. Are there any specific use cases or scenarios where you believe these additional killswitches would be particularly beneficial?
3. Have you encountered any privacy concerns with existing hardware that could be mitigated with the implementation of killswitches?
|
|
|
|
| problem with debian emmc boot |
|
Posted by: G4zCDzWb - 07-23-2024, 12:41 PM - Forum: Linux on Rock64
- Replies (10)
|
 |
I have been struggling with trying to get debian installed and booting on my rock64 v2 via emmc.
So far, the most current method I have tried is this guide. Everything seemed to go fine until the install finished and I rebooted. Upon boot-up I saw the following on serial console:
Code: U-Boot TPL 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21)
LPDDR3, 800MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000)
Trying to boot from MMC2
NOTICE: BL31: v2.8(debug):
NOTICE: BL31: Built : 06:31:44, Nov 25 2022
NOTICE: BL31:Rockchip release version: v1.2
INFO: ARM GICv2 driver initialized
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
INFO: BL31: cortex_a53: CPU workaround for 855873 was applied
WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000)
Model: Pine64 Rock64
DRAM: 2 GiB
PMIC: RK8050 (on=0x50, off=0x10)
Core: 228 devices, 24 uclasses, devicetree: separate
MMC: mmc@ff500000: 1, mmc@ff520000: 0
Loading Environment from MMC... Card did not respond to voltage select! : -110
*** Warning - No block device, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Pine64 Rock64
Net: eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2904 bytes read in 4 ms (709 KiB/s)
## Executing script at 00500000
32688064 bytes read in 848 ms (36.8 MiB/s)
36095 bytes read in 10 ms (3.4 MiB/s)
30462286 bytes read in 775 ms (37.5 MiB/s)
Booting Debian 6.1.0-23-arm64 from mmc 0:1...
Moving Image from 0x2080000 to 0x2200000, end=41d0000
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Working FDT set to 1f00000
Loading Ramdisk to 7b20f000, end 7cf1c14e ... OK
Loading Device Tree to 000000007b203000, end 000000007b20ecfe ... OK
Working FDT set to 7b203000
Starting kernel ...
[ 4.349873] rockchip-pm-domain ff100000.syscon:power-controller: failed to get ack on domain 'hevc', val=0x88220
[ 6.195026] rockchip-pinctrl pinctrl: pin gpio0-2 already requested by vcc-host-5v-regulator; cannot claim for vcc-host1-5v-regulator
[ 6.196127] rockchip-pinctrl pinctrl: pin-2 (vcc-host1-5v-regulator) status -22
[ 6.196802] rockchip-pinctrl pinctrl: could not request pin 2 (gpio0-2) from group usb20-host-drv on device rockchip-pinctrl
[ 6.197825] reg-fixed-voltage vcc-host1-5v-regulator: Error applying setting, reverse things back
[ 7.526011] mmc1: mmc_select_hs200 failed, error -110
[ 7.526497] mmc1: error -110 whilst initialising MMC card
[ 8.488081] mmc1: mmc_select_hs200 failed, error -110
[ 8.488567] mmc1: error -110 whilst initialising MMC card
[ 9.452265] mmc1: mmc_select_hs200 failed, error -110
[ 9.452753] mmc1: error -110 whilst initialising MMC card
[ 10.489412] mmc1: mmc_select_hs200 failed, error -110
[ 10.489902] mmc1: error -110 whilst initialising MMC card
Gave up waiting for suspend/resume device
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/d08756f8-8dcd-41f0-b02b-c4ff2da5e68b does not exist. Dropping to a shell!
BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
I am able to run the installer and install to an SD card without any issues. Reboot will result in a working system. If I pull the EMMC card out and mount it on a separate machine via adapter, the files and partition layout look like what I would expect, the dtb seems to be in place and correct for the hardware, etc. I poked around a bit in the busybox shell but didn't have a solid plan for what I was trying to achieve other than basic investigation.
Does anyone here have any idea where I should look next? I've gone through this setup/install process multiple times and the result is the same each time. I did have arch linux running on this board for a month or so but updates broke it twice and both times I just reinstalled. I got tired of that since this is normally a headless system in a place where I don't want to have to remove it over and over.
|
|
|
|
| SBC Case Builder and Pine64 SBC |
|
Posted by: hominoid - 07-21-2024, 06:10 PM - Forum: General
- Replies (1)
|
 |
SBC Case Builder is an autonomous case building tool written in OpenSCAD who’s case parameters can be adjusted through a Customizer GUI. With automatic SBC openings and a parametric capable accessory subsystem, standard and custom cases are possible across many different base case and adapter designs.
Several Pine64 SBC models have been added to SBC Model Framework(SBCMF) and the previous models which were not verified have undergone improvements to reach verified status. This allows SBC Case Builder to generate case designs for the: A64, A64-LTS, Rock64, RockPro64, Quartz-A, Quartz-B, Star64 and SoEdge-A.
Eight test cases used to verify SBCMF status are available in the saved cases pickbox above the Tabs at the top of the window: A64_shell, A64-LTS_shell, Rock64_shell, RockPro64_shell, Quartzb_shell, Quartza_shell and SoEdge_A_Baseboard_shell. Any of the test cases can be used as a starting point for a different case by changing the base design or by making any other customization which can then be saved as a new case.
The test cases use 2.5mm and 3mm inserts and screws as needed. Some cases are top fastened and some are bottom fastened, some countersunk or blind and some recessed, some are actively cooled and others are passive configurations. All the adjustments and options can be changed so take the time to review and change the necessary settings to match your personal preferences and available fasteners.
As opportunity allows, other Pine64 SBC will be added. The current SBCMF model for the Pine H64B still needs work and I don’t have access to one right now, so it isn’t ready for use and the status has not changed. Anyone interested can find SBC Case Builder and SBC Model Framework available at my git repository.
https://github.com/hominoids/SBC_Case_Builder
https://github.com/hominoids/SBC_Model_Framework
If you have an issue or question, or something isn’t working as expected, post a question here or open an issue at the git repository.
|
|
|
|
|