| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,943
» Latest member: WayOffside
» Forum threads: 16,329
» Forum posts: 117,429
Full Statistics
|
| Latest Threads |
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
Yesterday, 01:01 PM
» Replies: 17
» Views: 8,183
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
Yesterday, 02:37 AM
» Replies: 1
» Views: 1,910
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 705
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 479
|
How can I record video on...
Forum: General Discussion on PinePhone
Last Post: baptx
03-25-2026, 12:55 PM
» Replies: 23
» Views: 18,463
|
u-boot rk356х (rockchip r...
Forum: Quartz64 Tutorials
Last Post: hamsterbacke
03-25-2026, 09:39 AM
» Replies: 18
» Views: 34,043
|
A/V output enable
Forum: Linux on Rock64
Last Post: 8lall0
03-24-2026, 04:45 PM
» Replies: 0
» Views: 101
|
If your USB-C port is fla...
Forum: PinePhone Pro Hardware
Last Post: Zebulon Walton
03-24-2026, 02:25 PM
» Replies: 0
» Views: 122
|
Pinebook problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
03-18-2026, 08:58 AM
» Replies: 2
» Views: 4,696
|
Pine a64+ power supply
Forum: General Discussion on PINE A64(+)
Last Post: davidspencer
03-18-2026, 01:02 AM
» Replies: 0
» Views: 198
|
|
|
| Quick question about the SPDIF header |
|
Posted by: theophile - 09-24-2020, 04:07 PM - Forum: General Discussion on ROCK64
- Replies (2)
|
 |
Hi all! I'd like to use the SPDIF pin on the 22-pin GPIO header to be able to do AC3 and DTS passthrough to my AV receiver over coax. I'm not trying to do optical out, and not trying to use an external DAC. The Rock64 is running Linux (libreelec) and I have an audio output device for SPDIF. Is it as simple as taking an RCA jack and just connecting the tip to the SPDIF pin and ring to a ground pin? Or is a more sophisticated circuit required for some reason? Thanks in advance!
.boom-extension-active{cursor: crosshair !important} .boom-extension-active *:hover{cursor: crosshair !important} .boom-extension-hovered-element{outline: 2px solid rgba(130, 170, 210, .6) !important} .boom-extension-expanded-element{background: transparent !important;border: 0 !important;float: none !important;margin-left: auto !important;margin-right: auto !important;padding-left: 0 !important;padding-right: 0 !important;position: relative !important;max-width: initial !important;min-width: initial !important;width: 100% !important;}
|
|
|
|
| Battery Weight/Removing back cover frequently |
|
Posted by: janat08 - 09-24-2020, 05:01 AM - Forum: PineTab Hardware
- Replies (1)
|
 |
What is the battery Weight? Can you buy spare back covers as they're not designed to be frequently used, and how many will you need. Do you still sell spare parts only for repairs including the batteries. I'd like to be able to remove the battery if I intend to use the thing in bed and was wondering how much lighter it would get.
|
|
|
|
| Pinebook Pro doesn't boot most of the time unless connected via USB-serial! |
|
Posted by: nib0 - 09-24-2020, 04:02 AM - Forum: General Discussion on Pinebook Pro
- Replies (16)
|
 |
My Pinebook Pro has evolved into a lazy AI. It sometimes boots, but most of the time it can't be bothered.
It all started yesterday, when after a couple months of non-use, I decided to re-install a fresh manjaro. Since I was trying different versions of the distro, I cloned a couple of times to the eMMC and finally settled on a minimal version which I cloned to the eMMC using dd.
After that, the machine failed to boot, with only the power led turning on, but in orange. I tried rebooting a few times and finally opened up the case, flipped the switch and connected the serial to USB cable to check for any error messages.
The machine turned on!
I tried a couple of reboots, all worked ok, so I disconnected the serial cable.
The machine stopped turning on!
Since then, the machine mostly turns when connected via serial but not every time. It also sometimes starts without a problem without the cable connected, but most of the time it doesn't!
I managed to capture some boot logs.
Failed boot 1:
Code: U-Boot TPL 2020.07-2 (Aug 14 2020 - 07:33:56)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.07-2 (Aug 14 2020 - 07:33:56 +0000)
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
Trying to boot from MMC1
mmc_load_image_raw_sector: mmc block read error
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
Failed boot 2:
Code: U-Boot TPL 2020.07-2 (Aug 14 2020 - 07:33:56)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.07-2 (Aug 14 2020 - 07:33:56 +0000)
Trying to boot from MMC2
and finally a working boot:
Code: U-Boot TPL 2020.07-2 (Aug 14 2020 - 07:33:56)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.07-2 (Aug 14 2020 - 07:33:56 +0000)
Trying to boot from MMC2
U-Boot 2020.07-2 (Aug 14 2020 - 07:33:56 +0000) Manjaro ARM
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
In: serial
Out: serial
Err: serial
Model: Pine64 Pinebook Pro
Net: No ethernet found.
Hit any key to stop autoboot: 0
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3c0000: USB EHCI 1.00
Bus dwc3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus dwc3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 3 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Device 0: unknown device
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
236 bytes read in 16 ms (13.7 KiB/s)
1: Manjaro ARM
Retrieving file: /initramfs-linux.img
8462110 bytes read in 384 ms (21 MiB/s)
Retrieving file: /Image
33174016 bytes read in 1458 ms (21.7 MiB/s)
append: initrd=/initramfs-linux.img console=tty1 console=ttyS2,1500000 root=LABEL=ROOT_MNJRO rw rootwait bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash
Retrieving file: /dtbs/rockchip/rk3399-pinebook-pro.dtb
80685 bytes read in 30 ms (2.6 MiB/s)
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f46f3000, end f4f04f1e ... OK
Loading Device Tree to 00000000f46dc000, end 00000000f46f2b2c ... OK
Starting kernel ...
:: running early hook [udev]
Starting version 246.5-1-arch
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on '/dev/mmcblk2p2'
ROOT_MNJRO: clean, 60318/3809280 files, 760427/15205211 blocks
:: mounting '/dev/mmcblk2p2' on real root
:: running cleanup hook [udev]
Welcome to Manjaro ARM!
I reinstalled u-boot and followed the instructions to dd the 2 files, didn't make a difference.
I re-seated the eMMC module, it didn't make a difference.
The strangest thing is the fact that, when connected via serial, the machine boots most of the time! I'm afraid that this would that it could be hardware issue, maybe having to do with intermittent power failure. Everything seems ok and plugged in on the board however. The charging light also turns on.
Really sorry for the very long post, especially since it's my very first. Tried to include any relevant info.
Any help will be greatly appreciated.
|
|
|
|
| Software store crashes |
|
Posted by: LMalilil - 09-24-2020, 02:50 AM - Forum: Mobian on PinePhone
- Replies (3)
|
 |
I haven’t been able to use the software store in a couple weeks now. Crashes as soon as I go to updates or try to search categories for apps. I see people talking about this megapixels app that was apparently included in the nightly build a couple nights ago but it’s not on my phone. Does updating from CLI not update the OS as well? That’s the only way I have been able to get any updates
|
|
|
|
| No sound from Rock64 DAC |
|
Posted by: codebreaker - 09-23-2020, 09:27 PM - Forum: Rock64 Hardware and Accessories
- Replies (2)
|
 |
I bought the rock64 dac from ameridroid:
https://ameridroid.com/products/rock64-s...ifi-shield
I de-soldered the ethernet port so that it would fit in the pine64 aluminum case.
I flashed a fresh copy of armbian onto an emmc module and booted. I built and installed musikcube and tried every one of the alsa audio devices available, but I get no sound out of the dac. Any suggestions?
Code: cbrown@rock64:~$ aplay -L
default
Playback/recording through the PulseAudio sound server
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
sysdefault:CARD=rockchiprk3328
rockchip,rk3328, ff000000.i2s-i2s-hifi i2s-hifi-0
Default Audio Device
dmix:CARD=rockchiprk3328,DEV=0
rockchip,rk3328, ff000000.i2s-i2s-hifi i2s-hifi-0
Direct sample mixing device
dmix:CARD=rockchiprk3328,DEV=1
rockchip,rk3328, ff010000.i2s-rk3328-hifi ff410000.codec-1
Direct sample mixing device
dmix:CARD=rockchiprk3328,DEV=2
rockchip,rk3328, ff030000.spdif-dit-hifi dit-hifi-2
Direct sample mixing device
dsnoop:CARD=rockchiprk3328,DEV=0
rockchip,rk3328, ff000000.i2s-i2s-hifi i2s-hifi-0
Direct sample snooping device
dsnoop:CARD=rockchiprk3328,DEV=1
rockchip,rk3328, ff010000.i2s-rk3328-hifi ff410000.codec-1
Direct sample snooping device
dsnoop:CARD=rockchiprk3328,DEV=2
rockchip,rk3328, ff030000.spdif-dit-hifi dit-hifi-2
Direct sample snooping device
hw:CARD=rockchiprk3328,DEV=0
rockchip,rk3328, ff000000.i2s-i2s-hifi i2s-hifi-0
Direct hardware device without any conversions
hw:CARD=rockchiprk3328,DEV=1
rockchip,rk3328, ff010000.i2s-rk3328-hifi ff410000.codec-1
Direct hardware device without any conversions
hw:CARD=rockchiprk3328,DEV=2
rockchip,rk3328, ff030000.spdif-dit-hifi dit-hifi-2
Direct hardware device without any conversions
plughw:CARD=rockchiprk3328,DEV=0
rockchip,rk3328, ff000000.i2s-i2s-hifi i2s-hifi-0
Hardware device with all software conversions
plughw:CARD=rockchiprk3328,DEV=1
rockchip,rk3328, ff010000.i2s-rk3328-hifi ff410000.codec-1
Hardware device with all software conversions
plughw:CARD=rockchiprk3328,DEV=2
rockchip,rk3328, ff030000.spdif-dit-hifi dit-hifi-2
Hardware device with all software conversions
cbrown@rock64:~$
|
|
|
|
| Change Baudrate for Built-On Serial |
|
Posted by: R0b0t1 - 09-23-2020, 09:22 PM - Forum: General Discussion on ROCKPRO64
- Replies (1)
|
 |
The serial port on the RPi header has a baud of 1,500,000. This is fine for most tools, but some are capped at the values present in the baud tables in various places in the Linux kernel and other utilities.
How do I change the baud to 460800? I've found the uarts in rk3399.dtsi in the kernel tree, but am unsure how their clocks are actually generated.
As expected software seems unable to change the speed of the serial port.
|
|
|
|
Easy cross-compiling |
|
Posted by: elijahr - 09-23-2020, 09:16 PM - Forum: Linux on Pinebook Pro
- Replies (4)
|
 |
Hey all, I created some Docker images to make cross-compiling for Linux arm64 easy. I've successfully used my Macbook Pro to compile software for my Pinebook Pro, and it was quite a bit faster than compiling on the PBP itself. Thought others might find the project useful, but I'm also looking for testers.
The following instructions assume you have a PBP and a non-PBP running on the same LAN, and that the non-PBP has docker installed.
If compiling for Manjaro, run this on your non-PBP:
Code: docker run -p 3708:3708 elijahru/distcc-cross-compiler-host-archlinux:latest-amd64
If compiling for Debian, run this on your non-PBP:
Code: docker run -p 3608:3608 elijahru/distcc-cross-compiler-host-debian-buster:latest-amd64
On your PBP, install distcc via pacman or apt and update your PATH so that the distcc wrappers for gcc, g++, etc are found first.
Run this on your Manjaro PBP (assuming you use bash):
Code: sudo pacman -S distcc
echo 'export PATH=/usr/lib/distcc/bin:$PATH' >> ~/.bash_profile
# Replace X.Y.Z with the LAN IP address or hostname of your non-PBP
echo 'export DISTCC_HOSTS=X.Y.Z:3708' >> ~/.bash_profile
source ~/.bash_profile
Or run this on your Debian PBP:
Code: sudo apt-get install distcc
echo 'export PATH=/usr/lib/distcc:$PATH' >> ~/.bash_profile
# Replace X.Y.Z with the LAN IP address or hostname of your non-PBP
echo 'export DISTCC_HOSTS=X.Y.Z:3608' >> ~/.bash_profile
source ~/.bash_profile
Confirm that the executable found by running which gcc on your PBP is in /usr/lib/distcc:
Now any C / C++ compilation on the PBP will be transparently offloaded to the non-PBP. You can verify this by observing the distccd output on the non-PBP.
If the non-PBP can't be reached (for instance, if you are away from your LAN, or the docker isn't running), compilation will be performed locally.
Please let me know if you run into any issues.
Source code and documentation for the docker images: https://github.com/elijahr/distcc-cross-compiler
Cheers!
|
|
|
|
| Latest images from different distros failing to boot from SD card |
|
Posted by: jmonty42 - 09-23-2020, 09:07 PM - Forum: Linux on Pinebook
- Replies (2)
|
 |
