Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
Unboxed, charged, what no...
Forum: General Discussion on PineTime
Last Post: worik
11 hours ago
» Replies: 0
» Views: 9
|
MMS sending stopped worki...
Forum: General Discussion on PinePhone
Last Post: alaraajavamma
Yesterday, 02:25 PM
» Replies: 5
» Views: 2,233
|
mobian calamares fail
Forum: Mobian on PinePhone
Last Post: mdk
Yesterday, 02:10 PM
» Replies: 2
» Views: 327
|
Rock Pro 64 Won't power o...
Forum: General Discussion on ROCKPRO64
Last Post: matthewmkr
Yesterday, 12:57 PM
» Replies: 9
» Views: 574
|
used ppp ee on sale
Forum: General Discussion of PinePhone Pro
Last Post: Gravitate1765
Yesterday, 10:43 AM
» Replies: 1
» Views: 740
|
Quartz64 Zero HDMI
Forum: Quartz64 Hardware and Accessories
Last Post: grobbs
04-28-2025, 10:40 PM
» Replies: 2
» Views: 100
|
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: Kevin Kofler
04-28-2025, 04:00 PM
» Replies: 56
» Views: 15,180
|
FreeBSD developer build f...
Forum: PinePhone Pro Software
Last Post: teekay
04-27-2025, 01:29 AM
» Replies: 0
» Views: 85
|
debian mobian not bootabl...
Forum: General Discussion of PinePhone Pro
Last Post: henrythemouse
04-26-2025, 11:56 PM
» Replies: 3
» Views: 274
|
PinePhone keyboard not re...
Forum: Linux on Pinebook Pro
Last Post: Feemphynead
04-25-2025, 03:37 AM
» Replies: 0
» Views: 133
|
|
|
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
- No Replies
|
 |
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.
|
|
|
New PinePhone Pro fails... |
Posted by: P. Siera - 07-21-2024, 06:10 AM - Forum: General Discussion of PinePhone Pro
- Replies (5)
|
 |
I have a PinePhone for three years and it still functions well. The battery is now doing less well, but it is still doable with a simple power bank. In addition, there is no damage and the screen does not have a single scratch.
Now I have a PinePhone Pro for a week, but after a few days it stopped working on the phone and sound. The SIM card works properly, so it is something with the software or hardware. In addition, the battery drains quite quickly.
|
|
|
Rii mini 4 keyboard and touchpad work over Bluetooth |
Posted by: Peter Gamma - 07-19-2024, 08:02 AM - Forum: PinePhone Accessories
- No Replies
|
 |
Why to be smart if Bluetooth works?
I thought that the Rii mini 4 with 2.4 Ghz dongle would be the ultimate solution to solve the Pinephone keyboard problem. After a sleepless night in which I tested 6 cheap Aliexpress docks in all configuration with usb keyboard and mouse, none of the worked. Some time ago, one of them worked with usb keyboard and mouse, but I could not reproduce it. I thought a Rii mini 4 with 2.4 Ghz dongle would eventually the solution for the Pinephone keyboard problem together with the docking sation:
https://forum.pine64.org/showthread.php?tid=19350
But in the morning I decided not to buy any further Pinephone accessoires for a Pinephone I never use and put on the screed and take it down again for some tests.
In the afternoon, I thought, why not to try the Rii 4 over Bluetooth? Reports of Zebulon Walton about a Bluetooth mini keyboard where horrible:
https://forum.pine64.org/showthread.php?...316&page=2
Now i paired the Rii 4 mini over Bluetooth to my Pinephone with postmarketOS. There where no disconnection issues during 3 min tests as where reported with other Bluetooth keyboards:
https://forum.pine64.org/showthread.php?tid=13835
Keys, touchpad and scrollweel worked. One user reported to have issues with connecting a Bluetooth keyboard and mouse at the same time. Only one device worked, either keyboard and mouse. Other reported that Bluetooth keyboard and mouse work with Logitech devices:
https://forum.pine64.org/showthread.php?...316&page=3
But Logitech has not mini keyboards. The Rii mini 4 is a mini keyboard with dual mode BLE and 2.4 Ghz dongle. I did not get to work the 2.4 Ghz dongle, but the keyboard with touchpad.
The Rii 4 over Bluetooth is the best experience for a Pinephone keyboard for me personally to this date. It is available and worked for 3 min. reliably. And it has also a layout with many keys, similar to the Pinephone keyboard which makes it a great device. The keyboard is not much bigger than the Pinephone, and fit’s in a pocket.
|
|
|
Pinephone Pro: Determined To Make It (Drive-able) |
Posted by: USeeks - 07-18-2024, 11:58 AM - Forum: General Discussion of PinePhone Pro
- Replies (3)
|
 |
