| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: biketool
7 minutes ago
» Replies: 10
» Views: 6,761
|
what is the point?
Forum: General Discussion on PinePhone
Last Post: biketool
1 hour ago
» Replies: 4
» Views: 98
|
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: realchunkyflea
10 hours ago
» Replies: 3
» Views: 252
|
PinePhone sensors - Gyros...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11 hours ago
» Replies: 2
» Views: 58
|
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
Yesterday, 10:30 AM
» Replies: 10
» Views: 15,923
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
11-26-2025, 02:45 PM
» Replies: 10
» Views: 16,844
|
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: j_s
11-26-2025, 11:33 AM
» Replies: 4
» Views: 222
|
Quill OS for the PineNote
Forum: PineNote Software
Last Post: JhonSmith
11-26-2025, 01:42 AM
» Replies: 1
» Views: 136
|
auto-owning the SD card i...
Forum: PineTab Software
Last Post: biketool
11-25-2025, 04:16 AM
» Replies: 1
» Views: 406
|
Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: kapqa
11-23-2025, 02:02 AM
» Replies: 8
» Views: 15,569
|
|
|
| Got a case for my Pinebook Pro |
|
Posted by: GhostDragon - 09-24-2020, 05:36 PM - Forum: General Discussion on Pinebook Pro
- Replies (3)
|
 |
I just bought a case meant for an old model Macbook Air 13" (A1466 A1369), and it fits the PBP like a glove. I almost bought the 14" version of the case, but decided to go for the 13/13.5" version because the PBP is slim for a 14" laptop.
For reference, the PBP is 13" x 8.6" x 0.75", and the old Macbook Air 13" is 12.8" x 8.94" x 0.68"
Here is a picture of the PBP peeking out of the bag:
|
|
|
|
| New Pine Store is up! |
|
Posted by: Luke - 09-24-2020, 05:19 PM - Forum: News
- Replies (17)
|
 |
Hello Everyone,
The new Pine Store is now up. I'll explain the decision behind shutting the old store down for 72 hours and reopening with a new store in the upcoming October community update; at this point in time I just want to give you an intro to the new store. Before I do however, I want to give @fire219 and @gamelaster massive shout-out for helping getting the store operational in such as short time. Thanks guys!
Aside from the modern design and a vastly improved inventory categorization, the new Pine Store also offers a number of new features. Some of the more notable options include credit and debit card payments (via Stripe), as well as VAT and import Tax calculators for certain items. We will also be adding new features in the coming days - notably we wish to implement DHL's Remote Area Surcharge notification and calculator.
As many of you will immediately notice, the store has moved from store.pine64.org to pine64.com. The decision to move the Pine Store's domain to .com signifies the separation between the community .org domain(s) and the business aspects of PINE64. We think that it is the right move... pun intended. The store also runs on a much beefier VPS, on a newer overall architecture and it is much more secure. This, we hope, will assure great end-user experience even at the busiest of periods.
Many other improvements have been made to the system during the downtime too - for instance, order confirmation emails, shipping notifications, etc., will no longer end up in peoples spam folders.
Lastly, if you run into any issues with the new store, make sure to report them in this thread.
Once again, thank you for your patience!
|
|
|
|
| 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.
|
|
|
|
|