I've got a 2017 14" Pinebook with a 64 GB eMMC installed. When I got it, I put the standard Xenial Mate image to boot from eMMC and then didn't touch it for a while. I recently pulled it out and updated to the latest version of Mate available just through `do-release-upgrade`. But that seemed to break some things like the battery life indicator, so I decided to try to find a new image to flash instead.
First, I want to say that I'm pretty disappointed with the state of the wiki for the OG Pinebook. Lots of broken links and not very updated information.
After poking around looking for images to use, I decided to try out Armbian and Manjaro. I have tried the following images all with the same behavior:
- Manjaro-ARM-i3-pinebook-20.04-emmc-installer-20.04.img.xz
- Manjaro-ARM-i3-pinebook-20.08.img.xz
- Manjaro-ARM-kde-plasma-pinebook-20.08.img.xz
- Armbian_20.08.1_Pinebook-a64_focal_current_5.8.5_desktop.img
- Armbian_20.08.1_Pinebook-a64_buster_current_5.8.5_desktop.img.xz
- Armbian_20.08.1_Pinebook-a64_bionic_current_5.8.5.img (pretty sure this was the headless server)
Anyway, on each of these I would see the bootloader start up. If I pressed space during this I'd be taken to the uboot cli. I could sit at that cli for however long I wanted. If I didn't interrupt the bootloader, I would see a splash screen for the distro pop up and after 15 or so seconds the screen would flicker and go black. Even on the headless image without the splash screen, it would go through the startup sequence and at about the same amount of time the screen would flicker and go black. The screen would occasionally light up like it was waking from sleep but then would go back to black. This would last indefinitely, I left it over night one time and it was still occasionally lighting back up just to go back to black periodically.
To make sure it wasn't a power issue I bought a new cable and a new power supply. To make sure it wasn't an SD card, I bought a couple new SD cards. As a last ditch effort I flashed the original Xenial Mate image from the wiki (xenial-mate-pinebook-bspkernel-0.7.28-136.img) and that booted up just fine. It also boots totally fine from eMMC into the original Xenial image I've update there and I can use it and leave it powered on without the screen going black and becoming unresponsive. I even tried booting from a recent Android image (android-7.1-pine-a64-pinebook-v0.3.5-r61.img - is that recent? I don't know) and that worked just fine.
I'm assuming there's something in the most recent kernel that is not compatible with the original Pinebook? Is this a known issue and is there anyone that knows what the latest version of the kernel I can use for one of these images is? I will start trying to find one on my own, but it would be great if someone already knew.
|
|
|
|
|