Would love to make this device primary.
Any feedback on the problems / proposed solutions greatly appreciated.
Drove original PinePhone on postmarketOS SXMO + WayDroid for a while. PPP is amazing here, but strangely, suspend doesn't seem to work.
The device will discharge (to 0% battery) if not charged over night, and last ~2 hours without a charger. Random poweroffs.
All connectivity is kill-switched. dmesg reports - "PM: Some devices failed to suspend, or early wake event detected".
Read somewhere that PPP should last for 24h minimally if suspended, yet it doesn't seem to work regardless of OS.
Wireless charging case sadly isn't sold any more (to pair with a smartphone charging case).
Before velcro-fastening the most compact 20000mAh powerbank on a back of PPP, trying software fixes might be in order.
postmarketOS doesn't seem to use Megi's now legendary kernel though, due to it not being mainlined, missing on PPP-critical patches.
Megi's https://xff.cz/kernels/ offers pre-built ones, but sadly kinda lost on how to make it work on postmarketOS (based on Alpine).
Arch seems to use Megi's kernel or patches, but it didn't survive the night either.
Mobian seemed ok, but couldn't get the SXMO working.
The device is also pretty hot. Like, literally.
Convergence + heavier use might need better heat dissipation to prevent thermal throttling (think I read it starts at 65°C/149°F on PPP).
Thinking about using 0.05mm copper pads with kapton tape on conductive shielding to prevent short-circuits & improve cooling.
USB-C doesn't work for data transfers, camera neither, but that isn't deal-breaker.
Anyway, very thankful for the effort that has been put into this by some very talented individuals; making a real pocket privacy-respecting (air-gappable) device possible.
|
|
|
How to get the Rii 4 with 2.4 Ghz get to work with the PP |
Posted by: Peter Gamma - 07-18-2024, 08:22 AM - Forum: PinePhone Accessories
- Replies (1)
|
 |
I ordered a Rii 4 with a 2.4 Ghz usb dongle and connected it to the Pinephone via usb to usb-c cable
This keyboard is one of the most interesting keyboards for the Pinephone for me personally if it works.
I suppose it is with lesser issues than Bluetooth
But it was not possible to pair the keyboard to the dongle as described above.
Then I tried to use a usb keyboard and mouse.
Here are examples which show that this works with the PP:
https://petergamma.org/how-to-get-a-usb-...pinephone/
All of these examples use a usb-c dock
And here is a list of 3.th party docks which work with the Pinephone and keyboard and mouse:
https://petergamma.org/issues-with-four-...epone-pro/
I tested previously 3 cheap usb docks I bought on Aliexpress.
HDMI out worked with none of them.
keyboard and mouse worked with one of those, but I could not reproduce it today
usb-c adapters are tricky Sometimes I need to turn those around to get it to work.
I recently saw that is possible to read and write to an usb flash drive with an Android phone:
https://petergamma.org/the-problem-googl...oid-phone/
But it needs to be an OTG drive, and the right configuration in Android.
Do you have experience with these kind of adapters?
Does it need to be an OTG adapter for keyboard and mouse?
And does it need to be powered?
|
|
|
|