| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,700
» Latest member: runongw
» Forum threads: 16,260
» Forum posts: 117,188
Full Statistics
|
| Latest Threads |
Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: kapqa
Yesterday, 02:02 AM
» Replies: 8
» Views: 15,522
|
Reinstallation Arch Linux...
Forum: General Discussion on PineTab
Last Post: rth
11-22-2025, 08:25 PM
» Replies: 1
» Views: 205
|
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: brorean
11-21-2025, 08:45 PM
» Replies: 1
» Views: 130
|
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: brb78
11-20-2025, 04:15 PM
» Replies: 0
» Views: 109
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11-20-2025, 09:04 AM
» Replies: 5
» Views: 605
|
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 176
|
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 480
|
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,167
|
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 105
|
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 104
|
|
|
| Pinebook Pro - change default user |
|
Posted by: fonske - 01-23-2020, 06:43 AM - Forum: Linux on Pinebook Pro
- Replies (2)
|
 |
Hi all,
First thing we did was make another user than "rock" with the adduser command. Should've changed the password of "rock" immediately I guess.
The new user logged us in a gnome desktop with no functional trackpad.
When Chrome was launched (logged in as "rock") we saw "Fres-news.com" was already installed.
We followed the steps in the https://wiki.pine64.org/index.php/Pinebook_Pro under 2.1.1 to change from "rock" to another user.
Chrome was removed because going to settings to try to remove Fres-news always gave an error once you move the pointer in the settings tab.
1) Anyone else got infected by fres-news?
2) If anyone could tell me how to add users to Mate desktop, I'd be grateful.
|
|
|
|
| Free VS Code Workaround |
|
Posted by: pete - 01-23-2020, 06:10 AM - Forum: Pinebook Pro Tutorials
- Replies (2)
|
|
Hey guys, I figure this may be interesting to a few folks so wanted to share.
New to ARM and finding things can be a little trickier than I expected, so when I was setting up a dev environment I wanted to keep things simple and have my code compiled and running in an x64 machine.
So long story short I ran up an always free remote VPS and installed a virtual IDE there I can get at through the browser which will then be accessible across any of the images I boot on the PBP 
Quick steps are:
1) Get a free VPS - currently Oracle will give anyone two free linux boxes (plus DB plus other stuff) forever, so I like this option (cloud.oracle.com/free) although I'm sure other options are available.
2) SSH into the remote box and install docker | docker-compose
3) Setup an a record on your domain e.g. vs.*** points to server IP.
4) Here's the docker compose setup I use to run the container with SSL behind an NGINX reverse proxy.
Code: version: '2'
services:
proxy:
image: jwilder/nginx-proxy
container_name: proxy
restart: unless-stopped
labels:
com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
volumes:
- /var/run/docker.sock:/tmp/docker.sock:ro
- certs:/etc/nginx/certs:rw
- vhost.d:/etc/nginx/vhost.d
- html:/usr/share/nginx/html
- ./uploadsize.conf:/etc/nginx/conf.d/uploadsize.conf:ro
ports:
- "80:80"
- "443:443"
networks:
- "default"
- "proxy-tier"
proxy-letsencrypt:
image: jrcs/letsencrypt-nginx-proxy-companion
container_name: letsencrypt
restart: unless-stopped
environment:
- NGINX_PROXY_CONTAINER=proxy
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
volumes_from:
- "proxy"
depends_on:
- "proxy"
networks:
- "default"
- "proxy-tier"
portainer:
image: portainer/portainer
container_name: portainer
restart: always
environment:
- VIRTUAL_HOST=dock.YOURDOMAIN
- LETSENCRYPT_HOST=dock.YOURDOMAIN
- LETSENCRYPT_EMAIL=hi@YOURDOMAIN
volumes:
- ./portainer/:/data
- /var/run/docker.sock:/var/run/docker.sock
ports:
- "9000:9000"
code-server:
image: linuxserver/code-server
container_name: code-server
restart: unless-stopped
environment:
- PUID=1000
- PGID=1000
- TZ=Australia/Perth
- VIRTUAL_HOST=vs.YOURDOMAIN
- LETSENCRYPT_HOST=vs.YOURDOMAIN
- LETSENCRYPT_EMAIL=hi@YOURDOMAIN
- PASSWORD=YOURPASSWORD
- SUDO_PASSWORD=YOURSUDO
volumes:
- /codeserver/config:/config
ports:
- 8443:8443
volumes:
certs:
vhost.d:
html:
networks:
proxy-tier:
e' voila!
Ideally I was going to run the head melted vs code locally and then just ssh to the server as a remote host, but this currently isn't supported in the hed melted version as the feature is pre-release in VS code.... If anyone knows the workaround to that I'd be interested - as that feels like a cleaner approach!
|
|
|
|
| Serial cable voltage should actually be 3.0V, with mod! |
|
Posted by: jhiesey - 01-23-2020, 05:55 AM - Forum: Pinebook Pro Tutorials
- Replies (8)
|
|
I recently (early January) got my ANSI keyboard PBP, including the serial console cable I ordered. Based on other threads I knew the cable had an incorrect 5V signal level, but I wanted to investigate the situation a bit more myself.
So I looked at the schematics and RK3399 SoC datasheet, and realized that the UART signal voltage isn't 5V, but it isn't 3.3V either, as other threads have said... It's actually supposed to be 3.0V!
If you trace the signal from the headphone jack through the schematic, it leads you to the lower right corner of page 10:
![[Image: uart-page10-lower-right.png]](https://hiesey.com/web-public/pbp/uart-page10-lower-right.png)
This helpfully shows this group of pins on the SoC can be configured as 1.8V or 3.0V, but based on the connection of pin APIO4_VDD to 3.0V (see green circle) and a quick look at the datasheet, I concluded that in the PBP the correct voltage is 3.0V. These UART signals do go through U7002 to switch the jack between headphone and serial modes, but that does nothing to convert voltages.
I double-checked the voltage with a voltmeter on the PBP's TX line, which also indicated 3.0V.
My next question was whether the SoC could tolerate 3.3V on these pins, but I checked the datasheet and it indicates a maximum of 3.15V:
![[Image: rk3399-gpio.png]](https://hiesey.com/web-public/pbp/rk3399-gpio.png)
So not only is 5V too high, but so is 3.3V!
Unfortunately, 3.0V isn't a standard voltage for USB serial cables, and I didn't find any commercially available (but I didn't look too hard). And since I already had the 5V one from Pine64, I decided to mod it!
Here's the schematic of my mod. Original is in pencil; my changes are in blue:
![[Image: pbp-uart.png]](https://hiesey.com/web-public/pbp/pbp-uart.png)
There are conceptually two changes:
- Previously, the receive line had a 4.7K pullup resistor to 5V. I changed this to use a voltage divider that pulls up to 3V and has roughly the same impedance as the original, using an 8.2K resistor to 5V and a 12K resistor to ground. You could probably get away with leaving the 4.7K resistor in and just adding a 7K resistor to ground instead.
- I added a voltage divider on the transmit line to create 3V output signals using a 240 ohm series resistor and a 360 ohm resistor to ground.
The resistor values aren't super critical, but the ratios should be kept the same to ensure the right voltage.
The resulting cable shouldn't interfere with boot or WiFi, and it doesn't for me I verified that it works fine even at the crazy high 1.5Mbit/s speed used by the PBP, and the signals look pretty clean on a scope too.
Signal going from USB cable to PBP:
![[Image: SDS00020.png]](https://hiesey.com/web-public/pbp/SDS00020.png)
And from PBP to USB cable:
![[Image: SDS00021.png]](https://hiesey.com/web-public/pbp/SDS00021.png)
STEPS FOR THE MOD:
1. Pry the plastic of the USB connector end open with a screwdriver or spudger. It's friction fit but a bit tight. Twisting the cable strain relief may help get it open.
2. Remove the 4.7K surface mount pullup resistor, which was originally in the red circle:
![[Image: IMG_1081.jpeg]](https://hiesey.com/web-public/pbp/IMG_1081.jpeg)
3. Wire the four new resistors in like this, making sure to insulate wires that cross using heat shrink tubing (black in the picture):
![[Image: pbp-uart-wiring.png]](https://hiesey.com/web-public/pbp/pbp-uart-wiring.png)
![[Image: IMG_1084.jpeg]](https://hiesey.com/web-public/pbp/IMG_1084.jpeg)
I also cut out the red wire since it isn't needed and was getting in the way.
3. Insulate the resistor pairs with heat shrink tubing (blue in the picture) to ensure they don't short to each other or the metal crystal can to their left:
![[Image: IMG_1085.jpeg]](https://hiesey.com/web-public/pbp/IMG_1085.jpeg)
4. Squeeze the plastic case back together.
Good luck! Seriously though, Pine64 needs to ship the proper cable!!!
|
|
|
|
| Openjdk-11-jdk / Java on Arm64 |
|
Posted by: AJN - 01-23-2020, 04:53 AM - Forum: General Discussion on Pinebook Pro
- Replies (2)
|
|
Hello Pine64 Community,
since Oracle has no available option for Java 11 for Arm64 I was asking and looking for different ways and sources.
I found out that Azul Systems (https://www.azul.com/downloads/zulu-comm...ackage=jdk)
and also Bellsoft (https://bell-sw.com/pages/java-11/) both distribute a Java Version that is made for Arm64 Systems and thus should work for Pinebook Pro.
Nevertheless, since I am quite a novice I was not able to properly install them and make them work.
Is it even possible to install them on the Pinebook Pro and make Java 11 work for Arm64 (yet)?
When I tried to install from the terminal there was no executable option to install (e.g. like configure)
When I tried to install via package installer the option to install was greyed out.
It would be so great if one of you could answer my questions or even help me work around my problem.
Maybe someone could provide me with a "how to" or "step by step" support as Iam currently about to give up.
Thanks!
|
|
|
|
| NVMe adaptor fix timelines |
|
Posted by: phuzy - 01-22-2020, 10:04 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (1)
|
 |
In @Luke's stickied post, a fix for the NVME adapter was mentioned.
Two questions:
- As part of the 2nd community batch of PBP shipments, if you ordered an adapter with your PBP and received one, will you be automatically receiving the parts required for the NVME adapter fix?
- What are the timelines for the new parts to ship?
|
|
|
|
| Keyboard, Trackpad, and USB unresponsive on ANSI PBP |
|
Posted by: SpankyWorks - 01-22-2020, 10:04 PM - Forum: General Discussion on Pinebook Pro
- Replies (10)
|
|
Hello! I seem to have possibly messed up my ANSI layout PBP but I'm not sure what I might have done or what the problem is exactly.
I was booting from a microSD of the Manjaro ARM KDE 19.12 eMMC Installer image found here https://osdn.net/projects/manjaro-arm/st...sma/19.12/ and all seemed to be going well. I selected the eMMC device and it ran through the xz decrypt and flashed the eMMC steps fun but then it said press any key to continue and when I pressed a key nothing happened.
I have tried booting from other images on the microSD and this problem now seems systemwide. The keyboard and trackpad simply do not work anymore. Furthermore, a mouse and keyboard that I have confirmed are working on other devices simply get no power from the PBP anymore. I've also removed the battery and powered on from mains and the problem persists.
This is puzzling to me because the power button (which seems to be part of the nonworking keyboard) still works fine and the computer itself has no problem booting from either eMMC or from microSD.
I'd really like to be able to fix this, but I don't have the knowledge to diagnose the issue.
|
|
|
|
| down arrow having problems |
|
Posted by: bsammon - 01-22-2020, 08:21 PM - Forum: General Discussion on Pinebook Pro
- Replies (2)
|
|
Just got my PBP yesterday. Most of the stuff looks good. One big problem I am having is that the
down-arrow cursor key is not working so well. Like it's registering double-touches when I hit it once, or thinking I'm holding it down when I press it briefly. It's making it quite frustrating when I have to navigate text-mode menus (which I've found myself doing a few times).
Anybody else having this problem?
Is it already discussed in another thread that I can't find?
I'm running version 1.9 of the OS according to /usr/share/myver
I've done the keyboard/trackpad firmware upgrade, and I think it went fine, but I'm not sure how to double-check that (I suppose I could just try to run it again).
|
|
|
|
| Manjaro XFCE: Enable Natural Scrolling (Reverse scrolling direction) |
|
Posted by: kiddailey - 01-22-2020, 08:10 PM - Forum: Pinebook Pro Tutorials
- No Replies
|
|
Just thought I'd share for anyone else trying to figure this out. Enabling Natural Scrolling for Manjaro XFCE in the touchpad settings panel does not currently work. You can however, set it via the command-line according to the Arch Wiki. I'm not sure if this is the best/appropriate way to fix the issue, but it did work for me:
1. Using the package manager, install the xorg-xinput package, which contains the xinput utility
2. From the terminal, run the following command and note the ID number for the Touchpad:
3. Run the following command and note the number for the property labelled "Natural Scrolling Enabled (<propertyID>)" It should have a "0" next to it, indicating that it is disabled. Replace the <deviceID> with the ID for your Touchpad:
Code: xinput list-props <deviceID>
4. Set the scrolling property to "1" (enabled) by running the following command, replacing <deviceID> with your Touchpad's ID and <propertyID> with the ID number for the natural scrolling property:
Code: xinput set-prop <deviceID> <propertyID> 1
Note that this doesn't persist after a reboot, and the deviceID and propertyIDs appear to change. If you want to persist the changes, you will need to use the string names for the device and property in a .xprofile script in your home root. For example:
Code: #!/bin/bash
xinput set-prop "HAILUCK CO.,LTD USB KEYBOARD Touchpad" "libinput Natural Scrolling Enabled" 1
Enjoy!
|
|
|
|
|
