| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,969
» Latest member: Bianca
» Forum threads: 16,334
» Forum posts: 117,438
Full Statistics
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 179
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,737
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 271
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 121
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 217,188
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 225
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 315
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,097
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 956
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 611
|
|
|
| PCI-e to Dual SATA-II Interface Card only works with one disk |
|
Posted by: taube - 11-25-2019, 07:44 PM - Forum: RockPro64 Hardware and Accessories
- Replies (4)
|
 |
Hi
after extensive testing of my newly arrived setup I pinned down the problem described earlier (https://forum.pine64.org/showthread.php?tid=8359 and https://github.com/ayufan-rock64/linux-build/issues/299) to the official PCI-e to Dual SATA-II Interface Card. As I'm pretty sure that the card is the culprit in this case, I'm re-posting the problem here.
My setup:
RockPro64 4GB
2x4TB Seagate IronWolf 3.5" HDD
PCI-e to Dual SATA-II Interface Card
NAS case with fan and Pine64 power supply (5A)
With two HDDs connected, the system does not boot or crashes frequently (power cycle required to reboot). Before the crash, I can hear the HDDs repeatedly "trying to spin up". I tried with different OS images, including ayufans openmediavault builds (version 0.9.14, armhf and arm64) and "vanilla" armbian buster server (kernel 4.4). Both HDDs are working (tested using an USB-to-SATA adapter) and both SATA cables are tested and OK. Powering the HDDs with a separate PSU didn't help, so the power supply is not the problem.
Connecting only one hard drive to either of the two SATA connectors works without problems. I also tried hot-plugging the second hard drive, which results in the following dmesg output (repetitive, for ata1 or ata2):
Code: [ 322.470646] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
[ 322.470669] ata2: irq_stat 0x00400040, connection status changed
[ 322.470687] ata2: SError: { PHYRdyChg CommWake DevExch }
Searching for this error, most people seem to suggest a broken cable. I remember reading somewhere on this forum that the signal quality of the PCIe card is not the best, which would explain why two cards could potentially "interfere" on the hardware-level. Did anyone experience similar issues and knows how to fix them?
Otherwise it seems that the pine64 was a total misbuy and I have to find another SATA card now...
|
|
|
|
| PineTime case |
|
Posted by: VMMainFrame - 11-25-2019, 02:21 PM - Forum: General Discussion on PineTime
- Replies (15)
|
|
I got my PineTime dev kit this morning. Very nice packaging. When I unpacked everything I found that the case back had come off the watch. I have been trying to get get the two parts of the watch together so I can charge it for over 30 minutes with no luck. It looks like the case back should just snap onto the watch but no matter how hard I press this does not happen. I have the back properly positioned, with the charging pins over the metal connectors on the circuit board. Is there a trick to getting the case back onto the watch?
|
|
|
|
| Charging via USB-C |
|
Posted by: Luke - 11-25-2019, 04:54 AM - Forum: General Discussion on Pinebook Pro
- Replies (11)
|
 |
It has become apparent to me that charging via USB-C only works properly (fast) when the PBP is on.
The suspicion is that this has to do with PD negotiation failing when the device is powered off. This results in slow standard USB charging.
The graph below shows the charging pattern with the device on (orange boxes) and off (between the two boxes).
I'll talk to the relevant people and ask about what can be done. In the meantime, if you want your PBP to charge at its optimal using USB-C, make sure that its turned on.
This doesn't affect charging via the barrel jack.
It may be a issue specific to the default Debian MATE or other OSs too - haven't checked. Please report below if you've got experience with other OSs.
![[Image: khCuoq0.png]](https://i.imgur.com/khCuoq0.png)
|
|
|
|
| order deadline for next production run |
|
Posted by: bsammon - 11-23-2019, 10:56 PM - Forum: General Discussion on Pinebook Pro
- Replies (6)
|
|
What is/was the order deadline for the next production run?
General timetable information would be appreciated as well. (with the understanding that everything is estimates/plans, not promises)
This is probably in a thread somewhere, but I looked for 5 minutes, and didn't find it.
Also, I'm lazy/wondering why it's not a pinned thread.
|
|
|
|
| Re-partitioning; Adding swap partition; Using GPT partitions |
|
Posted by: Arwen - 11-23-2019, 05:39 PM - Forum: Pinebook Pro Tutorials
- Replies (24)
|
 |
Here is a guide of how I repartitioned my eMMC to allow for a physical swap partition, and used GPT partition layout, (instead of DOS).
Basically you need an 8GB or larger SD card you can over-write.
Note that both Linux experience and command line familiarity is required. Any mistake and you could accidentally overwrite your working OS. Last, backups, (preferably multiple), is recommended.
This copies the low level boot information:
Code: # dd if=/dev/mmcblk1 bs=512 count=262144 of=/dev/mmcblk0
This section prepares the SD card. I had a 32GB one, so that is used in the sample below.
I don't give the details of how to use "fdisk", as the program has builtin help and can be quite verbose in use. But, you need to create a new partition label, (GPT in this example), as the one copied from above would almost certainly be wrong for the size of the media. Not to mention having a duplicate UUID number.
Do not change the start of either the "/boot" or the first partition, (swap or OS). Nor the size of the "/boot" partition. There is u-Boot code in there somewhere we don't want to overwrite.
Code: # fdisk /dev/mmcblk0
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/mmcblk0p1 32768 163839 131072 64M Microsoft basic data
/dev/mmcblk0p2 262144 4456447 4194304 2G Linux swap
/dev/mmcblk0p3 4456448 61497310 57040863 27.2G Linux filesystem
Create the file systems:
Code: # mkfs.fat -n sd_boot -v /dev/mmcblk0p1
# mkswap -L sd_swap /dev/mmcblk0p2
# mke2fs -b 4096 -j -L sd_root -m 1 -t ext4 -v /dev/mmcblk0p3
This copies the boot partition:
Code: # mount -t vfat /dev/mmcblk0p1 /mnt
# rsync -aAHSXx --stats /boot/ /mnt/
# vi /mnt/extlinux/extlinux.conf
{change references to root FS from /dev/mmcblk1 to /dev/mmcblk0}
# umount /mnt
This copies the OS partition:
Code: # mount -t ext4 /dev/mmcblk0p3 /mnt
# rsync -aAHSXx --stats / /mnt/
# vi /mnt/etc/fstab
Add /boot & swap lines:
/dev/mmcblk0p1 /boot vfat defaults 0 0
/dev/mmcblk0p2 swap swap pri=5 0 0
# umount /mnt
Then reboot. If you have the ability to boot SD cards, this will create a bootable SD card.
Whence booted to SD card, you can redo do the eMMC as desired. I choose to allow for additional root file systems, so I made my first OS partition only 27GBs. More than enough with the 32bit ARM default OS.
Code: root@Debian-Desktop:~# df -h / /boot;swapon
Filesystem Size Used Avail Use% Mounted on
/dev/root 27G 4.0G 23G 16% /
/dev/mmcblk1p1 64M 50M 15M 78% /boot
NAME TYPE SIZE USED PRIO
/dev/mmcblk1p2 partition 6G 0B 5
Code: root@Debian-Desktop:~# fdisk -l /dev/mmcblk1
Disk /dev/mmcblk1: 116.5 GiB, 125069950976 bytes, 244277248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3F39B914-D8D7-470B-BF6E-E7A2F2B33ABB
Device Start End Sectors Size Type
/dev/mmcblk1p1 32768 163839 131072 64M Microsoft basic data
/dev/mmcblk1p2 262144 12845055 12582912 6G Linux swap
/dev/mmcblk1p3 12845056 69885918 57040863 27.2G Linux filesystem
/dev/mmcblk1p4 69885952 126926814 57040863 27.2G Linux filesystem
|
|
|
|
|
![[Image: dIwgtMS.png]](https://i.imgur.com/dIwgtMS.png)
